-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Nest test
/it
calls under a single describe
label instead of repeating the describe
label for each test
#3342
Comments
We probably should implement it, if someone else from the core team agrees I might work on it. |
Seems like a good idea 👍 |
On that note, can we make it that failed tests log last? edit: |
@simylein That's a good point. Jest shows the pass/fail result for each test inline, but batches the logging of all the verbose stuff (Expected/Received/etc.) at the end of the output. With Jest's format it's much easier to see everything that needs to be addressed in one place without much scrolling, if any. |
Any updates on this? It would make testing with bun much more prettier and useful. |
I don't think it's really prioritized right now, maybe when bun gets more stable we can think about this. But right now we have lots of issues to fix. |
I don't think you have enough context to say this :)
No real updates, other than we should do this before Bun 1.0. |
Can we create a Milestone or Label on github for stuff we need to do before Bun 1.0? |
Reopening, see #12189 (comment) |
What is the problem this feature would solve?
bun test
currently repeats thedescribe
label for eachtest
/it
call. Take the following test file as an example:This produces the following output:
What is the feature you are proposing to solve the problem?
I would prefer a more concise output like Jest, where the
describe
label is only printed once and thetest
/it
labels are nested beneath it. I believe this is not just cleaner, but also clearer visually.Here is Jest's output for the same test file:
What alternatives have you considered?
No response
The text was updated successfully, but these errors were encountered: