We performed a comparison between Inflectra SpiraTest and Rally Software based on real PeerSpot user reviews.
Find out what your peers are saying about OpenText, Microsoft, IDERA and others in Test Management Tools."The reporting functionality helps vendors and technical resources identify bugs and issues that need to be addressed. The simple dashboard-style home page makes training end-user testers simple and straightforward. The actual testing UI is VERY straightforward and very intuitive for the end-users that test the system since very often we pull from business and operational users to help test new systems."
"I found Inflectra SpiraTest intuitive enough. It's also easy to learn, so this is what I like about it."
"The features of this product most valuable to me were the test case management and the visual status, by which it was displayed."
"We were able to add a step-by-step procedure for someone to follow to assist in testing."
"The ability to reuse test cases already used across projects is the most valuable feature of this solution. We don't need to create new ones."
"Inflectra SpiraTest has a lot of functionality, which is good."
"The user-friendly features are the most valuable. For example, migration of requirements and migration of test cases and the creation of traceability. You have various reports that you need. The plug-ins that are available to connect with the other tools."
"Helps me plan an estimate of how soon or how far out we'll be able to deliver something."
"With this product, searching for historical information or the evolution of the requirement, detecting conflict between projects has helped a lot."
"We've actually used it for virtual PI planning. We have teams in different locations, and we actually virtually do PI planning, big-room planning, using the tools."
"The most useful part is how it breaks down tasks into parents and children, manageable tasks. It has a whole project as an initiative, and then it breaks it down further and further. And then you get to actual user stories and tasks that you can sit and develop."
"The transparency it allows us to provide, both from the team level all the way through the executive level within the company and the work that we are doing."
"It allows us to work in a more dynamic fashion and track more of the development lifecycle."
"It documents stories in a way where we do not have to be heavy on front-end requirements, front-end documentation, and front-end workflows."
"The reporting, and being able to roll that up across the verticals, was an important selling point for us."
"It should develop integration with JIRA. We have some complexities which caused us not to decide to integrate it with our JIRA, like synchronous data."
"Two areas that can stand improvement: integration with third party products and making it more intuitive."
"Migrating is not very easy. It depends on the organization, how efficient and effective the decision-making process is. The plug-ins should be easier and more integrated rather than the user trying to integrate the tools which are more popular, like Jira et al."
"The folder organization in Inflectra SpiraTest could be better, though I cannot comment whether that is structure-related. Most of what I need would probably be in the tool, but as a test manager, I need to be able to create dashboards and reports easily."
"Being able to add scripting for testing can and does save a lot of time. When you are able to just ‘run’ a test case rather than manually add it and run it."
"The UI for managing test cases, test sets, test runs could be a little more integrated, currently, these feel disjointed at times and confusing. Also, the test steps page needs to display the test steps closer to the top of the UI so as to not have to scroll down to find."
"The user interface is slightly complicated and not very consistent. It could be more user friendly."
"The stronger CA can get on dependency mapping the better. That's the biggest hiccup. As you're setting up your features, they should make it easier to flag the dependencies, either across features or across projects. Then you're more set up for success."
"I think there is a missing link with the development activity. Some developers are pushing in new versions of the code, but you cannot make the link from the user story to a specific application version."
"It's a bit cumbersome to manage the Project Picker. As we sunset teams or projects close out - but we still have test cases tied to those teams or projects that are being used in other spaces - we have this monstrous list in the Project Picker that becomes really difficult to manage and find, and we can't clean that up ourselves. It would be nice if it was easier to do that and not lose your history."
"I think the interface could be a little bit more visual and less wordy. Right now, it seems like it's just a lot of text on the page. In other ticketing systems where it's more visual, you can see more of a flow. But in this one it's more just a list of tasks. I would like to see that a little bit better, especially considering it has so many great organizational features, like child tasks, different artifacts. It would be great to see it presented more appropriately."
"In terms of improvement, perhaps some more metrics. If they could add some additional, that would be cool."
"What I don't like about it is that it is really hard to find old work to reference information and use the reporting section of the application in terms of trying to analyze trends. If I am trying to find out which interfaces took this long and I want to compare and measure improvement from one quarter to another quarter, the reporting mechanism within Rally is very troublesome. They have an Excel plugin that you're supposed to use, but you literally have to pull the raw data out before you can do the analysis. You can't do it within Rally, and if you can, it is a secret, and I don't know how to do it. It should have better, easier, and user-friendly reporting without having to use the Excel add-in. It is very clunky. There is a lot of data in there, but it is not organized in such a way that makes it intuitive. You really have to kind of look for where do you put your documentation or dates. Some customization is available, but it is not plug-and-play like Jira. When I switched from TFS to Jira, I just went and started using Jira, whereas with Rally, you kind of have to really get in and figure out what you need to do before you set stuff up, or you're going to get yourself stuck. You can just start using Jira and be successful."
"Customization features may not be exposed or unavailable, so people may be looking for them. So, customization is an area people have told me is more desirable."
"More importantly, we are seeing internal challenges from Atlassian because of their highly integrated suite that enables further automation and centralization of activities that are also highly necessary – messaging notifications cued off builds, collaboration on Solution Architecture Documentation, etc."
Inflectra SpiraTest is ranked 15th in Test Management Tools with 25 reviews while Rally Software is ranked 8th in Application Lifecycle Management (ALM) Suites with 116 reviews. Inflectra SpiraTest is rated 7.4, while Rally Software is rated 8.2. The top reviewer of Inflectra SpiraTest writes "Intuitive enough and easy to learn, but in terms of folder organization, it could be better". On the other hand, the top reviewer of Rally Software writes "A solution that enables users to accurately estimate the time required for building large software projects". Inflectra SpiraTest is most compared with Microsoft Azure DevOps, Jira, IBM Rational DOORS and Jama Connect, whereas Rally Software is most compared with Microsoft Azure DevOps, Jira, TFS, Jira Align and OpenText ALM / Quality Center.
We monitor all Test Management Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
