Test automation guide: How to move away from chain tests
summary
Rabobank automates the whole test stack to stop chain tests and enable same-day releases: a log-tracking JUnit Jupiter extension asserts logs for void methods, WireMock runs stubs and proxy rules for auth and signatures, Testcontainers hazelcast smoke tests exercise the real cache image instead of an embedded hashmap, and Pactflow contract verification checks consumer/provider compatibility; Split.io runs A/B experiments. The pipeline runs these checks and reports deployable or not, enabling daily releases for several platform services.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:06Move away from chain tests
- 3:33Manual testing challenges
- 5:40Reusable testing extensions
- 12:22WireMock for service mocking
- 18:23Testcontainers for databases
- 24:33Contract testing dependencies
- 31:48A/B testing rollouts
- 33:57Summary
related talks
45mBuilding a successful test automation architecture in a microservices environment
48mModern Testing Patterns
02h 58mOverview of Testing in Our Applications
46mModern Testing Tools for Java Developers
44mAPI Testing following the Test Pyramid
57mModern Testing Tools for Java Developers
31mModern Testing Tools for Java Developers
02h 36mTesting Java Microservice
