Test status indicator issue

[yantakus]

When there's a failing test, the indicator turns red:

When I fix it, the comment disappears, but the indicator is still red:

[orta]

oh yeah, that's weird, I've not seen this before - can you clone the repo and have a look with the debugger at the status of that it? Is there two wit the same name by any chance?

[bookman25]

When you fix it, are the files you're modifying back to an unchanged state in git (unstaged/uncommited)?

I've seen one case if you fix and either commit, or the fix goes back to unchanged state. Jest is only acting on unstaged/uncommited files and as a result the editor doesn't currently update the decorators for files it thinks have no changes.

[bookman25]

We made some improvements here, if you're still seeing the issue feel free to reopen.

[thedgbrt]

Still seeing this with latest version

[bookman25]

I've also seen variations of this as well. I'm going to try to find some time to track down the specific repro and hopefully fix. Basically there's some cases where the decorators aren't updating when they should.

[svdHero]

Same problem here with vscode 1.16.1 and Jest extension 2.4.2 under Linux:

[daldridge-cs]

I've seen this occur in the following scenario:

• Start with a test that is passing
• Edit the test and save, causing the watcher to detect the change and run the test. Test is correctly shown as failing.
• Undo the edits to the failing test, reverting the file back to what it was (no difference in git working tree). Because the file matches SCM, the watcher doesn't re-run the test, so it fails to go back to green.

Likely related/same as #32?

[jfcere]

@daldridge-cs I noticed the same thing and it has been reported here: #308