Inflectra SpiraTest Reviews

Apart from bugs reporting and tracking, which are obvious features for test management tool, these are the important features:

• Simplicity and usability - SpiraTest is very intuitive and easy to learn
• Integration with other tools - I was integrating SpiraTest not only with Inflectra's Rapise, but also with MS TFS. I found the procedures straight forward, intuitive, logical and fairly easy to maintain. Spira Test has plugins for a number of tools.
• Reporting - Flexible reporting feature made managers' life much easier. XML based templates, easy to tailor to user's needs were really helpful in providing up to date feedback of projects progress.

We came from Excel and mindmaps to using the professional management tool, thus there were plenty of benefits. Out of the blue, we were able to link issues with requirements, hold the history of test runs, differentiate results in regards to release, provide complex reports. The organization finally became organised.

To be fully honest, it's been some time since I've last used SpiraTest, thus some of these could be addressed already. But from memory, there were as follows:

• More flexibility in setting default behaviour of particular items, e.g. releases/iterations do not inherit their child nodes' test cases, the same with requirements and subrequirements etc.
• Working better adaptability of custom fields, especially in terms of integration with other tools
• More projects interoperability, also some root settings could be able to apply for each project. I missed the ability to establish the same workflow for each project, when a change was applied, to keep the consistency we had to update each project separately
• More visual flexibility. To change the size of input fields, we had to dig into application code. Each new SpiraTest update obviously turned it all to default
• Tool integration plugins are great, which doesn't mean they couldn't be better. Synchronizing items is fine, but why not synchronize relations between them?

I've used it for nearly two years.

No issues encountered.

This is the biggest plus. I'd rate it 10/10. For the whole time I was using SpiraTest, I had an impression of being the only customer which counts. They answered even the most naive questions, patiently explained everything, went ste by step with more complex issues, even helped to fix corrupted database. If I were to recommend SpiraTest to others, I'd start with excellent technical support!I worked with TestLink, free tool not comparable with SpiraTest, in advance to the latter. Never evaluated any test management tool.

I worked with TestLink, free tool not comparable with SpiraTest, in advance to the latter. Never evaluated any test management tool.

Straightforward. As simply as it is.

If you think about the complex solution and did not purchase any tool yet, it could be wise to consider the full SpiraTeam Enterprise solution. Although integration plugins are great, it's nothing better than having the whole solution perfectly integrated with no need to spent weeks on maintaining. And the price is really good as for the quality of the system. Try the solution first, Inflectra is usually fine with extending trial period if required. And for this price - do you really think about limited number of users...?

Read the documentation first and do not shorten the process yourself. If you have any concerns, do not hesitate to ask technical support - they will help.

• Price
• Ease of use
• Integration with automation.

SpiraTest is cheaper than its rivals.

It has very simple UI designs. We don’t need to train testers for SpiraTest. Everyone can handle it.

We are using custom automation tools. SpiraTest’s client engine mechanism is very dynamic for integrating custom automation tools.

Test case management was an issue for us before SpiraTest. Now, we have more than 4K functional UI test scenarios, and by integrating Spiratest with automation, we run our automation scripts periodically.

We have faced some performance issues. Inflectra may check the performance of SpiraTest. Also, test importing from Excel should be reviewed. We had some issues with this.

We have been using SpiraTest more than four years.

No, definitely we did not.

We faced some performance issues, which could be a problem with the scalability.

Technical Support is fast enough to answer questions and problems.

In our company, we did not use any tool for test management before SpiraTest.

It is definitely very simple to setup SpiraTest. Especially when we compare with rivals, SpiraTest is pretty much the easiest one to set up.

Instead of IBM or HP tools, SpiraTest has affordable prices and support.

We checked HPE tools. But initial setup, maintenance, ease of use, and price were crucial for us. SpiraTest is the winner.

Depends on their user count, they can contact Inflectra about performance issues. We are using them with 20 concurrent users.

• Test case documentation and execution history providing full traceability.
• Ease of use.
• Role based access.
• Ability to customize functions, such as roles, form attributes etc.
• Plugins to various other systems.

Our organization has become more efficient in our everyday test case documentation and in the execution of both manual and automated testing.

This, in turn, raises the quality of both our work and products.

Currently, I am waiting for a major improvement when it comes to sharing all artifacts across projects, this is something the Inflectra team is working on.

Cross-browser stability, i.e. not everything works as is designed in each of the major browsers, i.e. IE, Edge, Chrome, and Firefox.

Six to seven years.

No.

Not in general, but a certain plugin for source code repository connection could be better.

10 out of 10. The Inflectra team is quick to respond and even helps with solutions when I've found it necessary to contact them.

No, we only had Excel or Word for test case documentation.

Straightforward, providing the pre-requisites were in place.

Can't beat it, in my opinion.

Yes, but sadly, I can't remember them all. My main reasons for selecting SpiraTeam were as follows:

• Value for money.
• Ease of use.
• No client side installation necessary which some of the other solutions required.
• Faith in the vendor to listen to me and our needs as a customer. I experienced exceptional customer service and have continued to do so.

I would advise anyone to try it first and make sure it fulfills their requirements for this type of system.

The fact that you are able to structure and keep track of the complete test process has been the main goal.

Test approach can be set up with the use of multiple test teams who (thanks to SpiraTest) are able to work in collaboration with each other (follow-up of testing, division of tasks and effort, high level of traceability).

• Not much room for tweaking of menus.
• It's not open for use of add-ins/automation, or at least instability the moment a version differs.
• Slow response of server, possibly because of the cloud performance.

I've used it for two years.

The integration with Atlassian JIRA was forseen and configured, but the moment a new build of SpiraTest arrived, the add-in used for this integration became non-working, so there's no more integration with JIRA.

It's decent, but I'm not ecstatic about it.

It was very straighforward, because of the web-based implementation, so there's no need for a lot of hardware installation/configuration.

We used an in-house configuration manager. You should always evaluate the compatibility with your existing environment/tools.

Before there was nothing, so implementing this was a big step towards a structured test process, so it's priceless.

Considering the cost and complexity of a test management tool like HP Quality Center, SpiraTest provided an acceptable alternative solution, but there are also more alternatives available at this moment.

Don’t be afraid to pay for component you urgently need, but also: don’t hesitate to refuse to pay for aspects you consider to be obsolete).

SpiraTest is a damn fine test management tool, but it seems that they run the risk of missing the ‘innovation train’ if Inflectra doesn’t act fast…

Currently, I work as an SDET only and I don’t write or run tests. However, I use SpiraTeam existing tests so I can decide how to automate them. I use Spira RemoteLaunch to schedule a test server, which in turn schedules various test clients which run Ranorex.

In the future, we intend to use SpiraTest to store a script which will be passed on to the test server. This will run the tests and return the pass/fail result. We will generate the test script using a web page server.

In my previous job, I used SpiraTest to design and document tests. I would have a technician run manual tests using SpiraTest. I used Spira RemoteLaunch to run Ranorex automated tests and store test results. I would use SpiraTest to produce reports to generate a Test Plan, and also to produce a test result based on both manual and automated tests.

My team uses SpiraTeam to document tests and test results.

1. Sometimes I need to restart Spira RemoteLaunch because it goes into a bad state and is not listening for new tests.
2. Spira RemoteLaunch does not have the capability to run simultaneous tests in more than one server.
3. Spira RemoteLaunch does not have the capability of communicating with an ongoing test (e.g., send it commands). So it’s not possible to have a one-to-one relationship between manual test steps and automated tests.
4. The preset test reports are very limited, thus I had to XSL to modify tests. This is quite involved. My biggest suggestion for improving SpiraTest/SpiraTeam is to provide an editor to produce test report templates that are more flexible. For example, one should be able to specify variables (e.g., unit-under-test name, IP address, or web site reached).

I have used SpiraTeam and Spira RemoteLaunch for about one year. Previously, I used SpiraTest for about two to three years.

Yes, I just noted that sometimes RemoteLaunch goes into a bad state and I need to restart it. I have noticed this in the past that sometimes the RemoteLaunch does not schedule things properly. It’s been a long time, so I cannot provide details about this at the moment.

Yes, I noticed in my previous job, as one generates many test reports, database access becomes very slow to the point of being unusable.

I have not requested technical support on this job. Previously, before purchasing SpiraTest, the support was superb. However, after purchasing the product, I noticed that sometimes I had to wait for days to get a response. The regular support people were not as knowledgeable as the sales support.

In my previous job, I introduced SpiraTeam after looking at different test management products. At the time, there were not using any. I chose SpiraTeam because it was one of the few products that supported Ranorex, which is the test tool that the company was using.

I don’t remember much, but I don’t believe that the setup was difficult.

From my recollection, SpiraTest was reasonably priced so that was not a big factor in convincing people about getting it. The bigger issue was whether it was the right product for us.

I looked at public domain tools and found one that I liked (don’t remember the name), but the problem was that it did not explicitly support Ranorex. I looked at other tools, but they were too expensive.

