Project Structure


The Project Explorer displays all your current projects. The sample screen shot shows a newly created Total Test project Accounting with test folder RegressionTest. The Test Folder includes only the Scenarios folder when creating a new project, unlike previous releases of Total Test. 

image2022-11-8_16-56-2.png

Important

Project structures created with prior versions remain compatible.

The additional content for the project will be created when recording test cases within the project or with project folder context menu selection Total Test > image2022-11-8_16-58-38.png Create Unit Test Folder.

image-2023-3-16_15-40-35.png

Project Folders

Table Project Folders describes the purpose of each folder.

Folder

Description

Project Name Folder

Top-level Project Folder for Total Test.

Contains all the Test Folders for a Total Test project. In the above sample it's named "Accounting". A project folder can contain multiple test folders

Total Test creates additional subfolders and files when creating and executing tests. For valid file extension names, see Renamed-Functional-Test-file-extensions.

Test Folder






















Total Test Folder

Contains the Test folder structures for the Total Test tests.
The Test folders can be multiple folder levels to group multiple tests under a common theme, for example:

  • MyTests
  • SimpleDB2
  • CICS
  • Program1
  • Program2

Each folder level can contain the Test folder structures for Total Test.

Interfaces

Test Interfaces

Contains the interface files which define the technical and functional aspects of a call interface.

JCL


JCL templates

Contains the templates used to create the job submitted to execute tests on the target platform. The JCL templates are only created if the Total Test preference Use the classic Test Run dialog is checked. See also Create JCL Template.

Output


Unit Test Output folders

Contains all Non-virtualized Test and/or Virtualized Test results output files that were created during a test execution as well as the History sub-folder holding all information of a test run. When opened, all generated Result Report formats as selected in the Preferences will be displayed.

Non-virtualized Test results are identified by the .result extension, for example CWKTCOBX.result. Virtualized Test results are identified by the .archive extension, for example, CWKTCOBX_Scenario.archive.

Projects created before Release 20.03.01 also included the now obsolete JUnit, Last Execution, Sonar and Reports subfolders. These subfolders are no longer created. Instead all files are placed directly in the Output folder, and the junit and sonar report files have .junit.xml and .sonar.xml as extensions.


History

Archived Tests

Contains test archives of earlier Virtualized Test executions, if the option Save time stamped files has been selected in the Total Test Project-Properties. When opened, a Result Report will be displayed.


JUnit
 (obsolete)

Jenkins Report

Contains the Result Reports in XML format that can be copied into Eclipse or any other tool that supports JUnit.


Last Execution
 (obsolete)


Test Results from Last Execution

Contains the plain results of the check conditions in a test run. Can be used to import results into any quality management tool.


Reports
 (obsolete)


Static Report

Contains the Result Reports as displayed when opening a test archive, but saved as static HTML file.


Sonar
 (obsolete)

SonarQube Report

Contains the Result Reports in XML format that can be imported into SonarQube or any other tool that supports Sonar files.

Properties

Properties Information

Contains properties information for the Total Test test structures. Also includes the Coded Debug launch configuration if test case was generated from an Coded Debug session.

Remapping

Remapping Structure Information

Contains saved remapping information.

Scenarios

Test Scenarios

Contains the Total Test Scenario files (Non-virtualized Test .scenario and Virtualized Test .testscenario) and execution context files (.context) holding all information necessary to perform tests: test cases with the interfaces used, input data, and check conditions.

Structures

Parameter Structures

Contains structures used as parameters in interfaces in a language-independent format.

Stubs

Test Stubs

Contains data and program stubs defining the simulated return data for calls to a given interface.

Suites

Test Suites

Contains test suites defining a collection of test scenarios to be executed with this suite.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*