-
Notifications
You must be signed in to change notification settings - Fork 18.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace integration-cli suite with API test suite #32866
Comments
We should probably update the contributing guidelines to indicate that users should not be using integration-cli. Or at the least only make API tests. To go along with this either docker/cli needs to setup integration testing or some separate integration repo for "docker-ce". |
@cpuguy83 yes and we need to setup a ci check with those for the time being. I'll start working on that next week 😇 |
Note that there is discussion happening in https://forums.mobyproject.org/t/evolution-of-testing-moby/38 |
Opened #34407 to document the proposal from the forum thread. |
Current status: #34000 and #34407 have merged so we have a new suite and a document for testing guidelines. A validation check has been added to prevent any new cli tests from being added (#34552). Ongoing: removing cli-only tests: #34560 and #34548 Next steps:
I'll update the description of this issue as well. |
Hello, everyone, What is the latest status of this task? I saw there had been quite a few PR's working on migrating legacy CLI test cases into API cases. But the CLI cases are still the majority of all integration test. Is this job still calling for contribution? Just want to know if I can help in this issue. |
Many tests in
integration-cli
rely on the Docker CLI. The CLI has moved into into a new repo, and moby should not depend on docker, so the integration test suite needs to be transitioned to a new API test suite.Testing guidelines doc: ./TESTING.md
Execution plan:
These tests should be replaced with unit tests
integration/
integration-cli/docker_api_*_test
tointegration/
See #34623 for a checklist of prioritized tests
The text was updated successfully, but these errors were encountered: