written 8.7 years ago by | • modified 8.7 years ago |
This question appears in Mumbai University > Software Testing & Quality Assurance Subject
Marks: 5M
Year: Dec 2013
written 8.7 years ago by | • modified 8.7 years ago |
This question appears in Mumbai University > Software Testing & Quality Assurance Subject
Marks: 5M
Year: Dec 2013
written 8.7 years ago by |
Metrics for monitoring test execution:
1.Test Case Escapes (TCE) :
The test engineers may find the need to design new test cases during the testing, called test case escapes, as testing continues.
The number of test case escapes is monitored as it rises.
A significant increase in the number of test case escapes implies the deficiencies in the test design process, and this may adversely affect the project schedule.
2. Planned versus Actual Execution (PAE) Rate:
The actual number of test cases executed every week is compared with the planned number of test cases.
This metric is useful in representing the productivity of the test team in executing test cases.
If the actual rate of execution falls far short of the planned rate, managers may have to take preventive measures so that the time required for system testing does not adversely affect the project schedule.
3. Execution Status of Test (EST) Cases:
It is useful to periodically monitor the number of test cases lying in different states – failed, passed, blocked, invalid and untested – after their execution.
It is also useful to further subdivide those numbers by testing categories, such as basic, functionality and robustness.