Skip to content

Output

Jump to bottom
William Niemiec edited this page Sep 4, 2021 · 11 revisions

🖨 Output

Test path

By default there are two types of output: console or file. The console will be displayed in this order:

  • Test method signature
  • Signature of the tested method
  • Test paths of the tested method

In the file, the output will be:

  • Test method signature
  • Test paths of the tested method

Console

The output consists of displaying a header with the text EXPORT followed by the pattern mentioned above. An example can be seen below:

--------------------------------------------------------------------------------
				     EXPORT
--------------------------------------------------------------------------------
examples.others.SimpleTestPath.simpleTestPath()
examples.others.auxClasses.AuxClass.factorial(int)
[35, 36, 37, 36, 37, 36, 37, 36, 37, 36, 39]

[...]

--------------------------------------------------------------------------------
				     EXPORT
--------------------------------------------------------------------------------
examples.others.SimpleTestPath.simpleTestPath()
examples.others.auxClasses.AuxClass(int)
[12]

File

A directory will be created (by default it will be results) and in it will be created directories in the following format:

package_name/class_name.method_name(parameter_types)

As an example, suppose that the test path of the method with this signature will be generated:

controlFlow.TestClass_ControlFlow.ifElseMethod(int)

The test paths for this method will be placed in this directory:

testPaths/controlFlow/TestClass_ControlFlow.ifElseMethod(int)

Methods called by tested method / constructor

The generation will be in a CSV file containing the method / constructor tested followed by the methods invoked by it. The file will be saved, by default, in the same directory as the test paths - results - with the filename MCTMC.csv (Methods Called by Tested Method / Constructor).

Methods and constructors used in test method

The generation will be in a CSV file containing the tested method / constructor followed by the test methods that invoke it. The file will be saved, by default, in the same directory as the test paths - results - with the filename MCUTM-<TYPE>.csv (Methods and Constructors Used in Test Method), where <TYPE> can be:

  • ALL: Contains all methods and constructors that are used by test methods
  • EFFECTIVE: Contains all methods and constructors that are used by test methods and has their test path computed by the application.

Source file processed

The source code modified during processing will be exported in a file called SRC.txt. The test path will be computed from it, and it is in the same structure as the test paths.

Clone this wiki locally