The NavigationSimulator provides a better interface for simulating navigations in unit tests than the fine grained methods of RenderFrameHostTester (in particular it provides correct swapping of test RFHs). We should convert unit tests to use it in order to ensure that they keep testing a correct interleaving of navigation events.
To do that, we need the following:
1) Extend NavigationSimulator to cover browser-initiated navigations.
2) Remove usage of RenderFrameHostTester::SimulateNavigationStart/SimulateRedirect/SimulateNavigationCommit/SimulateNavigationError/SimulateNavigationErrorPageCommit/SimulateNavigationStop in unit_tests, and remove these methods from the content/public/test API.
3) Consider moving away from those methods in content_unittests that don't test navigation specifically.
Comment 1 by clamy@chromium.org
, Jul 17 2017Owner: clamy@chromium.org
Status: Started (was: Untriaged)