> For the complete documentation index, see [llms.txt](https://magdalenaolak.gitbook.io/istqb-foundation-level/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://magdalenaolak.gitbook.io/istqb-foundation-level/5-test-management/5.3-test-monitoring-and-control/5.3.1-metrics-used-in-testing.md).

# 5.3.1 Metrics Used in Testing

Metrics can be collected during and at the end of test activities in order to assess: 

* Progress against the planned schedule and budget 
* Current quality of the test object  Adequacy of the test approach 
* Effectiveness of the test activities with respect to the objectives 

Common test metrics include: 

* Percentage of planned work done in test case preparation (or percentage of planned test cases implemented) 
* Percentage of planned work done in test environment preparation 
* Test case execution (e.g., number of test cases run/not run, test cases passed/failed, and/or test conditions passed/failed) 
* Defect information (e.g., defect density, defects found and fixed, failure rate, and confirmation test results) 
* Test coverage of requirements, user stories, acceptance criteria, risks, or code 
* Task completion, resource allocation and usage, and effort 
* Cost of testing, including the cost compared to the benefit of finding the next defect or the cost compared to the benefit of running the next test