Rational ClearQuest

This tool in other languages: de-DE

Description

IBM Rational ClearQuest offers comprehensive software change management.
It provides change tracking, process automation, reporting and lifecycle traceability for better visibility and control of the software development lifecycle.

Categories

Defect- and Change Management, General

Rating

1 2 3 4 5
Rational ClearQuest
IBM Deutschland GmbH https://www.testtoolreview.de/images/Logo_Hersteller_IBM.png halloibm@de.ibm.com +49 800 225 5426 +49 7032 15 3777
IBM-Allee 1 71139 Ehningen GERMANY
5.00 von 5 based on 1 ratings

You have to be logged in to execute this action.

Cancel

Manufacturer

IBM Deutschland GmbH

IBM-Allee 1

71139 Ehningen

GERMANY

+49 800 225 5426

http://www.ibm.com/us/en/

Criteria:

client OS

installation

license model

localisation

provider service

test level

Comments

To write a comment, you need to be logged in.

05.08.2013 by Özgür

A very powerful and helpful tool, adaptable to your own change management process.
Filters which can be freely configured across all data fields make it possible to handle (x-) thousands of defect reports.
You can define them in a very intuitive way without the need for a tutorial.
It’s also no problem to bind on several databases or to maintain several software projects within each database or several software versions within each project in a parallel and secure way.

The only downers are:
- The window for the textual defect description is often too small as there are a lot of data fields shown.
- To create printable reports and defect charts fitting your needs a short introduction is needed.

Yet, you won’t use these features so often or set them up only once.
You can make filters, reports and charts also directly available for other users via database (public/private) or exchange them via import export function.

Although there is a huge amount of ascertainable data (must have input/ nice to have input) it would be great to be able to set a structure to the actual defect description (continuous text), too. This would constrain an at most consistent defect description and minimize callbacks from developers to testers.
At least you can configure a template for the defect text.