SpiraTeam

Comentarios: Overall, I like SpiraTeam. There's a bunch of different ALM solutions out there. I prefer something easy of a lot of confusing functionality. SpiraTeam is somewhere in the middle. It has a good balance. I use it for keeping track of test cases, but don't use the requirements functionality. I wish we did use the Requirement functionality, but the developers I work with have a thing about NOT documenting what they are developing... In any case, I can produce the results of the test effort rather easily so the rest of the team can see where we are within the project.
Some of the annoyances are the ability to produce a report and distribute to the rest of the team. With the templates that SpiraTeam provides, I would like something a lit bit different. The templates just don't provide the information that I need. I know there is a way to modify the templates, but never had time to devote to figure it out. Also, the way arranging tests in folders and then moving tests around in the folders has been difficult over the versions of SpiraTeam. I like how tests are arranged in that way. It helps keep everything organized in a good manner, but the implementation of it is not entirely perfect. test cases often get put in the wrong place and have to spend some time moving them around. My last annoyance is how test cases are copied and pasted. When pasting a test case, it places it on the top of the test case I copied, not underneath it. That bugs me more than anything.
But when judging SpiraTeam as a whole, I do like the product, but it's those little interface annoyances that get in the way.

Puntos a favor: I like the concept of how test cases are arranged, within folders.

Contras: I don't like how the concept of the folders was implemented. Often times, when copying and pasting test cases, it gets placed in the wrong location. Have to spend extra time getting test cases and folders placed in the right location.

Comentarios: With Spira Team we are building out our B2B and B2C solutions. We use the Planning Boards for SPrint Planning and daily stand up reference. WE use the Incidents page for tracking defects and Test Cases for Test Management. We also use Requirements for High Level Requirements, decomposing into Use Cases. We can bring in third parties as required to communicate their cards.

Puntos a favor: Where you are in the B2B market and have tech clients who remain Waterfall in their planning, yet you are more enlightened, this is a suitable tool. It does allow you to plan your dev trains according to iterations and project onto a scrum board. At the same time it allows you to map these cards to a set of requirements. In addition, you can plan your test cases and track defects all in the one platform. Sure, you could go down the Atlassian route, Inflectra appears to be better value for money, especially when adding modules.

Contras: Insufficient integrations available with market defacto standard testing tools. The training model is on a consulting model - not great for start ups and scale ups. Need more training videos dealing with the set up in situations of increasing complexity! Was advised that Inflectra is responsive to customer feedback feature requests. Have not experienced this yet, despite regular feedback. Because most teams spend so much time in the Planning Board, more investment is required to improve usability of this page. Its good, just not great yet. It would be great to restrict visibility of external users to specific pages or to specific cards, instead we have to create separate projects for these groups, which is not always ideal when inserting external groups into internal team work.

Comentarios: The primary goal of the software we were looking for was the management of requirements and testing along with a built-in traceability matrix and reports. SpiraTeam included these at a reasonable cost. We purchased the 4.2 version and have not upgraded to the latest. We like the feature that not only maps the requirement to test case(s) but also indicates how many of the associated test cases have passed/failed. The filtering on tables for Requirements, Test Cases and Incidents is very helpful. Also like the folder and subfolder concepts to easily group system features. We have not used the Test Sets feature. We've been able to generate requirements and test reports and make some modifications. I am not a developer so this was a bit challenging and was not able to figure out how to create a report for bugs not linked to test cases. SpiraTeam does have a report showing Test Cases with associated incidents of which I was able to expand to get additional incident information other than just the ID. They have a handful of other reports as well. We used several administrative features. Adding new users and projects is fairly easy and straight forward. We configured the Incident work steps (workflow) to meet our business workflow (e.g., added Works as Designed and Close (by Design)), added some custom fields and adjusted field properties (e.g., hide, require) per the workstep. We used the email notifications feature as well. We also synchronized with Jira but abandoned this. We could not get the components to map but mostly because after trying it, we found it much easier to manage defects in one system for our internal processes. Once a bug is synchronized and written to Jira, you can only update it from Jira, not SpiraTeam. It would be nice to have a feature that lets you know when a test case should be retested because the associated bugs are fixed. Customer Service is responsive and professional. Sometimes I found answers to my questions on their Knowledge Base. Overall good experience. Really helps to see that requirements are covered by test cases and gives the ability to manage test case (pass/fail) in one place without having to use spreadsheets!

Comentarios: Most excellent, brings our Business and testing together in understanding the req.

Puntos a favor: The Software made Automation easier. Integration easy, total revolutionary product. Very powerful tool if used as designed.

Contras: Users. Misunderstanding the designed use compared to their personal opinion.

Comentarios: Spira is a very good QA tool. It is very easy to use and very nice documents to follow. Very affordable price. Very good customer service. I am very happy using this tool and pleased with the customer service quick responses. However, here are some of the improvements and enhancement suggestions. 1. Is this compatible to use in all the browsers. Currently, if I am using chrome, when I try to edit the test case there is no way of saving. Save button is disabled. Update button is not displaying on the edited step. Today I started using IE to see if it will work better. Any ideas on that which browser it works well or is it properly tested to use in all browsers? 2. If working on a test script or projects using Spira, user accidently deletes the test case, is there a way that we can restore the data? Any history to bring back the deleted test case? If this is not there now, I request to add as a future enhancement to benefit. 3. Why do we need in Test cases also Execute button and in Test Sets also Execute button? It is very confusing. Usually it should be in Test Sets. 4. Axosoft and Spira test documents can be clearer to understand from a QA tester perspective. 5. I am still learning and trying to experiment the full features. Thanks.