Closed
Bug 617818
Opened 14 years ago
Closed 14 years ago
Need to be able to pass an expected build ID into the update test script
Categories
(Mozilla QA Graveyard :: Mozmill Automation, defect)
Mozilla QA Graveyard
Mozmill Automation
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gmealer, Assigned: whimboo)
References
Details
Attachments
(2 files)
2.56 KB,
patch
|
gmealer
:
review+
|
Details | Diff | Splinter Review |
4.58 KB,
patch
|
gmealer
:
review+
|
Details | Diff | Splinter Review |
We discussed this a bit yesterday, and I think we kind of agreed that taking it from the python script command line and sending it to the JS tests via the persisted object was the best bet.
However, I'm not in love with any one solution, so long as I can send in the expected ID and verify it during the test. Whatever works, works.
Reporter | ||
Comment 1•14 years ago
|
||
Henrik, going ahead and assigning to you per discussion yesterday. If that's premature, feel free to clear it.
Assignee: nobody → hskupin
Blocks: 617816
Assignee | ||
Comment 2•14 years ago
|
||
(In reply to comment #0)
> We discussed this a bit yesterday, and I think we kind of agreed that taking it
> from the python script command line and sending it to the JS tests via the
> persisted object was the best bet.
Right. There will be another option for the command line script. In the tests itself we will only run this comparison when the persisted property has been set. The reason is that we don't want to break tests executed by other users, who do not work with any trigger message.
I will put it on my list to have it ready by early next week.
Assignee | ||
Updated•14 years ago
|
Hardware: x86 → All
Assignee | ||
Comment 3•14 years ago
|
||
Patch for the software-update module, which adds another check for a target build id if given via the command line.
Attachment #497222 -
Flags: review?(gmealer)
Assignee | ||
Comment 4•14 years ago
|
||
Patch for the testrun_update automation script to accept a --target-buildid option and forward it to the update tests.
Attachment #497223 -
Flags: review?(gmealer)
Assignee | ||
Updated•14 years ago
|
Attachment #497222 -
Attachment description: Patch v1 → Patch v1 (tests)
Assignee | ||
Updated•14 years ago
|
Attachment #497223 -
Attachment description: Patch v1 → Patch v1 (scripts)
Reporter | ||
Comment 5•14 years ago
|
||
Comment on attachment 497222 [details] [diff] [review]
Patch v1 (tests)
Looks fine.
I think in this case you could have gone with just "if (!info.target_buildid)" since that'd also skip past blank strings, but what's there is fine too.
Attachment #497222 -
Flags: review?(gmealer) → review+
Reporter | ||
Comment 6•14 years ago
|
||
Comment on attachment 497223 [details] [diff] [review]
Patch v1 (scripts)
Looks great! Thanks bunches for the patch.
Attachment #497223 -
Flags: review?(gmealer) → review+
Assignee | ||
Comment 7•14 years ago
|
||
(In reply to comment #5)
> I think in this case you could have gone with just "if (!info.target_buildid)"
> since that'd also skip past blank strings, but what's there is fine too.
I think you wanted to say: "if (info.target_buildid)". That makes total sense! Thanks for catching it. I will checkin the updated patch.
Pushed both patches as:
http://hg.mozilla.org/qa/mozmill-automation/rev/b306e1053fcb
http://hg.mozilla.org/qa/mozmill-tests/rev/fd24cfe19aca
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 8•14 years ago
|
||
Hah, yeah, I did. Thanks for the correction!
Updated•11 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•