BrowserTests: Wait for content script updates as part of adding extensions |
|
Issue descriptionWe've seen flaky tests due to tests running *before* content scripts are updated. For example, see issue 895068 . Extension tests should wait for the update to be received by the renderer before proceeding with the test. Once this has been implemented, the stop-gap solution to deflake those tests should be removed. |
|
►
Sign in to add a comment |
|
Comment 1 by bugdroid1@chromium.org
, Dec 21