I'm submitting a ...
What is the current behavior?
Parametrizing a test creates container json files for the parametrized parameter that doesn't seem to be used at all, as it does not have a children node.
It does not appear on the setup section of the tests, which is not a big problem as the parametrization for each test instance is written inside the result json itself.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
import pytest
@pytest.mark.parametrize("message",[
"a",
"b"
])
def test1(message):
assert 1 == 1
What is the expected behavior?
Add a children node to the created container json files, so parametrization appears on setup, or don't create a container json for test parametrization at all.
What is the motivation / use case for changing the behavior?
Have a consistent behavior and do not create files if not needed.
Please tell us about your environment:
Other information
I'm submitting a ...
What is the current behavior?
Parametrizing a test creates container json files for the parametrized parameter that doesn't seem to be used at all, as it does not have a children node.
It does not appear on the setup section of the tests, which is not a big problem as the parametrization for each test instance is written inside the result json itself.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
What is the expected behavior?
Add a children node to the created container json files, so parametrization appears on setup, or don't create a container json for test parametrization at all.
What is the motivation / use case for changing the behavior?
Have a consistent behavior and do not create files if not needed.
Please tell us about your environment:
Other information