Skip to content
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

Highlight the first error, not the last #434

Open
1 task done
emmenlau opened this issue Apr 5, 2024 · 1 comment
Open
1 task done

Highlight the first error, not the last #434

emmenlau opened this issue Apr 5, 2024 · 1 comment
Labels
incomplete Make sure you followed the issue template

Comments

@emmenlau
Copy link

emmenlau commented Apr 5, 2024

Checklist

Is your feature request related to a problem? Please describe.
Currently, when I click on a failed test that has multiple failures, the test extension will jump to the last error. However, I have found that in case of multiple errors, the last error often is in response to the earlier errors. This has mislead me already a few times, when following up a failed test.

Would it be possible to always jump to the first error instead?

Here an example with 4 errors, of which the last one is highlighted, but the first one caused the problem:
image

Describe the solution you'd like
When I click on a failed test (in the left side-panel, that shows the overview of all tests), then the editor should jump to the first error in that test, not the last one.

Describe alternatives you've considered
I usually scroll manually to the first failure, but this is more cumbersome. I also sometimes use the small overview of failures in the bottom right side panel, but that is also more cumbersome for me, and i.e. I sometimes overlook that there are multiple errors.

Thanks a lot for your consideration and the great work!

@matepek
Copy link
Owner

matepek commented Oct 19, 2024

Which test framework, etc.... ?

@matepek matepek added the incomplete Make sure you followed the issue template label Oct 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
incomplete Make sure you followed the issue template
Projects
None yet
Development

No branches or pull requests

2 participants