Beyond unit tests: Contributing high level tests for Amazon ECS
summary
Two integration suites land in Cloud Driver for Kubernetes and Amazon ECS, each running as a gradle task (local runs need Docker) and taking up to ~15 minutes so PRs treat them as optional but master requires pass; tests mock AWS calls and assert details like Fargate launch type and correct target group calls. Deck gets functional UI tests written in Cypress with fixtures that stub API responses and record videos/screenshots. End-to-end work runs nightly via Jenkins (Python tooling today) and aims to execute a full ECS deployment end-to-end.
AI-written summary · about
chapters (12)
- 0:00Introduction to high-level testing
- 1:02Why write high-level tests
- 2:26When heavier tests are needed
- 3:50Test types in Spinnaker
- 5:13Integration tests for cloud driver
- 7:40Lessons from integration tests
- 9:23Functional UI tests in deck
- 14:21Lessons from functional tests
- 18:58End-to-end tests overview
- 20:21Contributing ECS end-to-end tests
- 21:45Challenges with end-to-end tests
- 22:05Key takeaways and next steps
related talks
11mCD Demands Continuous Testing: Why We Built a Testing Platform Layer on ECS Usin...
43mIntegration testing a cloud native application with JavaScript｜
28mAre You Covered? Falling in Love With E2E Testing
39mFor the love of PROD, Test your Code!
06mCloud-Native Application Testing Approaches
56mTestOps at scale
08mAdaptation of the E2E Tests for a Big Project
39mGetting Started with E2E Tests for True CI/CD