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
Better indication of pending tests when Wallaby.js is slow? #1677
Comments
We can definitely experiment with it. My concern would be to check (given the already overheated laptop) that re-rendering the error messages in a different color doesn't make the performance even worse (up to the point when the editor process doesn't get enough CPU time and editing starts lagging). |
We do hide the error message on the line that is being edited. What do you reckon if we hide all error messages in the file being edited if a test run takes more than 1 second? |
Ah but sometimes I want to see those old messages... |
I'm suffering a similar thing at the moment actually, and have some other suggestions (happy to spin into a new issue if required). When you've got a lot of tests it's difficult to know from the App when things are ready. It'd be really great if:
|
Reporting the amount of tests completed while running tests would be immensely helpful as stated above. "completed 12/200 tests". |
Issue description or question
Suppose you're running Jest tests on an overheating laptop and some unit tests take >=1 seconds to run. After editing a line, the red error text next to lines that throw an error is the same shade of red while tests are re-running. That can be confusing, especially if the tests take several seconds.
Can they be a duller shade of red or otherwise indicate they're out of date while tests are pending?
Wallaby.js configuration file
Code editor or IDE name and version
Visual Studio Code v1.23.0
OS name and version
Windows 10
The text was updated successfully, but these errors were encountered: