SpiraTest

You don't need to spend a lot of money in a Test Management Tool - Use SpiraTest

Avantages :

Great usability. It has a lot of features, easy to configure and customize. We need to migrate our projects from HP QC/ALM to SpiraTest and it has a great tool to migrate everything (releases, traceability, requirements, test cases, executions, ...). We've tested in some projects and works great.

Inconvénients :

It needs only more BI or reporting customization, but I think is enough now for most projects. Some other integrations will be great, like some tools for exploratory or acceptance testing (Microfocus Sprinter, ...).

SpiraTest compares very well to other well known project management applications.

Commentaires : SpiraTest compares very well to other well known project management applications.
SpiraTest beats Quality Center in the ability to create different workflows for multiple incident types, and workflow customization is based on a simple interface rather than on VBScript. The ability to link project artifacts together seems much easier and intuitive the Quality Center. Best of all, SpiraTest has a tool to communicate with Quality Center if you need to work in both applications.
SpiraTest also compares well with Pragmatic Software Planner. Information is much more accessible in SpiraTest, and everything actually works. Software Planner loses points for having a more rigid workflow, a non-intuitive interface, and for features that just don't work, like custom reports.

Avantages :

You can't beat SpiraTest without paying a lot more (and even then you might be disappointed). - Surprisingly easy set up. - Fantastic ease of use once you get used to the workflow paradigm (change status, verify newly required fields, then update). - Traceability: We love how all project components can be linked together. - Test case management: Create individual steps for each test case, and link steps from one test case to another to prevent step duplication. Create a test run, and send information to your automated testing software. Software testing heaven. - Workflow management: custom workflows by project or even by incident type. Cusomtization is implemented by interface, not language. - Support: Inflectra support has been fantastic in helping us migrate data into SpiraTest from our previous system. - Meets our needs: Our consulting firm needed a one-stop app that would work for multiple long- and short-term projects. We found SpiraTest, we tried it, and we love it.

Inconvénients :

Enhancements to current features, rather than new features, seems to be the rule: - ability to create and administer user groups on a project level instead of only at the application level. - mass updating of multiple artifacts (change all incidents with this type to that type) - update workflow transitions by user type instead of altering each transition. - Workflow takes a little getting used to; transitions must be performed in the following order - 1. Select the desired status, 2. Fill out ALL the newly required fields (check all the tabs), and then 3. Update. - Custom fields are hidden on their own tab in the lower half of the main pane. It would be nice to have the option to place some custom fields on the main pane. - Would be nice to be able to hide fields that aren't desired for a certain project. - Would like the ability to assign certain SysAdmin rights on a project level. - Would like a few more report cusomization options.

Spira Test Version v2.1 has many functionalities of a Robust Testing Tool.

Commentaires : Spira Test Version v2.1 has many functionalities of a Robust Testing Tool, it is complex and has what a project needs to start testing, but it is difficult to implement and I can see project monitoring a little bit weak if the test execution was not correctly followed from the start. It would be good to see a few more features and clean up the UI to be able to have a better feeling of the projects you are currently working on. A concern is the security when using Jira integration, I don't think we need to personalize and configure every bit of the tool specially in installation files adding sensitive information should be left optional (like in other project settings). New features in the configuration management would also help to identify the items we are working on. Thanks for all your continuous support. Alejandra Gonzalez

Avantages :

- Defects will open new ticket in Jira ( with new ID ) email notification will be set to Spira Test ID - Integration with documents from MS Office available in HTML, XML, Word and Excel formats. - Integrated with third party software: Available Jira Integration - Available to Import test cases from excel with provided SpiraTestImporterTemplate.xls - Highlights changes to requirements and test cases in History - Changes can trigger e-mail alerts or notification of users set up. - Updates are available for download in the website. - Monitor Environment and Resource Usage: Available in Application event logs from server to administrator - Can add attachments to requirements and test cases, but need to click on it to open it and the description is an alt tag to the name of file. - DB Backup options available to db administrator. - Tool support resources: Comprehensive on-line help, email, and examples supplied in demo trial.

Inconvénients :

- Would like the User interface to be a little more friendly and easy to use. - Spira Test implementation needs to configure too many sensitive user information in the configuration file, would like to see another version that does not need this - Was not clear if the history of execution status is saved after many executions just saw some saved. - Email sent from Incidents created from Spira test makes tracking difficult, the subject of project. is not in the title of email, only the id, that is the next ID available for all projects. - Server performance issues, Spira Test requires too many resources. - Record and play not available in this Software version. - Need to update installation files (*.config) for each user that is using the tool. User setup and access process is too long.

Way better than Excel, Testuff, and other lower price point Test Management tools.

Commentaires : Test data management without the risk of irreversible or unaudited changes.
A cloud accessible test management tool for my test team

Avantages :

The ability to group test cases, the folder hierarchy, test sets and test runs per release. So glad the all tests with tests steps view was added (Table view) Customisable reports are very useful once configured/scripted correctly (although the interface/mechanism is too complex for non-developers/non-technical people. It is far from intuitive)

Inconvénients :

Data imported to the Excel template via the Excel add-on should arrive in a format that could be immediately exported back to Spira. This would facilitate faster creation of duplicates with minor amendments, such as copying large tests sets to be rerun in a new release. Reporting. It's difficult to find the report you want without having to run one to see the story it tells. A snapshot of the report with generic data would be handy. Failing/blocking a test should start creating the incident. These should be seamless. Select existing incident should be an option there also. There should be a way to clear results from a step, not just select a different result. There needs to be a X by Y grid matrix of requirements to tests in Reports The Export to Excel option should work for multiple selections The data structure should be made available within the Reporting UI to facilitate customised report writing. A drag and drop UI would be a big improvement, as would a sample view to see the impact of your changes with dummy data without having to run the report The name of the current test should remain on screen while the steps for it are visible. As the last step scrolls off the screen the next test name can then appear.

Overall it's good an makes test management and running a lot smoother

Avantages :

The history features of test cases are nice. The ability to link requirements to test steps is nice (allthough could be improved as it is lost on clone). The tracking of progress is nice and ability to create incidents from a specific test steps helps a lot. All the different types of reports that are available to generate are also quite nice.

Inconvénients :

The lack of branching/versioning of test cases. This is a big con for us and we're hoping that it will be looked at in the future. Another problem is the linking of requirements to test steps, it feels like it's lacking a bit; it should be possible to 1. Clone a test case and keep the requirements on the test steps (currently they're lost) 2. If a requirement is just linked to a test step the result should be possible to link to that, currently if a step not at all related to the requirement fails the requirement will also fail. Also we'd like a report where it's easy to see the traceability and result of test run and requirement, e.g.: REQ1 PASSED REQ2 FAILED Currently it is possible to get the requirement and what Test case it is tested in and then print out all of the test cases to see the results. We'd just like a bit of an easier report/tracking here. If possible it would also be nice to add a comment to FAILED, maybe what test case failed (if it is tested in more than one) and perhaps even incident numbers of some sort.