Closed zotlann closed 3 months ago
Hi, I had the same problem. Upgrading the gtest library solved the issue, as older versions do not report the test file name in the json test results.
That makes sense, updating gtest to a new version for what I can seems to work. Unfortunately I can't do this for all of my work projects, but this will work for now. Thanks.
Hey! Sorry, not a whole lot of time to look into this during the holidays.
Could you please provide the gtest version that doesn't include the file path in results, so I can look for a workaround?
That said, using anything from Google and going against their "live at head" will likely yield other issues too.
I was actually able to work around my work build infrastructure stuff to use a newer version of gtest. We have to support older versions for reasons, but at least for local development I can use the newer versions usually without issue. The version I was running into this issue with was 1.10, not sure if it is worth the effort to add a workaround.
Thanks for your work on this!
Same problem here with version 1.10.
Any chance this can be solved without needing a newer version?
Looks like the only issue is knowing the file name from a test name, but this should be possible with the registry generated using ConfigureGtest
instead of from the GTest JSON output.
This happens whenever I try to run tests with this adapter, but is easily reproducible with my small aocpp repo. Steps to reproduce and full error output below.
./build.sh -c -b -g
:Neotest summary
.:ConfigureGtest
withoutput/bin/LibAOCPPUnit
TEST(Day01Test, Ascend)
lineError output:
neotest version:
neotest-gtest version:
nvim version:
neotest config: