Closed
Bug 377790
Opened 18 years ago
Closed 16 years ago
Create buildbot scripts for running l10n tests in test farm
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: rcampbell, Unassigned)
Details
(Whiteboard: [l10n])
To verify the repack process, a number of tests will need to be added to an automated framework and run on a nightly basis (at minimum).
Order of operation should be (on each platform):
1) download en-US
2) download localized repacks
3) run ./verify_l10n.sh
4) run additional tests when available
Results can be reported to tinderbox and/or litmus.
Updated•17 years ago
|
Component: Testing → Release Engineering
Product: Core → mozilla.org
QA Contact: testing → release
Version: Trunk → other
Comment 1•17 years ago
|
||
If we still want to do this, and I'd say it's marginal value as is, it's certainly lower priority than other l10n tasks right now, so off to Future.
That said, if we'd had a check on complete mar files it would have caught bug 466894 before release time.
Component: Release Engineering → Release Engineering: Future
Updated•16 years ago
|
Whiteboard: [l10n]
Comment 2•16 years ago
|
||
Axel, we are doing triaging of futured bugs and we would like to hear your input on this. Is this still useful? If so could you extend on which tests would be useful to run.
Comment 3•16 years ago
|
||
I don't have any stakes in this bug.
This is about a continuous check how verify_l10n.sh would be doing in a release cycle. That might have value, but probably more for releng than for l10n.
Comment 4•16 years ago
|
||
Thanks Axel for your comments. We will triage accordingly.
Comment 5•16 years ago
|
||
I agree with comment #1, I don't think there's much value-added here.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
Comment 6•15 years ago
|
||
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
| Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•