Test Coverage for Network Configurations
summary
NetCov identifies which router configuration lines a test suite actually exercises by tracing data-plane facts back to contributing config lines using an information flow graph and an on-demand provenance algorithm. It takes configs, routing tables and test traces (works with Badfish) and reports per-line coverage. Applied to Internet2, it finds only 26% coverage of relevant lines; adding three targeted tests increases covered lines by 17 percentage points, showing the tool effectively exposes and fixes testing gaps.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:26Why did network tests miss the bug?
- 1:46A simple network.
- 2:57Test this simple network
- 4:36What about complete testing of this?
- 5:12Solution: Guide users with configuration coverage
- 5:45Defining configuration coverage
- 7:56Key problem
- 8:46Insight
- 10:27Approach overview
- 12:38Existing test suite
- 15:16Conclusion
related talks
12mMetha: Network Verifiers Need To Be Correct Too!
21mFinding Network Misconfigurations by Automatic Template Inference
36mNetwork Machinery: A United-Front for Network Troubleshooting with CRDs
40mA Test Harness to Verify Traffic Router Performance
27mNetComplete: Practical Network-Wide Configuration Synthesis with Autocompletion
03mTest coverage
25mNetDevOps: Applying lessons of DevOps to networking
16mContributing to Kubernetes Conformance Coverage