| name | regression-tests |
| description | Run, scope, or debug telepresence regression tests under regression_test/ — the integration-level suite. Use when the user wants to run an area, suite, or single test, debug a failure, or says "/regression-tests". Runs `go test ./regression_test` scoped with -run, in the background, writing to a log file so heavy output stays out of context. |
regression-tests
Runs the telepresence regression suite from the main conversation, where this
harness's shell-env quirks are known.
Background to assume
- Tests live under
regression_test/ and need a working k8s cluster (kind /
minikube / Docker Desktop) plus images it can reach. For a local cluster set
RTEST_REGISTRY=local and LOAD the images into it rather than pushing.
regression_test/README.md is the reference: fixture-engine rules, the
RTEST_* table, catalogs, labels, coverage. Read it before debugging a
fixture problem.- The shell environment always wins; there is no config file. That means a
stale
export in the user's shell silently changes a run.
Scoping: plain go test -run
Areas are ordinary Go tests, suites and methods are subtests, so one -run
expression selects at any depth:
go test ./regression_test -run '^TestIntercept$'
go test ./regression_test -run '^TestIntercept$/^HeaderFilter$'
go test ./regression_test -run '^TestIntercept$/^HeaderFilter$/^Test_PathPrefix$'
There is no TEST_SUITE/TEST_NAME indirection and no make-argument dance:
inline VAR=value prefixes work in this harness, so run go test directly
and keep make check-regression for the full unscoped suite.
Always pass -count=1 (results must never come from the test cache) and a
that fits the scope: minutes for one suite, for a
full run.
