micst/ctestadapter

A Test Adapter for VisualStudio to run CTest tests

ctestadapter's Issues

Add check for installed childprocess debugging tool when debugging a test

debug from the VS test explorer

Hi There,

I installed the test adapter and the tests show now in vs2017 test explorer. but I am can not debug ( step through the code ) when I run a test in debug. can you advise/help with that?

the second I ma trying to update the ctestAdapter to VS 2019 but unsuccessfully. is there a plan to make ctestadapter support vs 2019?

thanks;
-GG

CTestAdapter may crash if logfile cannot be opened

CTestAdapter fails if CMake cache contains value of type UNINITIALIZED

Add git hook

Add some git hooks to improve code consistency.

Output Window: file paths are not shown as full links when the paths contain spaces

Add more verbose message when Building CTestAdapter and VSSDK is not found

Add version of running CTestAdapter when opening new logfile

Passing Environment Variables that with multiple values fails

I tried to set the PATH variable for the execution of my tests and noticed that only the first value is getting through if add more than one path. Here is a simple repro case:

add_test(
  NAME test_run   
  COMMAND test_executable
)
set_property(
  TEST test_run
  PROPERTY ENVIRONMENT
    "FOO=A;B;C"
    "BAR=D;E"
)

when getting the value of the variable using:

std::string get_environment(const char* env_var)
{
    std::string value;
    char* buf = nullptr;
    size_t sz = 0;
    if (_dupenv_s(&buf, &sz, env_var) == 0 && buf != NULL) {
        value = buf;
        free(buf);
    }
    return value;
}
...
std::cout << "FOO=" << get_environment("FOO").c_str() << std::endl;
std::cout << "BAR=" << get_environment("BAR").c_str() << std::endl;

I only get the first value. I.e.:
FOO=A
BAR=D

when setting the variable in the visual studio project settings of 'test_executable' and run the executable directly (not from Test Explorer), everything works as expected:
FOO=A;B;C
BAR=D;E

Contact (from legacy project)

Find the original issue here

@toeb wrote:

Hi - sorry there is no PM in github so I had to create an issue here ;)

I saw that you created CTestAdapter. (also ctesttestadapter was a mouthful - even though more consistent - I thought about CTestAdapter as well but found it too ambiguous - mistake ) It looks very good :) and thanks for the credits.

I see the project uses CMake to add dotnet projects and I have a couple of questions because I might want to add some stuff to cmakepp to make dotnet/CMake easier

• Did you think of the CMake code to create these projects yourself and/or do you have resources for dotnet/CMake.
• Does using CMake and dotnet work well? (in comparison to normal visual studio csproj) or are major features missing normally available in VS?
• Why did you do it? (cross platfrom dotnet build / multitarget version (VS10-15) or just because you like cmake?

If you could elabarate it would be greatly appreciated

Cancel mechanism of CTestExecutor does not always work

cancelling does not kill any child processes which are started from ctest

Add Support for integrated CMake support from Visual Studio

Currently CTestAdapter only works with generated solution which are opened using Visual Studio. When opening a CMake codebase with the new 2017 "open folder" mechanism, it does not work.

Not possible to install CTestAdapter v3.2.0 on Visual Studio 2017 update v15.6

Installation of CTestAdapter on Visual Studio 2017 Update 15.6 not possible.

Most probably because of changes in the version of some dependencies e.g. from 15.0 to 15.6 the installation is not allowed. After manually patching all manifest files of the vsix package, to refer to version [15.0,16.0) instead of [15.0] the installation was possible.

Clicking on the test in TestExplorer does not always point to the right line

Tests should be updated when Configuration is changed in Visual Studio.

Add some more verbose message when CTestAdapter is loaded

Should be configurable in the option page