Skip to content
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

Integration tests should execute on an isolated CLI installation #144

Closed
cruhland opened this issue Aug 17, 2016 · 0 comments
Closed

Integration tests should execute on an isolated CLI installation #144

cruhland opened this issue Aug 17, 2016 · 0 comments

Comments

@cruhland
Copy link
Contributor

When running the integration tests, I noticed that some of them use the standard config directory (~/.dcos) because I had failures due to my configuration. For example, I had the kafka subcommand installed, and that resulted in the test for the "top level" menu output failing.

The integration tests should always use a CLI that has been installed into a temporary directory, and configured to use generated, test-specific resources. That would prevent unwanted interactions between the tests and any actual CLI installations on developer machines.

@armandgrillet armandgrillet transferred this issue from dcos/dcos-cli Jan 15, 2019
@janisz janisz closed this as completed Jun 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants