You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The test explorer is working just fine in my VS code thanks, but as a colorblind developer, I find it really difficult to find passing/failing tests in the explorer view. I think that the curly-braces used to indicate namespaces and/or test suites turn red or green depending upon pass/fail, but I have an incredibly difficult time seeing the difference between them. I know that the icons inside are either tick/cross and that's fine, but it means I have to expand every suite to find the failing ones.
Suggestions
Make the colors configurable, perhaps with presets suitable for the various forms of colorblindness
For the red braces, invert the icon's background/foreground (so it's a white brace inside a red background square). This way the icon is noticeably different from the green braces even if the developer is unable to perceive color.
Use shades of red/green with markedly different lightness (for example a very pale/faint green, but a bold/solid red). This way they are distinguishable by lightness even if the developer cannot do so by hue
Workaround
For now, what I am doing is ensuring that the "Add to Problems" setting is enabled. This way, I can find the failing tests that way, instead of using the explorer. It does make the explorer a little less useful though.
The text was updated successfully, but these errors were encountered:
The test explorer is working just fine in my VS code thanks, but as a colorblind developer, I find it really difficult to find passing/failing tests in the explorer view. I think that the curly-braces used to indicate namespaces and/or test suites turn red or green depending upon pass/fail, but I have an incredibly difficult time seeing the difference between them. I know that the icons inside are either tick/cross and that's fine, but it means I have to expand every suite to find the failing ones.
Suggestions
Workaround
For now, what I am doing is ensuring that the "Add to Problems" setting is enabled. This way, I can find the failing tests that way, instead of using the explorer. It does make the explorer a little less useful though.
The text was updated successfully, but these errors were encountered: