22
edits
Bugzilla:Infrastructure: Difference between revisions
→cg-bugs01.mozilla.org: Firefox and Selenium Server updated.
(Centralize server version info and add DNS services) |
(→cg-bugs01.mozilla.org: Firefox and Selenium Server updated.) |
||
| Line 33: | Line 33: | ||
*Uses Tinderbox Client v2.01 to run Perl, Docs, QA, Xt and checksetup Bugzilla test suites. | *Uses Tinderbox Client v2.01 to run Perl, Docs, QA, Xt and checksetup Bugzilla test suites. | ||
*Reports test results to the Tinderbox Server maintained by Mozilla. See [http://tinderbox.mozilla.org/Bugzilla/ tinderbox.mozilla.org/Bugzilla/] for latest results. | *Reports test results to the Tinderbox Server maintained by Mozilla. See [http://tinderbox.mozilla.org/Bugzilla/ tinderbox.mozilla.org/Bugzilla/] for latest results. | ||
*Current activity of the tests can be viewed by attaching to a screen session | *Current activity of the tests can be viewed by attaching to a screen session running under the ''tinderbox'' user. There's two sessions, one for QA tests (named ''qa'') and one for all the other tests (named ''tbox''). Use commands '''screen -r qa''' or '''screen -r tbox''' to attach. | ||
*Selenium Server v2. | *Selenium Server v2.5.0, Test::WWW::Selenium Perl module v1.24 and Firefox v6.0.2 are used by the QA tests. Be careful when updating these so that the trees won't burn unnecessarily. | ||
*Selenium Server | *Selenium Server is manually installed to the '''/usr/local/share/selenium-server/''' directory. Scripts to start it and to list related processes are in the '''/usr/local/bin/''' directory. | ||
* | *Firefox is manually installed to the '''~/firefox-6.0.2/''' directory of the ''tinderbox'' user. The system has Firefox v3.6.x but it's not used for the tests. | ||
*The perl-Test-WWW-Selenium package is installed/updated from Repoforge (previously known as RPMforge) but is excluded from normal yum updates so it needs to be manually updated (use '''yum update --disableexcludes=rpmforge perl-Test-WWW-Selenium''' command) when needed. | |||
*Any local RPM building should be done when logged in as the user ''build'' because that user has the correct RPM build environment configured. | *Any local RPM building should be done when logged in as the user ''build'' because that user has the correct RPM build environment configured. | ||