Suggestion for documentation enhancement

[arshantz]

Hi -

I'd like to suggest an enhancement to the parametrization documentation to make it easier for people to grasp concepts easier.

The current documentation names each parameter as fixtures when calling the test. When there are several parameters to pass, this becomes cumbersome & repetitive (especially when there's multiple tests). Luckily, you guys have been smart enough to make it possible to pass dictionaries as test data. This example provides passing a list of dictionaries as parameters.

I think this suggestion will also help people make cleaner code.

Thanks for your consideration!

Notes:

1. The two fixtures could be combined into one. I separated them for clarity.
2. I'm calling both fixtures from the test to illustrate it is possible to call multiple fixtures & pass parameters to only one fixture.
3. I've omitted my assertion because it's irrelevant to the illustration of calling a fixture. For reference, I am comparing the 'payload' dictionary to the 'User().create()' response while omitting comparison of certain properties (User().create() contains parameters, such as the userId, in the response that aren't in the request payload). Please let me know if you need additional code for illustrative purposes.

Questions/comments welcome.

conftest.py:

#create the payload used to create the user
@pytest.fixture
def f_user_payload(request):

    user = {
          "countryCode": {
            "countryCode": request.getfixturevalue("test_data")['country_code'],
          },
          "type": {
            "typeId": request.getfixturevalue("test_data")['type'],
          },
          "name": request.getfixturevalue('test_data')['name']
        }

    return user


#create user
@pytest.fixture
def f_create_user(f_user_payload):
    response = User().create(data=f_user_payload)
    yield response
    User().delete(id=response['userId'])

test_user.py:

test_data = [
    pytest.param(
        {"name": "adam1",
         "type": 1,
         "country_code": "US"},
        id='adam1-1-US'
    ),
    pytest.param(
        {"name": "adam2",
         "type": 2,
         "country_code": 'US'},
        id='adam2-2-US'
    ),
]

@pytest.mark.parametrize("test_data",
                         test_data
                        )
class TestMe:
    def test_create_name(self,
                                                f_user_payload,
                                                f_create_user,
                                                test_data):
       assert ...

[The-Compiler]

I fail to see how this makes anything more clear or simpler to be honest. I can see some value with parametrizing a test with dataclasses or named tuples for more complex parametrization, but I think there is a lot of value in having separate arguments for separate values.

[arshantz]

When a fixture has 20 parameters, and you have a class that passes each of those parameters to multiple tests, that’s a lot of parameter name duplication. Having the documentation show possible options gives the developer ideas about what style suits their implementation the best. AdamOn Sep 4, 2025, at 8:07 AM, Florian Bruhin ***@***.***> wrote: I fail to see how this makes anything more clear or simpler to be honest. I can see some value with parametrizing a test with dataclasses or named tuples for more complex parametrization, but I think there is a lot of value in having separate arguments for separate values. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[RonnyPfannschmidt]

Thats also usually the point where one might create a dataclass for charity

Dict based data manager eventually grts out of hand