Skip to main content

​
PaaS Test Matrix

Last updated: 2026-02-17
Scope: si paas workflows in tools/si

​
Matrix

LevelCoverage GoalPrimary AreasCommand
UnitValidate command parsing, contracts, and pure helper logiccommand/action wiring, usage contracts, magic-variable resolution, add-on merge conflict checks`docker run —rm -v “$PWD:/work” -w /work golang:1.25 go test ./tools/si -run ‘TestPaasActionNamesMatchDispatchSwitchesTestPreparePaasComposeForDeployRejectsAddonMergeConflictsTestPreparePaasComposeForDeployRejectsUnknownMagicVariable’ -count=1`
IntegrationValidate cross-component behavior in the CLI packagedeploy/apply transport flow, rollback orchestration, blue/green cutover, add-on lifecycle, event/audit/log routing`docker run —rm -v “$PWD:/work” -w /work golang:1.25 go test ./tools/si -run ‘TestPaasDeployApplyUsesRemoteTransportTestPaasDeployBlueGreenApplyUsesComposeOnlyCutoverPolicyTestPaasAppAddonContractEnableListDisableTestPaasDeployResolvesMagicVariablesAndAddonComposeManifest’ -count=1`
E2E RegressionValidate end-to-end operational paths with realistic command sequencesupgrade/compatibility path, deploy->health->rollback, webhook/ingress/alert continuitydocker run --rm -v "$PWD:/work" -w /work golang:1.25 go test ./tools/si -run TestPaasRegressionUpgradeDeployRollbackPath -count=1
Broad SmokeCatch unintended regressions across all current PaaS testsall TestPaas* coverage in tools/sidocker run --rm -v "$PWD:/work" -w /work golang:1.25 go test ./tools/si -run TestPaas -count=1

​
Execution Policy

  1. Run Unit and Integration before every WS merge touching tools/si/paas_*.
  2. Run E2E Regression for deploy/runtime/rollback/webhook/ingress changes.
  3. Run Broad Smoke before pushing multi-ticket slices.
  4. Treat any regression as a merge blocker until fixed or explicitly waived in ticket notes.