IBM Engineering Lifecycle Management vs. SpiraTest

The software is robust enough to handle highly complex software development or other product development and can be used well beyond the range to do what a client needs. However, because of the inability to hold its users to proper best practices, things can get wildly out of hand and cascade over the years, creating unnecessary technical debt. The system has a lot of usable features, but they don't funnel users toward the correct processes and practices.

Incentivized

I think SpiraTest is well suited as a test suite, but in situations where the team is already using multiple products from one particular provider, it may be better to go with that provider's test solution. This is because integrations are very important nowadays, and should be considered when picking your project management software. It should be noted that management selected SpiraTest primarily due to the low cost of the test software. I'm less familiar with other test software in the field, but if cost is an issue, you should take a look at SpiraTest.

Incentivized

• Open Services supporting Lifecycle Collaboration (OSLC).
• Required definition management and managed capabilities enabling.
• Rational DOORS Web Access for local on the test field presence.
• On-sites established reporting system.
• Approved linking requirements to test plans
• Engineering Requirements Management DOORS traces requirements thereby eliminates manually processes and spreadsheets, for improved productivity.
• Returns the investment efficiently.

Incentivized

• A clean view of test case steps, expected results and the ability to record a result for each step quickly on one page per test set. This really helps testers work through executing manual test cases.
• Hierarchical structure of releases and builds, requirements, and test cases.
• Can quickly build test sets and/or test runs per build/release.
• Simple identification of each test case, requirement, test run, build, release, etc.

• I feel like it is too heavy sometimes and updating is not very straight forward. For example, if I want to change an incident ticket (IN) to a service request (SR) and add some comment for the change, I have to first change the IN to SR, then click refresh which takes a few seconds, then add a comment. If I forget the refresh step, my comment will be discarded without warning like my ticket is not in the latest status. This also happens when somebody else changes the ticket during my edit as I can not lock the ticket exclusively.

Incentivized

• Training can be difficult to find at times.
• Basic reporting can become very verbose unless you set lots of filters and parameters.
• The ability to customize some of the verbiage in the application would help bridge the gap between translating what SpiraTest's testing terminology is and the company culture uses for testing terminology.

Incentivized

At the moment we are required by contract to continue to use the IBM DOORS software for our current client. Given that it can be expensive, if we were to use it after our current client's needs were met, we would have to secure other projects in order to justify the continued use of the software.

Incentivized

The UI is terrible and not intuitive. Users need training in order to complete tasks. Much like SAP, it's not the clearest tool. The tracing feature is especially complicated because you must write the scripts yourself. There is a learning curve. Also, even the setup, installation, and logging in each time takes a considerable amount of time.

Incentivized

It does a basic job and has the potential to complete some robust reporting tasks, however, it really is a clunky piece of software with a terrible user interface that makes using it routinely quite unpleasant. Many of our legacy and maintenance projects still use DOORS but our department and company use many alternatives and are looking for better tools.

Incentivized

As promised during product selection, SpiraPlan support has always been quick and helpful. Replies almost always come back in hours (and often in an hour or two). And SpiraPlan's online tech support maintains all support conversations online so no need to look through emails to try to recall repllies.

Incentivized

No problems

Incentivized

It was easier to do all the change management-related activities, even configurations were handled very effectively. New process definitions and initiatives made it easier for better project deliverables. Effective resource allocations and better reporting and defect management. The overall cost of the tool is great too and well within budget.

Incentivized

Incentivized

• It's part of CLM suite so it can be used to manage the whole lifecycle with tight integration with development module (Rational Team Concert) and quality module (Rational Quality Manager).
• Comprehensive reports and dashboards provide better visibility.
• License cost is on higher side.

Incentivized

• SpiraTest can be improved in terms of its dashboard and reporting. This will be really helpful for the management as well.

Incentivized