Discover published sets by community

Measures the number of defects per unit size of the software (e.g., per KLOC - thousand lines of code) and is used to assess the quality of a software product.

Measures the percentage of identified defects vs the total number of defects, to evaluate how effectively tests can discover defects.

Assesses the proportion of the software that is exercised by the tests and is used to ensure that most paths are tested.

Quantifies the average time interval between inherent failures of a system during operation, used to measure reliability.

Indicates the average time required to repair a failed component or system, used as a measure of maintainability.

Measures how quickly a team can assess and prioritize bugs, reflecting on the responsiveness of the quality assurance process.

Measures customer satisfaction with a product or service, typically through surveys, and is a direct reflection of quality perception.

Calculates the ratio of requirement changes to the total number of initial requirements, indicating the stability of project requirements.

Tracks the number of defects that were not caught during testing but were found after release, used to assess the effectiveness of the QA process.

Measures the speed at which test cases are executed, not necessarily related to the effectiveness but to the efficiency of testing.

Measures the amount of code changes over time, which can help in understanding the stability of a codebase and the pace of development.

Reflects the average time taken to fix a defect after it's reported, an indicator of the team's responsiveness and process efficiency.

Expresses the total time from when work begins to when it is delivered, used to measure the efficiency of the development process.

Counts the number of defects discovered by users after the product has been released, highlighting the effectiveness of the prior testing.

Measures how often the software build fails and requires fixing, indicating the robustness of the code integration process.

Tracks the remaining amount of work versus time until a release, helping to estimate if the team will complete their work in the intended timeframe.

Indicates the percentage of automated tests that pass during the development cycle, used to evaluate the stability of the codebase.

Counts the number of deployment attempts that have resulted in failures, reflecting the effectiveness of deployment strategies.

Measures the extent to which tests are automated, highlighting the efficiency of the QA process and potential for human error reduction.