Skip to main content

Test Efficiency

What is Test Execution Efficiency?
It is generally very difficult to measure the efficiency of the testing process or the testing team for a project. Test Efficiency helps to calculate the efficiency of testing i.e. how many defects were leaked to the customer as compared to number of defects reported by the testing team. Generally almost 10-15 % of defects will be leaked and is considered acceptable. In the recent years, Companies have stared spending huge amount of money for developing quality. Due to this defect leakage percentage has come down to less than 10%.

How to Measure?
The Excel Sheet Attached helps us to calculate the efficiency of a testing process based on the number of defects reported by Customer and to the number of defects identified by the Testing Team.

Steps


1) Provide Ranking to each severity.
In the excel sheet the severity rankings have been assigned as

a) Critical--4
b) Serious – 3
c) Moderate –2
d) Minor –1


2) Collect the list of defects reported by the Testing and Customer based on Severity.
For example:
The customer has Reported 1 Critical, 1 Serious, 2 Moderate and 5 Minor Defects. The Testing Team should have identified these defects. The defects that were not *******ble in a test environment but only in a live production environment should not be considered.

The Testing Team has Reported 10 Critical, 5 Serious, 10 Moderate and 10 Minor Defects.

The Test Efficiency is calculated as follows: (T/T+C) * 100
T=4*10+5*3+10*2+10*1=85
C= 1*4+1*3+2*2+5*1=16
So Test Efficiency is (85/85+16) * 100=84.16%

Suppose if the Customer had not identified any defects in above example then the Test Efficiency will be 100%.

Consider a small project in which the testing team and customer did not find any defects (Assume you had a good programmer who did unit testing properly) then also the Test Efficiency will be 100%.If the Testing Team Failed to find any Defects and the Customer were finding them then the efficiency of the testing will be 0%. The formula used required fine-tuning in this case

Comments

Popular posts from this blog

Test Automation Experience

  ๐Ÿš€ Super thrilled to share my incredible test automation journey in the healthcare domain! ๐Ÿฅ๐ŸŒŸ From pioneering success to finding the perfect balance, it has been an exhilarating ride that shaped my understanding of test automation. ๐Ÿ’ป๐Ÿงช During the mid-2000s, our forward-thinking healthcare company established a dedicated automation group armed with powerful tools like Windrunner and QTP. With a unique blend of software test engineers and healthcare SMEs, we gained comprehensive insights into the intricacies of the healthcare domain. ๐Ÿ’ก๐Ÿ‘ฉ‍๐Ÿ’ป๐Ÿ” https://testmetry.com/test-automation-at-a-healthcare/ Our secret to success? Maintaining script stability and an impressively low false failure rate by keeping our regression testing scripts actively engaged. Efficiency soared with a vast library of reusable functions, and parallel execution capabilities revolutionized our testing environment. ๐Ÿš€๐Ÿ“ˆ๐Ÿ’ป The "rolling regression" approach tackled complexity head-on, while user-friendly

Scriptless vs Scripted Automation Frameworks

The quality engineering team has a crucial role in improving the time to market for services and product, and in ensuring customer delight. Architects have been developing new practices to automate the life cycle processes to reduce test cycle time and improve the product quality. Scriptless test automation is one such practice that is an alternative to the traditional automation, which was programming language dependent. The adoption rate of Scriptless frameworks has improved in the last couple of years but still, there prevail apprehensions around its capabilities. Difference between the Working of Scriptless Automation Testing Tools and Scripted Automation Testing Tools Scriptless automation tools use the technique of auto-generating test scripts instead of an automation engineer writing a test script manually using a programming language. The language used in the tool might be proprietary or open, depending on the tool strategy of the vendor.  The Scriptless technique is slightly