1. Use a fast web server with lots of memory.
2. Limit the amount of log messages for the test report.
3. Try to pick test clients in the same subnet as the test server. This will reduce scheduling and communications issues.

• Test traceability - drill down from requirements to tests and incident
• Custom report functionality
• JIRA integration and the option to integrate it with many other test tools e.g. scheduler for running SOAPUI/Ranorex/scripts
• Good technical support

At first we used MS Excel for setting up test scenario’s and managing the test progress. As the test team kept growing, it turned out that Excel was not adequate anymore. Having undertaken a lot of research, SpiraTest came out the winner. With this tool, we were able to make our software testing life cycle more efficient as well as create more transparency.

A great feature in SpiraTest is that you can use an existing project as a template for setting up new projects (workflows, custom properties, and data sync are copied). However, when you need to apply a change to a workflow which is used in multiple projects, you need to modify the projects one by one. For this reason maintenance is sometimes quite time consuming.

I've been using it since September 2013.

So far we haven’t encountered any downtime or any major stability problems.

Inflectra support staff respond to raised tickets within one or two days. So encountered problems are taken care by them very quickly. Also, any suggested enhancements are taken into consideration by them for future release.

The initial installation was quite easy. For the setup you only need a web (IIS) and database server (SQL server 2008). However, it is advisable that you have full admin access to the database or at least have a database admin who can assist you when setting up the database in a cluster environment (shared SQL server). Especially when the database policy does not allow database users (like a SpiraTest database user) to have full admin rights.

The SpiraTest database user is required to be a full system admin user (DBO role is insufficient) for creating the necessary database objects. The user manual is quite extensive and a great help for doing the initial setup. Basically the initial setup is quite straightforward, but time consuming.

The implementation was done by an in-house test team.

• Testlink
• TestTrack
• TestRail
• Zephyr
• Tarantula

If you are looking for a decent test management tool with a good balance of cost and functionality, SpiraTest would be a very good option, especially when you have a limited budget.

The most valuable thing is that it's a test management system, in which you can handle a mass of test case specifications and executions.

It has not probably improved anything. It is just generic test management which has quite a small price tag. Of course it has provided us way to handle our test specifications.

The tool doesn't restrict the usage, so if an organization wants to plan a lot they can, so this tool is good in that sense.

It's low score is mainly because of the problems with the user interface, usability and lack of user guidance - meaning that tool has no predefined way of work.

I would like to see improvement in handling test way of work. The current version does not provide enough support for test management way of work. You have too much to plan by yourself. For example, the linkage between artefacts is hard without planning and guidance for end users. The UI has it's limitations and current folder system is hard to manage. User right handling is hard because you need to grand too much rights to the users.

I have used it about three years. I have been the main user of the product and planning how the tool should be used.

Scalability wise, it needs hardware resources. Only Microsoft IIS is supported, and it's not a Linux based solution. We had to give more resources because it was stuck with lots of users.

Support has been good so far.

Setup is pretty easy but the user guidance for the end users is complicated.

We used an in-house implementations. I advise to plan a lot about the process itself, because the tool does not support that one very well. Also, the report functions are useless without good data consistency.

The price tag is be quite cheap I guess so in that sense it is one alternative. However, a lot of time goes into handling the test objects in the tool

Plan beforehand how the team shoudl use the tool. In that sense there are better solutions available

Integration with the JUnit test cases is the most valuable feature. I am able to integrate my automation of JUnit cases with the SpiraTest very easily, i.e., by just adding a few parameters in my source code.

You may find the detailed information for the integration from the link below:

https://www.inflectra.com/Documents/SpiraTest-Team%20Automated%20Testing%20Integration%20Guide.pdf

It has helped a lot for the testing side for our applications. The test scripts are written in SpiraTest, which define the step-by-step information with the detailed information about the version of the application, so as to conduct the functional as well as automated tests. The same scripts are run for every new release.

Requirement/test case baseline functionality would be a great feature to add.

I have used this solution for two years.

There were no stability issues.

There were no scalability issues.

Technical support is very good. I would rate it a nine out of 10.

Personally, I haven't used any other solution before this one.

The initial setup was very much straightforward and we didn't face any issues with the integration.

It's worth investing in Inflectra for your internal system as it's very useful.

I have been using SpiraTest for a team of 10 users and am very much satisfied with its licensing and price (a free trial is a plus). The more I use SpiraTeam, the more I like it.

It is the best QA management tool, good for all types of industries.

It provides the ability to create, edit, and manage your project's requirements in an hierarchical requirement matrix, where the high-level business requirements can be decomposed into appropriate system requirements.