Different collection order if parametrized fixture is not function-scoped

[chbndrhnns]

I noticed an interesting behaviour when running this test module.

import pytest

@pytest.fixture(
    scope="class",
    # scope="function",
    params=["param1", "param2"],
)
def f(request):
    return request.param

def test_one(f):
    assert f

def test_two(f):
    assert f

Using a function-scoped fixture, pytest orders the test list by functions:

<Dir x>
  <Module test.py>
    <Function test_one[param1]>
    <Function test_one[param2]>
    <Function test_two[param1]>
    <Function test_two[param2]>

When changing the scope to "class" or higher, pytest orders the test list by parameters:

<Dir x>
  <Module test.py>
    <Function test_one[param1]>
    <Function test_two[param1]>
    <Function test_one[param2]>
    <Function test_two[param2]>

Is this somehow expected?
It breaks the test tree view in Pycharm (cf. https://youtrack.jetbrains.com/issue/PY-61131/Using-parametrized-fixture-with-non-function-scope-loses-test-result-grouping).

[RonnyPfannschmidt]

Yes pytest is reordering tests to minimize the number of times higher scope fixtures have to be setup/ teardown