Running Tests in Continuous Integration
summary
How to run tests reliably in Continuous Integration: use containerized or templated build agents and spin short-lived agents for flaky system-state tests, store tests and tests-as-code in version control, and parameterize job templates. Collect XML test reports so CI can display per-commit histories, gate long test suites behind fast smoke stages, and run performance tests against a fixed baseline (example thresholds: 50% degradation or a 1000 ms reference) on dedicated consistent hardware.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:04Automate test runs
- 3:33Continuous Testing principles
- 5:17Tests as app code
- 6:38Test infrastructure setup
- 8:46Cleanup after tests
- 10:28Test results reporting
- 12:12CI tools vs scripts
- 15:55Test config creation
- 17:38Agent setup specifics
- 19:22Performance tests specifics
- 24:25Efficient pipeline building
- 27:16Pipeline demo
- 30:43Multi-platform testing
- 34:59Unified test pipeline benefits
- 38:22Q&A
related talks
01h 00mAutomation Engineer’s Way to Continuous Integration
24mOrchestrating automation tests for Continuous testing
26mContinuous Integration Testing
31mThe Build That Cried Broken: Building Trust in Your Continuous Integration Tests
32mBuilding Confidence Together: Continuous Integration & Testing
30mContinuous Integration; Tips & Tricks
34mUsing Test Automation for Continuous Integration, Delivery and Quality
40mThe Build That Cried Broken: Building Trust in Your Continuous Integration Tests