Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space DTPDEVEL and version 2024.2

...

Table of Contents
maxLevel12

Overview

The Test Explorer provides detailed information about unit and functional tests, such as test traces, history of runs, and coverage information. Click on a unit or functional test widget from the Report Center dashboard to access the Test Explorer (see Widgets). You can also access the test explorer from the Coverage Explorer (see Coverage Explorer#Viewing Test Information). The test explorer is divided into four panels:

  1. Search panel - see Using the Search Panel
  2. Search results table - see Viewing Search Results
  3. Source panel - see Viewing Source Code
  4. Actions panel - see Resolving Test Failures

Using the Search Panel

The most common workflow is to open the Test Explorer by clicking on a test-related widget in your DTP dashboard, which will populate based on the parameters configured in the widget. You can also modify the search parameters to home in on specific parameters. 

...

Info
titleSome 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.

Viewing Search Results

The search results panel shows tests based on the parameters entered in the search overlay.

...

  • Click on a row to view additional information in the actions panel; see Resolving Test Failures.
  • Click on a column header to sort results.
  • Click and drag a column header to the area labeled Drag a column header and drop it here to group by that column to create grouped views of the search results. By default, the table is grouped by test file name.

Anchor
Viewing Tests Executed in Different Environments
Viewing Tests Executed in Different Environments
Viewing Tests Executed in Different Environments

If your tests execute on different machines, you can add the Test Environment tab to the search results table so that you can view the results for each environment. See Navigating Explorer Views for additional information on filtering the results table.

...

Refer to DTP Concepts for additional information about session tags, build IDs, and other metadata that enable DTP to organize and aggregate data.

Anchor
Resolving Test Failures
Resolving Test Failures
Resolving Test Failures

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.

Prioritization Tab

Click on the Prioritization tab to access several actions to help you remediate unit and functional test failures.

...

Excerpt Include+
nopaneltrue
scrollPageIdC0A8C701018D6C1AC4BFE0390C637BB4

Anchor
CreatingIssueThirdParty
CreatingIssueThirdParty
Creating an Issue in Third-party Systems

You can connect a project in DTP to a project in one of the following requirements/issue tracking systems:

...

An issue will be created in your external system that links back to the test in DTP. Additionally, a link to the issue will appear in the Prioritization tab, create a bi-directional path between DTP and your external system.

Unlinking a Created Issue

Once an issue has been created, it will be linked to the violation. You can unlink the issue from the violation by clicking the "X" icon beside it.

...

Only the link will be removed; the issue in the third-party system will not be affected.

Modification History Tab

Click on the Modification History tab to show when test metadata was updated. 

...

If you want to filter for comments, you can enable the Only show comments option.

Test History Tab

Click on the Test History tab to show when tests were run and the status of each run. You can click on a column header to sort the contents of the table.

Traces Tab

When viewing unit test data, the Traces tab shows stack traces for failed and incomplete tests. If you are viewing functional or manual tests, the tab shows error messages for test failures.

Unit Test View

Click on an entry under an error message to show the test in the source code in the source panel; see Viewing Source Code.

Functional and Manual Test View

The failed test is highlighted in the source panel. The messages associated with the test failure appear in the Traces tab.

...

Click Show Traffic for the desired message to view the data requested during the test and the application’s response.

Viewing Test Coverage Information

The coverage panel shows a hierarchical view of the files associated with the tests. Each node in the hierarchy shows how much of each file or directory is covered in brackets. Coverage information is not currently available for functional tests.

...

  • Click on a disclosure triangle to navigate the tree. When an item is loaded that does not have any siblings, its children are automatically loaded and displayed. This behavior will cascade until the tree reaches a branch with multiple items at the same level (a decision point) or until the branch cannot be expanded any further. The coverage tree panel will not automatically expand nodes again if it has been previously expanded and collapsed unless the search criteria has changed, or the page has been reloaded.

  • Click on file nodes to view it in the source code panel. See Viewing Source Code for more information.

Details Tab

Click the Details tab to view information about the test.

You can click an associated artifact to view it in the external system integrated with DTP (note: this functionality is not currently supported for DOORS Next). You can also add some details shown in the tab to the search results table.  See See Navigating Explorer Views for additional information.

Anchor
Viewing Source Code
Viewing Source Code
Viewing Source

...

Code

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 full or 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 viewing functional or manual tests, the source code panel shows a hierarchical view of the test suite data collected. No additional permissions are required to view functional test data. See Viewing Functional and Manual Test Sources for information on viewing functional test data.

Viewing Unit Test Source Code

Click on a file link in the Traces or Coverage tab to load the contents of a source file into the sources panel. This enables you to view test and coverage information in the context of the code. Displayed sources are marked with color coded flags for at-a-glance coverage information after clicking links in the Coverage tab of the actions panel. Lines with green flags are covered. Lines with red flags are uncovered.

...

When you make a selection in the tests table, the file name and the component that opened the file appears in the code panel.

Anchor
Viewing Functional and Manual Test Sources
Viewing Functional and Manual Test Sources
Viewing Functional and Manual Test Sources

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.

...