SpiraTest by Inflectra is the premier Test Management and Quality Assurance solution for companies and Agile teams of all sizes, including those working in regulated industries. The platform includes requirements, release, and test case management, exploratory testing, source code management, and document collaboration all in a single platform. SpiraTest comes with a customizable reporting engine and insightful executive dashboards for testers, devs, and managers. Methodology agnostic, SpiraTest is available in both cloud-hosted (AWS) and on-premise/air-gapped editions.
With an open architecture and vast library of plugins for bug trackers, requirements management, and automated testing tools, SpiraTest will transform your testing process with immediate ROI.
Images
Check Software Images
Customer Reviews
SpiraTest Reviews
Mike B.
Advanced user of SpiraTestWhat do you like best?
1. Excellent Technical/Customer Support. Both knowledgeable and personable!
2. Easy to use UI.
3. Great integration with their companion Automated Testing product – Rapise.
4. Ability to add Custom fields and Lists in many parts of the application.
5. Excellent support for creating Requirements that can be converted automatically to Test Cases.
6. Great dashboards for monitoring nearly all stages of testing and reporting.
7. Ability to integrate with GitHub. Not just for Version Management, but GitHub is very efficient at transferring/storing large amounts of data in a very timely manner. It can also be used as an alternative to TFS when using DevOps.
8. Built-in support/integration with Microsoft DevOps. Although we're not ready to use this yet, it is a MUST HAVE for our automated regression testing. We intend to trigger the Spira tests to run by having DevOps push a change in build # into Spira. SpiraTeam can be configured to run ‘On Change in Build Number', so this process should be completely automated (once the regression testing scripts and SpiraTeam are set up.)
What do you dislike?
Separate (customizable) directory structures for Requirements, Test Cases, Test Sets, and Documents provide a ton of flexibility when creating these records. However, with that Flexibility, I've found it difficult to keep the directory areas somewhat similar so that when I'm looking at the directory for Requirements, I know where in the directory of Test Cases to find the related Test Case. Once the Test Case has been linked to the original requirement, Spira provides a link to easily navigate between Requirements and related Test Cases within either record, but I like the ability to make that move without having to open the Requirement or Test case record first. By carefully maintaining the Directory structures in different locations, I've been able to move past this.
2. Website Knowledge Base – I've had some difficulty searching and locating relevant items in Inflectra's Knowledge base. I love a new feature in Inflectra's companion product Rapise that displays context-sensitive functions, Knowledge Base Articles, and other documentation in a panel on the right side of the screen. Now it's very easy to locate Rapise KB articles and other documentation without ever leaving the Rapise development area.
What problems are you solving with the product? What benefits have you realized?
Currently, we're using Rapise/Spira for a mix of automated and manual testing. As the automated testing increases, the testing process is going faster and getting done with fewer Testing resources. While we haven't realized this benefit yet, using Spira with DevOps will fill one of the gaps in making our product a true SAAS product. That's the ultimate goal, and Spira is going to help us get there!
