Closed
Bug 771029
Opened 13 years ago
Closed 13 years ago
Use relative paths of tests for test_start and test_end events
Categories
(Testing Graveyard :: Mozmill, defect)
Testing Graveyard
Mozmill
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: whimboo, Assigned: whimboo)
References
Details
Attachments
(1 file, 1 obsolete file)
Showing only the filename of the test as run by Mozmill is not that helpful:
TEST-START | test1.js | setupModule
TEST-START | test1.js | testInstallTheme
The test object should have a relpath property which gives us the relative path to the root manifest:
TEST-START | restartTests/testAddons_changeTheme/test1.js | setupModule
TEST-START | restartTests/testAddons_changeTheme/test1.js | testInstallTheme
This will help a lot with debugging the tests and also for our dashboard so that we no longer have to determine that folder on our own.
A fix for this issue will be dependent on a manifestparser update, which I will file in a bit.
| Assignee | ||
Comment 1•13 years ago
|
||
Pointer to Github pull-request
| Assignee | ||
Comment 2•13 years ago
|
||
Comment on attachment 639206 [details]
Patch
This patch will make use of relpath if available. Otherwise it will fallback to the absolute path of the test.
Attachment #639206 -
Attachment description: Pointer to Github pull request: https://github.com/mozautomation/mozmill/pull/63 → Patch
Attachment #639206 -
Flags: review?(jhammel)
Comment 3•13 years ago
|
||
(In reply to Henrik Skupin (:whimboo) from comment #2)
> Comment on attachment 639206 [details]
> Patch
>
> This patch will make use of relpath if available. Otherwise it will fallback
> to the absolute path of the test.
I'll review this after bug 771030 is landed. Also, this will require mozmill to use the new (and as yet unreleased) ManifestDestiny
Comment 4•13 years ago
|
||
Comment on attachment 639206 [details]
Patch
taking this down for review as the dependent bug isn't landed
Attachment #639206 -
Flags: review?(jhammel)
| Assignee | ||
Updated•13 years ago
|
| Assignee | ||
Updated•13 years ago
|
Comment 5•13 years ago
|
||
(In reply to Jeff Hammel [:jhammel] from comment #4)
> Comment on attachment 639206 [details]
> Patch
>
> taking this down for review as the dependent bug isn't landed
Hmmm...and now that the blocking bug is fixed this gives me a 404
| Assignee | ||
Comment 6•13 years ago
|
||
Comment on attachment 639206 [details]
Patch
Because the mozmill repository has been moved. I will create a new request.
Attachment #639206 -
Attachment is obsolete: true
| Assignee | ||
Comment 7•13 years ago
|
||
Pointer to Github pull-request
| Assignee | ||
Updated•13 years ago
|
Attachment #650291 -
Flags: review?(jhammel)
Comment 8•13 years ago
|
||
Comment on attachment 650291 [details]
Pointer to Github pull request: https://github.com/mozilla/mozmill/pull/63
Looks good to me. You may also want to bump the required version of ManifestDestiny for mozmill (which, to be fair, isn't released yet: bug 781105)
Attachment #650291 -
Flags: review?(jhammel) → review+
| Assignee | ||
Comment 9•13 years ago
|
||
Updated pull request with a follow-up comment which bumps ManifestDestiny to 0.5.5. Lets wait for bug 781105 now.
Whiteboard: [needs manifestdestiny=0.5.5 before landing]
| Assignee | ||
Comment 10•13 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Whiteboard: [needs manifestdestiny=0.5.5 before landing]
Updated•9 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•