As we flesh out the set of CLI e2e tests, we should publish those as an image on hub that can be used by downstream projects for testing.
The pattern we've been using is to support either mounting docker.sock or a DOCKER_HOST environment (with client certs) pointing to a swarm-mode manager, or EE controller/manager. The tests then run against that target cluster and do their thing. Exit with a zero for pass, or non-zero for fail. Additional optional tuning can be done via command line arguments or env vars to skip tests or refine behavior, but the default image cmd/entrypoint should run the typical set of tests.
bsousaa
commented
1 year ago
As we flesh out the set of CLI e2e tests, we should publish those as an image on hub that can be used by downstream projects for testing.
The pattern we've been using is to support either mounting
docker.sockor a DOCKER_HOST environment (with client certs) pointing to a swarm-mode manager, or EE controller/manager. The tests then run against that target cluster and do their thing. Exit with a zero for pass, or non-zero for fail. Additional optional tuning can be done via command line arguments or env vars to skip tests or refine behavior, but the default image cmd/entrypoint should run the typical set of tests.