pytest-profiling does not profile fixtures

Consider the following example:

import pytest


@pytest.fixture()
def work_func_fix():
    s = 0
    for i in range(1000):
        s += i * i
    return s


def work_func_test():
    s = 0
    for i in range(1000):
        s += i * i
    return s


def test_example(work_func_fix):
    assert work_func_fix == work_func_test()

Apparently, only test_example is profiled. work_func_test appears in the profiling results, but work_func_fix does not.

Is it a design choice? I’ve been searching but found no reference to that. Or is there a flag I should pass to enable fixture profiling?

We use pytest to test a Flask application. Fixtures create the database, and instantiate and initialize the application. We’d like to profile the initialization process but it does not appear in the results.

In fact, the profiling result in my example above shows a lot of things I don’t care about (everything that is not under test_example), but not the fixture I do care about.

[eeaston]

Hi @lafrech - thanks for raising this and it’s definitely a valid use case. There’s a number of issues with the profiling that I’m working through at the moment and I’ll cover this as well. Your example implementation is good - we need to get the profiler turned on early enough to cover fixture execution.

[mehdisadeghi]

I am getting different results when I profile with cProfile and pytest --profile. Since I use fixtures, I think that is due to this issue. Can somebody explain why pytest-profling skips fixtures? In my case I use caching in my fixture to run subsequent tests faster.