You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned in pytest-dev/pytest#12146, pytest has a bug that a fixture's scope will get changed when using variables to set argument values in parametrization, causing unexpected fixture setups and teardowns.
We recently ran into this problem when running ACL tests in a multi-dut device (#12715), and later we pushed a fix (#12824) to bypass this issue. However, we have many places in our repo that are also passing variables during parametrization, .e.g, metafunc.parametrize("fixture_name", variables, scope="module"). Therefore, we need to find a way to fix this problem completely.
Results you see
a fixture's scope will get changed when using variables to set argument values in parametrization
Results you expected to see
a fixture's scope won't get changed when using variables to set argument values in parametrization
Is it platform specific
generic
Relevant log output
No response
Output of show version
No response
Attach files (if any)
No response
The text was updated successfully, but these errors were encountered:
Issue Description
As mentioned in pytest-dev/pytest#12146, pytest has a bug that a fixture's scope will get changed when using variables to set argument values in parametrization, causing unexpected fixture setups and teardowns.
We recently ran into this problem when running ACL tests in a multi-dut device (#12715), and later we pushed a fix (#12824) to bypass this issue. However, we have many places in our repo that are also passing variables during parametrization, .e.g,
metafunc.parametrize("fixture_name", variables, scope="module")
. Therefore, we need to find a way to fix this problem completely.Results you see
a fixture's scope will get changed when using variables to set argument values in parametrization
Results you expected to see
a fixture's scope won't get changed when using variables to set argument values in parametrization
Is it platform specific
generic
Relevant log output
No response
Output of
show version
No response
Attach files (if any)
No response
The text was updated successfully, but these errors were encountered: