Using Test Automation for Continuous Integration, Delivery and Quality
summary
Describes how test automation plugs into build automation and environments so CI/CD actually blocks bad code: Jenkins TeamCity Bamboo TFS drive standardized builds, environments are zero-touch deployment jobs, and promotion happens automatically when criteria pass. Unit tests run fast, with an example of seven tests taking five minutes to write and one minute to execute (manual two minutes) showing payback within five runs. Integration UI performance and security tests run later in CI/CD on staging that mirrors production.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:24Test Automation
- 0:47Manual Testing
- 1:49Example
- 3:49Fails
- 5:10DevOps Process
- 5:57DevOps Promotion
- 6:49Unit Tests
- 8:35Quality Assurance
- 9:25Security Testing
- 10:20Build Tools
- 12:26Automation
- 13:37Quality
- 22:24Staging
- 23:24Continuous Delivery
- 24:10Questions
- 28:29When to use integration tests
related talks
01h 00mAutomation Engineer’s Way to Continuous Integration
32mBuilding Confidence Together: Continuous Integration & Testing
24mCI/CD Best Practices to Deliver Software Faster
35mMassively Continuous Integration: From 3 days to 30 minutes
19mBusiness Impact Delivery Using Test Automation
01h 15mThe Practices That Make Continuous Integration
24mOrchestrating automation tests for Continuous testing
42mTesting in a Continuous Delivery World