-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
In the UI show test report when clicking on a test #6747
Comments
This would improve the UI and make it more usefull 👍 |
@pav-stastny Yes but :) Quick solution, have it open the report tab for that test or if not possible, for the file. Thanks |
This is especially bad because tests have |
Fixes by #6900 |
@sheremet-va Thank you so much for this! When can we expect this to drop? Will it be in v2.x.x or? |
This will be in Vitest 3 which comes out in January |
awesome! is it already in the beta that just came out? Would love to try it out |
The beta is out, but this change is not yet released. Should be available later today though |
awesome, thank you so much! |
Clear and concise description of the problem
Currently when I use the UI with the
--ui
flag, when I click a test on the UI nothing happens, there's a button to show the source code - but that's less useful (and also doesn't show the source of the test, just the source of the entire file)There is an "Open test details" that is available only on the test file level - the same icon on the test level does the "show code" functionality.
Suggested solution
The dream would be to click a test and see why it failed.
When I click on the test in the left panel, show that specific test's report.
If I had my way, the tabs should be "Report" "Console" (also preferrably for the clicked test only) than code and module graph.
Checkout this stackblitz to see my current experience:
https://stackblitz.com/edit/api-test-example-qrjqcu?file=test.spec.ts
Alternative
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: