Versions Compared

Old Version 1

changes.mady.by.user Hiromi Takahashi

Saved on

compared with

New Version Current

changes.mady.by.user Izabela Jarosz

Saved on

Key

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

...

This setting enables or disables using helper methods.

Acceptable Values

trueUsing helper methods is enabled. The generated tests classes will separate regular test methods from helper methods that prepare objects but do not make assertions. 
falseDefault. Using helper methods is disabled.

jtest.uta.mocking.static.enabled

This setting enables or disables static method and constructor mocking. Mockito inline 3.5+ required when this option is enabled. 

Acceptable Values

trueStatic method and constructor mocking is enabled. UTA will automatically create mocks for all required mockable static methods and/or constructors. UTA will automatically add static mocks to test cases during test creation, or display recommendations that will help you add mocks after your tests are run (see Creating Mocks). The mockStatic() method will be used to mock static methods of a class. For details about the mockStatic() method, see mockStatic. 
falseDefault. Static method and constructor mocking is disabled.

Anchor
jtest.uta.mocking.static.patterns.exclude
jtest.uta.mocking.static.patterns.exclude
jtest.uta.mocking.static.patterns.exclude

This setting allows you to exclude certain methods and/or constructors from static mocking.

Acceptable Values

[pattern]

Methods and/or constructors excluded from static mocking. Use qualified method names and wildcards (*) to match patterns. The patterns that end with .* or  <init> will be matched with constructors.

Example Usage

In the following example, the following configuration will be excluded from mocking:

...

This setting allows you to override the excluded pattern specified with the jtest.uta.mocking.static.patterns.exclude setting. UTA will mock specific excluded methods and/or constructors.

Acceptable Values

[pattern]

Specific excluded methods and/or constructors which will be mocked. Use qualified method names and wildcards (*) to match patterns. The patterns that end with .* or  <init> will be matched with constructors.

Example Usage

In the following example, the following configuration will be excluded from mocking:

...

This setting allows you to customize the default list of values for byte parameters.

Acceptable Values

[byte]

Default:

0, 1, -1 — common simple values.

Byte.MAX_VALUE — largest byte value (127).

Byte.MIN_VALUE — smallest byte value (-128).

jtest.uta.parameterization.values.char

This setting allows you to customize the default list of values for char parameters (single characters).

Acceptable Values

[char]

Default: '*','0','a','Z','(' — symbols, digits, uppercase, and lowercase letters.

jtest.uta.parameterization.values.double

This setting allows you to customize the default list of values for double parameters.

[double]

Default:

0.0d, 1d, -1d — basic values.

1.23456e300d, .3333d, 1e1d, 3.14159d —  large, fractional, and scientific notation values.

Double.MIN_VALUE — smallest positive nonzero value.

Double.MAX_VALUE — largest finite double.

Double.MIN_NORMAL — smallest positive normal value.

-Double.MAX_VALUE — largest negative finite double.

jtest.uta.parameterization.values.float

This setting allows you to customize the default list of values for float parameters.

[float]

Default:

0.0f, 1f, -1f — basic values.

-1.23e-23f, .3f, 3.14f — fractional and small scientific values.

Float.MIN_VALUE — smallest positive nonzero float.

Float.MAX_VALUE — largest finite float.

Float.MIN_NORMAL — smallest positive normal float.

-Float.MAX_VALUE — largest negative finite float.

jtest.uta.parameterization.values.int

This setting allows you to customize the default list of values for integer parameters.

[integer]

Default:

0, 1, -1 — simple common values.

Integer.MIN_VALUE — smallest integer (-2,147,483,648).

Integer.MAX_VALUE — largest integer (2,147,483,647).

jtest.uta.parameterization.values.long

This setting allows you to customize the default list of values for long parameters.

[long]

Default:

0L, -1L, 1L — simple values.

Long.MAX_VALUE — largest long (9,223,372,036,854,775,807).

Long.MIN_VALUE — smallest long (-9,223,372,036,854,775,808).

jtest.uta.parameterization.values.short

This setting allows you to customize the default list of values for short parameters.

[short]

Default:

0, -1, 1 — simple values.

Short.MAX_VALUE — largest short (32,767).

Short.MIN_VALUE — smallest short (-32,768).

jtest.uta.parameterization.values.string

This setting allows you to customize the default list of values for string parameters.

[string]

Default:

<NULL> — a null string.

"" — empty string.

" " — string with a single space.

"hello world" — simple text.

"01234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890" — Long numeric string

jtest.uta.parametrized.enabled

...

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 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

...