MV3: Dapp Interactions Test Cases

[hilvmason]

• Ensure user remains connected to a Dapp after service worker re-start

NOTE: Remove or replace previous test that is currently failing on the mv3 folder.

• Ensure user can connect to various Dapps and remains connected to all of them after service worker re-start

• Ensure dapp functionality is preserved after service worker re-start

• Reenable mv3 tests running on the pipeline.

We are currently piping the test errors coming from the mv3 test script that runs in the PR pipeline for it to fail silently.

That bypass is made here.

[tmashuang]

The current status of MV3 as of this comment pertaining to dapp interactions is that any dapp that sends transactions will break the user experience after restarting the service worker.

[danjm]

Hey team! Please add your planning poker estimate with Zenhub @brad-decker @DDDDDanica @pedronfigueiredo @PeterYinusa

[gauthierpetetin]

This ticket may no longer be required as if all goes well, we won't have to re-start service worker.
Google said service workers will not have to be restarted but this needs to be confirmed.
We'll keep this ticket open until we have more info about service worker persistence.
In case there are edge cases, where service workers get disconnected, we'll have to refine this ticket more, and test Extension behaviour when we kill the service worker manually.

We'll have more info once our E2E tests work with MV3: #21496