---
title: "Comment by Алексей Каллистов on \"How to Use Fixtures as Arguments in pytest.mark.parametrize\" | Hashnode"
description: "Hello! And what could you suggest, if I need to use in parametrization a fixture, which returns unpredictable number of values? Of course, we could use it in pa"
url: "https://hashnode.com/posts/how-to-use-fixtures-as-arguments-in-pytestmarkparametrize/5fb8ef570ae19203f6d92a80/comment/6006b577b2c54030097c3f38"
---

[Discussion](https://hashnode.com/posts/how-to-use-fixtures-as-arguments-in-pytestmarkparametrize/5fb8ef570ae19203f6d92a80)

Comment [How to Use Fixtures as Arguments in pytest.mark.parametrize](https://hashnode.com/posts/how-to-use-fixtures-as-arguments-in-pytestmarkparametrize/5fb8ef570ae19203f6d92a80)

[Алексей Каллистов](https://hashnode.com/@mailakallistov)

[Jan 19, 2021](https://hashnode.com/posts/how-to-use-fixtures-as-arguments-in-pytestmarkparametrize/5fb8ef570ae19203f6d92a80/comment/6006b577b2c54030097c3f38)

Hello! And what could you suggest, if I need to use in parametrization a fixture, which returns unpredictable number of values? Of course, we could use it in parametrization as a regular Python function, but what if it's impossible? For example, this question is discussed here, but no solution was found: [github.com/pytest-dev/pytest/issues/349](https://github.com/pytest-dev/pytest/issues/349)

In my case, I definitely need a fixture and not a regular function, because parametrized value depends on HTTP service response.

Here is example code which matches my case: [pastebin.com/gLn1CrAa](https://pastebin.com/gLn1CrAa)

Of course, it doesn't work, because I'm trying to use fixture directly in mark.parametrize. Maybe, there is some suitable solution?

[Nima](https://hashnode.com/@nima994)

[Jul 1, 2021](https://hashnode.com/posts/how-to-use-fixtures-as-arguments-in-pytestmarkparametrize/5fb8ef570ae19203f6d92a80/comment/6006b577b2c54030097c3f38#reply-60dd8d2d95305075b93395b8)

You are right, this solution is not valid. It is just a complex way to do an easy task not the actual topic