TAZFT: Functional Testing messages

A message ID is a unique identifier used to track information or exceptions. A message ID for the Functional Testing is represented by a string “TAZFTnnnnx” where “TAZFT” indicates the message is an Functional Testing message, “nnnn” represents the unique numerical identifier for the message, and “x” represents the severity level of the given message. Severity level can either be represented by I, W, or E.

I
An informational message that calls attention to a command that can assist the programmer.
W
A warning for a situation that may not be what is expected.
E
An error has been detected with the test builder.

TAZFT1100I Initializing extension

Explanation

Extension is being initialized.

System action

Extension is being initialized and commands are generated.

User response

No user response is needed.

TAZFT1101I Extension has activated

Explanation

Extension has been activated.

System action

Extension is activated and user can start using extension to record transactions and generate tests.

User response

No user response is needed.

TAZFT1102I Extension has deactivated

Explanation

Extension has been deactivated.

System action

Extension is deactivated and user will not be able to use extension to record transactions or generate tests.

User response

No user response is needed.

TAZFT1104E Workspace not found, please open a project to start a workspace

Explanation

Extension is unable to find an open workspace.

System action

Extension will not work unless a workspace is opened.

User response

Open a workspace to continue.

TAZFT1200I Generating test cases for {0}

Explanation

Extension is generating test cases for a specified file.

System action

Extension is building test cases for a specified recording file.

User response

No user response is needed.

TAZFT1201E Error running test generator

Explanation

An error occurred while running the test generator.

System action

Test generator for the extension is not working properly, system cannot perform test generation.

User response

Check to make sure the extension is the latest version and that the extension has been activated.

TAZFT1202I Generating Galasa properties files

Explanation

Extension is about to generate the write the cps.properties file at the desired location.

System action

Extension is about to generate the write the cps.properties file at the desired location.

User response

No user response is needed.

TAZFT1203E Error creating Galasa cps.properties file {0}

Explanation

Extension failed to create the cps.properties.

System action

Extension failed to create the cps.properties.

User response

Check the error listed in the pop-up and the logs and try again.

TAZFT1304I Generating {0} directory

Explanation

Generating directory for extension files.

System action

Extension is initializing ft directory where extension files are stored across project.

User response

No user response is needed.

TAZFT1305I Configuration directory created

Explanation

Configuration directory has been created.

System action

Extension is creating configuration directory if one does not already exist.

User response

No user response is needed.

TAZFT1306I Did not generate since file already exists

Explanation

A new config is not generated as it exists in the project directory.

System action

Extension is not generating new config file since it already exists.

User response

No user response is needed.

TAZFT1307I File generated successfully

Explanation

Config file has been successfully generated.

System action

Extension has generated default config file in the project directory.

User response

No user response is needed.

TAZFT1321I Creating Recording Directory

Explanation

The extension is about to create the .taz/ft/recordings directory.

System action

The extension is about to create the .taz/ft/recordings directory

User response

No user response needed.

TAZFT1400I Preparing Galasa project

Explanation

Extension is preparing Galasa project.

System action

Extension is initializing local galasa environment, generating the galasa project and building the galasa project.

User response

No user response needed.

TAZFT1402I Galasa project prepared successfully.

Explanation

Galasa project has been prepared.

System action

Extension has successfully initialized galasa environment, generated the galasa project, and built the galasa project.

User response

No user response needed.

TAZFT1403I Galasa project is already prepared.

Explanation

Galasa project has already been prepared.

System action

Extension has found an already an existing galasa project with this name.

User response

No user response needed.

TAZFT1407I Generating galasa project..

Explanation

Galasa project is being generated.

System action

Extension is generating galasa project with necessary files.

User response

No user response needed.

TAZFT1408I Generated Galasa project to {0} directory.

Explanation

Galasa project has been generated to specified directory.

System action

Extension has successfully generated the galasa project to the specified directory.

User response

No user response needed.

TAZFT1409E Failed to generate galasa project: {0}.

Explanation

Galasa project could not be generated.

