IBM Engineering Test Management Reviews

VF dashboard view looks okay. It allows user to add whichever widget (predefined) based on the need. It has integration with CCM and RM to achieve traceability.

Organizing the test cases is tedious. There is no mechanism to keep and maintain the test cases as hierarchy. This should be seriously addressed. As the number of test cases grows, it’ll be really difficult to maintain the test cases. The tool should be able to support and maintain the test cases in a folder-wise structure to identify the different module/phase-wise test cases.

Around three years.

No.

No.

Not applicable.

Yes. Customer requirement.

Not applicable.

I suggest to go for other tools. As the number of test cases grow, it’ll be really difficult to maintain the test cases. The tool should be able to support and maintain the test cases in a folder-wise structure to identify the different module test cases.

In the latest version, Global Configuration is the most promising feature as it allows the user to maintain different versions of the same artifact in different streams. Another feature that I consider important is integration with the automation tools.

Reporting on the QA activities as well as managing test execution cycles helped our organization to better manage the QA activities.

There are a couple of things that can be improved:

1. The user interface can be improved; it is the same interface that I have been seeing for the past so many years, whereas the other CLM modules changed significantly.
2. It does not provide inbuilt capabilities for managing the tasks and planning activities related to testing. For this purpose, you need to buy another module, i.e., IBM Rational Team Concert (RTC).

I have used this solution for seven years.

Recently, we encountered some defects related to the global categories. We opened the defects with IBM, and later on, they provided us with a fix pack.

There were no scalability issues.

Technical support is above average.

The setup was a bit complex as it requires some expertise.

Two types of licensing policies are available:

1. There is the Authorized license which is bound to the user, i.e., if the user is not using it, then others can't use it either.
2. There is floating one, which is a pool of licenses (if the user is not using it, then others can use it).

When I joined my current organization, they were already using IBM RQM.

Tweak your testing process. It is also better to align the organization in terms of how the tool works.

Integration throughout the complete product development process. Also, the integration of third-party automation test tools.

Easy collaboration between several development teams such as design, development, and testing.

• Management of artefacts
• Support of paramater needs to be easier
  

I've used it for three years.

No issues encountered.

No issues encountered.

No issues encountered.

It was easy.

It was done in-house.

Project realization has been carried out much faster. The integration of test automation tools.

Use workgroup licenses for smaller environments.

Plan the training and usage properly. Also, proper planning of the architecture and test execution artefacts needs to be dond.