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
It would be very useful to be able to ignore GTEST_SKIP() through a command-line flag (just like DISABLED_).
A common scenario is that big important changes in a project may cause tests deemed of lesser importance to fail, so these tests are disabled/skipped to not block progress but they still need to be looked into at a later point. If instead of requiring code changes to re-enable them locally, we could run them with a simple flag added to the command line, that would streamline debugging and avoid mistakes.
The text was updated successfully, but these errors were encountered:
The --gtest_also_run_disabled_tests command-line flag forcibly run all the DISABLED_ tests, although it doesn't (to my knowledge) circumvent the GTEST_SKIP() macro.
c0d1f1ed
changed the title
Running skipped or disabled tests
Flag to also run skipped tests
May 16, 2022
The --gtest_also_run_disabled_tests command-line flag forcibly run all the DISABLED_ tests, although it doesn't (to my knowledge) circumvent the GTEST_SKIP() macro.
Thanks for pointing that out! It was indeed a GTEST_SKIP()'ed test I was trying to run, and I assumed DISABLED_ was also missing a flag to force running them. I've adjusted the request.
It would be very useful to be able to ignore
GTEST_SKIP()
through a command-line flag (just likeDISABLED_
).A common scenario is that big important changes in a project may cause tests deemed of lesser importance to fail, so these tests are disabled/skipped to not block progress but they still need to be looked into at a later point. If instead of requiring code changes to re-enable them locally, we could run them with a simple flag added to the command line, that would streamline debugging and avoid mistakes.
The text was updated successfully, but these errors were encountered: