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.

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. While the training is adequate, I would like to have a more robust online training option available for various users of the system, since there are admins users and test creators and end testers I feel that having training targeted to each of the basic roles would be helpful.

The user interface is slightly complicated and not very consistent. It could be more user friendly.

In my opinion, they are very clever at creating solutions and making adaptations; they focus more on that than creating a great user interface.

The product search is user-friendly, but guidance for integration with other tools needs to improve further. If an organization decides to move from an existing tool to spiratest, a migration through integrstion is the best way, in my opnion. But the guideline and menu to such features needs some effort from the user. Some smart guidelines for integration can help. The bestvpart is that most plugins required for an integration are available. Just that the search friendliness can be improved further. For example, Migrating can be improved further by giving a trello like UI for a pick and choose. 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. Particularly on the DevOps based development platform. I think there's a lot of exploration that needs to be done on SpiraTest.

Add scripting functionality: 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, it saves so much time and effort. SpiraTest does not have that functionality now and I do not know if they will add it.

Since it can only store documented test cases, that is half our effort when we test. The rest is running the test case and adding over 400 test cases can take a lot of time and effort, especially when we upgrade quarterly.

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.

Areas of improvement are all minor things to streamline the process of setting up a release. For example it would be nice if adding a new test case to an release iteration would also add that test case to the parent release.

Whilst the tool was fantastic there were some areas which were not as user friendly as they could have been. The biggest complaint was the folder structure/functionality. We found that a number of our users struggled to create or move test scripts into the correct locations. This extended out to test sets and requirements. As most users are accustomed to Windows XP/7 environments, a similar method of managing the testing hierarchy would have been a much more preferable solution.

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?

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.

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.

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

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

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.

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.

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

In general, the look and feel and performance issues:

1. When a test case is edited, the fields to edit content are smaller. Would be nice to have options to expand them in the same view instead of opening each field in a new window. That is very incovenient.
2. When multiple test steps are edited, some edition field(s) get locked and all changes are not saved anymore, which causes loss of time when the test case has many steps.
3. Lack of quick response causes loss of time when test case details are edited and during test case execution.
4. Sometimes the test cases screen disappears and automatically goes back to the "Test Set" page, which causes loss of time.
5. Make the test cases editable during the cases execution in order to save time.
6. Only works fine in Firefox but not in other browsers.
7. The look and feel is old style, please make it more friendly and prettier.

Customizing test reports seems to be something one must have (or gain) expertise in.

V4 is available with improvements to the UI.

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.

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.

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. 

I would like to see a more flexible configuration of the reports in the next release of this solution.

Some of the reporting can be limited. The test cases and test sets portion has its limitations and can be cumbersome when changes are needed to test scenarios. Also, the search for test cases can be time consuming and creating test sets from the cases can be hard if there are many Test Cases loaded. It would be nice to have a better search functionality within the Testing area.

• Manual test case writing
• Test management and protocol of the results

Its user interface as well as its graphs.