[Fabian]

Hi,

that solution is working for us. All test targets are listed in Test Explorer now.

Thank you!

 

Best Regards

• This reply was modified 3 months ago by Fabian.
• This reply was modified 3 months ago by Fabian.

[Fabian]

Hi,

thank you for the explanations.

Sticking with patching the test framework for the moment seems to be most efficient.

We’ll be looking forward for multiple test target support.

 

Best Regards

[Fabian]

Another thing:

Trying to integrate the unittests from the minimal cmake project (where test discovery and execution worked) into our main project did not work directly.
I followed your suggestions and compared the binaries and .vgdbcmake files, but they matched.
What was different was the SelectedCMakeTarget in .visualgdb\VisualGDBCache\xyz-Debug-Simulation\xyz.vgdbtestcontainer.

It seems only the unittests of the target marked as “Startup Target” are being discovered successfully.

In our project, we define multiple targets containing unitests. Having to select every target on its own for test execution is not very convenient.

[Fabian]

Hi,

I just realized that you patched the gtest/gmock library to include the test hooks.

After using the gtest/gmock version from %LOCALAPPDATA%\VisualGDB\TestFrameworks\com.sysprogs.unittest.googletest\ test execution reports correctly to the Test Explorer.

Is there a way avoid having to include the patched gtest/gmock library and use a vanilla instead?

Our current just use case just involves a “Simulation” (Windows-based) platform, no on-target testing.

 

Another question I noticed working with the current VisualGDB version (v6.0R3):

Configuration of a CMake based VisualGDB project using CMake Presets currently doesn’t allow me to create a “Simulation” platform.
Of course, a native CMake Preset defining the Host as target platform results in the expected compilation result (host binaries), but from VisualGDB’s perspective it’s still an Embedded target.
Debugging of such an executable is not working, assuming a target debugging would be involved.

Will the CMake Presets support extended in the future or should we create a native C++/CMake VisualStudio project instead in this case?

Thanks and Regards

[Fabian]

Hi,

thanks for your reply.

I managed to get a minimal cmake project running by including the %LOCALAPPDATA%\VisualGDB\TestFrameworks\com.sysprogs.unittest.googletest\Platforms sources into the build.

Unfortunately the Test Explorer cannot evaluate the test result (see attachment).

The pipe within TestOutputPipe is created successfully.

Any additional code I should include?

 

Thanks and Regards

 

Attachments:

You must be logged in to view attached files.

[Author]

Posts