Mutating Test Scenarios
summary
A framework called phase tests evolves into “mutational” scenarios that actually mutate data, inject events, and reorder steps; implemented in Java with TestNG, using Faker-style data mutation and an open‑source branch demo. It runs interruptive shuffles for upgrades, non‑interruptive chaos via a Gremlins event that toggled prices to −1 (revealing cache bugs fixed by an added cache reset), and generates logical order permutations (three permutations in the demo) to find real failures across migrations and upgrades.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:52Traditional test scenarios limits
- 6:06Upgrade automation with phase testing
- 10:22Phase to mutation testing
- 12:30Data mutation in tests
- 15:52Event-based mutations
- 22:39Chaos testing with events
- 27:39Order mutations and dependencies
- 30:56Future of adaptive tests
- 33:07Q&A
related talks
41mMutation testing in practice
45mMutation Testing
48mModern Testing Patterns
37mHow to Write Better Code Using Mutation Testing
07mWho is Testing the Tests?
55mThe Absolute Beginner’s Guide To Mutation Testing
59m.NET Testing Techniques You Didn’t Know You Needed
20mUnleashing the Power of Mutation Testing: Supercharging Software Quality and Resilien...