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
It is not related to remote-vscode or I checked the following issue
Imagine yourself into my position and think how hard to debug the issue without insufficient information.
I understand that you have privacy concerns and I expect you to understand that this extension is developed for free.
Thanks.
Describe the bug
When a test changes status it sometimes disappears from the test explorer UI. I notice this more when going from fail -> pass, but sometimes get this when going from fail/success -> not run.
This can also happen to groupings of tests.
To Reproduce
Create a failing test
Update to make the test pass
Re-run by clicking Run in the test explorer UI
Test disappears from the tree, all other tests from that grouping remain
I might forget to mention that PLEASE attach an EXTENSIVE log. A lot of times reportes just select what they think it is important and those logs sometime not sufficient.
Sorry these tests are in an export controlled system so I have to manually redact them. If you need more please let me know.
The text was updated successfully, but these errors were encountered:
Checklist
I understand that you have privacy concerns and I expect you to understand that this extension is developed for free.
Thanks.
Describe the bug
When a test changes status it sometimes disappears from the test explorer UI. I notice this more when going from fail -> pass, but sometimes get this when going from fail/success -> not run.
This can also happen to groupings of tests.
To Reproduce
Screenshots (optional)
Desktop
Name: C++ TestMate
Id: matepek.vscode-catch2-test-adapter
Description: Run GoogleTest, Catch2 and DOCtest tests from VSCode
Version: 4.12.0
Publisher: Mate Pek
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=matepek.vscode-catch2-test-adapter
Regression bug?
I don't think so, I've noticed this for a long time.
**Log** (optional but recommended)
Sorry these tests are in an export controlled system so I have to manually redact them. If you need more please let me know.
The text was updated successfully, but these errors were encountered: