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
If I don't want to give each suite a unique name, I will also have to put them into an anonymous namespace. Depending on the project style guide, this can lead to 3 indention levels:
This produces huge diffs when porting from Boost.Test or other unit test frameworks. Is there a way to avoid this without having to turn-off clang-format for the suite?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've ported my unit tests from Boost.Test to UT and one thing I've noticed is, that while in Boost.Test I had multiple files with
in UT I need to create a suite:
If I don't want to give each suite a unique name, I will also have to put them into an anonymous namespace. Depending on the project style guide, this can lead to 3 indention levels:
This produces huge diffs when porting from Boost.Test or other unit test frameworks. Is there a way to avoid this without having to turn-off clang-format for the suite?
Beta Was this translation helpful? Give feedback.
All reactions