-
Notifications
You must be signed in to change notification settings - Fork 781
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Let simple array data in test.each() serve as automatic labels #1733
Labels
Component: Core
For module, test, hooks, and reporters.
Type: Enhancement
New idea or feature request.
Milestone
Comments
Krinkle
added
Type: Enhancement
New idea or feature request.
Component: Core
For module, test, hooks, and reporters.
help welcome
good first issue
Straight-forward to start and receive help with.
labels
Nov 9, 2023
Krinkle
removed
help welcome
good first issue
Straight-forward to start and receive help with.
labels
Sep 5, 2024
Krinkle
added a commit
that referenced
this issue
Sep 5, 2024
Krinkle
added a commit
that referenced
this issue
Sep 5, 2024
Krinkle
added a commit
that referenced
this issue
Sep 5, 2024
Krinkle
added a commit
that referenced
this issue
Sep 5, 2024
Krinkle
added a commit
that referenced
this issue
Sep 5, 2024
Krinkle
added a commit
to Krinkle/qunit
that referenced
this issue
Sep 5, 2024
Krinkle
added a commit
that referenced
this issue
Sep 7, 2024
Fixes #1733. Co-authored-by: Vivien Tintillier <vtintillier.privatedev@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Component: Core
For module, test, hooks, and reporters.
Type: Enhancement
New idea or feature request.
Follows-up #1568
What are you trying to do?
Code that reproduces the problem:
What actually happened?
mytest [0]
mytest [1]
mytest [2]
.What did you expect to happen?
For simple cases like this, it would be valuable if we let values serve as the test case label. In other words as:
mytest [foo]
mytest [bar]
mytest [_]
Example
EDIT: Example based on the implementation at #1799.
The text was updated successfully, but these errors were encountered: