Closed Bug 872319 Opened 11 years ago Closed 10 years ago

post-merge-day unittests

Categories

(Release Engineering :: Release Automation: Other, defect, P3)

Product:
Release Engineering
Component:
Release Automation: Other
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: mozilla, Unassigned)

Details

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
Product: mozilla.org → Release Engineering
We're going to be automating merge day, so any verification would happen as part of that.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.