This Manager is at Release level. You can view the Javadoc documentation for the Manager here.

Overview
Configuring
Provided annotation
Code snippets and examples

Overview

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 Logger, StoredArtifactRoot, ResourceString, RunName and TestProperty annotations.

The Logger annotation 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.

The StoredArtifactRoot annotation 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. You can use this output for review or to enable compares to be done when tests fail.

The Core Manager uses methods including getCredentials, getUsernamePassword, getRunName and ConfidentialText credentials. getCredentials lets you retrieve a user id and password from a file to use in your test as well as other forms of credentials such as tokens, whilst getUsernamePassword lets you retrieve a user id and password only from a file to use in your test and ConfidentialText ensures 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. The Core Manager supports Gherkin keywords.

Including the Manager in a test

To use the Core Manager in a test you must import the @CoreManager annotation into the test, as shown in the following example:

@CoreManager
public ICoreManager coreManager;

You also need to add the Manager dependency into the pom.xml file if you are using Maven, or into the build.gradle file if you are using Gradle.

If you are using Maven, add the following dependencies into the pom.xml in the dependencies section:

<dependency>
<groupId>dev.galasa</groupId>
<artifactId>dev.galasa.core.manager</artifactId>
</dependency>

If you are using Gradle, add the following dependencies into build.gradle in the dependencies closure:

dependencies {
compileOnly 'dev.galasa:dev.galasa.core.manager'
}

Configuring

The following are properties used to configure the Core Manager:

Configuration Properties

Annotations provided by the Manager

The following annotations are provided by the Core Manager:

Code snippets and examples

import dev.galasa.ICredentials;
import dev.galasa.ICredentialsUsernamePassword;
...
@Test
...
ICredentialsUsernamePassword credentials = coreManger.getUsernamePassword("SIMBANK");
credentials.getPassword();
credentials.getUsername();

secure.credentials.SIMBANK.username=IBMUSER
secure.credentials.SIMBANK.password=SYS1

coreManager.registerConfidentialText("SYS1", "IBMUSER password");

Path requestPath = artifactRoot.resolve("communications").resolve("messages").;
Files.write(requestPath, content.getBytes(), new SetContentType(ResultArchiveStoreContentType.TEXT),
StandardOpenOption.CREATE);

communications
|
---messages 

@StoredArtifactRoot
    public Path rasRoot;
Path jobOutput = \
rasRoot.resolve("zosBatchJobs").resolve("checkOutputIsStoredInRAS");
Files.write(jobOutput, content.getBytes(), StandardOpenOption.CREATE);

@TestProperty(prefix = "projectA", suffix = "data", infixes = {"first","choice"})
public String property;

@ResourceString(tag="myString", length = 4)
public IResourceString myResourceString;

    @Test
    	logger.info(myResourceString.getString());