$ recombobulate _
home / tips / generate-a-load-testing-script-from-your-api-routes
85

Generate a Load Testing Script from Your API Routes

recombobulate @recombobulate · Mar 25, 2026 · Workflows
generate-a-load-testing-script-from-your-api-routes

Load testing is something most teams intend to do but never get around to — because writing k6 or Artillery scripts from scratch is tedious. Claude can generate a full script from your API routes in under a minute.

Read my route file at routes/api.php and write a k6 load test 
script that exercises the 5 most critical endpoints. Use 50 
virtual users, ramp up over 30 seconds, and add realistic 
think time between requests. Include threshold assertions for 
p95 response time under 500ms.

Claude will produce a complete, runnable script:

// k6 load test — generated from your routes
import http from 'k6/http'
import { sleep, check } from 'k6'

export const options = {
  stages: [
    { duration: '30s', target: 50 },
    { duration: '1m', target: 50 },
    { duration: '10s', target: 0 },
  ],
  thresholds: { http_req_duration: ['p(95)<500'] },
}

export default function () {
  const res = http.get('http://localhost/api/products')
  check(res, { 'status 200': r => r.status === 200 })
  sleep(Math.random() * 2 + 1)
}

If you prefer Artillery, just say so — Claude adjusts the output to whichever tool you use. You can also ask it to add authentication headers, POST request payloads, or scenario weights based on your real traffic distribution.

A load test written in five minutes is infinitely more valuable than a perfect one that never gets written.

~/recombobulate $ tip --comments --count=0

Log in to leave a comment.

~/recombobulate $ tip --related --limit=3
0
Run Claude Code in GitHub Actions to Automatically Review Every Pull Request

Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.

recombobulate @recombobulate · 1 month ago
0
Ask Claude to Build a Deployment Checklist from Your Actual Infrastructure

Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.

recombobulate @recombobulate · 1 month ago
0
Ask Claude to Generate a README from Your Actual Codebase — Not a Template

Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.

recombobulate @recombobulate · 1 month ago