Inflectra SpiraTest Reviews

Frankly, I cannot find anything at the back of my mind that I can term valuable. It's a solution we have and use. It is as valuable as having any structured test management tool.

SpiraTest was adopted as a low cost solution in lieu of HP's Quality Center 9.2 or its upgrades. In early 2012, we were frustrated with the product, unable to achieve our objectives, slow response, etc., but over time and further upgrades these have improved.

The product needs to have finesse if it has to be adopted wholeheartedly by the entire testing community. Some improvements that remain at the back of my mind are -

1. Excel plug-in should support user incorporated native excel formatting
2. Asynchronous JIRA to SpiraTest synchronization
3. UI could use a lot of work.

• The folder structure representation takes up lots of screen space
• Should allow wildcard searches for test cases
• Should allow wildcard searches for test case names in a test set
• Universal searches to cover test cases, requirements and release summaries
• When trying to add a test cases to requirements or vice-versa, there should be a better way other than searching from the entire hierarchy or at least provide a large enough screen to make to easy for user to search.

HP's Quality Center made way for SpiraTest as a low cost solution.

The installation was carried out by the client.

It isn't as easy to adopt. Will need some getting used to.

• 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.

This solution provided us with our first database solution for test case management. It also provided our first opportunity to easily link requirements to test cases, and test cases to test runs.

Moving to a test case management solution like this improved our traceability of test cases to requirements, and our record keeping in general. Results were no longer spreadsheets stored on a server somewhere; they were much more readily available for review.

The bug tracking portion of this software, while ok, could use some improvement. Also, I think this software could benefit from better reporting options - which may now exist in newer versions.

We used it for about one year.

We found that, after a while, that after we entered hundreds of test cases into the system, operations like deleting a test case, or a test run, began to take over an hour to complete.

Our IT department took care of the installation, so I cannot comment on that. However, getting started with entering in tests, and creating hierarchies for structures was easy to do.

After installation, I basically took over getting our test cases entered, our upcoming requirements entered, and so on. The most important thing to know here is that this is a very time consuming process. Not necessarily due to the software, but due to the unavoidable fact that hand entry can take a long time. The software does support importing from certain formats, however if they don't line up with the way you were doing your documents beforehand, it won't be useful. Give your team sufficient time to enter in items as it will save time in the future, and will be well worth the commitment.

For the price, this is a very simple solution, with limited functionality, that will definitely improve any department still using spreadsheets as their documentation. Once implemented, and transferred over, much, much time will be saved in test case execution, and reporting.

• 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.

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.

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.

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…

The features of this product most valuable to me were the test case management and the visual status, by which it was displayed.

Senior management cares about where we are. They don’t have time to look at a lot of data. SpiraTest provided good visibility at a high level looking at where things were.

Two areas that can stand improvement: integration with third party products and making it more intuitive.

The deciding factor to not use SpiraTest anymore was because it was cumbersome to integrate with TFS. Once it was put into place, we found out at the time, it did not support file attachments. That was huge for us because our developers relied heavily on having visual examples of bugs we found.

The other area which could stand improvement is flexibility in reports where one can actually create custom reports rather than work with canned reports.

At my prior job, we used this for 5 years.

SpiraTest was incredibly stable. Usually when there were problems, they were internal to our organization, not Inflectra.

I would rate technical support at Inflectra as an eight and a half out of 10. They are very responsive in a timely fashion.

No, this was the first test solution used at that organization.

The setup was done prior to me coming to the organization, but it was my understanding that it was not cumbersome at all.

The pricing was excellent. I would recommend the enterprise solution.

No other options were evaluated.

Before implementing the product, consult with all the stakeholders who may be using this solution in terms of what is not only important to you, but to them as well. If you plan on using SpiraTest as a bug tracking tool for QA, ensure that it meets your requirements in regards to integration of the tools within your organization. This may rely on what goes on in QA.