System action

Extension cannot generate galasa project due to an error with galasactl command.

User response

Check GALASA_HOME exists on local system and points to local galasa installation file.

TAZFT1410I Building galasa project using Maven.

Explanation

Extension is using Maven to create galasa project.

System action

Extension is using Maven build command to build galasa project.

User response

No user response needed.

TAZFT1411E Maven build of galasa project failed {0}.

Explanation

Maven build of galasa project failed, galasa project cannot be generated.

System action

Extension is using Maven to build galasa project but failed due to a Maven command error.

User response

Check to make sure Maven is installed successfully on local system and Maven commands can run without error.

TAZFT1412I Maven build was successful to build galasa project.

Explanation

Maven build was successful to build galasa project.

System action

Extension was able to perform a maven build to help build galasa project.

User response

No user response needed.

TAZFT1413E Failed to build galasa project: {0}.

Explanation

Extension failed to build galasa project.

System action

Extension attempted to perform a maven build to help build galasa project but failed due to an error.

User response

Check to make sure Maven is installed successfully on local system and Maven commands can run without error.

TAZFT1414E Project location was not selected or operation was canceled.

Explanation

A project location for the galasa project was not selected or project creation operation was canceled.

System action

Extension could not find project location or could not finish creating project because the operation was terminated.

User response

Try creating galasa project again and specify a valid project location.

TAZFT1415E Project name was not entered.

Explanation

A project name has not been entered while creating galasa project.

System action

Extension did not receive project name for galasa project from user and could not complete creating galasa project.

User response

Try creating galasa project again and enter a valid project name.

TAZFT1416W Please input a valid lower-case project name. Example: ftsampleproject

Explanation

The project name entered is invalid.

System action

The entered project name needs to be all lowercase letters.

User response

Input a valid project name to continue.

TAZFT1417I Galasa test file added or updated.

Explanation

Galasa test file has been added or updated with test cases.

System action

Extension has created or added test cases from recording to the galasa test file.

User response

No user response needed.

TAZFT1418E Error generating a Galasa test.

Explanation

An error occurred while generating a galasa test file.

System action

Extension could not generate galasa test file.

User response

Check to make sure the extension is the latest version and that the extension has been activated. Check to make sure config file is generated in project directory.

TAZFT1418W A project with this name already exists

Explanation

User entered a project name that already exists.

System action

The extension cannot create a project with a non-unique name.

User response

Enter a valid project name that does not already exist.

TAZFT1419E Prerequisites validation failed

Explanation

User system has incorrect versions of prerequisites installed.

System action

Extension checked the versions of the required prerequisites and found that incorrect versions were installed.

User response

Install or upgrade the prerequisites and try again.

TAZFT1600I Created Galasa home directory: {0}

Explanation

Extension created the galasa home directory.

System action

Extension created the galasa home directory.

User response

No user response is needed.

TAZFT1601I CPS properties at {0} was successfully moved to {1}

Explanation

It was found that the cps.properties file already existed at the desired location and so the extension needed to move the pre-existing file to a backup file and it was done so successfully.

System action

Extension moved the pre-existing file to a backup file successfully.

User response

No user response is needed.

TAZFT1602E Error renaming file {0} to {1}: {3}

Explanation

It was found that the cps.properties file already existed at the desired location and so the extension needed to move the pre-existing file to a backup file and it was done so unsuccessfully.

System action

Extension failed to move the pre-existing cps.properties file to a backup file.

User response

Remove or rename the pre-existing file and try again.

TAZFT1603I Created the Galasa cps.properties file in the {0} location

Explanation

Extension successfully generated the cps.properties file at the desired location.

System action

Extension successfully generated the cps.properties file at the desired location.

User response

No user response is needed.

TAZFT1604E Error creating cps.properties: {0}

Explanation

Extension failed to create the cps.properties.

System action

Extension failed to create the cps.properties.

User response

Check the error listed in the pop-up and the logs and try again.

TAZFT3100W A problem occurred while reading the template file!

Explanation

Unable to read the template file. This template file is a template for the pom.xml file that is read, manipulated, and written to the project directory.

System action

Extension attempted to read the template file.

User response

Check to make sure the extension is the latest version and that the extension has been activated.

TAZFT3101W Unable to extract Manifest!

Explanation

Unable to extract the Manifest file from the dev.galasa.db2.manager-{dfg_version}.jar in your Maven directory.

System action

Extension attempted to extract the Manifest file from the maven directory but failed.

User response

Verify that your Maven was installed correctly. Navigate to the ~/.m2/repository/dev/galasa/dev.galasa.db2.manager/{dfg_version} directory and verify that the jar file exists.

TAZFT3102W Problem applying db2 license to Manifest!

Explanation

Unable to edit the Manifest file by adding the Db2 license.

System action

Extension attempted to edit the Manifest file by adding the Db2 license but failed.

User response

Check to make sure the DFG is the latest version and is installed correctly.

TAZFT3103W Failed to copy db2 License jar to db2 Manager! db2jcc_license_cisuz.jar not found at: {0}

Explanation

Failed to locate db2jcc_license_cisuz.jar at the root of the project.

System action

Extension attempted to locate the db2jcc_license_cisuz.jar at the root of the project but failed.

User response

Verify that the db2jcc_license_cisuz.jar is at the root of the project.

TAZFT3104W Unable to apply license jar or manifest changes to db2 manager!

Explanation

Failed to edit the Db2 manager jar with the new Manifest file updates and the db2jcc_license_cisuz.jar file.

System action

Extension attempted to edit the Db2 manager but failed.

User response

Check to make sure the DFG is the latest version and is installed correctly and try again.

TAZFT3105W License cleanup failed!

Explanation

Failed to cleanup the license file that was temporarily moved to the maven directory.

System action

Extension attempted to cleanup the temporary license file but failed.

User response

No user response needed.

TAZFT3106W Manifest cleanup failed!

Explanation

Failed to cleanup the Manifest file that was temporarily moved to the maven directory.

System action

Extension attempted to cleanup the temporary Manifest file but failed.

User response

No user response needed.

TAZFT3107I Db2 driver license applied successfully to Db2 manager version {0}

Explanation

Successfully applied the Db2 license file to Db2 manager {0}.

System action

Extension successfully applies the Db2 license.

User response

No user response needed.

TAZFT3107W Failed to apply db2 driver license to galasa db2 manager. Db2 related tests may fail if license is required and not available!

Explanation

Db2 license was not applied successfully. Db2 related tests may fail if license is required and not available.

System action

Extension attempted to apply the Db2 license but failed.

User response

If you intended to have Db2 related tests in the generated test file, check to make sure the DFG is the latest version and is installed correctly and try again. Otherwise, no user response needed.

TAZFT3108W Unable to find galasa db2 manager in local maven repository or unable to find local maven repository at: {0}

Explanation

Unable to find the Db2 manager directory on the local system.

System action

Extension failed to find either the .m2 directory in the home directory or the db2 manager version directory in the local maven directory.

User response

Check to make sure the DFG is the latest version and is installed correctly.

TAZFT3109W Failed to check if db2 license exists.

Explanation

Unable to check the contents of the Db2 manager jar to verify the Db2 license was applied correctly.

System action

Extension attempted to check the contents of the Db2 manager jar to verify the Db2 license was applied correctly but failed.

User response

Check to make sure the DFG is the latest version and is installed correctly and try again.

TAZFT3110W Failed to find java path!

Explanation

Unable to verify java was installed correctly.

System action

Extension attempted to verify java was installed correctly but failed.

User response

Verify that java is installed correctly by running the java -version command.

TAZFT3111I Db2 driver license already applied to Db2 manager version {0}

Explanation

The Db2 driver license file is already applied to the current version of Db2 manager version.

System action

Extension discovered that the license was already applied and does not need to reapply.

User response

No user response needed.

TAZFT3200I Meta data written:

Explanation

Recording meta data has been written for test generation purposes.

System action

Transaction recording meta data has been written and can be successfully used to continue generating test for recording.

User response

No user response needed.

TAZFT3201E BMS file not found!

Explanation

BMS file cannot be found by extension.

System action

System attempted to find BMS file as specified in the config file within the project directory and BMS file with specified name could not be found in project.

User response

Check that BMS file is included in project directory if specified in the config file. Make sure BMS file name in project directory matches the name of the BMS file specified in the config file.

TAZFT3202E Recording file not found!

Explanation

Recording file could not be found.

System action

Extension attempted to find recording file and could not find the specified recording file.

User response

Check that the ft directory exist in project directory, check that the "recordings" directory exists in the project directory and make sure the recording file is located within the ft/recordings directory.

TAZFT3203W An issue occurred while processing recording file.

Explanation

Recording file could not be processed successfully.

System action

Extension attempted to process recording file but encountered an issue, generated test may not accurately represent recording.

User response

Create a new recording and try generating a test from the new recording.

TAZFT3204W An issue occurred while reading recording file.

Explanation

A problem occurred while attempting to read recording file.

System action

Extension attempted to read recording file but encountered an issue, generated test may not accurately represent recording.

User response

Create a new recording and try generating a test from the new recording.

TAZFT3205W An issue occurred while reading BMS map file.

Explanation

A problem occurred while attempting to read BMS map file.

System action

Extension attempted to read BMS file but encountered an issue, generated test may be missing BMS map information.

User response

Check that the BMS file is valid and has the necessary information.

TAZFT3206E Specified MFS file not found in file directory!

Explanation

MFS file cannot be found by extension.

System action

System attempted to find MFS file as specified in the config file within the project directory and MFS file with specified name could not be found in the project.

User response

Check that the MFS file is included in the project directory if it is specified in the config file. Make sure the MFS file name in the project directory matches the name of the MFS file specified in the config file.

TAZFT3207E IMS DBD file cannot be found in config-files directory

Explanation

User is attempting to use a DBD file that cannot be found in the config-files directory.

System action

User is attempting to use a DBD file that cannot be found in the config-files directory.

User response

Verify that the DBD file specified in the Zapp profile you are using exists in the local .taz/ft/config-files directory and that the name of the file is spelled correctly.

TAZFT3300I Creating Obr POM

Explanation

The extension is about to create the Obr POM file.

System action

The extension is about to create the Obr POM file.

User response

No user response needed.

TAZFT3301I POM file written to {0}

Explanation

POM file has been written to {0} directory.

System action

Extension has successfully created and written the POM file to the {0} directory.

User response

No user response needed.

TAZFT3302I Galasa variable config file does not exist.

Explanation

Galasa variable config file does not exist in project directory.

System action

Extension could not find galasa variable config file so one will be created.

User response

No user response needed.

TAZFT3303I Using pre-existing Galasa variable config file.

Explanation

A galasa variable config file already exists and will be used to store galasa variables.

System action

Extension identified a pre-existing Galasa variable config file and will update that file with information.

User response

No user response needed.

TAZFT3304I Test generated: {0}

Explanation

Test has been generated to test directory.

System action

Extension has successfully generated tests from the recording.

User response

No user response needed.

TAZFT3305W Galasa variable config file not found.

Explanation

Galasa variable config file does not exist in project directory.

System action

Extension could not find galasa variable config file.

User response

Check galasa variable config file can be found in config-files directory within project directory.

TAZFT3306W Cannot find POM file

Explanation

Extension could not find POM file.

System action

Extension could not locate POM file, may result in problem generating test.

User response

Check to make sure the extension is the latest version and that the extension has been activated.

TAZFT3307E Current Java Version is not IBM Semeru, please make sure to install and use IBM Semeru Java

Explanation

Extension discovered that the version of Java installed on the system is not an IBM Semeru version of Java.

System action

Extension found the wrong version of Java was installed. This will result in a problem running the Galasa tests.

User response

Uninstall the current Java version and follow the instructions to download the IMB Semeru version of Java