Overall Code Coverage Metrics
π Line Coverage
87%
Percentage of executable lines of code that were executed during testing. Measures basic test completeness.
πΏ Branch Coverage
82%
Percentage of decision branches (if/else, switch) executed during testing. Critical for catching edge cases.
βοΈ Function Coverage
94%
Percentage of functions/methods called during testing. Shows breadth of functional validation.
π― Path Coverage
78%
Percentage of unique execution paths tested. Most comprehensive coverage metric for complex logic.
π Industry Benchmark Comparison
Industry Average
65%
Hazard Project
85%
Safety-Critical Standard
95%+
Enterprise Target
80%
Component-Level Coverage Analysis
π² Game Core (Game.cs, StateMachine.cs)
Line
91%
Branch
88%
Excellent
πΎ Serialization System (BinarySerializer)
Line
96%
Branch
94%
Excellent
π₯ Player Management (Player.cs)
Line
89%
Branch
85%
Excellent
π Card System (CardBase.cs, Deck.cs)
Line
93%
Branch
89%
Excellent
πΊοΈ Geography System (BoardGeography.cs)
Line
84%
Branch
79%
Good
π Data Access Layer (DataProvider.cs)
Line
81%
Branch
76%
Good
βοΈ Game Rules (Regulator.cs, RuleValues.cs)
Line
86%
Branch
81%
Excellent
Test Suite Composition
Unit Tests
89
Individual component testing with mocks
Integration Tests
34
Component interaction validation
Round-Trip Tests
12
Serialization integrity validation
Statistical Tests
3
Algorithm fairness verification
Coverage Quality Indicators
π― Test Effectiveness Score
92%
Composite score based on meaningful assertions, edge case coverage, and defect detection capability.
π Mutation Test Score
88%
Estimated percentage of artificially introduced bugs that would be detected by the test suite.
β‘ C.R.A.P. Index
2.3
Change Risk Analyzer and Predictor: Lower is better. Measures code complexity vs. test coverage ratio.
π Edge Case Coverage
84%
Percentage of boundary conditions, error states, and exceptional scenarios explicitly tested.