Closed
Bug 631665
Opened 14 years ago
Closed 12 years ago
Add Firebug test runner to buildbotcustom
Categories
(Release Engineering :: General, defect, P5)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: ahal, Unassigned)
References
Details
(Whiteboard: [testing][automation])
Attachments
(1 file, 4 obsolete files)
(deleted),
patch
|
Details | Diff | Splinter Review |
Add Firebug class to hg.mozilla.org/build/buildbotcustom/steps/unittest.py
Reporter | ||
Updated•14 years ago
|
Assignee: nobody → ahalberstadt
Status: NEW → ASSIGNED
Reporter | ||
Comment 1•14 years ago
|
||
WIP Patch, not sure if this will work yet. Here for reference.
Reporter | ||
Comment 2•14 years ago
|
||
Attachment #509917 -
Attachment is obsolete: true
Reporter | ||
Comment 3•14 years ago
|
||
Attachment #511598 -
Attachment is obsolete: true
Reporter | ||
Comment 4•14 years ago
|
||
See https://github.com/ahal/Firebug-Test-Runner/tree/buildbotInt for fb_run.py and installfirebug.py code.
Attachment #511601 -
Attachment is obsolete: true
Attachment #512880 -
Flags: review?
Attachment #512880 -
Flags: feedback?
Reporter | ||
Comment 5•14 years ago
|
||
Removes the fb_server and fb_version variables from unittest.py, this will be handled within the firebug runner code itself. See above link for the firebug runner code.
This works in our own buildbot staging environment but I ran into an issue where %(exepath)s resolved to 'firefox-bin' on linux instead of 'firefox' so I got some missing library errors. I left it the same way all the other PackagedTest classes do it in the hopes that the releng staging environment doesn't have this issue.
Finally this will need to be run on tryserver (also let me know if I should get someone else to review it).
Attachment #512880 -
Attachment is obsolete: true
Attachment #512880 -
Flags: review?
Attachment #512880 -
Flags: feedback?
Reporter | ||
Updated•14 years ago
|
Summary: Add Firebug tests to buildbotcustom's unittest.py → Add Firebug test runner to buildbotcustom
Reporter | ||
Updated•14 years ago
|
Assignee: ahalberstadt → nobody
Component: General → Release Engineering
Product: Testing → mozilla.org
QA Contact: general → release
Version: unspecified → other
Reporter | ||
Comment 6•14 years ago
|
||
Comment on attachment 513199 [details] [diff] [review]
Patch 1.3
Just some background. The Firebug team has a set of unit tests that they run and maintain on their own. What we're trying to do here is incorporate these tests into tinderbox so that we can figure out when there is a regression in Firefox that breaks Firebug.
Lukas, let me know if you have any questions or if I should throw the review to someone else.
-Andrew
Attachment #513199 -
Flags: review?(lsblakk)
Comment 7•14 years ago
|
||
Hi Andrew, I'll give this a run in staging and get back to you.
Assignee: nobody → lsblakk
Reporter | ||
Comment 8•14 years ago
|
||
Thanks, before you get too far, I forgot to mention that the code isn't checked into m-c yet.. we hope to have that done by the end of today.
Comment 9•14 years ago
|
||
Andrew: any news? Is the code checked in yet?
Reporter | ||
Comment 10•14 years ago
|
||
Last week I got really sick so didn't get anything done. The code was checked in over the weekend but we're still working on a way to get a webserver within the build network to run the tests (see bug 635019).
Right now it is configured to use http://10.250.5.0 so if the releng staging environment is on the office network then you should be able to go ahead and test it. Otherwise we'll need to wait for the above mentioned bug.
Sorry for keeping you in the dark :(
Comment 11•14 years ago
|
||
I'm out of office this week, working remotely so I'll check in on this again next week.
Comment 12•14 years ago
|
||
Comment on attachment 513199 [details] [diff] [review]
Patch 1.3
removing myself from review on this for now. Will need to see and have access to firebug/installfirebug.py and firebug/fb_run.py for testing in staging.
Attachment #513199 -
Flags: review?(lsblakk)
Comment 13•14 years ago
|
||
Also removing myself from the assignee for this bug - depending on when this is ready for testing I might be able to take it back, but ping releng in #build and we can see who is able to do so at the time.
Assignee: lsblakk → nobody
Status: ASSIGNED → NEW
Priority: -- → P5
Whiteboard: [testing][automation]
Comment 14•13 years ago
|
||
found in triage.
Component: Release Engineering → Release Engineering: Automation (General)
QA Contact: release → catlee
Reporter | ||
Comment 15•12 years ago
|
||
This is no longer a goal
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Assignee | ||
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•