Publish e2e CLI tests as an image on hub
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing CLI e2e tests and the Docker image publishing configuration; the issue does not name specific files or entry points. Check how those tests currently target docker.sock or DOCKER_HOST, then define the image's default test command and its zero/non-zero exit behavior for passing and failing runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli, devops, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100