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
When using parametrization with | operator would be nice to be able to give each test a unique identifier, to make spot of issues easier and to avoid weird behaviors. E.g. when using parametrization with | the number of assertions is way higher than the same set of tests using for();
Actual Behavior
When comparing different ways of adding test parameters, we have:
The first way, using | has two problems: it doesn't allow test name customisation, leaving to warnings during failures, and it creates way more assertions than the second approach.
Ideally would be nice that both ways have a consistent behavior and that no extra assertions get generated in the print.
Steps to Reproduce the Problem
Running the snapshot above should already give you that.
Specifications
Version: v1.1.9
Platform: Linux
Subsystem: Ubuntu
The text was updated successfully, but these errors were encountered:
lgrossi
changed the title
Parametrization with | operator doesn't allow name customisation
Feature: allow test name customisation when using parameters via | operator
Aug 27, 2023
Expected Behavior
When using parametrization with | operator would be nice to be able to give each test a unique identifier, to make spot of issues easier and to avoid weird behaviors. E.g. when using parametrization with | the number of assertions is way higher than the same set of tests using for();
Actual Behavior
When comparing different ways of adding test parameters, we have:
The first way, using | has two problems: it doesn't allow test name customisation, leaving to warnings during failures, and it creates way more assertions than the second approach.
Ideally would be nice that both ways have a consistent behavior and that no extra assertions get generated in the print.
Steps to Reproduce the Problem
Running the snapshot above should already give you that.
Specifications
The text was updated successfully, but these errors were encountered: