Your team can set overall quality objectives and manage
both entry and exit criteria. These objectives are defined at the
project level and implemented in individual test plans, where you
can track whether or not each objective has been met.
About this task
Quality objectives often track things like the number
of open defects and the number of blocked or failed execution records.
Any quality objectives involving defects now take into account those
defects that are managed in OSLC-linked Change and Configuration Management
(CCM) providers such as Rational® Team Concert and Rational ClearQuest®.
Note: To
prevent inaccuracies in the evaluation of quality objectives when
using
Rational ClearQuest as
your defect provider:
- Verify that the Rational ClearQuest server
is correctly configured for Collaborative Lifecycle Management integrations
- Verify that the State Predicates correctly define the "Closed"
status.
For details, see technote 21433074.
Here is an
example of how a test team can use quality objectives: