Previously, when assigning a scope for a fully-indirect parameter set, when there are multiple fixturedefs for a param (i.e. same-name fixture chain), the highest scope was used, but it should be the lowest scope, since that's the effective scope of the fixture.
3 lines
202 B
ReStructuredText
3 lines
202 B
ReStructuredText
Fixed a bug that when there are multiple fixtures for an indirect parameter,
|
|
the scope of the highest-scope fixture is picked for the parameter set, instead of that of the one with the narrowest scope.
|