Support older ctest without --output-junit support

[thewierdnut]

Would it be possible to support older ctest installs that don't have --output-junit support? A simple Yes/No based on the ctest return status would be sufficient for my purposes, but bonus points if you can parse the --log-output format.

I'm currently stuck using ctest version 3.16.3

[brobeson]

@thewierdnut, I've actually been thinking about archiving CTest Lab. The cmake-tools extension added CTest integration awhile back. I just assumed most users would go with that instead of installing another extension. That said, if there is still demand for CTest Lab, I'm open to maintaining and improving it.

bonus points if you can parse the --log-output format.

Did you mean the --output-log format? I don't see --log-output in the CTest 3.16.3 documentation.

[thewierdnut]

@thewierdnut, I've actually been thinking about archiving CTest Lab. The cmake-tools extension added CTest integration awhile back. I just assumed most users would go with that instead of installing another extension. That said, if there is still demand for CTest Lab, I'm open to maintaining and improving it.

I haven't been able to get cmake-tools working on my projects, mostly because the compiler structure I am forced to use doesn't match what cmake-tools expects to find. Its easy enough to directly run cmake with the relevant build arguments and environment I need. I mostly was just curious if there was a tool that I could point to a build directory to integrate a unit testing gui into vscode.

If you want to archive this project, don't let me stop you. I can modify it to suit my own needs, I was just hoping somebody who knew javascript better than I could handle it.

Did you mean the --output-log format? I don't see --log-output in the CTest 3.16.3 documentation.

Yes, sorry.

[brobeson]

I'll look into adding it. My thought is to release just the pass/fail/skipped status, then try to parse the actual test output. The test status output from CTest is pretty uniform, so that should be easy. The actual test output might be trickier since different test libraries have different output format.

[thewierdnut]

The actual test output might be trickier since different test libraries have different output format.

I would just stick to the ctest output, and not bother with the test binary output. The junit xml output doesn't give you anything better than the binary success/fail status either.