GitLab

During the module.json extensions migration, we discovered that these
two tests were breaking on the sources/network migration. However, many
other tests that use/interact with the sources and/or network panel are
passing. A closer investigation of these showed that they are relying on
an intricate loading order, which assumes the module.json loading. Since
we are changing the loading order, these tests start failing.

Taking a closer look at the intent of the tests, we realized that we
already have existing e2e-test coverage in the DevTools frontend.
Therefore, we propose removing the problematic tests to unblock the
extensions migration, while we maintain coverage through our e2e-tests.

R=aerotwist@chromium.org

Also-By: andoli@chromium.org
Bug: 1134103
Change-Id: I56a57d1c190897c8419b6c9c1a0b4c016966df52
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2584164
Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org>
Commit-Queue: Yang Guo <yangguo@chromium.org>
Auto-Submit: Tim van der Lippe <tvanderlippe@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#835671}