Open Bug 1147008 Opened 9 years ago Updated 2 years ago

Uninstalls of GMPs should have additional tests

Categories

(Firefox :: General, defect, P3)

38 Branch
x86
macOS
defect

Tracking

()

People

(Reporter: spohl, Unassigned)

References

Details

We've added the ability to uninstall GMPs (see meta bug 1142655 and the dependent bugs there). We should review our test coverage and add new tests as necessary.
Stephen: what work is left for the uninstall tests? Who should own this?
Flags: needinfo?(spohl.mozilla.bugs)
Priority: -- → P2
This list is from the top of my head and makes no claim to be comprehensive:
1. Verify that old GMP has been physically removed from disk after an update by verifying that the path no longer exists.
2. When a DRM-free repack is launched, all CDMs are physically removed from disk. This could be simulated by setting media.eme.enabled=false in prefs.js before launching Firefox during the test.
3. Check for sane behavior when a GMP is updated while in use. This may require additional client-side changes to delay the removal of the old GMP, or we may choose to just leave the old GMP on disk and implement the general GMP cleanup in bug 1053729.

As mentioned in comment 0, we should go through all the dependent bugs in bug 1142655 and make sure that we have sufficient test coverage.

I'm happy to look into this once my other priorities have been taken care of. Unfortunately, this may well take several weeks.
Flags: needinfo?(spohl.mozilla.bugs)
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.