SpiraTest Reviews and Ratings

Rating: 8 out of 10

Score

8 out of 10

Community insights

TrustRadius Insights for SpiraTest are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Business Problems Solved

SpiraTest has proven to be valuable for a range of use cases across various industries. One notable example is its application in the entertainment/hospitality industry, where it has been successfully used for a large and complex project. By making work on requirements agile and enabling scalability for the QA team, SpiraTest has significantly contributed to the success of this project.

JetRuby's quality analysts, project managers, and product owners have also found great value in using SpiraTest for their specific needs. Whether it's solving various problems or streamlining the development process, SpiraTest has proven to be a convenient tool for these roles. Its user-friendly interface has made it easy for the entire organization to adopt, allowing for seamless collaboration between teams.

In addition, SpiraTest's capabilities within the quality assurance department have been highly beneficial. It allows users to run tests on websites and ensure that all features are functioning properly. The ability to assign test cases to specific users has been particularly valuable in testing with actual end users and managing their expectations effectively.

Furthermore, organizations have found that SpiraTest's competitive pricing enables them to allocate enough licenses to accommodate their user base. This allows teams to fully utilize its features without any limitations.

SpiraTest is often used alongside Excel sheets, offering a more efficient way of sorting requirements, tests, and progress. This integration significantly improves productivity by simplifying workflow management.

One feature that stands out among users is SpiraTest's cloning capability, which allows for linking similar test cases. This feature has received high praise as it saves time and effort by eliminating the need to create repetitive test cases from scratch.

Overall, SpiraTest has successfully addressed various user needs and provided solutions across different industries. Its simplicity, flexibility, and powerful features make it a valuable tool for improving project management, collaboration, and overall efficiency.

Reviews

8 Reviews

SpiraTest - very good/solid product

Rating: 8 out of 10

Incentivized

May 22, 2022

Use Cases and Deployment Scope

We use SpiraPlan (which includes the SpiraTest function) to manage requirements, test cases, incidents, and releases for our medical device products. We use it for all current products, both hardware, and software. We migrated to the SpiraPlan platform from Jazz and at this point, it allows us to accomplish all that Jazz allowed us to do.

Pros

Easily link and associate artifacts
Webforms/web UI is intuitive
Lots of flexibility with filtering and sorting
Search function (across all products) is very useful

Cons

Custom report generation needs to be easier. It has a steep learning curve.
It should be easier to copy and paste items in artifacts - particularly collections of test steps.
It is difficult (impossible?) to share artifacts among different SpiraPlan 'products'
SpiraPlan does not have a workflow structure that allows for multiple approvers of artifacts. This feature should be added.

Likelihood to Recommend

Two big uses for us are 1) managing requirements and verifying requirements with test cases; and 2) Software source control via TaraVault and Git. For item 1 (requirements/test case management)... I cannot imagine any scenario where it would not be suitable for this need. I do wish custom report generation was easier though. SpiraPlan has a great artifact linking ability - generating custom reports showing this linking is much harder than (I think) it should be. For item 2 (software source control)... We do not have many software products

Verified User

Engineer in Engineering (11-50 employees)

Vetted Review

2 years of experience

SpiraTest - Can be better!

Rating: 8 out of 10

Incentivized

December 18, 2018

Use Cases and Deployment Scope

We use SpiraTest across the test teams for all the testing needs. SpiraTest makes it very easy to sort requirements, tests, and progress. We use SpiraTest along with Excel sheets but SpiraTest makes work so much easier. The best thing about SpiraTest is cloning, which can be used to link similar test cases.

Pros

It is easy to manage requirements.
Users and roles are easily managed.
Cloning is really helpful to stack all the similar test cases.

Cons

Dashboard can be made a little easier to read.
Reporting is also not that great.
Includes a little learning curve.

Likelihood to Recommend

SpiraTest is helpful for the test teams to manage the test cases. It can integrated to JIRA and the integration works great. The dashboard and metrics are little out of the place and there is a lot of improvement to be made in that area. Cloning can be a boon to many QA teams.

Verified User

Employee in Corporate (5001-10,000 employees)

Vetted Review

2 years of experience

