Use yellow and red colors for suites with partial and no tests passing
See original GitHub issueWould it be possible to add color-coding to the test output, so that a test suite with zero passing tests doesn’t output in green?
It took me a bit to figure out that this didn’t say that all tests were passing 😅 you might respond with “just read” but I feel like the color is misleading?
Would it be possible to at least add a section in red for Failed: X
?
Thanks for the great tool btw!
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
How to Use Color Blind Friendly Palettes to Make Your ...
People who suffer from blue/yellow color blindness have difficulty distinguishing between blue and yellow colors. This particular form of color ...
Read more >Visually Encoding Program Test Information to Find Faults ...
Large test suites are frequently used to evaluate software systems and to locate errors. ... The system uses a principled color mapping to...
Read more >Test Your Color Vision | Ishihara Test for Color Blindness
See if you are colorblind by taking our online Ishihara Color Test. Learn about Color Blind treatments and how to pass a color...
Read more >use the ScalaTest shell
Using the ScalaTest shell · color (the default) - display results in color (green for success; red for failure; yellow for warning; blue...
Read more >Review of the Color Vision Tests Currently in Use
This test has two options. The first option is to screen for both red-green and blue-yellow defects. The second option is to classify...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t want to add a condition for such a rare and weird edge case tbh. Esp since the end result is expected and gonna be the same anyway.
It feels like your tests aren’t being awaited correctly, and that may be the test-utils causing things to freak out. Not at my computer but will have to check later
You should move your test-utils file into your fixtures so that it’s not being loaded. Also don’t think you need to have
-i package.json
in the cli usage