You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am aware that with GUnit there is no more need to have the SetUp and TearDown method declarations, but in my tests I still have it for my own organization.
So while using GUnit, I see that the SetUp method is being called twice. Find the stack of the first and second call attached.
You can see that in the second call the only difference is the extra GTEST<>::TestBody() call.
I see that there is a call in line 247 and 249 of GTest.h. After commenting it stops to call it twice.
I am not very familiar with the internals, is there a reason to call the SetUp and TearDown there?
The text was updated successfully, but these errors were encountered:
rafaelBauer
changed the title
SetUp or Test constructor is called twice
SetUp and TearDown being called twice
Sep 8, 2022
I am aware that with GUnit there is no more need to have the SetUp and TearDown method declarations, but in my tests I still have it for my own organization.
So while using GUnit, I see that the SetUp method is being called twice. Find the stack of the first and second call attached.
You can see that in the second call the only difference is the extra GTEST<>::TestBody() call.
I see that there is a call in line 247 and 249 of GTest.h. After commenting it stops to call it twice.
I am not very familiar with the internals, is there a reason to call the SetUp and TearDown there?
The text was updated successfully, but these errors were encountered: