Creating Freestyle Project

In a Freestyle project, you can configure the project by adding a build environment and build steps.
There are two build step options: CT test execution and CT custom command, and it is recommended to use only one of the two build steps to configure the project.
Please refer to Using Version Control Tools for Regression Testing for details of the project and source code settings.

Build Steps – CT test execution

Project Settings

Set the project you want CT Jenkins plugin to test.

• General Project
  • For general project, you must enter the path to project exported from CT.
  • When exporting a project, you must include the source code and toolchain.

• Team Project
  • For team project, you must enter the team project name that exists on the Team Testing Server.
  • Team project must be analyzed.

Source Code Settings

Source code settings are used when regression test with a specific branch in the Git repository.
The source code setting synchronizes the source code of the project selected above based on the top-level path to the source code in the Git repository.
You can check CT test results for source code that changes with this setting in a CI/CD environment.
If the option is not selected, the test is performed using the source code of the project selected above.

Test Settings

Set test execution options.

• Self-healing (Auto Recovery)
  • CT Jenkins plugin automatically performs an integrity check and selects reconfiguration candidates and execute tests.
  • Self-healing runs until all tests succeed or until the number of retries is reached.

Report Settings

Select the format in which you want to generate the resulting report.

Build Steps – CT custom command

This is a build step that allows the user to set workspace and CT CLI settings without using the CT test execution build step.
For detailed usage instructions and issues, please contact us through the technical support contact information at the bottom of manual’s troubleshooting page.