/LoadTestStressTestScenario
Design a load test for a system stress-test scenario — e.g. a system that must survive a 10x traffic spike.
Your AI Command Vault
Summoning the AI overlords…
PerformanceTesting
24 commands
Design a load test for a system stress-test scenario — e.g. a system that must survive a 10x traffic spike.
Design fuzz testing for a performance regression — e.g. an api that got noticeably slower after the last release.
Design a load test for a data corruption issue — e.g. reports of order totals being saved incorrectly.
Design fuzz testing for a high-traffic api endpoint — e.g. an endpoint expecting 5000 requests per second on launch day.
Design a load test for a bug reported in production — e.g. a bug where some users can't complete checkout.
Design fuzz testing for a backlog of beta tester feedback — e.g. 40 unsorted feedback notes from a closed beta.
Design a load test for a vaguely described user-reported issue — e.g. a support ticket saying 'the app just doesn't work'.
Design fuzz testing for a bug appearing only on some devices — e.g. a layout bug appearing only on older android devices.
Design a load test for a newly released feature — e.g. a new checkout discount feature going live tomorrow.
Design fuzz testing for an intermittent test failure — e.g. a test that fails roughly one run in twenty.
Design fuzz testing for a reported security vulnerability — e.g. a report of an exposed admin endpoint.
Design a load test for a performance regression — e.g. an api that got noticeably slower after the last release.
Design fuzz testing for a user-facing input form — e.g. a form accepting arbitrary text and file uploads.
Design a load test for a high-traffic api endpoint — e.g. an endpoint expecting 5000 requests per second on launch day.
Design fuzz testing for a system stress-test scenario — e.g. a system that must survive a 10x traffic spike.
Design a load test for a backlog of beta tester feedback — e.g. 40 unsorted feedback notes from a closed beta.
Design fuzz testing for a data corruption issue — e.g. reports of order totals being saved incorrectly.
Design a load test for a bug appearing only on some devices — e.g. a layout bug appearing only on older android devices.
Design fuzz testing for a bug reported in production — e.g. a bug where some users can't complete checkout.
Design a load test for an intermittent test failure — e.g. a test that fails roughly one run in twenty.
Design fuzz testing for a vaguely described user-reported issue — e.g. a support ticket saying 'the app just doesn't work'.
Design a load test for a reported security vulnerability — e.g. a report of an exposed admin endpoint.
Design fuzz testing for a newly released feature — e.g. a new checkout discount feature going live tomorrow.
Design a load test for a user-facing input form — e.g. a form accepting arbitrary text and file uploads.