Rapise 8.4 introduces an easy method to run multiple test sets and rerun failed test sets across multiple products. To leverage these features, integrate the TestRunner module into your framework. With TestRunner, you can also do AI-powered root cause analysis of failed test cases, analyze historical data of test case runs and generate reports in PDF format, and more.
A customer in a webinar recently questioned how to get a count of the test cases in a test set that is not marked as completed. This KB article answers this request.
The Cost of Quality (CoQ) is about both product quality and process quality. As part of these considerations, quality assurance can focus on additional patterns. In this article, we will discuss how to graphically show the summary information on these metrics.
Sometimes you want to get a report of all the test sets with their included test cases along with their test steps with the tests organized by the order in which they are displayed in SpiraTest. The custom reporting system in Spira allows you to create a custom report of all the test cases (by test set) and test steps sorted by test case order. This articles describes the process for creating such a report.(There are different versions of the ESQL query to use based on the version of Spira that you are using)
We had a customer looking for a consolidated report of the test sets and their test cases, grouped by release and test set folder. The report needed to have the individual test case instances in the test set along with the associated test runs.
A customer of ours asked for a custom report for displaying the list of failed Test Cases that do not have any incidents attached or created during testing.
One of our customers asked us how to extract the defects/incidents linked to the blocked test cases in a report. This article shows you how to do this using a simple custom report.
We had a customer that was looking for a more automated way to remove test cases from a test set. The good news is that our REST API makes this easy.
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.
A customer asked us if we could provide a report of all the test cases and test results across all projects and programs. In the future we plan on having built in screens for quality managers to be able to see the test results and test metrics across all projects without needing to run a report. However this report will give you the information in the meantime.
Sometimes you want a simple test execution report that includes the list of test cases, execution dates and raised defects, without all the ancillary information in the standard Spira reports. This article provides an example of such a report.
One of the limitations in SpiraTest and SpiraTeam v4.x was that for performance reasons we could not handle test sets with very large numbers of test cases and that the system was not able to display the counts of the test cases and the execution status for test set folders.