Package scope fixture: experimental status?
See original GitHub issueJust noticed that package
scope is still marked as experimental:
https://docs.pytest.org/en/stable/fixture.html#package-scope-experimental
Should we remove that warning and mark it as official for 6.0?
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
pytest fixtures: explicit, modular, scalable
Scope : sharing a fixture instance across tests in a class, module or session¶ ... This functionality is considered experimental and may be...
Read more >Understand 5 Scopes of Pytest Fixtures | by Xiaoxu Gao
Pytest fixtures have five different scopes: function, class, module, package, and session. The scope basically controls how often each fixture will be ...
Read more >Make your python tests efficient with pytest fixtures
Fixture scopes can be set for each fixture which will helps tremendously in saving a lot of time and computing resources while running...
Read more >pytest fixtures nuts and bolts | pythontest
fixture ()' and add a request param to my fixture, it looks like this, but doesn't run any different. ` @pytest.fixture(scope='function', params= ...
Read more >pytest Documentation - Read the Docs
2.3.3 Scope: sharing fixtures across classes, modules, packages or session ... skipif - skip a test function if a certain condition is met....
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 Free
Top 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
Thank You for keeping it. Salt’s test suite depends heavily on subprocesses which run some daemons. Historically we started the daemons at the start of the test suite and stopped them at the end. These daemons are not required for unit tests or functional tests, so the package scope, when properly working, solves this issue for us.
The feature stays