Python logging does not log when used inside a Pytest fixture

Question

I have a Pytest + Selenium project and I would like to use the logging module.

However, when I set up logging in conftest.py like this

@pytest.fixture(params=["chrome"], scope="class")
def init_driver(request):
    start = datetime.now()
    logging.basicConfig(filename='.\\test.log', level=logging.INFO)
    if request.param == "chrome":
        options = ChromeOptions()
        options.add_argument("--start-maximized")
        web_driver = webdriver.Chrome(ChromeDriverManager().install(), options=options)
    if request.param == "firefox":
        web_driver = webdriver.Firefox(GeckoDriverManager().install())
    request.cls.driver = web_driver
    yield
    end = datetime.now()
    logging.info(f"{end}: --- DURATION: {end - start}")
    web_driver.close()

looks like test.log is not created at all and there are no error messages or other indications something went wrong.

How can I make this work?

you are yielding before the actual logging, are you sure the code reaches the `logging.info` part? And do you get a file when you put a `logging.info` directly after the `logging.basisConfig` line? — Thymen, Mar 05 '21 at 09:46
I tried it and I don't get the file even when logging directly after the logging.basicConfig. — Mate Mrše, Mar 05 '21 at 09:57
I do get a `test.log` file when running `logging.basisConfig` and `logging.info` behind each other directly in a terminal. So that raises the question if you are actually running that part of the code? Try putting a print statement in the code and see if it is running. — Thymen, Mar 05 '21 at 10:15
But are you running them in pytest? When I add a print statement directly before logging.info() it is printed to console. — Mate Mrše, Mar 05 '21 at 10:18
I didn't, but maybe [this](https://stackoverflow.com/questions/4673373/logging-within-pytest-tests) post can help you? — Thymen, Mar 05 '21 at 10:21

score 6 · Accepted Answer · answered Mar 12 '21 at 09:01

Two facts first:

logging.basicConfig() only has an effect if no logging configuration was done before invoking it (the target logger has no handlers registered).
pytest registers custom handlers to the root logger to be able to capture log records emitted in your code, so you can test whether your program logging behaviour is correct.

This means that calling logging.basicConfig(filename='.\\test.log', level=logging.INFO) in a fixture will do nothing, since the test run has already started and the root logger has handlers attached by pytest. You thus have two options:

Disable the builtin logging plugin completely. This will stop log records capturing - if you have tests where you are analyzing emitted logs (e.g. using the caplog fixture), those will stop working. Invocation:
```
$ pytest -p no:logging ...
```
You can persist the flag in pyproject.toml so it is applied automatically:
```
[tool.pytest.ini_options]
addopts = "-p no:logging"
```
Or in pytest.ini:
```
[pytest]
addopts = -p no:logging
```
Configure and use live logging. The configuration in pyproject.toml, equivalent to your logging.basicConfig() call:
```
[tool.pytest.ini_options]
log_file = "test.log"
log_file_level = "INFO"
```
In pytest.ini:
```
[pytest]
log_file = test.log
log_file_level = INFO
```
Of course, the logging.basicConfig() line can be removed from the init_driver fixture in this case.

I guess a third option would be [`getLogger`](https://docs.python.org/3/library/logging.html#logging.getLogger) instead of `basicConfig`, giving you access to the root logger regardless. Not sure if it works though. — bwdm, Mar 16 '21 at 03:57

Python logging does not log when used inside a Pytest fixture

1 Answers1