Journey Lanes

Cases

Ordering slows to a crawl when everyone orders at once

Fine for one employee. Too slow when a whole company orders at the start of the month.

  • Employee

Why ordinary tests miss it

Every test calls the order endpoint once. A slow query or a missing index only shows with many requests in flight, and that happens on the busiest day.

Set it up

Describe the journey

An employee logs in. The employee sees the products and orders a product. The employee sees their orders.

The flow Journey Lanes draws from the sentence above Employee: Log in via Keycloak, then Products (GET /api/products), then Order product (POST /api/orders), then Orders (GET /api/orders). EmployeeROLE_EMPLOYEE Mock backendCollections Screen Products GET /api/products Action Order product POST /api/orders Screen Orders GET /api/orders Data Product Mock collection Data Order Mock collection
Drawn by Journey Lanes from the sentence above, against the sample portal API.

  1. Describe the journey in one sentence. The flow signs the employee in, lists the products and orders one.

  2. Open “Load test” in the top bar and pick the order step. The steps before it run once, to sign in and pick a product.

  3. Choose the number of requests and how many run at once, and set your limits for the error rate and the p95 response time.

  4. Run it on a live environment whose domain you verified. The console shows throughput and p95 while it runs.

The moment it’s caught

Load test on Acceptance: Order a product, 1,000 requests, 50 at once
  1. ✓ ErrorsPOST /api/orders 0.4%, limit 1%
  2. ✗ p95POST /api/orders 2,840 ms, limit 800 ms
  3. ✓ AfterwardsGET /api/orders Count checked: all 1,000 orders are there
An example of what you see, in Journey Lanes’ own words. The numbers and names are made up.

You see it on a test environment, with the step that is slow, before the first of the month does it for you.

What you use

Next case: Nobody can log in after the login page got a new look

Catch this one in your own product

Connect a repository, describe the journey, and run it against the mock in a few minutes.

Log in See how it works