SpiraTest

Rating: 9 out of 10

Incentivized

August 7, 2018

Use Cases and Deployment Scope

SpiraTest has a simple easy and intuitive user interface. I like how the testing requirements are organized much like a project plan work breakdown structure; this makes it very simple for the rest of the organization to use the tool. Being able to assign out test cases to specific users is very valuable and allows us to test with actual end users rather than have IT test everything; this gives us a great tool to solicit feedback on what is about to be rolled out and helps manage the expectations with the end user base. With the pricing being so competitive we can allocate enough licenses to any user we would like. While there are other test tracking tools out there they took numerous hours to build them into a model that would function like SpiraTest.

Pros

Easily manages testing requirements.
Easily manage users and roles.
Great out of the box reporting for test cases and bugs.

Cons

Training can be difficult to find at times.
Basic reporting can become very verbose unless you set lots of filters and parameters.
The ability to customize some of the verbiage in the application would help bridge the gap between translating what SpiraTest's testing terminology is and the company culture uses for testing terminology.

Likelihood to Recommend

Very useful for testing any new product or software even in an Agile Project management methodology.

Verified User

Project Manager in Information Technology (5001-10,000 employees)

Vetted Review

3 years of experience

SpiraTest

Rating: 6 out of 10

Incentivized

June 22, 2016

Use Cases and Deployment Scope

Spiratest is being used in our team as a one stop tool for the complete testing life cycle. It is only being used by QA department as a trial. All the requirements, enhancements, test cases, bugs are organized in one single tool and are easily accessible.

Pros

SpiraTest works well in organizing the requirements. The best part is the requirements can be categorized as use case/user story based on the project.

Cons

Defect tracking module of the application can be improved. There are several options for the user while creating a defect and this might be confusing
User Dashboard page can be improved. Pulling metrics for a project is too complicated.

Likelihood to Recommend

Pulling project metrics is too confusing.

Verified User

Analyst in Information Technology (501-1000 employees)

Vetted Review

1 year of experience

SpiraTest Review

Rating: 8 out of 10

Incentivized

June 10, 2016

Use Cases and Deployment Scope

SpiraTest is being used by a department. It mainly addresses the need of the QA department to have labs and an ability to map requirements to tests to tickets. Most people in the company use JIRA which SpiraTest integrates with.

Pros

Intergration
Undo deletes
Reporting
Filtering

Cons

Speed
Integration with automated tools

Likelihood to Recommend

With the growing popularity of Agile, SpiraTest can improve in this area.

Verified User

Manager in Information Technology (51-200 employees)

Vetted Review

3 years of experience

SpiraTest is the best solution for test management

Rating: 8 out of 10

Incentivized

March 8, 2016

Use Cases and Deployment Scope

We chose SpiraTest over a year ago after studying different test management software. Today it is used by JetRuby's quality analysts, project managers as well as product owners. This tool helped us to solve various problems, making work on requirements agile, the QA team scalable and storage of test documentation and metrics during the product development more convenient.

Pros

Working on requirements as a team.
Distribution of testing sets among QA team members.

Cons

One lacks convenient ways of reports customization.
The SpiraTest to JIRA integration leaves much to be desired. We use a cloud version of SpiraTest and Linux machine hosted JIRA version. To configure the integration we need a server on Windows.

Likelihood to Recommend

Pavel Skvortsov

QA Engineer in Quality Assurance at JetRuby Agency (11-50 employees)

Vetted Review

2 years of experience

View profile

Intern's Review of SpiraTest

Rating: 7 out of 10

Incentivized

February 16, 2016

Use Cases and Deployment Scope

Spiratest was being used within the quality assurance department - we were using it to run tests on our websites to ensure that all implemented features worked at any given time. It was just being implemented when I began my work at my company as an intern. The other intern and I were trained in using it. I was impressed with the good job it did of helping someone walk through test cases - and how test cases could be copied and reapplied for different, future tests as features were added.

Pros

Creating test cases that can easily be reused.
Helping individuals organize test cases.
Helping teams communicate about test cases when performing QA duties.
If I remember correctly, there were integrations that could also be performed with SpiraTest - these were helpful!

Cons

Slight learning curve when starting out.
Minor difficulty integrating into existing software suite.
A bit complex.

Likelihood to Recommend

I think SpiraTest is well suited as a test suite, but in situations where the team is already using multiple products from one particular provider, it may be better to go with that provider's test solution. This is because integrations are very important nowadays, and should be considered when picking your project management software.

It should be noted that management selected SpiraTest primarily due to the low cost of the test software. I'm less familiar with other test software in the field, but if cost is an issue, you should take a look at SpiraTest.

Verified User

Former Employee in Quality Assurance (51-200 employees)

Vetted Review

SpiraTest - fail

Rating: 7 out of 10

Incentivized

January 15, 2016

Use Cases and Deployment Scope

SpiraTest is being used currently for a large, complex project with an ambitious time frame in the entertainment/hospitality industry.

Pros

A clean view of test case steps, expected results and the ability to record a result for each step quickly on one page per test set. This really helps testers work through executing manual test cases.
Hierarchical structure of releases and builds, requirements, and test cases.
Can quickly build test sets and/or test runs per build/release.
Simple identification of each test case, requirement, test run, build, release, etc.

Cons

While there are some nice, live reports, test results per build/release is an obvious omission. The canned reports that can be configured are mostly text based. Some graphs included in those would be a nice addition.
Recording a Fail for a test step does not facilitate recording a defect. Defects must be manually reported separately. It would be nice if some standard fields were offered when a failure was recorded (e.g. summary, actual result, expected result, description) were recorded with system-known data such as the test steps (steps to reproduce), release, tester's name, etc. and turned into a defect to be recorded in Spira, or sent to an integrated 3rd party defect tracker (Jira, Mantis, TFS, etc.).
While the import (from Excel) tools are nice and work efficiently (2 way sync of data, hierarchy easy to implement, tests can be linked to requirements before import/export), there are some default fields I would like to have seen included in there so I could import the 1500+ test cases with less post import/export data manipulation required in Spira across the imported data

Likelihood to Recommend

Great for recording results for manual testing. Spira have made some changes in their most recent version (v5) that allow testers not only to see each step of a test case on one page, but all steps in a test set (containing multiple test cases) and to be able to save results for those steps with one click per step or per test (Pass all steps only). This facilitates efficiency during manual test execution.

Dave Furlani

Senior Consultant - Test Manager / Project Manager in Quality Assurance at RXP Services Limited (501-1000 employees)

Vetted Review

View profile

Loading Reviews List....

Home
,
Test Management
,
SpiraTest
,
Reviews and Ratings

SpiraTest - fail

Rating: 7 out of 10

Incentivized

January 15, 2016

Use Cases and Deployment Scope

SpiraTest is being used currently for a large, complex project with an ambitious time frame in the entertainment/hospitality industry.

Pros

A clean view of test case steps, expected results and the ability to record a result for each step quickly on one page per test set. This really helps testers work through executing manual test cases.
Hierarchical structure of releases and builds, requirements, and test cases.
Can quickly build test sets and/or test runs per build/release.
Simple identification of each test case, requirement, test run, build, release, etc.

Cons

While there are some nice, live reports, test results per build/release is an obvious omission. The canned reports that can be configured are mostly text based. Some graphs included in those would be a nice addition.
Recording a Fail for a test step does not facilitate recording a defect. Defects must be manually reported separately. It would be nice if some standard fields were offered when a failure was recorded (e.g. summary, actual result, expected result, description) were recorded with system-known data such as the test steps (steps to reproduce), release, tester's name, etc. and turned into a defect to be recorded in Spira, or sent to an integrated 3rd party defect tracker (Jira, Mantis, TFS, etc.).
While the import (from Excel) tools are nice and work efficiently (2 way sync of data, hierarchy easy to implement, tests can be linked to requirements before import/export), there are some default fields I would like to have seen included in there so I could import the 1500+ test cases with less post import/export data manipulation required in Spira across the imported data

Likelihood to Recommend

Dave Furlani

Senior Consultant - Test Manager / Project Manager in Quality Assurance at RXP Services Limited (501-1000 employees)

Vetted Review

View profile