We performed a comparison between Inflectra SpiraTest, Jira, and Polarion Requirements based on real PeerSpot user reviews.
Find out what your peers are saying about IBM, Atlassian, Siemens and others in Application Requirements Management.
"The features of this product most valuable to me were the test case management and the visual status, by which it was displayed."
"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."
"We were able to add a step-by-step procedure for someone to follow to assist in testing."
"I found Inflectra SpiraTest intuitive enough. It's also easy to learn, so this is what I like about it."
"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."
"The flexibility to create different flows is most valuable."
"I can use Jira Query Language (JQL) to write queries to see the stories that are there for the current sprint. I can also sort them by assignment. I also use Jira is for burndown charts, which give an indication of how efficiently the squad is performing. I also use the Active Sprints function and a feature called Planning Poker."
"Great for tracking my development team's productivity."
"The most valuable aspect of this solution is its ability to connect everything together."
"The ordinary user has an interface that is very clear."
"The solution works well and does what it needs to do."
"The board has been a very valuable feature because it can be very simple for teams that are not technical. It can also be highly technical and have lots of data for teams that are technical. So we use it for both instances."
"We can integrate a lot of tools with the solution."
"Its flexibility and APIs are the most valuable."
"We can easily customize it because of the web services and open APIs. Also, the APIs are available. We integrated Polarion with one of Siemens' products, Teamcenter, which is especially useful for automotive industries. There is an open API for integration with Jira as well, so for me, customization is a strong point."
"We worked with the web interface."
"The solution is especially great for organizing folders effectively."
"I like the way this solution is structured."
"In my opinion, Polarion Requirements' most beneficial feature is the ability to manage specifications within a work-like document that functions as a work item. Its collaboration features have worked very well and have been very useful. We can easily exchange information with the testing team, the business, and with DevOps."
"The biggest improvement would be in the transparency we have now. We have very complex products. We make whole systems with difficult and diverse areas such as hardware, software, mechanical and printing, etc. To get the overview of all the requirements into a system, at that sizing, is the main advantage we have in the organization now."
"Polarion Requirements' most valuable features are link tracing, book entry, and sequence training features."
"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."
"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."
"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 user interface is slightly complicated and not very consistent. It could be more user friendly."
"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."
"I have had problems with performance and unresponsiveness. All of a sudden, the performance slowed down, and I had a number of users that could not use the tool."
"What I don't like is that perhaps there are not so many different apps that can add value over the management side of the product."
"Something I do not like about the new version is that there is a need to browse all the way back to the beginning, should a person click on a task that is specifically for his group and wish to go back and look at the other portfolios or people."
"I would like to see it connecting to Git. That could be useful. We use it for Stash, but I think there is one for Git also. I don't know if it's a plug-in that exists already, but that could be nice."
"Something I would like to see improved is the traceability feature. When you have a user story, if you can see all the test cases, it would be an improvement if you could see any design documents or any change management."
"As the solution is highly configurable, it has very poor governance."
"There are some features and reports we need that are not there. For example, if I have to find out the capacity of the current sprint by user and compare it with the previous sprint, that visibility isn't there."
"I would like to see visualization of release planning. I can list the releases and I can give dates to releases, but to show how they are happening on a timeline, I would need to order the Portfolio part. But just for this, it may be too much to use the Portfolio for that."
"It is not a stable solution, as we had issues with shared licenses."
"Its user interface could be more user friendly. In addition, a lot of features are missing for test management. It should have the test case ordering feature."
"One thing to consider is increased flexibility in terms of workflow configuration."
"Polarion Requirement needs to have a feature where we can track changes and compare documents. Currently, we do it manually."
"The risk assessment functionality needs improvement, like FMEA risk management."
"The one thing I would mention is the license policy is a little bit difficult. For different roles, you will need different license models. That seems a little bit difficult for us. Especially when you introduce such a complex system, you want to know the right way is to do licensing. It's not clear what that best way would be. The solution will be here for a long time, and I just think it could be more clear."
"Integration can be a little tricky if you're not aware of basic computer science or programming language."
"The usability of the solution should also be improved."
