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

[RFE] config.yaml should not be needed for testing #84

Open
phracek opened this issue Sep 6, 2017 · 3 comments
Open

[RFE] config.yaml should not be needed for testing #84

phracek opened this issue Sep 6, 2017 · 3 comments

Comments

@phracek
Copy link
Member

phracek commented Sep 6, 2017

Update meta-test-family, so config.yaml in some cases is not needed.

In case it is already implemented, document it in user_guide section, how developer / tester can use it.

@jscotka
Copy link
Collaborator

jscotka commented Sep 20, 2017

should be fixed by
#103
in case you not have your config.yaml, or configured via CONFIG envvar, there is used minimal config. it is good for base tests (or modules what does not provide any service)
but you have to set URL=to_some_link to not test default values in minimal config, byut what you want like:

MODULE=docker URL=docker.io/fedora avocado run your_test_or_modulelint

@phracek
Copy link
Member Author

phracek commented Jan 16, 2018

@jscotka @dhodovsk I would like to test just dockerfile linter over Dockerfile. For this case URL is really not needed.

@dhodovsk
Copy link
Collaborator

+1 for removing the need for URL from requirements of static linters. User might want to run linters on newly created/not pushed to registry Dockerfiles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants