Scriptless test builders
Every test type in MaxoPerf has a Scriptless builder action alongside Upload script. Instead of bringing a .jmx, a k6 script, or a Selenium file, you compose the scenario directly in the console. MaxoPerf renders the underlying test from what you build — you can inspect the generated scenario at any time, and switch back to file upload later if you outgrow the builder.
There are two builders, shared across the three test types:
- The HTTP request builder powers both Performance API tests and Functional API tests — the same request model, with the load profile (continuous VUs vs. a single locked iteration) set by which card you started from.
- The Browser step builder powers Browser tests.
HTTP request builder
Section titled “HTTP request builder”Used for performance tests and functional API tests. Compose a sequence of HTTP requests, each independently configured:
tests-builders/http-request-builderWhat to show:MaxoPerf scriptless HTTP request builder showing a sequence of HTTP requests with method, URL, headers, query params, body, and assertion fields
The HTTP request builder — add requests to the sequence and configure each one without writing a script.
For each request in the sequence:
| Field | Notes |
|---|---|
| Method | GET, POST, PUT, PATCH, DELETE, HEAD, or OPTIONS |
| URL | Query parameters can be typed inline or added as separate rows |
| Headers | Literal values, or bound to a workspace secret — secret values are never re-rendered in the builder |
| Body | application/json, application/x-www-form-urlencoded, text/plain, or application/xml |
| Assertions | Status code, body-contains (one or more literal strings), and JSON path (with an optional expected value) |
The builder enforces the same abuse limits as the API: up to 50 requests per test, 50 headers and 50 query parameters per request, and a 256 KB body cap.
Browser step builder
Section titled “Browser step builder”Used for browser tests. Drag steps from a palette onto a canvas to compose one or more transactions — named groups of steps, similar to a JMeter transaction controller — inside one or more scenarios:
tests-builders/browser-step-builderWhat to show:MaxoPerf scriptless browser test builder showing a step palette on the left and a drag-and-drop step canvas with transactions on the right
The browser step builder — drag steps from the palette to compose transactions without writing Selenium or Playwright code.
The step palette is organized by category:
| Category | Example steps |
|---|---|
| Navigation | Go to URL, open/switch/close window, switch frame, maximize/resize window |
| Interaction | Click, double click, type, send keys, select an option, drag and drop, submit |
| Wait | Wait for a condition, pause for a fixed duration |
| Assertion | Assert text, assert value, assert title, assert JavaScript expression |
| Store | Store text, value, title, a literal string, or a JavaScript expression into a variable |
| Output | Take a screenshot, run arbitrary JavaScript, clear cookies, echo a string |
| Control flow | If / else, loop, for-each element, loop over a data file |
- Add a scenario and a transaction. A scenario groups the transactions that make up one flow; a browser test can have multiple scenarios.
- Drag steps onto the canvas from the palette, or use the Frequently used shortcuts once you’ve added a few.
- Configure each step — most interaction, wait, and assertion steps need a locator (how to find the element) plus a value (text to type, condition to wait for, expected text, …).
- Reorder or nest steps —
If,Loop,For each element, andLoop over dataare containers that hold their own child steps. - Preview the generated scenario before saving, and adjust scenario-level settings (browser, viewport) alongside the canvas.
You can also import a MaxoPerf Recorder session into the builder instead of building from scratch — record yourself clicking through the flow in the browser extension, then bring the captured steps in as a starting point and keep editing them in the canvas.