| title | TRAILHEAD overview |
|---|
TRAILHEAD is the AzureLocal live-cluster validation framework. Where MAPROOM runs offline against synthetic fixture data, TRAILHEAD runs against real hardware — real cluster state, real network conditions, real hardware quirks.
| Scenario | Use |
|---|---|
| Test module logic offline, no cluster needed | MAPROOM |
| Validate behavior against real cluster state | TRAILHEAD |
| Regression testing in CI (offline, fast) | MAPROOM |
| Validate a release is safe to ship to customers | TRAILHEAD |
Both are routinely used together: MAPROOM gates CI, TRAILHEAD gates a release.
A TRAILHEAD cycle is one structured run of a tool against a real cluster. Each cycle:
- Has a named scenario (e.g.,
pre-release,post-upgrade,regression) - Produces evidence — timestamped logs, command output, screenshots
- Is compared against prior cycles to detect regressions
- Results in a GitHub Issue that records pass/fail/notes
Cycles are repeatable. Running the same scenario against the same cluster twice should produce the same evidence unless the cluster or tool changed.
platform/testing/trailhead/
├── scripts/
│ ├── TrailheadLog-Helpers.ps1 — Write-TH*, Close-THRun helpers
│ └── Start-TrailheadRun.ps1 — parameterized run initializer
Consumer repos keep their own scenario scripts in tests/trailhead/scripts/ and dot-source
the platform helpers.
TRAILHEAD touches live clusters. Read the safety checklist before every cycle — especially the pre-run isolation checklist.