[Optional] Generating a Galasa Test with a chosen naming convention

The following section describes how to generate a Galasa Test with a chosen naming convention.

About this task

Once the recording is generated for the first time, you will see a new config file in the .taz/ft/config-files directory. The config file name will match the generated name of the newly generated galasa test file.

Example config file
functions:
- generatedName: testSSC1t0000587C
  name:
- generatedName: testSSP1t0000594C
  name:
generatedName: Ssp1ssc1dbrm
name:
type: test

This config file can be used to set the file name, the java class name, and names of each function.

The functions list is a mapping of the generated name and the expected name. If name is null, the generated name will not be replaced. If name is set, the next time the tests are generated the function name will be set to name instead of generatedName. Do not change the value of generatedName as this is the mapping key.

The generatedName at the root of the yaml file is the name of the java test file as well as the name of the galasa class. Do not change the value of generatedName as this is the mapping key. To rename the java class and the file, edit the value of name. If name is null, the generated name will not be replaced. If name is set, the next time the tests are generated the file/class name will be set to name instead of generatedName.

Procedure

  1. Edit the corresponding java test config file to set the functions names and/or the file/class name.
  2. Re-generate the file by right-clicking on the resulting playback file and click Generate Galasa Functional test.
  3. The newly generated file will have the new names based on the values set in the config file.