The Chaos Engine
A failure injection system that randomizes bugs, delays, and broken selectors every session. Your automation adapts — or it doesn't.
Random API Failures
Endpoints randomly return 500s, 429s, and malformed JSON. Your retry logic gets a real workout.
Network Delays
Responses arrive between 200ms and 8 seconds. Hardcoded waits will break. Explicit waits won't.
Mutating Selectors
IDs, classes, and DOM structure shuffle on every page load. Only data-testid survives.
Race Conditions
Concurrent state mutations, double-submits, and stale cache reads. Real production nightmares.
02 > challenges.list
Pick a challenge.
Most people fail the first time.
Shadow DOM Checkout
Complete a purchase flow where every form field is wrapped in Shadow DOM. Standard selectors won't work.
Flaky Cart API
The cart endpoint randomly returns 500s, stale data, and delayed responses. Build retries that actually work.
Auth Rate Limiter
Login with OTP. Get rate-limited after 3 failures. Handle cooldowns, session expiry, and error states.
Dynamic Product Grid
Products load with random delays, shuffle order, and inject skeleton states. Assert the right items render.
Race Condition Checkout
Two tabs. Same cart. One coupon code. Automate the race and validate which session wins.
A11y Violation Hunt
Find 12 intentional WCAG violations: missing labels, broken focus order, low contrast, and missing ARIA.
03 > system.modules
Six modules.
All designed to break your scripts.
Chaos Mode// danger zone
Randomized IDs, dynamic delays, and Shadow DOM — the ultimate selector resilience drill.
E-Commerce Flows
Cart race conditions, price injection, coupon edge cases — a storefront that actively fights your assertions.
Practice commerceAPI Explorer
Hit real endpoints. Get auto-generated Selenium, Playwright, and Rest Assured code. Chain API calls into UI flows.
Launch explorerAuth & Sessions
OTP workflows, rate limiting after 3 failures, session expiry mid-flow. Every negative path a real app throws at you.
Test auth flowsBug Hunting
50+ planted defects across UI, API, and forms. Find them before your test suite does — or explain why it didn't.
Hunt bugsA11y Audit
12 buried WCAG violations: broken focus traps, missing ARIA, low contrast. Find them all with axe or bare hands.
Start testing04 > proof.generate
Don't just practice. Prove it — publicly.
Complete challenges, earn shareable proof, and make your GitHub README speak louder than your resume.
Chaos Survivor Badge
Survive 3 consecutive clean runs with zero flaky failures. Embed the badge in your GitHub README. When other SDETs see it, they'll ask "How do I get that?"
embeddable SVG · works in GitHub READMEs
Proof of Kill
Complete a challenge, get a branded card with your brutality stats — bugs found, time, flaky runs. One-tap share to LinkedIn with a pre-written post.
"I Dare You" Post
Complete a challenge, get a pre-built dare with your actual stats. Post your time, tag a friend — and watch them try to beat it.
"I dare any SDET to beat 4m 12s on Chaos Mode checkout. 👇"
05 > faq.list
FAQ
- Yes — that's the entire point. Write scripts that demonstrate API-chained UI tests, data-driven testing, and POM patterns against a production-grade sandbox. Push to GitHub and let the code speak.
- Yes. Use the built-in API Explorer, downloadable Postman collection, and REST gateway to chain API and UI scenarios together.
- Every session is different. Chaos Mode randomizes failures, delays, and DOM structure so your scripts can't rely on memorized patterns. Other practice sites are static — this one fights back.
- Yes. Key components use stable data-testid attributes with a consistent naming convention (ptn-* prefix). See the Test IDs Reference page for a comprehensive list organized by module.
- Absolutely not. Load testing is strictly prohibited and will result in an immediate IP ban. PassTheNote is for functional UI/API testing only. Accounts generating >5 requests/second are automatically blocked.