Articles Tagged 'trace'

Articles
Creating a Requirements Traceability Report of Requirements Tests and Defects

A customer asked us if it was possible to create a version of the requirements traceability report that would display the following:

  • Requirement (name and ID)
  • Test Case (name and ID)
  • Test Run (ID and execution status)
  • Incident (ID)
Requirement - Test Step Traceability Report

Of the unique needs of a requirements and test management system when working in the Defense industry, specifically when designing, building, and testing mission systems, is the ability to link individual test steps to the requirements.  This article provides you with a custom report to use to display such a traceability matrix.

How to Get Rapise Trace Logging Information

When using Rapise, it is often useful to see how Rapise is identifying objects in the Application Under Test (AUT) and if necessary find out why Rapise is not able to locate a specific object. This article outlines how to increase the logging level in Rapise.

This article is obsolete. There is no ribbon in Rapise since version 6. If you have Rapise 6.0+ then follow these steps to change the verbose level.

Adding Document Version to Test Case Attachment Grid

We had a customer that was looking to add the current document version to the grid of attachments shown in the standard Test Case Detailed report. This article explains how you can easily add this field.

Displaying a Test Case - Risk Traceability Matrix Report

With SpiraPlan, you have the ability to create and manage risks, requirements and test cases in the same system. You can use the Associations feature to link the requirements to risks, and the test coverage feature to link requirements to test cases. However, it is often useful to be able to generate a traceability matrix between test cases and their associated risks. This custom report generates such a table for you quickly and easily.

Displaying a Requirements - Risk Traceability Matrix Report

With SpiraPlan, you have the ability to create and manage both risks and requirements in the same system. You can use the Associations feature to link the requirements to risks. However, it is often useful to be able to generate a traceability matrix between requirements and risks. This custom report generates such a table for you quickly and easily.

Creating a Program Requirements Traceability Report in Spira

Some customers have asked us how they can create a program-level requirements traceability report (RTM) in Spira using the custom reporting functionality. This article explains the process.

Querying Child Requirements in a Custom Report

In our standard requirements traceability report, we display a list of test cases associated with the current requirement. However for parent requirements (Epics) that have child requirements that map to test cases, they are don't display the child requirements' test cases. This article explains how you can modify the report to include them.