Add some test coverage to keep data collection permissions in sync with gecko
Categories
(WebExtensions :: General, task, P2)
Tracking
(firefox142 fixed)
| Tracking | Status | |
|---|---|---|
| firefox142 | --- | fixed |
People
(Reporter: willdurand, Assigned: willdurand)
References
(Blocks 1 open bug)
Details
(Whiteboard: [addons-jira])
Attachments
(1 external file)
This is about adding a test to make sure the list of data collection permissions in gecko and Android are kept in sync. This is mainly about the localized strings for these permissions, since the permissions themselves are defined once in the gecko layer.
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
|
||
This patch allows us to keep the data collection permissions in sync
between Gecko, GeckoView and Android Components.
First, A new test helper has been added to the GeckoView layer so that
we can retrieve the list of permission names defined in the (toolkit)
WebExtensions JSON schemas.
In GeckoView, a new test guarantees that the set of data collection
permissions known by GeckoView (via the DATA_COLLECTION_PERMISSIONS
property) is the same as the one defined at the toolkit level. Since
data collection permissions might change over time, this will ensure
that we keep parity between Gecko and GeckoView.
The main reason for keeping all these permissions in sync is to make
sure Firefox for Android will get proper support, including localized
strings, etc. That's why the second part of this patch exposes the
GeckoView WebExtension.DATA_COLLECTION_PERMISSIONS property to the
GeckoWebExtension class in Android-Components, and a new test-only
dependency has been added to the feature-addons component, which is
where localized strings for data collection permissions are defined.
Now I am not entirely sure about this, but I cannot think of a different
way to cover the list of localized strings without duplicating the list
of permission names like it was done before this patch.
I opted to add a new property to the browser-engine-gecko so that we
don't need to deal with a GeckoView dependency in the feature-addons
(mainly because I doubt it's a trivial dependency declaration compared
to other libraries/components).
Updated•1 year ago
|
Updated•1 year ago
|
Comment 4•1 year ago
|
||
Reverted this because it was causing junit failures.
- Revert link
- Push with failures
- Failure Log
- Failure line: TEST-UNEXPECTED-FAIL | org.mozilla.geckoview.test.AutocompleteTest#loginSelectAccept | org.mozilla.geckoview.test.rule.GeckoSessionTestRule$RejectedPromiseException: InvalidStateError: An exception was thrown
| Assignee | ||
Updated•1 year ago
|
Backed out for causing junit failures @AutocompleteTest#loginSelectAccept.
Comment 9•1 year ago
|
||
| bugherder | ||
| Assignee | ||
Updated•1 year ago
|
Description
•