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.

Sign up for GitHub

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

Jump to bottom

[QoL suggestion] Make adapter test discovery errors discoverable/survivable #365

Open
fnune opened this issue Feb 19, 2024 · 0 comments
Open

[QoL suggestion] Make adapter test discovery errors discoverable/survivable #365

fnune opened this issue Feb 19, 2024 · 0 comments

Comments

@fnune
Copy link

fnune commented Feb 19, 2024

Two things that should hopefully reduce the amount of "my adapter can't find tests" issues here, or at least improve their quality:

  • When an adapter fails to discover tests for some reason (e.g. [BUG] No test found #348, [BUG] no tests found #303), make other adapters in the same project continue running. Currently, if e.g. neotest-jest fails, neotest-python will not run at all and will report "no tests found".
  • When an adapter fails, show an error in message or show something within :Neotest summary like an error sign.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fnune