Tests & builders
Every MaxoPerf test starts with the same two decisions: what kind of test you are running, and how you want to author it. This section covers both. It describes the three test types in the console, the full catalog of executors you can bring a script for, and the scriptless builders that build a test without a script.
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, …) using the full executor catalog. You never pick the engine by hand. -
Scriptless builder: build the test 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, with the same load configuration, locations and capacity, and failure criteria. Scriptless is the fastest way to a working test when you have no script, and you can edit everything afterward. Either way, you land on the same authoring page: