Skip to content

Tests broken because of calling fixture functions directly #35

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
butla opened this issue Jan 13, 2019 · 0 comments · Fixed by #40
Closed

Tests broken because of calling fixture functions directly #35

butla opened this issue Jan 13, 2019 · 0 comments · Fixed by #40

Comments

@butla
Copy link

butla commented Jan 13, 2019

It was causing warnings for some time and it looks like the newer versions of pytest are changing these into errors.

______________________________________ test_docker_services_failure ______________________________________
Fixture "docker_services" called directly. Fixtures are not meant to be called directly,
but are created automatically when test functions request them as parameters.
See https://docs.pytest.org/en/latest/fixture.html for more information about fixtures, and
https://docs.pytest.org/en/latest/deprecations.html#calling-fixtures-directly about how to update your code.

I have a way of fixing that, but I'm unsure that I should actually fix the tests, or just replace them with ones that don't rely on mocking that heavily. Please check out this PR - #34

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant