Closed Bug 1686727 Opened 4 years ago Closed 3 years ago

Refactor tests using the storage actor directly to use it via resourceWatcher.watchResources([STORAGE_TYPES...])

Categories

(DevTools :: Storage Inspector, task, P3)

task

Tracking

(Fission Milestone:M8, firefox91 fixed)

RESOLVED FIXED
91 Branch
Fission Milestone M8
Tracking Status
firefox91 --- fixed

People

(Reporter: ochameau, Assigned: ochameau)

References

(Regressed 1 open bug)

Details

(Whiteboard: dt-fission-m3-mvp)

Attachments

(5 files)

Bug 1644192 dependencies are going to make the storage actor unused by DevTools frontend. Only tests and may be some external tools using RDP may be using this old codepath.
devtools/server/actor/storage.js will still be used via storage Watcher classes, but no longer as a target-scoped actor.

We should refactor the tests in order to cover the new codepath, using ResourceWatcher API.
i.e. resourceWatcher.watchResources([STORAGE_TYPES...])
"STORAGE_TYPES..." will be COOKIE, INDEXEDDB, LOCAL_STORAGE, ...

I think that's only these 6 tests:
https://searchfox.org/mozilla-central/search?q=listStores%28%29&path=&case=false&regexp=false
Note that all storage panel tests should be using the panel code and so the ResourceWatcher codepath. Here we only have to refactor tests manually querying the storage front.

Tracking dt-fission-m3-mvp bugs for Fission M7 (blocking Beta experiment).

Fission Milestone: --- → M7
Severity: -- → S3
Priority: -- → P3

Tracking dt-fission-m3-mvp test and infrastructure bugs for Fission M8 (blocking Release experiment).

Fission Milestone: M7 → M8

Tracking DevTools Post-M8 bugs for Fission MVP milestone. They don't block the Fission Release channel experiment, but we would like them to be completed before we roll out Fission by default.

Fission Milestone: M8 → MVP
No longer blocks: 1644397
Blocks: 1698891
Fission Milestone: MVP → M7a
Fission Milestone: M7a → MVP
Depends on: 1713810

We should stop using StorageActor.listStores in favor of ResourceCommand.
listStores still forces to involve message manager in the server codebase.
This breaks when we enable JSWindowActor based targets.

We should stop using StorageActor.listStores in favor of ResourceCommand.
listStores still forces to involve message manager in the server codebase.
This breaks when we enable JSWindowActor based targets.

We should stop using StorageActor.listStores in favor of ResourceCommand.
listStores still forces to involve message manager in the server codebase.
This breaks when we enable JSWindowActor based targets.

We should stop using StorageActor.listStores in favor of ResourceCommand.
listStores still forces to involve message manager in the server codebase.
This breaks when we enable JSWindowActor based targets.

This test is not relevant in fission as we aren't using listStores,
nor do we have any EXTENSION_STORAGE resource to test yet.

Assignee: nobody → poirot.alex
Status: NEW → ASSIGNED
Fission Milestone: MVP → M8
Pushed by apoirot@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/bcb1103c708d
[devtools] Migrate browser_storage_updates to ResourceCommand. r=ladybenko
https://hg.mozilla.org/integration/autoland/rev/6f5900fd6c02
[devtools] Migrate browser_storage_listing to ResourceCommand. r=ladybenko
https://hg.mozilla.org/integration/autoland/rev/f59fc0817dd9
[devtools] Migrate browser_storage_cookies-duplicate-names to ResourceCommand. r=ladybenko
https://hg.mozilla.org/integration/autoland/rev/5a4f2fe5ee61
[devtools] Disable browser_storage_webext_storage_local on fission. r=ladybenko
https://hg.mozilla.org/integration/autoland/rev/c9d6f02ad2f6
[devtools] Migrate browser_storage_dynamic_windows to ResourceCommand. r=ladybenko
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: