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
I often use many dozens of tests for the testing of a single function and include those inside a single testing file. It would be very useful if I could label tests or label/title/name a block of tests, so that it is easy to see which test failed.
Currently, I see that 78 tests passed and then an error occurred. But it is often not at all obvious which test actually failed. If tests can be labelled, or if a block of tests can be labelled (when using a block of tests to test a specific aspect of the tested function), then it should be possible to see that test "XYZ" failed or that a test from block "ZYX" failed. That can speed up error finding enormously.
Could it be made possible to label tests or to jointly label a block of tests and then access that label when a test file fails?
(I know there is an "info" argument, but that is not the same, I guess)
The text was updated successfully, but these errors were encountered:
I often use many dozens of tests for the testing of a single function and include those inside a single testing file. It would be very useful if I could label tests or label/title/name a block of tests, so that it is easy to see which test failed.
Currently, I see that 78 tests passed and then an error occurred. But it is often not at all obvious which test actually failed. If tests can be labelled, or if a block of tests can be labelled (when using a block of tests to test a specific aspect of the tested function), then it should be possible to see that test "XYZ" failed or that a test from block "ZYX" failed. That can speed up error finding enormously.
Could it be made possible to label tests or to jointly label a block of tests and then access that label when a test file fails?
(I know there is an "info" argument, but that is not the same, I guess)
The text was updated successfully, but these errors were encountered: