QA Metrics - Testing Progress Metrics

Quality Progress Metrics

Start tracking before Test Execution


User Stories, Features or Requirements Coverage Progress
  • Are test cases being authored for all required stories, features or requirements? Are test cases for important features or requirements being targetted first? Are number of test cases (for stories, features or requirements) proportional to effort required for their development? Are there any features, stories or requirements being left over? Is team on target in covering all required features, stories or requirements?

Test Case Readiness Progress
  • When will all the test cases be ready to run? Will all the test cases be ready to run by the end of the iteration? How many test cases must the team still write and review? How many test cases are ready to run?

Test Automation Progress
  • How many test cases has been automated? How many test cases being automated on regular basis? Is the team on track in automating the test cases?

Start tracking during Test Execution


Test Plan Progress
  • How much testing has the team completed? Is the team likely to finish the testing on time? How many tests are left to be run? How many tests are passing, failing or blocked?

User Stories / Features / Requirements Testing Progress
  • Which user stories have a low overall count of test cases? Which user stories have a high overall count of test cases that are blocked or have never been run? Does the test coverage for each user story meet expectations? Which user stories have high rate of test failures? What is the average number of test cases that are defined per user story? Is the test team running test cases for each user story? If test cases are blocked or not being run, does the team understand the blocking issues, and is the team addressing them?

Manual Test Activity Progress
  • Is the trend of manual tests that the team is running consistently increasing? Do you identify any spikes in the test activity that you cannot account for?


Bug Progress
  • How quickly is the team resolving and closing bugs? Is the team fixing bugs quickly enough to finish on time? How many bugs is the team reporting, resolving and closing per day?

References:


Links to missing sections (automation etc),More sample graphs for displaying progress,Discuss on further analysis after verifying the regular progress

Comments

Post a Comment

Popular posts from this blog

Performance Test Run Report Template

You have gathered requirements from clients, identified key critical business scenarios, analyzed the workload distributions, found out performance goals and requirements, identified  tool for generating load, setup the test environment, designed the scripts, executed the performance run, collected the raw data, analyzed it, what next?  Send information to stakeholders? No!!  Wait!! It needs to formatted, customized for different stakeholder(s) and reported accordingly. This article suggests one of the ways to report performance run results to client especially if the performance testing activity has been outsourced to yours company.  It discusses the performance report template and importantly the reasons for including the items in the report. The performance report template contains information by data collected from client side only and doesn’t discuss / talk about data from server side like processor utilization etc. Broadly the performance report has been divided in three major
Read more

Understanding Blockchain

This notes will cover below questions... Introduction to Blockchain What is the difference between Blockchain and Bitcoin? What are some other uses of blockchain that go beyond bitcoin? History of blockchain Could you explain the blockchain process in laymen terms? If all data is available to the public. Can anyone know my bank balance (in Bitcoin)? Introduction to Blockchain The Blockchain is a decentralized and distributed public (digital) ledger where transactions are recorded and confirmed anonymously. It’s a record of events that is shared between many parties. More importantly, once information is entered, it cannot be altered without altering subsequent blocks. WTF is the blockchain? A guide for total beginners What is the difference between Blockchain and Bitcoin? The blockchain is a technology
Read more

Bugs Management in Agile Project

Agile has a refreshing approach to bugs, especially when contrasted with traditional waterfall practices. Historically, teams would postpone bugs to a stabilization phase. This stabilization phase was long and tedious, typically with high stress and long hours. Agile, on the other hand, promotes the following thought processes: Carrying bug debt is unhealthy and sometimes, even destructive. We should fix bugs, not track them. A feature isn't done until the bugs are fixed. Quality is part of the overall cost. Bugs are prioritized against new features. A bug needs to be more important than the next new feature. Notes All new features have a "bug tail." The bug tail is the diminishing number of open bugs on the new functionality. When a feature is added, bugs are introduced. Most are discovered and fixed immediately by the team as a part of feature development: some a few days later, others not until long after a story is considered &quo
Read more