Forum Replies Created
-
Posts
-
Hi,
i turned off all other VS plugins, no change.
I installed your v6 Beta version and that fixed the problem. The list of unit tests doesn’t disappear
anymore.
One thing I noticed with v5.6:
Just before the list disappears it pops up a message like “loading from cache” or so. It just
very briefly pops up and then the list is gone.
Anyways v6 Beta fixes the problem and continue working with that. Hope you have a release soon.Hi,
VS2022 Test Explorer randomly hangs.
I am testing and debugging C++ gtest unit tests.
Randomly the Test Exploer hangs and it is not possible to stop the session.
Sometimes a message pops up VisualGDB can’t connect to the debug target.
I have to restart the VM and Visual Studio 2022 to get it working again.my environment:
VisualGDB, Visual Studio 2022 17.6.5, Linux Ubuntu 22 on VMWare.I am still facing problems with synchronizing source code files from those shared projects. They are in a directory parallel to the VisualGDB test unit project. I tried several settings in “Synchronize Directories” etc. but code coverage still insists saying the source code file from that parallel directory is not mapped, which is not the case.
Is there a guideline on how to properly map local to remote directories in a larager project where the source code files in a parallel directory?
Somehow confused how to set it up properly.Thanks for any help
Thanks for the quick response. I guess we have some issues with the taget path setup.
Could you send a very simple solution with Item Shared Projects and how you set up the
targets?
Thank you in advance.Thanks for your feedback.
After running unit tests code coverage is just fine in headers and gtest .cpp files but not in .cpp files located
in the shared items project.Not sure if this is important but we do have issues with synchronizing files on the remote linux host (Ubuntu). We have to run
“rm -r <project-dir>” each time we changed code.
At this point it seems as if it doesn’t matter what Sync settings we have in “VisualGDB Settings”.
Could this contribute to the problem with the code coverage highlighting?We continue to try to isolate both problems and try to provide a simple project that shows the issue.
