-
-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[GoogleTest] Invalid test in test list #55
Comments
Could you comment the output of your executable with argument: |
I got it and fixed it. Gonna release soon. (version>2.3.13) But I would like to see your logfile please. (generated with the new version) My fix will filter it (and it will work), but the reason I am asking you log is because somehow the xml generation or processing fails in your case. |
If you have time @OpenNingia the log would be appreciated. :) |
Sorry for the late, I'll send you the log file asap |
Here is the logfile, I redacted some of the paths but it should be readable. |
Thank. Was the log created with the version > 2.3.13? Here is how the parser works:
In your case phase 2 fails, but I don't understand why. The problem was in the 3th phase. There is an extra line what the parser couldn't handle (fixed), but still cant see why is 2th phase fails in your case. If you have time you could run the test executable with the example and analyse what happening. If we can solve it the "jump to test" button will work again in your case too (xml contains file&line info, but output doesn't). |
aparently my version of GTest doesn't support |
It crossed my mind. |
Before you file an issue, please check the README.md's known issues section.
Describe the bug (A clear and concise description of what the bug is.)
In the test list of my project I find a strange test:
Running main() from gmock_main.c
Running this test does nothing.
To Reproduce (Steps to reproduce the behavior:)
It's always there.
Expected behavior (A clear and concise description of what you expected to happen.)
That test shouldn't be there.
Screenshots (If applicable, add screenshots to help explain your problem.)
Desktop (please complete the following information):
Version: 1.30.2 (user setup)
Commit: 61122f88f0bf01e2ac16bdb9e1bc4571755f5bd8
Date: 2019-01-07T22:54:13.295Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
OS: Windows_NT x64 10.0.15063
Log (Attach log. (optional, Set:
catch2TestExplorer.logfile
and reproduce the bug.) Warning: Log probably contains file and test names too.)Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: