One of the customer asked if it is possible to create a bar chart of the estimated duration and the actual duration of a test case against the owner. This article addresses the requirement.
One of our customers recently asked about creating a report that brought the test set, test case, and test step in a specific format to help them with their test planning. This KB article explains how this can be done.
Customers running Spira v5.0 or v5.1 may experience an issue where the system will let you create test case folders that point to one of their children as parent. This causes an infinite loop which will break the system. This article provides a solution to fix the issue (though we recommend upgrading to v5.4 to prevent it happening in the future).
This article is obsolete.The infinite loop issue was fixed in later versions of Spira.
Sometimes customers will contact us regarding questions as to why the execution status indicator of their test sets is not being updated (i.e. everything still looks as not run) even after running some of the test cases. This article explains why this might be the case and provides solutions.
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.
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.
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.
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, as part of a risk based testing methodology, you will often want to see which of your test cases have the greatest overall, aggregate associated risk; if you are limited in time, these are the most critical tests to execute. This custom report generates such a view for you quickly and easily.
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.
When you upgrade from v5.4 to v6.0 upon opening a test case detail page you receive the error: "The 'TestCaseWorkflowId' property on 'TestCaseType' could not be set to a 'null' value". This article explains the cause and provides the solution
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.