Скачать или смотреть How to Make pytest Ignore pytest.ini Configuration Files

Learn how to bypass `pytest.ini` configurations in your unit tests with simple command line options. Improve your testing flexibility today!
---
This video is based on the question https://stackoverflow.com/q/62460410/ asked by the user 'asmeurer' ( https://stackoverflow.com/u/161801/ ) and on the answer https://stackoverflow.com/a/62478621/ provided by the user 'hoefling' ( https://stackoverflow.com/u/2650249/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Make pytest ignore pytest.ini

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Make pytest Ignore pytest.ini Configuration Files

When working with Python's powerful testing framework, pytest, developers may sometimes find themselves in a situation where they need to ignore the settings specified in the pytest.ini configuration file. This scenario can arise when you want to test without certain overridden configurations or simply want to debug your tests in isolation from the pytest.ini definitions.

The Challenge with pytest.ini

At present, pytest does not offer a built-in command line flag specifically designed to ignore the pytest.ini file, which can be a bit restrictive. Unlike the --noconftest flag which disables conftest.py, users may find themselves searching for a similar option to bypass configurations potentially set in pytest.ini.

Understanding pytest.ini

The pytest.ini file is used by pytest to manage various configurations including:

Command line options

Plugins

Test discovery settings

When you're running tests, pytest automatically reads this file for configurations, which can sometimes lead to unexpected outcomes, especially if you've made changes and want to test under different settings.

How to Bypass pytest.ini

While there isn't a direct command line option to ignore the pytest.ini, there are effective workarounds that can achieve the desired behavior. Here are the options:

Option 1: Rename pytest.ini

One straightforward approach is to temporarily rename the pytest.ini file before running your tests. Here’s how you can do it:

Rename the File: Change pytest.ini to something like pytest_old.ini.

[[See Video to Reveal this Text or Code Snippet]]

Run Your Tests: Execute your tests as you normally would.

Restore the Name: After your tests are complete, rename the file back to pytest.ini.

[[See Video to Reveal this Text or Code Snippet]]

Option 2: Use Null Device as Config Source

There is an alternate workaround that some users prefer, which involves directing pytest to use a null device as the configuration source. This effectively means ignoring any configurations that might be set in pytest.ini.

For Linux / macOS:

[[See Video to Reveal this Text or Code Snippet]]

For Windows:

[[See Video to Reveal this Text or Code Snippet]]

This command tells pytest to look for configurations in a non-existent or empty file, effectively skipping any settings provided in pytest.ini.

Conclusion

When faced with the need to ignore pytest.ini, these workarounds not only prove to be effective but also enhance your testing flexibility. Whether you choose to temporarily rename the configuration file or use the null device option, both strategies should help you maintain greater control over your testing environment with pytest.

By implementing one of these methods, you can avoid unexpected behaviors due to configurations and ensure that your tests run as intended. Happy testing!