mirror of https://github.com/docker/compose.git
9622395c8a
The E2E tests can be run in plugin (`docker compose`) or standalone (`docker-compose`) mode. Existing logic was in place to ensure that the helper method is always used, which will invoke the right one based on how tests are being executed. However, this logic was too easy to (unintentionally) bypass given the myriad of ways that commands can be run. The check has been made stricter and pushed to a lower-level to more aggressively catch instances. As a result, a bunch of calls to `RunDockerCmd` are now updated to be `RunDockerComposeCmd`, which will ensure that the invocation is correct based on test mode. Signed-off-by: Milas Bowman <milas.bowman@docker.com> |
||
|---|---|---|
| .. | ||
| fixtures | ||
| cancel_test.go | ||
| cascade_stop_test.go | ||
| compose_build_test.go | ||
| compose_down_test.go | ||
| compose_environment_test.go | ||
| compose_exec_test.go | ||
| compose_run_test.go | ||
| compose_test.go | ||
| cp_test.go | ||
| ddev_test.go | ||
| e2e_config_plugin.go | ||
| e2e_config_standalone.go | ||
| framework.go | ||
| ipc_test.go | ||
| logs_test.go | ||
| main_test.go | ||
| metrics_test.go | ||
| networks_test.go | ||
| ps_test.go | ||
| restart_test.go | ||
| scan_message_test.go | ||
| secrets_test.go | ||
| start_fail_test.go | ||
| start_stop_test.go | ||
| volumes_test.go | ||