Releases · smarie/python-pytest-cases

03 Jun 15:35

Fixed ValueError when @parametrize is used to parametrize a class. Also, added a more explicit TypeError when @parametrize is used to parametrize a class and at least a fixture reference is present. Fixed #215.

Assets 2

31 May 19:38

The current_cases fixture now contains case parameters if any. Fixes #214
The current_cases fixture entries are now instances of namedtuple.
New in_cls argument in unpack_fixtures so that it can be used inside classes. Fixes #201
Fixed minor issue where empty entries could be present in currentcases. Fixes #213

Assets 2

21 May 13:07

Fixed issues where the currentcases fixture would not return the correct case function. Fixed #212

Assets 2

18 May 13:41

Assets 2

07 May 09:52

New: Users can now easily access the current cases for each parametrized argument thanks to the new current_cases fixture. A new helper function get_current_cases is also provided, for direct access from a hook. get_current_case_id becomes deprecated in favour of these two. Fixes #195
Bugfix: Fixed issue where the cache of a lazy_value used for a tuple of parameters (several argnames) was not considering the pytest context and thus was wrongly used across pytest nodes. Fixes #202
Improved error message when a fixture parametrized with several argnames as once is not able to unpack the parameter values received (non subscriptable object).
parametrize_plus and fixture_plus are now deprecated in favour of parametrize and fixture, as most users seem to have adopted these names without issues.
(internal) Replaced the "used" parameter with a dedicated singleton USED

Assets 2

12 Apr 10:05

LazyValue, LazyTuple and LazyTupleItem are now hashable. This increases compatibility with plugins hashing the parameter values, such as pytest-steps. See pytest-steps#41 . Fixes #199

Assets 2