Page tree

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

This section covers change-based testing. Parasoft's change-based testing helps you optimize your testing efforts by automatically identifying the test cases directly related to your most recent source code modifications. You can then rerun only the impacted test cases rather than retest the entire system after each modification.

In this section:

Correlating Code via Test Case Execution

Project Center helps you monitor which source code is exercised when a test executes, then correlate that source code with the appropriate task, requirement, or defect. 

To do this, you need to:

  1. Enable reporting to Parasoft Project Center - see Connecting to Project Center.
  2. Mark which task, requirement, or defect each test is related to - see Indicating Code and Test Correlations.

Correlating Tests

If you are correlating code via test case execution (as described above) no additional configuration is necessary for this.

Otherwise, you need to:

  1. Enable reporting to Parasoft Project Center - see Connecting to Project Center.
  2. Mark which task, requirement, or defect each test is related to - see Indicating Code and Test Correlations.

In addition to enabling change-based testing and requirements-based testing, correlating tests with tasks, requirements, and defects allows Project Center to track the number of project PRs/FRs/tasks that have test cases, track PR/FR/task test case status details (passed, failed).

Determining Where Retesting is Needed

From Project Center

You can determine where retesting is needed in the following ways:

Change-Based Testing: Test Scenarios Report

The Change-Based Testing: Test Scenarios report indicates which manual test scenarios should be retested because there have been changes in the source code that was correlated to the previously-tested functionality. In other words, if a manual test scenario A was correlated to requirement B and the source code related to requirement B has changed, manual test scenario A will  be marked as a recommended test.

 

 

The Priority column sorts tests by priority. The more changes that are introduced to the specific functionality related to a test, the higher the priority is.

The Relations column shows project artifacts with which the scenario is linked.

The report date period specifies the period for which code changes are considered. You can adjust the date range by clicking the Last 7 | 15 | 30 days Last 12 | 26 | 52 weeks area—or by clicking the Switch to range mode icon then specifying the desired to/from date range.

Clicking the priority cell value will display code details. For example:

 

The details report presents all the source code revisions that:

  • Are associated with specific functionality and
  • Were committed to source control after the recent manual test run.

Change-Based Testing: Requirements/Defects Report

This report indicates which requirements or defects should be retested because there have been changes in the source code that was correlated to them. In other words, if code correlated to requirement A has changed, requirement A will be marked as needing retesting.

 

 

Clicking the priority cell value will display details about the entity that changed. For example:

 

The details report presents all the source code revisions that:

  • Are associated with specific requirement/defect and
  • Were committed to source control in the specified timeframe.

 

  • No labels