Meet the assertable Chaos Monkeys
summary
Claims that Arquillian plus the Cube and Cube Q extensions let tests control Dockerized systems, inject failures and measure resilience. Uses ShrinkWrap to deploy WARs, RestAssured for HTTP checks, Docker/Docker Compose for repeatable environments, and Toxiproxy plus Netflix-style fault injection to add latency, kill containers or fill disks. Demo runs Node and Java services in containers, runs three builds in parallel cutting ~10 minutes of sequential runs to ~3.5 minutes, and the chaos scenarios trigger circuit-open behavior. Arquillian Cube Q Toxiproxy ShrinkWrap
AI-written summary · about
chapters (25)
- 0:00Introduction and speaker intro
- 0:29Why software testing matters
- 4:04Unit tests and mocking pitfalls
- 6:52Need for high-level tests
- 7:34Challenges with high-level tests
- 8:37Introducing Arquillian testing middleware
- 10:03Arquillian demo with Java EE
- 14:42Arquillian testing principles
- 15:26Repeatable testing with Docker
- 18:38Docker basics for testing
- 20:29Arquillian Cube for Docker control
- 21:55Docker setup with Arquillian Cube
- 23:25Container-less testing with Cube
- 24:51Node.js testing demo with Docker
- 25:57Node.js test execution
- 27:01Speeding up high-level tests
- 28:27Parallel testing with Docker
- 29:52Demo of parallel test execution
- 30:56High-level tests as waste
- 31:37Introducing Chaos testing with Cube Q
- 33:47Network chaos demo setup
- 34:31Chaos testing demo execution
- 36:39Recap and key takeaways
- 39:10Arquillian ecosystem overview
- 39:54Closing and resources
related talks
46mThe Arquillian Universe: A Tour Around the Astrophysics
48mUsing Docker for Testing Legacy Code
42mUse Docker to test microservices
38mCreating chaos in containers
51mTesting for Unicorns
30mUsing Docker & Compose to Simplify Integration Testing
37mCreating chaos in containers
34mWrite tests that spark flow