Test Prioritization Tool
The test prioritization tool, also known as the tselect tool, enables the profile-guided optimizations on all supported Intel® architectures, on Linux*, Windows*, and
operating systems, to select and prioritize tests for an application based on prior execution profiles.
The tool offers a potential of significant time saving in testing and developing large-scale applications where testing is the major bottleneck.
Development often requires changing applications modules. As applications change, developers can have a difficult time retaining the quality of their functional and performance tests so they are current and on-target. The test prioritization tool lets software developers select and prioritize application tests as application profiles change.
The information about the tool is separated into the following sections:
- Features and benefits
- Requirements and syntax
- Usage model
- Tool options
- Running the tool
Features and Benefits
The test prioritization tool provides an effective testing hierarchy based on the code coverage for an application. The following list summarizes the advantages of using the tool:
- Minimizing the number of tests that are required to achieve a given overall coverage for any subset of the application. The tool defines the smallest subset of the application tests that achieve exactly the same code coverage as the entire set of tests.
- Reducing the turn-around time of testing. Instead of spending a long time on finding a possibly large number of failures, the tool enables the users to quickly find a small number of tests that expose the defects associated with the regressions caused by a change set.
- Selecting and prioritizing the tests to achieve certain level of code coverage in a minimal time based on the data of the tests' execution time.
See Understanding Profile-guided Optimization and Profile an Application topics for general information on creating the files needed to run this tool.
Test Prioritization Tool
The test prioritization tool needs the following items to work:
- The .spi file generated by Intel® compilers when compiling the application for the instrumented binaries with the-prof-gen=srcpos(Linux* and) ormacOS*/Qprof-gen:srcpos(Windows*) option.
- The .dpi files generated by the profmerge tool as a result of merging the dynamic profile information .dyn files of each of the application tests. Run the profmerge tool on all .dyn files that are generated for each individual test and name the resulting .dpi in a fashion that uniquely identifies the test.
- User-generated file containing the list of tests to be prioritized. For successful instrumented code run, you should:
- Name each test .dpi file so the file names uniquely identify each test.
- Create a .dpi list file, which is a text file that contains the names o