Skip to content

[Feature] Live unit testing #4059

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

Closed
Lokathor opened this issue Apr 20, 2020 · 1 comment
Closed

[Feature] Live unit testing #4059

Lokathor opened this issue Apr 20, 2020 · 1 comment
Labels
A-vscode vscode plugin issues C-Architecture Big architectural things which we need to figure up-front (or suggestions for rewrites :0) ) E-hard S-unactionable Issue requires feedback, design decisions or is blocked on other work

Comments

@Lokathor
Copy link

One thing that would be helpful, is to have an indicator along the status bar which shows just a count of passed tests out of total tests, eg cargo-test: 12/12, or something like that. Green if you've got 100% passed and red if there were failures.

Then RA can just rerun all tests on every save and re-display the value. Lets you keep track as soon you poked something out of alignment.

Clicking the indicator could perhaps even open up a terminal tab with the last set of cargo-test output so that you can check on any error messages.

@lnicola lnicola changed the title [Feature] Test suite pass/fail indicator in the status bar [Feature] Live unit testing Jan 22, 2021
@lnicola lnicola added A-vscode vscode plugin issues C-Architecture Big architectural things which we need to figure up-front (or suggestions for rewrites :0) ) E-hard S-unactionable Issue requires feedback, design decisions or is blocked on other work labels Jan 22, 2021
@matklad
Copy link
Member

matklad commented Apr 26, 2021

closing in favor of #8420

@matklad matklad closed this as completed Apr 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-vscode vscode plugin issues C-Architecture Big architectural things which we need to figure up-front (or suggestions for rewrites :0) ) E-hard S-unactionable Issue requires feedback, design decisions or is blocked on other work
Projects
None yet
Development

No branches or pull requests

3 participants