Closed Bug 563535 Opened 15 years ago Closed 14 years ago

Create a daily test-run script which can be used by crontab

Categories

(Mozilla QA Graveyard :: Mozmill Automation, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: whimboo, Assigned: whimboo)

References

Details

We have to update our crontab scripts on OS X and Linux, and the scheduled tasks on Windows to not start the next tests while the current ones are still running. The best would be to have a wrapper script which executes all tests in a row and only requires a single entry in the crontab.
Summary: Update crontab scripts to use the new automation scripts → Update crontab scripts to use the new automation scripts for daily test-runs
I put a script up on github which let us run our daily test-runs against installed builds. All the configuration happens inside an ini file so the script can be used for different platforms. http://github.com/whimboo/mozmill/commit/8e442ab93357deb664820675ffde4c1a294564c4 Jeff, would be great if you could take a look at it. Thanks.
Summary: Update crontab scripts to use the new automation scripts for daily test-runs → Create a daily test-run script which can be used by crontab
see notes on github: see http://github.com/whimboo/mozmill/commit/8e442ab93357deb664820675ffde4c1a294564c4#commitcomment-81824 and http://github.com/whimboo/mozmill/commit/8e442ab93357deb664820675ffde4c1a294564c4#commitcomment-81816 As stated, I would put whatever config-file parsing directly into the parser(s) (e.g. http://github.com/whimboo/mozmill/blob/8e442ab93357deb664820675ffde4c1a294564c4/scripts/firefox-automation/testrun_bft.py#L48 ) and set the environment variable in the crontab. But this is all a nice to have and non-blocking. Looks fine (except for the ('darwin') vs ('darwin',) error which should be fixed).
I have fixed the mentioned error and pushed it to the master. Everything works and I will follow up with the remaining items later. Thanks Jeff! So you would suggest that we also give the testrun class itself the possibility to read an ini file to scan for default values? Sounds like a good idea.
(In reply to comment #3) > I have fixed the mentioned error and pushed it to the master. Everything works > and I will follow up with the remaining items later. Thanks Jeff! > > So you would suggest that we also give the testrun class itself the possibility > to read an ini file to scan for default values? Sounds like a good idea. This is what I would do. It provides additional functionality and eliminates the need for a front-end script. You can look at some example code I put up that does something like this: http://k0s.org/hg/ConfigOptionParser/ (there is also a pypi package) It may/may not be sufficient for your purposes OOTB, but maybe it will give some ideas.
Assignee: hskupin → nobody
Component: Mozmill → Mozmill Tests
QA Contact: mozmill → mozmilltests
Move of Mozmill related project bugs to newly created components. You can filter out those emails by using "Mozmill-Tests-to-MozillaQA" as criteria.
Component: Mozmill Tests → Mozmill Automation
Product: Testing → Mozilla QA
QA Contact: mozmill-tests → mozmill-automation
Whiteboard: [mozmill-automation]
Version: Trunk → unspecified
I don't want to keep this bug longer open. We have such a script for a long time now. It's not perfect but it works. It will soonish replaced by a complete new system, once we transitioned over to probably Selenium.
Assignee: nobody → hskupin
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.