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
Using ASSERT_* macros inside a lambda that returns void (like this callback) will only exit the lambda, not the entire test case. If the assertion fails, the rest of the test in the main thread will continue to execute, potentially leading to confusing results or crashes if subsequent code depends on the assertion. Use EXPECT_* instead, or a mechanism to propagate the failure to the main thread.
ASSERT_FALSE is intentional here. I want the assertion to terminate the callback if no technologies are returned, while allowing the test to continue so that the final ASSERT_TRUE(called) reports that the tethering callback was never invoked. This gives us both relevant failure messages.
Activity
EddyTheCo commentedon Aug 21, 2026
ASSERT_FALSE is intentional here. I want the assertion to terminate the callback if no technologies are returned, while allowing the test to continue so that the final ASSERT_TRUE(called) reports that the tethering callback was never invoked. This gives us both relevant failure messages.