Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

Test parametrization is supported for JUnit 4 and 5. UTA generates parameterized tests using the testing framework and parameterization type configured using the jtest.uta.testing.framework setting.

Acceptable Values

trueCreating parameterized test cases is enabled.
falseDefault. Creating parameterized test cases is disabled.

jtest.uta.parameterized.junit.type

This setting allows you to specify the framework for creating parameterized test cases. It is required, if JUnit 4 is specified as jtest.uta.testing.framework.

Acceptable Values

JUnitParamsDefault. JUnitParams framework will be used to create parameterized test cases.
JUnit4ParametrizedJUnit4Parametrized framework will be used to create parameterized test cases.

jtest.uta.parameterized.parameter.set.count

This setting specifies the maximum number of parameter sets that will be created for one test case.

Acceptable Values

[number]The maximum number of parameter sets that will be created for one test case. The default is 5.

Example Usage

jtest.uta.parameterized.parameter.set.count=5

...

This setting enables or disables creating unit tests for private methods. 

Acceptable Values

trueCreating unit tests for private methods is enabled.
falseDefault. Creating unit tests for private methods is disabled.

jtest.uta.recommendations.additional.threads

This setting enables or disables displaying recommendations for additional threads which may impact the state of your test after test execution. 

Acceptable Values

trueDisplaying recommendations for additional threads is enabled.
falseDefault. Displaying recommendations for additional threads is disabled.

jtest.uta.recommendations.assertions.inaccessible

This setting enables or disables displaying recommendations for inaccessible fields that have been modified during execution and generating assertion templates after test execution. 

Acceptable Values

trueDefault. Displaying recommendations for inaccessible fields is enabled.
falseDisplaying recommendations for inaccessible fields is disabled.

jtest.uta.recommendations.files.created

This setting enables or disables displaying recommendations for files that were created during the test run, but were not removed after execution.

Acceptable Values

trueDisplaying recommendations for files that were created during the test run, but were not removed after execution, is enabled.
falseDefault. Displaying recommendations for files that were created during the test run, but were not removed after execution, is disabled.

jtest.uta.recommendations.mockable.invocations

This setting enables or disables displaying recommendations for calls to mock objects that can be modified to ensure proper test isolation. 

Acceptable Values

trueDefault. Displaying recommendations for calls to mock objects that can be modified to ensure proper test isolation is enabled.
falseDisplaying recommendations for calls to mock objects that can be modified to ensure proper test isolation is disabled.

jtest.uta.recommendations.no.assertions

This setting enables or disables displaying recommendations when no assertions have been made after test execution. 

Acceptable Values

trueDefault. Displaying recommendations when no assertions have been made is enabled.
falseDisplaying recommendations when no assertions have been made is disabled.

jtest.uta.recommendations.properties.changed

This setting enables or disables displaying recommendations for system properties that were modified during the test run, but not restored after execution. 

Acceptable Values

trueDisplaying recommendations for additional threads system properties that were modified during the test run, but not restored after execution is enabled.
falseDefault. Displaying recommendations for  system properties that were modified during the test run, but not restored after execution is disabled.

jtest.uta.recommendations.setup.problems

This setting enables or disables displaying recommendations for root causes of bulk test failures that share a common exception or issue, indicating potential setup problems within the project.  

Acceptable Values

trueDisplaying recommendations for potential setup problems is enabled.
falseDefault. Displaying recommendations for potential setup problems is disabled.

jtest.uta.recommendations.static.fields.changed

This setting enables or disables displaying recommendations when static fields have been modified during test execution. 

Acceptable Values

trueDisplaying recommendations when static fields have been modified during test execution is enabled.
falseDefault. Displaying recommendations when static fields have been modified during test execution is disabled.

jtest.uta.recommendations.static.invocations

This setting enables or disables displaying recommendations for calls to mockable static methods or constructors based on the specified mocking configuration. 

Acceptable Values

trueDisplaying recommendations for calls to mockable static methods or constructors is enabled.
falseDefault. Displaying recommendations for calls to mockable static methods or constructors is disabled.

jtest.uta.recommendations.uncovered.code

This setting enables or disables displaying recommendations for uncovered blocks of code after test execution. 

Acceptable Values

trueDisplaying recommendations for uncovered code is enabled.
falseDefault. Displaying recommendations for uncovered code is disabled.

jtest.uta.test.class.name.pattern

This setting allows you to specify the package and class name pattern for tests.

Acceptable Values

[pattern]

The package and class name pattern for tests.

The default pattern of "${package_name}.${class_name}${test_kind}Test" will put tests in the same package as the class being tested and add "${test_kind}Test" suffix to the class name. A custom pattern can also be specified using the following variables:

  • Spring - Separates Spring tests from other tests in JUnit 4 and 5.
  • Parameterized - Separates parameterized tests from regular tests in JUnit 4. In JUnit 5, regular and parameterized test cases are added to the same file.

For tests that are not Spring or parameterized tests, the ${test_kind} variable resolves to empty string.

jtest.uta.test.source.folder

This setting allows you to specify the root directory where tests created with UTA are saved.

Acceptable Values

[path]

The path to the directory where tests created with UTA are saved. By default, the project's settings are read to determine where tests should be saved. If the project does not specify where tests are located, then either update your project's configuration so a test source folder is specified, switch to one of the predefined patterns, or create a pattern manually using the following variables:
${project_name} - The name of the project (module for IntelliJ) that includes the tested class.
${source_folder} - The name of the folder that contains the source files of the project.

Example Usage

jtest.uta.test.source.folder=${project_name}/tests

...

This setting allows you to specifies test templates which will be used to control the structure of test classes in order to specify common configurations that are required for your particular tests.

Acceptable Values

[template name]Test templates to be used for your tests.

Example Usage

jtest.uta.test.templates=ParasoftCUSTOM

...

This setting specifies which template will be used for the quick add actions.

Acceptable Values

[template name]The template that will be used for the quick add actions (non-bulk creation).

Example Usage

jtest.uta.test.templates.active=ParasoftCUSTOM

...

This setting allows you to specify the testing framework UTA will use to create new tests.

Acceptable Values

JUnit 4Default. JUnit 4 testing framework will be used to create new tests.
JUnit 5JUnit 5 testing framework will be used to create new tests.

Anchor
jtest.uta.timeout.enabled
jtest.uta.timeout.enabled
jtest.uta.timeout.enabled

This setting enables or disables specifying a time limit for executing a test suite. The time limit can be set with the jtest.uta.timeout.time option. If the time limit is exceeded, the test execution will stop, the test suite will fail, and the information about the error will be displayed as a Recommendation in the UTA interface. 

Acceptable Values

trueDefault. Specifying a time limit for executing a test suite is enabled.
falseSpecifying a time limit for executing a test suite is disabled.

Anchor
jtest.uta.timeout.time
jtest.uta.timeout.time
jtest.uta.timeout.time

This setting allows you to specify the time limit (in milliseconds) for executing a test suite if the jtest.uta.timeout.enabled option is set to true. If the time limit is exceeded, the test execution will stop, the test suite will fail, and the information about the error will be displayed as a Recommendation in the UTA interface.

Acceptable Values

[seconds]

The time limit for executing a test suite. The default is 5000 milliseconds.

Example Usage

jtest.uta.timeout.time=5000

...

This setting enables or disables adding only test cases that increase coverage during bulk creation.

Acceptable Values

trueDefault. Only test cases that increase coverage will be added during bulk creation.
falseAll test cases are added during bulk creation, regardless of coverage increase.