In version 6.2.1 of SpiraPlan, SpiraTeam and SpiraTest we have added a new reporting API that lets you access the reporting capabilities of Spira programatically.
By default, the reports displayed within Rapise report back each test activity and assert statement as a line in the report with all of the activities and events being displayed in a single flat list regardless of whether they happen inside the main Test() function or a sub-function. This articles explains how you can extend the reporting.
Sometimes when you try and run certain reports you may get an strange error message "The passed in report ID or report format ID does not exist". This message is unfortunately a red herring, and there is a different reason for this error.
A customer asked us if it was possible to create a version of the requirements traceability report that would not display each of the individual mapped test cases, but instead would give summary counts by priority.
We often get enquiries from customers looking to customize some of the reports in Spira. Although our support does not generally extend to writing such reports for customers (we have consultants and partners who would be happy to do it as a service), in this article we explain a common situation that we get asked about.
We had a potential customer that was looking to generate simplified test result reports from SpiraTeam that had more details for each of the executed test steps, with full size screenshots displayed, rather than the small table cells that are in the small reports. This article contains an example of such a report.
Customers sometimes ask us for a simple Release Notes report that can be used to display the list of new features and enhancements / fixed bugs in a specific release. We use a report like that ourselves to generate the Release Notes for our products (Rapise, SpiraTest, SpiraTeam, etc.). This article describes how you can create a similar report yourself
Our Spira platform (SpiraPlan, SpiraTest, SpiraTeam) has powerful custom reporting capabilities that let you build custom reports using the Microsoft Entity SQL language. This article provides some pointers on writing such reports.
When you display a graph in the SpiraTeam reporting page, you can download a graph as a CSV file. Some customers have asked about ways to get the data making a REST call. This article explains the components of the API.
As part of the v5.0 update to SpiraTest, SpiraPlan and SpiraTeam, we made major changes to the database structure to improve performance and usability as well as lay the foundation for v5.1, v5.2 and v5.3 due out later this year. Customers using custom reports
that relied on the old v4.2 database structure will need to modify their custom reports.
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)
The new release of SpiraTest, SpiraPlan and SpiraTeam 4.1 includes the ability to write custom reports against various reportable entities. This article provides a list of the available entities:
The Tester.EndTest() function in Rapise is describes as: Marks end of a currently executed test. Calculates test results and performs finalization of test execution. We have found that some of our customers have been confused as what the purpose of this function is.
The build in reports in SpiraTest / SpiraTeam are primarily geared to display the # passes, # fails, etc. from the perspective of test cases. It assumes that even a single fail / block / caution of any of the steps constitutes a failure of the entire test case. However some of our customers were looking for ways to display the execution information at the test step level. This articles describes how to create a simple custom report to display this.
This articles describes the steps to create a custom report that displays a table of test cases with the following fields:
- Test Case ID
- Test Case Name
- Last Execution Date
- Last Execution Status
- Number of Test Runs
Sometimes you want to get a report of all the tests executed along with their test cases 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 runs and test run steps sorted by test case order. This articles describes the process for creating such a report.
A customer asked us the following question: "I run an automated test suite consisting of the same 250 tests every night. I'd like to be able to run a report in the morning that shows me the tests that failed, but had passed the previous night. How can I accomplish this using the reporting mechanism ??"
The web-based custom reporting system in Spira v4.1 (or later) is designed to let you easily change the layout and contents of the various reports (and to create your own reports). It works in a format-agnostic manner, so that the same templates and layouts can be used regardless of whether the final report will be in PDF, HTML, Excel or MS-Word format. However sometimes there is a need to modify the specific template used to generate a specific format (e.g. MS-Word). This article describes the process.
Several users have asked -- if it is possible to extract all incidents logged in a SpiraTest sever no matter what the project is. Using the built-in Incident reports or Excel Add-In, you have to extract incidents for each project and then move into one spreadsheet however they wanted to know if it was possible to do this as one extract from within the tool.
The new release of SpiraTest, SpiraPlan and SpiraTeam 4.0 includes the ability to write custom reports against various reportable entities. This articles provides a list of the available entities: