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)

defect
Not set
normal

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.
Depends on: 771030
Attached file Patch (obsolete) —
Pointer to Github pull-request
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)
(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 on attachment 639206 [details] Patch taking this down for review as the dependent bug isn't landed
Attachment #639206 - Flags: review?(jhammel)
Depends on: 781105
Blocks: 781105
No longer depends on: 781105
No longer blocks: 781105
Depends on: 781105
(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
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
Attachment #650291 - Flags: review?(jhammel)
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+
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]
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Whiteboard: [needs manifestdestiny=0.5.5 before landing]
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: