Articles Tagged 'spirateam'

Sometimes you create user accounts in SpiraTeam for real users to login and test the system. For example you may have a UAT (user acceptance testing) phase, or a crowdsourced testing event (like our Software Testing Bowl). You then want to turn over the data to a third party supplier, but you need to anonymize the users' personal information

Organizations sometimes maintain a risk register and map risks from the risk register to individual projects. Each project may apply different risk rating scale, such as one project using FMEA and another using the standard Probability/Impact Assessment. This article addresses how this can be done.

This knowledge base article describes how to connect to the SpiraTest, SpiraPlan & SpiraTeam SOAP web services using .NET code written in C#. The code assumes that you're using Visual Studio 2008 or later and are using the newer .NET 3.0+ Windows Communication Foundation (WCF) "Add Service Reference" rather than the older .NET 2.0 ASMX web service client.

We have had some customers looking to upload files to Spira using our REST API. This article provides some sample code.

With the establishment of the EU General Data Protection Regulation (GDPR), you now may need to find old SpiraTeam projects that are not active any more so that you can delete them and reduce unnecessary storage of personal data.

Some of our customers who have SpiraTest, SpiraPlan, and SpiraTeam installations wanted to know how you can remove the "News Feed" RSS widget from all users' dashboards since it was causing Spira to access the www.inflectra.com domain.

SpiraTeam has been designed to work with a variety of different software development methodologies, including several different flavors of agile, waterfall and hybrid. This articles describes one of the more popular waterfall methods called the V-Model and gives best practices for how to use SpiraTeam on such projects.

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

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.

In some cases it is convenient to store tests in the same Git repository where source code of an application under test is located. For example, if you are using Visual Studio Team Services.  From this article you will learn how to execute Rapise tests stored in a Git repository with SpiraTeam and leverage the power of SpiraTeam reporting and analysis features.

This article is obsolete. There is much simpler approach with use of RapiseLauncher Extension for Azure DevOps.

We had a customer that was integrating Spira that was hosted on-premise with a cloud instance of KronoDesk. When they used the feature to log the incident in Spira from a KronoDesk ticket, the incident was created in Spira, but the information did not reflect back in KronoDesk, and an error message was displayed.

Customers often ask us about the process for upgrading from SpiraTest to SpiraTeam / SpiraPlan or from SpiraTeam to SpiraPlan. In this article we address some of the common questions for both cloud and on-premise customers.https://spiradoc.inflectra.com/Spira-Administration-Guide/System/#license-details

We have had some customers looking to upload files to Spira using our REST API. This article provides some sample code.

When you are installing SpiraTest, SpiraTeam, SpiraPlan or KronoDesk on a database server with a large 'model' database sometimes the install will fail because the initial Spira/KronoDesk database is not large enough to contain your model database. This article provides the solution

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.

Most of the artifacts in Spira are "soft deleted", i.e. they are simply marked with a deleted flag, and can be recovered easily by a project administrator using the Project History Changes option to review the changes, filter by deletes and revert the change. However when a system administrator deletes a whole project, it physically deletes the project and cannot be undone.

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.

In the standard reports that come with SpiraTeam, we have the 'Detailed' reports that are designed to include a primary artifact (e.g. requirements) and then include tables that display lists of related items (e.g. Tasks, Incidents, etc.). By default, we only show some of the fields in these tables. This article explains how to display the value of specific custom fields in the tables when you customize the standard reports.