chrome_test_util::AssertMainTabCount is a method that actually waits for the tab count to become an expected number. I'm not exactly sure why the wait was added at the first place, but if it waits, then it should be called waitForMainTabCount.
Sorry, I missed the question.
Yes, I think your understanding makes sense. Perhaps make a [ChromeEarlGrey waitForMainTabCount], which could call an underlying method chrome_test_util::GetMainTabCount (that does no waiting).
Comment 1 by liaoyuke@chromium.org
, Jun 21 2017