LOAD TESTING IN CI

Know it is slowerbefore it ships.

Verity writes one load-test script from your API spec and runs it with deterministic profiles: a 30-second smoke check on every pull request, and the profile you choose on merge — load, stress, spike, soak or breakpoint. p50, p95, p99 and error rate are tracked per run, and optional Core Web Vitals cover page-load speed.

What it checks

Latency regressions

A pull request that makes a key endpoint slower shows up in its smoke check, not in production.

Capacity

Load at your real peak, stress past it, or ramp until it breaks to find the ceiling.

Spikes and leaks

Sudden flash crowds and long soak runs that expose memory or connection leaks.

Page-load speed

Core Web Vitals for a page URL: performance score, LCP, CLS, TBT and FCP.

How it works

01
Add your OpenAPI spec
The AI writes only the requests; load shapes and thresholds are fixed, valid code.
02
Choose a merge profile
Set peak concurrency and duration in CI Setup.
03
Watch the trend
Each run's percentiles and error rate land on the Performance page.

tests/verity/perf/verity.k6.jsEXAMPLE

// One script, every profile:  PROFILE=smoke | load | stress | spike | soak | breakpoint
export function scenario() {
  const list = http.get(`${BASE_URL}/api/products`);
  check(list, { "list 200": (r) => r.status === 200 });
  const item = http.get(`${BASE_URL}/api/products/1`);
  check(item, { "item 200": (r) => r.status === 200 });
  sleep(1);
}

Why teams choose Verity

Honest tiers

The PR check is always labelled a smoke check — never passed off as a full load test.

Runs on your runners

No per-virtual-user pricing; your CI provides the load generator.

Configurable without regeneration

Concurrency and duration are knobs, so you tune load without new code.

One place for every test type

UI, API, visual, AI-agent, load and security results share one run history and one verdict per release. Every plan includes all six.

Frequently asked questions

Can I run load tests in GitHub Actions?

Yes. The Verity action installs the load engine on the runner and runs the profile for that tier. One runner typically drives a few hundred requests per second.

What is the difference between load, stress, spike and soak tests?

Load holds your normal peak; stress climbs past it to find where it degrades; spike jumps to ten times the load suddenly; soak holds steady for an hour to expose leaks; breakpoint ramps until something fails.

Does it measure front-end performance?

Optionally. Add a page URL and each run also records Core Web Vitals.

AI API testingGenerate API tests with AI from your OpenAPI spec: request chains, auth and response checks as Playwright code, plus automatic contract checks across every operation.Security testing in CIScan your running app and your code on every pull request: a passive dynamic scan on PRs, a time-boxed active scan on merge, and static analysis of changed files.Visual regression testingCatch unintended UI changes with visual regression tests written by AI.

Try it on your own app.

Free plan, no credit card: 15 AI-written tests a month and unlimited runs in your CI.