product: maestro audience: test-developer authority: normative
SDK Reference — Index
| Question | File |
|---|---|
| Why one YAML step = one method/function? | design-principle.md |
| .NET method signatures, return types, parameters, logging | dotnet-sdk.md |
| Python function signatures, return types, measurements in YAML | python-sdk.md |
| Vendoring pip wheels for air-gapped production stations | python-dependencies.md |
| Local debugging with MSTest | mstest-debugging.md |
| Local debugging with a Python runner script | python-debugging.md |
Critical difference: Python DOES NOT support MeasurementPointBase
The Python runner DOES NOT support returning MeasurementPointBase objects.
Measurements and their limits MUST always be defined in the YAML measurement: or
measurements: block for Python steps.
In .NET, you MAY choose between YAML-defined limits and code-defined limits
(MeasurementPointBase). In Python, only YAML-defined limits are available.
Runner dispatch reference
| YAML fields | Dispatched to |
|---|---|
type: delay |
Built-in delay runner |
type: mock |
Built-in mock runner |
type: prompt / type: manual |
Built-in operator prompt runner |
type: sequence + sequence: "path" |
Nested YAML execution |
runner: dotnet + runner_type: net10.0 |
.NET gRPC runner |
runner: python + runner_type: python3.11 |
Python gRPC runner |