Direct use of 'tmpdir' fixture causes warnings to be raised in latest pytest versions
See original GitHub issueThe following warning message appears after test runs:
RemovedInPytest4Warning: Fixture "tmpdir" called directly. Fixtures are not meant to be called directly, are created automatically when test functions request them as parameters. See https://docs.pytest.org/en/latest/fixture.html for more information.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Changelog — pytest documentation
Changelog¶. Versions follow Semantic Versioning ( <major>.<minor>.<patch> ). Backward incompatible (breaking) changes will only be introduced in major ...
Read more >How to use temporary directories and files in tests - Pytest
You can use the tmp_path fixture which will provide a temporary directory unique to the test invocation, created in the base temporary directory....
Read more >pytest fixtures: explicit, modular, scalable
fixtures have explicit names and are activated by declaring their use from test functions, modules, classes or whole projects. fixtures are implemented in...
Read more >API Reference — pytest documentation
For pre-releases, the last component will be a string with the prerelease ... Test functions can directly use fixture names as input arguments...
Read more >7.0.x PDF - pytest Documentation
In order to write assertions about raised exceptions, you can use pytest.raises() as ... Override a fixture with direct test parametrization.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@mpasternak I just release version 2.0.1 on PyPI. Happy testing!
@youtux thanks for the fix. I’ve also hit this bug today with clean
pip install pytest-splinter
.… also, I know it’s been only 23 hours since you committed the fix but… how about a release? 😃 Thanks.