Report: Test History

Description

Test history shows the progress of system testing of product requirements (functional, operational, security, safety, interface) or user acceptance testing of customer requirements (scenarios and qualities of service) over the duration of the iteration.

Healthy Example

In this example, scenarios become ready for test in a steady stream showing that work is progressing in small batches unhindered by blocking issues. Tests are then executed within a short lead time. The tests are successful showing that the scenarios have been met.

Data Series

Line	Description
Total Requirements	The total scope of requirements in the iteration.
Ready for Test	Requirements ready for test.
Test Complete	Test run successfully and requirements marked as closed.

Unhealthy Examples

In this example, blocking issues prevent scenarios from becoming ready for test. The root cause is hidden in the issue log.

In this example, lead time for tests is too long and all the functionality is not successfully tested before the end of the iteration. Possible root causes include poor quality in development or under staffing in testing.

In this example, tests are passing successfully and lead time on testing is short. Velocity on resolving scenarios, ready for test, is fast. Testing velocity is also fast.