Download as PDF, PPTX
Uploaded bySmartBear
Test Smarter: Efficient Coverage Metrics That Won't Leave You Exposed
The document discusses the importance of coverage metrics in software testing, highlighting three main types: statement coverage, branch coverage, and path coverage. It emphasizes that high coverage percentages do not guarantee effective testing and warns against focusing solely on metrics without considering overall quality. The document also suggests strategies for achieving meaningful coverage by identifying early issues and testing various parts of the application.
More Related Content
Similar to Test Smarter: Efficient Coverage Metrics That Won't Leave You Exposed
Test Smarter: Efficient Coverage Metrics That Won't Leave You Exposed
- 1. Efficient Coverage MetricsThat Won’t Leave You Exposed
- 2. Who are we? 2 NikhilKaul Rick Almeida
- 3. On our platetoday 3 • Why use coverage metrics? • Different types of coverage metrics • Where these coverage metrics may go wrong • Coverage goals and where to start?
- 4. Coverage metrics cancome in handy in a variety of ways 4 1 Areas not covered by tests Indirect measure of quality 2 3 Identifying redundant test cases
- 5. Variety of coveragemetrics are available to achieve these results 5 Coverage Metrics Statement Branch Path
- 6. Let’s start withStatement Coverage 6 No of statements run Statement Coverage = -------------------------------- * 100 Total number of statements Statement Coverage Branch Coverage Path Coverage
- 7. Source Code 100% statementcoverage doesn’t mean effective testing 7 Statement Coverage Branch Coverage Path Coverage TestCase Statement Coverage 100%
- 8. Statement coverage comeswith other challenges 8 Terminal condition Do-While Switch Statements Statement Coverage Branch Coverage Path Coverage
- 9. Branch Coverage 9 Statement Coverage Branch Coverage Path Coverage • Eachbranch (if statements, loops) has been executed at least once • Every “if statement” has two distict branches • No branches lead to abnormal behavior
- 10. Source Code To cover100% of branches, we need one more test case 10 Statement Coverage Branch Coverage Path Coverage TestCase Statement Coverage 100% Branch Coverage 50%
- 11. However, branch coveragecan ignore short circuit operators 11 Statement Coverage Branch Coverage Path Coverage No call to function1 Test Case 1: Condition 1 = true Condition 2 = true Test Case 2: Condition 1 = false Condition 2 = false
- 12. Next comes pathcoverage 12 Statement Coverage Branch Coverage Path Coverage T F T F T F 1 2 3 4
- 13. Source Code 50% pathcoverage with TT and FF 13 Statement Coverage Branch Coverage Path Coverage TestCases Branch Coverage 100% Path Coverage 50%
- 14. You are missing2 paths 14 Statement Coverage Branch Coverage Path Coverage T F T F T F 1 2 3 4
- 15. Path coverage isnot always optimal 15 Statement Coverage Branch Coverage Path Coverage Exponential increase in branches with added conditionals End up creating extra test cases
- 16. Where to startwith coverage 16 Find evident issues early and often Don’t focus on hitting high coverage metrics for individual parts of you app Test some of each part of you application
- 17. What to doonce you get started? 17 Call at least one method in every file or class Attain 80% to 90% branch coverage in each method Invoke 8 out of 10 methods, ignoring branch coverage
- 18. TestComplete for automatedfunctional testing 18
- 19. AQTime for codecoverage Optimizes code for developers & testers Supports multiple languages & frameworks Integrates with IDEs and TestComplete
- 20.
- 21.