SeaMonkey:QA:Testrunner

Revision as of 18:01, 10 September 2005 by Ajschult (talk | contribs) (initial version, mostly by opi)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

How we want organize Testrunner testing

We will use testrunner on http://www2.le-bit.de/bugzilla to manage the testrunns.

We will have 2 groups. The managers group can edit the testcases and manage the testruns. The runners group can run the testruns and mark them ok or failed.

The managers group will start new runs periodicaly or after request on IRC.

The runners group can work through the open testcases. Please look into the name of the testrun and ensure it is for YOUR system and that you test with the same Build ID. If you would like to run a testrun that do not exists, ask one in the managers group to start one.

If a testcase (one task out of the testrun) does not work properly, search bugzilla for an existing bugreport. If no such bug exists, file a new bug, add the "smoketest" keyword. But do not use the bugzilla system on the testrunner server use the normal https://bugzilla.mozilla.org/ but leave a note in bug and on the testcase that failed.

About starting testruns

Naming schema for starting testruns:

" SeaMonkey [trunk/branch] $buildid [Linux gtk1|Linux gtk2|Win95|Win98|WinME|Win2000|WinXP|MaxOSX 10.4]" Maybe something else as System (like Linux gtk2 MNG). The $buildid can be read out of the directory where the install files/package lay out or from the window title bar.

Please run the SeaMonkey Nightly and the SeaMonkey Alpha Milestone plan in rotating way for the testruns you start.

Managers Group

Andrew Schultz (ajschult), Alexander Opitz (opi), Carsten Book (Tomcat)

Testers Group