Tests & builders
Every MaxoPerf test starts with the same two decisions: what kind of test are you running, and how do you want to author it. This section covers both — the three test types the console offers, the full catalog of executors you can bring a script for, and the scriptless builders that let you compose a test without writing one.
The three test types
Section titled “The three test types”Clicking New test in the console opens a picker with three cards. Each maps to a different test_kind and a different default load shape:
Two ways to author each type
Section titled “Two ways to author each type”Every card offers the same two actions:
-
Upload script — bring an existing scenario file. MaxoPerf detects the engine from the file itself (a
.jmx, a k6.js, a Taurus YAML, a Selenium.py, …) against the full executor catalog — you never pick the engine manually. -
Scriptless builder — compose the test directly in the console with no file at all. A point-and-click form builds the HTTP requests (for performance and functional API tests) or the browser steps (for browser tests) and MaxoPerf renders the underlying scenario for you. See Scriptless test builders.
Both paths produce the same kind of test — same load configuration, same locations and capacity, same failure criteria. Scriptless is not a lesser mode; it is the fastest way to get a working test when you don’t already have a script, and it stays fully editable afterward.