Galasa Core Manager
- The Core Manager provides tests with access to some of the core features within the Galasa Framework. The Core Manager is always initialised and included in a test run and contributes the
Loggerannotation is provided by the Core Manager to create the log which is then automatically stored in the Result Archive Store (RAS) by the Galasa framework.
StoredArtifactRootannotation lets your test write specific output to the RAS. Whilst the Galasa framework automatically sends test output to be stored in the RAS, this annotation enables you to write code to send output specific to your application to be stored.
The Core Manager uses methods including
getCredentialslets you retrieve a user id and password from a file to use in your test and
ConfidentialTextensures that the password value is masked. The ability to get credentials from a file means that you do not need to hard code these values in your test and that the test can be run in different environments without the need to change a single line of code.
You can view the Javadoc documentation for this Manager here.
- Galasa Manager:
- Release State:
ClassDescriptionFill this field with the Core Manager instance.Used to annotate annotations that are to be used for Test Class fields.The Core Manager provides Tests with access to some of the most common features within the Galasa Framework To gain access to the Core Manager, include the following in the test class:-Fill this field with the Logger instance for this Test Class.Fill this field with a unique (within the ecosystem) string of a set length.Fill this field with the name of the Test Run.Fill this field Root path of the Stored Artifacts for this Test Run.Fill this field a test property from the Configuration Property Store