Storage

All necessary settings for the storage of the test data can be made in the Storage section. The settings include the naming of the data directory, the directory layout, optionally a reference directory for back-to-back tests, and report archive settings.

Storage section in the Execution Configuration dialog

General Settings

General Settings in Storage section

Directory

Specify the directory where the data concerning the test execution is gathered. For more information, see Test Execution Configuration - General settings.

Use (trash bin) to delete the content of the directory. The trash bin icon is dimmed when the directory is empty.

To delete only the test data from a single test case, right-click on it in the Project view and select Clear Test Data. Multiselection is supported. By default, the report folder is created in the test data folder and will thus be deleted too.

Report directory

The report is stored by default in a special report directory as subfolder of the test data folder. It is advised to select a location outside the test data folder. For more information, see Test Execution Configuration - General settings.

Use (trash bin) to delete the content of the report directory. The trash bin icon is dimmed when the directory is empty.

Directory layout

Specify the layout how the test data is stored in the directory. There are several options:

Hierarchical layout with indexes (based on test cases tree)

The data will be stored in a directory tree in accordance with the test case tree. An index counter is prepended to the directory names to ensure unique names and to retain the order of test cases for easier retrieval in the file system.

Hierarchical layout with unique IDs (based on test cases tree)

The data will be stored in a directory tree in accordance with the test case tree. The unique ID of each test case is appended to its directory name to ensure unique names that will not change even if the order of test cases changes.

Flat layout with indexes (no hierarchy)

The data will be stored in flat directories (no hierarchy). An index counter is added to the directory names to ensure unique names and to retain the order of test cases for easier retrieval in the file system.

Flat layout with unique IDs (no hierarchy)

The data will be stored in flat directories (no hierarchy). The unique ID of each test case is appended to its directory name to ensure unique names that will not change even if the order of test cases changes. You should use this option to avoid very long file paths that may cause problems in some execution environments.

Flat layout with unique IDs only (no hierarchy and no test case names)

The data will be stored in flat directories (no hierarchy). Only the unique ID of each test case is used for its directory name to ensure unique names that will not change even if the order of test cases or the test case names change. You should use this option to avoid very long file paths that may cause problems in some execution environments.

Flat layout with indexes and unique IDs (based on test case tree)

The data will be stored in flat directories (no hierarchy). The folder names end with Testcase_. The indexes of the parent test case folder and the index of the test case itself will be prepended.

Directory layout

Reference directory

The test results can be compared with reference data from earlier trials. One way to do this is to specify a path to the reference data. The data referred to can be used by a Signal Comparison assesslet, see Assesslet Types - Signal Comparison. Instead of using the Signal Comparison assesslet, you can set up the back-to-back test in the Execution section of the Execution Configuration dialog, see Back-to-Back Testing.

When the data directory is ${tpt.tptfile.dir}\TPTdata\, the reference directory could be ${tpt.tptfile.dir}\RefTPTdata\Stand_alone_test_engine in case the former execution was done using the stand alone test engine.

Reference root

Choose whether the reference directory is the Execution directory or the Platform directory.

Show warning before execution if test data directory already contains data

This is to prevent you from accidentally overwriting already existing test data, see Data storage.

Report Archive Settings

Report Archive Settings in Storage section

Compress report

Compresses the report as a ZIP file. Click the three dots button "..." to select a file path.

Delete report directory after compressing

Deletes the uncompressed report files automatically after the zip-file has been created.

Include

Report files

Includes the report files (HTML or PDF) and auxiliary files (CSS, PNG, etc) in the zip-archive.

Record files

Includes signal log files (.tptbin) from execution and assessment and auxiliary data files in the zip-archive.

The file report.tptbin will be excluded.

Summary files

Includes XML meta data for single test cases and summary XML files in the zip-archive.

The files testcase_exchange.params.xml and testcase_local.params.xml will be excluded.

Custom filters

It is possible to refine the filter settings. Select Custom filters to set an additional Include Filter or Exclude Filter.

The exclude filter has a higher priority than the include filter.

Include filter

Enter the file name (for example: testcase.tvm) or the file extension (for example: .tvm) you like to include in the report archive. Several entries are separated by a comma and whitespaces. Matching is case insensitive. Leave the include text field empty to include all files.

The wildcard character "?" represents a single character, the wildcard character "*" represents one or more characters.

Exclude filter

Enter the file name (for example: testcase.tvm) or file extensions (for example: .tvm) you like to exclude from the report archive. Several entries are separated by a comma and whitespaces. Matching is case insensitive. Leave the exclude text field empty to exclude nothing at all.

The wildcard character "?" represents a single character, the wildcard character "*" represents one or more characters.