-
-
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
Catch2 nested Sections not working properly #367
Comments
Thanks for looking into this issue. Remote debugging might prove difficult, I hope a complete log can help you:
|
Sadly, it is not.. :/ |
I have tried debugging this problem by myself and observed the following in the function Now I modified the code in the However, I was also able to determine why this bug only occurs on windows. In the |
Fixed in v4.3.8.This issue was mentioned in CHANGELOG.md under a released entry so it is assumed to be fixed. |
Nice work. Please verify it is working now. |
There is still a problem. Now the value of |
right.. |
Fixed in v4.3.10.This issue was mentioned in CHANGELOG.md under a released entry so it is assumed to be fixed. |
I can confirm,this has fixed the issue. Thanks a lot! |
Checklist
I understand that you have privacy concerns and I expect you to understand that this extension is developed for free.
Thanks.
Describe the bug
When using Catch2 (v3.1.1), repeated nested sections are not displayed properly. The Problem occurs if inside of a Section, there are two parallel Sections. See the following Code and Screenshot.
To Reproduce
Compile the following Unit Test. The Test "Bar" is either missing from the Test Explorer or displayed at the top level.
Screenshots
Desktop
Regression bug?
The oldest version I could Test ist 4.3.1, where the same error occurs. In all other Versions I just get an ENOENT during test discovery
Log
In the following Logs I have replaced the local paths with [PATH_TO_CPP] and [EXE_NAME].
C++ Testmate Log Output
Unit Test run Output with parameter
--reporter xml
The text was updated successfully, but these errors were encountered: