Autotest Coverage Visualization
summary
A CI pipeline generates a tiny Swagger file per API test, computes a swagger diff against the service spec, and reports which endpoints, parameters and status codes are exercised (finding for one project 349 endpoints with ~10% fully covered and 49% untested). Web tests record element/page/action hits, render UI hotspots, and link failing locators to Allure results and Selenoid video replays via an Allure plugin. The implementation uses rest-assured, Selenium (with Puppeteer support), Atlas and Selenoid, runs automatically, and is intended to improve test focus.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:28Autotest coverage misunderstanding
- 6:26Measuring test coverage
- 13:47Code coverage visualization
- 15:12API test coverage with Swagger
- 22:49Web test coverage via UI graph
- 31:41Summary
related talks
13mHelping developers with continuous testing
44mAPI Testing following the Test Pyramid
25mRethinking Software Quality: Why API Testing Needs to Change
40mAmplifying Test Automation using REST Assured
30mMeasuring Coverage and why Cypress Cloud UI Coverage is the Holy Grail
40mSaying goodbye to full stack tests with task analysis
27mQuest for Adequate Autotest Coverage
26mAutomate Your API Testing in CI/CD Pipelines
