post-merge-day unittests

RESOLVED INCOMPLETE

Status

Release Engineering
Release Automation: Other
P3
normal
RESOLVED INCOMPLETE
5 years ago
4 years ago

People

(Reporter: aki, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
Not sure which component this goes in.

Our merge days are smoother, but we're still prone to missing things.
It would be useful to have a post-merge-day set of unittests to run, to verify things.

The unittests themselves can get out of date as time goes on; it might behoove us to run these weekly? if possible.

* mozconfig diffs
* checking branding type issues
* l10n checks?
* anything else that bites us
bug 763903 would probably cover the mozconfig part of this.
Priority: -- → P3
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
(Reporter)

Comment 2

4 years ago
We're going to be automating merge day, so any verification would happen as part of that.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.