Closed
Bug 613804
Opened 14 years ago
Closed 14 years ago
Provide an easy to use method for running mozmill tests
Categories
(Testing Graveyard :: Mozmill, defect)
Testing Graveyard
Mozmill
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 568642
People
(Reporter: ehsan.akhgari, Unassigned)
References
Details
If we expect developers to care about the Mozmill suite, we should provide them with an easy way to run the tests. Here's my proposal:
Given the assumption that objdir is your object directory built with --enable-tests, this should be all you need to run the suite:
make -C /path/to/objdir mozmill
And this should also work for running a single test:
make -C /path/to/objdir mozmill TEST_PATH=path/to/test.js
IMO this blocks actually caring about mozmill failures on m-c.
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Comment 3•14 years ago
|
||
I have a basic patch up at:
http://k0s.org/mozilla/hg/mozilla-central-patches/file/tip/bug-568642
It doesn't do mozmill-restart test nor does it do the TEST_PATH logic, but its not a horrible first stab.
This doesn't quite work, however, because automation-build.mk, included to find the path to the binary on all OSes, quotes the path to the binary:
http://mxr.mozilla.org/mozilla-central/source/build/automation-build.mk#10
I'll file a subsequent bug involving separating out the binary-finding logic from the rest of the script
Updated•14 years ago
|
Assignee | ||
Updated•8 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•