SlashAI

Testing & QA / PerformanceTesting

Load Test ProductionBug

/LoadTestProductionBug
Testing & QAPerformanceTesting🟢 Beginnercoding

Try it in

When to reach for this

Deciding what to test and proving it works.

  • Test plans and the cases that actually catch regressions
  • Writing the tests, mocks and fixtures to go with them
  • Reproducing and narrowing a flaky or failing test
Area
PerformanceTesting
Effort
No blanks to fill
Difficulty
medium
Niche
24 commands here

Fresh and trending

Ordered by the catalogue's own addedAt and popularity fields — not by live traffic, which SlashAI never sees. Some addedAt values in the source data sit in the future, so treat “newest” as newest-in-catalogue rather than as a verified publication date.

/LocalizeMapViewLocalize MapViewNewest/LocalizeCameraFeatureLocalize CameraFeatureNewest/LocalizeSettingsScreenLocalize SettingsScreenNewest/LocalizeOfflineModeLocalize OfflineModeNewest/LocalizeDeepLinkingLocalize DeepLinkingNewest/StoryboardStoryboard VideoTop

Hashtags

#bug#production#triage#performancetesting#loadtest#coding#testing-and-qa#slashai
Post it:

What it does

Design a load test for a bug reported in production — e.g. a bug where some users can't complete checkout.

How to use

Share your expected peak traffic and current capacity. Bring a bug reported in production — for example a bug where some users can't complete checkout. You get back a load-test plan with target rps and success thresholds.

Example

/LoadTestProductionBug
Input: a bug where some users can't complete checkout
Ask: Share your expected peak traffic and current capacity.
Return: a load-test plan with target rps and success thresholds

Run it in

Paste the command, then attach the file or text on the same message - it handles mixed input well.

Free tier
bugproductiontriageperformancetestingloadtestcoding

How did this land?

Only you see this — stored on this device

Paste this command into your AI tool, then come back and say how it went. Your answer stays in this browser — SlashAI has no server and no account, so there is nothing to send it to and nobody who would read it.

You might also like

Testing & QA

/FuzzProductionBug

Design fuzz testing for a bug reported in production — e.g. a bug where some users can't complete checkout.

Testing & QA

/LoadTestDataCorruptionIssue

Design a load test for a data corruption issue — e.g. reports of order totals being saved incorrectly.

Testing & QA

/LoadTestUserReportedIssue

Design a load test for a vaguely described user-reported issue — e.g. a support ticket saying 'the app just doesn't work'.

Testing & QA

/LoadTestBetaFeedbackBacklog

Design a load test for a backlog of beta tester feedback — e.g. 40 unsorted feedback notes from a closed beta.

Something wrong? Report it