- Search panel; see Using the Search Panel.
- Search results table; see Viewing Search Results.
- Source panel; Viewing Source Code.
- Actions panel; Resolving Test Failures.
The Test Explorer opens using the settings of the unit or functional test widget you clicked as search parameters, but you can easily change the search to learn about the state of coverage in your application.
- Click Change Search to open the Search Options overlay.
- Choose a filter from the Filter drop-down menu (see Creating and Managing Filters, to learn more about filters in Report Center).
- Choose a build ID from the Build drop-down menu (see DTP Concepts to learn more about build IDs in DTP).
Choose your search parameters. You can also click the File Name option and enter a file name in the search bar to find a specific file.
Info title Some states disable the limit on test cases returned
The Pass → Fail and Fail → Pass state parameters disable the limit on number of test cases returned in the search results area.
- Click Search.
The search results panel shows tests based on the parameters entered in the search overlay.
Refer to DTP Concepts for additional information about session tags, build IDs, and other metadata that enable DTP to organize and aggregate data.
The actions panel provides information about the tested file and its tests to help you understand defects in your software. The panel also provides an interface for assigning test metadata to help you resolve test failures. Click on a tab in the actions panel to view information or assign tests with metadata to place it into a remediation workflow.
You can also add some details shown in the tab to the search results table. See Navigating Explorer Views for additional information.
If DTP is integrated with your source control system, then you can view the tested source code in an explorer view. If integration with your source control system has not been configured, you can still view sources tested by Parasoft code analysis and test execution tools (C/C++test, dotTEST, Jtest) by setting the
report.dtp.publish.src setting to
min when configuring the tool. This instructs the tool to transfer client source code to DTP when generating the report. See the documentation for your tools for additional information.
When you make a selection in the tests table, the file name and the component that opened the file appears in the code panel.
Click on a test in the search results panel to view functional tests performed with SOAtest 9.x or later in the Test Explorer. SOAtest 9.9.2 or later is required to view test authorship and parameterized tests. Data Collector parses the XML report file generated by SOAtest and displays the .tst file data, so the .tst file does not need to be published to DTP or stored in source control.