CD Demands Continuous Testing: Why We Built a Testing Platform Layer on ECS Usin...
summary
JPMorgan builds a testing platform layer on ECS that runs functional suites inside a controlled ECS task with kitchen-sync image, removing manual secret juggling and automatic evidence upload to the firm’s testsite/evidence store. Spinnaker triggers the stage which calls back to a managed runtime that supports Karate, Cucumber, Cypress, pytest, Playwright and uses on-behalf authentication for internal-IDP protected apps. It reduces user provisioning (no EKS clusters or secret rotation), increases adoption, and trades off slower dynamic-image starts and limited builder-node flexibility.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:24Legacy testing with Jenkins
- 2:29Integrating testing in SPER
- 3:12Manual setup and security issues
- 4:37Testing platform on ECS
- 5:40Tests on ECS and credentials
- 7:04Supported frameworks and feedback
- 8:07Trade-offs of ECS testing
- 9:12ECS versus EKS Fargate
- 9:34Future plans
related talks
23mBeyond unit tests: Contributing high level tests for Amazon ECS
31mLet Devs Be Devs: Abstracting Compliance + Reliability to Accelerate JPMCs Cloud Deployments
33mHow Our Continuous Delivery Platform Is Enabling the Public Cloud Migration Journey at JPMorgan Chase & Co.
25mTesting in production: Ideas, experiences, limits, roadblocks
26mOn-demand Test Infrastructure on ECS as code
31mContinuous Software Delivery Using Spinnaker and Jenkins in Cloud
28mAre You Covered? Falling in Love With E2E Testing
32mBuilding Continuous Integration and Feedback