Tier B post-launch verification
Checklist and follow-ups after CI Tier B is enabled in .github/workflows/e2e-test.yml. Plan / results: docs/e2e/E2E_AUTOMATION_PLAN.md (Tier B Final Validation & Success Report).
1. Functional checklist (full Tier B)
| Metric |
How to measure |
Notes |
| Job wall time |
GitHub Actions run updated_at − run_started_at |
Compare historical Tier‑A‑only runs vs Tier A+B; see E2E plan — metrics. |
| Python orchestrator |
Log line …all checks passed in X.XXs |
Isolated script time only; excludes dotnet run startup. |
| NuGet / pip cache |
Warm vs cold actions/cache hit |
Dominates variance; see Pipeline optimization. |
3. Stability (multiple consecutive runs)
4. Scalability and cost
- Parallel jobs: Tier A+B uses fixed localhost ports; do not duplicate this job on the same runner without port isolation. Cross-workflow parallelism:
unit-integration-tests.yml vs e2e-test.yml.
- Actions minutes: Two extra ASP.NET processes per PR; consider path filters or nightly Tier B if minute budgets tighten (team decision — Optimization).
- Dockerized mocks: Optional future — reduces JIT startup at the cost of image build/publish (see Team discussion hooks).
Document control
| Version |
Date |
Note |
| 1.0 |
2026-04-05 |
Initial post-launch checklist after Tier B workflow integration |
| 1.1 |
2026-04-06 |
Checklists completed; cross-refs to final validation + pipeline optimizations |