product: maestro audience: test-developer authority: normative
Naming Conventions
| Element | Convention | Example |
|---|---|---|
| YAML keys | snake_case |
low_limit, runner_type, post_execution_action |
| Package name | <ProductId>_<TestName>_v<NN> |
ESH10000121_FunctionalTest_v00 |
| Test name | Title Case, descriptive | "ESH10000121 Functional Test v00" |
| Step name | Descriptive phrase | "Measure 3V3 Rail", "Init DMM" |
| Measurement name | UPPER_SNAKE_CASE |
"VCORE", "RAIL_3V3", "DMM_SELF_TEST" |
| Variable name | snake_case |
supply_voltage, dmm_ready |
| Version (semver) | Semantic versioning | "1.0.0", "1.0.1" |
| Units | Standard abbreviations | "V", "A", "mV", "degC", "dBm", "MHz", "Ω" |
Package versioning strategy
Version IS encoded in the package name (_v00, _v01, …) to allow two generations
to coexist in the catalog simultaneously. The version semver field tracks patch
revisions within a named generation (limit corrections, bug fixes).
ESH10000121_FunctionalTest_v00 version: 1.0.2 ← Released (running in production)
ESH10000121_FunctionalTest_v01 version: 1.0.0 ← Evaluation (being validated)
Promotion workflow:
- Set
_v01lifecycle →Released - Set
_v00lifecycle →Obsolete
When to bump the version
A version bump IS required before every deployment. Deploying the same version twice may cause unexpected behaviour from the registry.
| Change type | Bump | Example |
|---|---|---|
| Limit correction, bug fix | Patch | 1.0.0 → 1.0.1 |
| New test steps or measurements | Minor | 1.0.0 → 1.1.0 |
| Breaking change to outputs or parameters | Minor | 1.0.0 → 1.1.0 |