Pluggable Test Infrastructures
summary
Groupon builds a runnable system where a single Gherkin behavior drives multiple implementations so one test, multiple implementations actually exercises web (Selenium/WebDriver), iPhone simulator, and API (curl) flows. They load step-definition folders by profile at runtime to avoid thousands of ifs and keep tests fast by running API checks first — API-first fast fail. The team runs ~1,000 functional tests alongside 17,000 unit tests and uses this as a post-deploy smoke-suite — load profiles at runtime.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:48Pliable test infrastructures
- 3:56Monolith to microservices
- 6:28Why pluggable test infrastructures solve real problems
- 8:15Behavior as test truth
- 11:26Avoiding test conditionals
- 13:54Cucumber profiles for flexibility
- 16:03Rake fastest-first tests
- 19:23When to use pluggable tests
- 21:30Consulting project case study
- 23:59Q&A
related talks
01h 08mGrails Plugin Testing Strategies
18mThe GPT-ification of Mobile App Testing
44mGenerative Integration Tests
01h 26mGroovy Mobile Automation
26mTesting the Tricky Stuff
21mEveryone Can Easily Write Tests
36mIt's not your test framework, it's you
33mIntentional and Unintentional Compromises in Test Automation
