Testrunner

Introduction

Testrunner is a test development tool built on top of Bugzilla, located at http://testrunner.mozilla.org --where QA (quality assurance) can create, modify and monitor test plans, test cases, test runs and test results.

Examples of other Testrunner installations:

• Eduardo Fuentetaja's server running v0.6.1-beta: http://testrunner.citat.se/

• Opi's server running a recent CVS pull (Warning: Under development! Might go poof at any time, but ideally this is what Seamonkey QA might use): http://www2.le-bit.de/bugzilla/index.cgi

To-do list

1. Upgrade from Testrunner 0.2 to 0.6 (or whatever the most recent version).
2. Migrate existing test plans, functional groups and test cases into the more recent Testrunner version. Also, ensure that they remain accessible and useable in the new version.
3. More seamless integration with the https://bugzilla.mozilla.org (b.m.o.) database, such as
   1. Allowing bug links in test cases and results (regardless of result status).
   2. Cross-referencing products and components from b.m.o. into Testrunner, instead of recreating them.
4. Define (and publically document) usage guidelines for Testrunner, such as describing priviledges, outlining typical workflow, etc. This might also include a tutorial (as time permits).
5. Improve Testrunner UI:
   1. Clarify navigation amongst test plans, test cases, test runs and test results.
   2. Improve maintenance, creation/editing and monitoring of test plans, test cases, test runs and test results.
   3. Allow for easier entry of comments for test runs and test cases.
6. Integrate with Mister:Home Page, the proposed tool to integrate https://update.mozilla.org (u.m.o.), Bouncer, the build systems (including Tinderbox/Bonsai), QA (noteably Testrunner and b.m.o.) and the release process.
7. Integrate with other QA tools (Eggplant? Smoketest extension?)
8. Integrate with Talkback (tracking build ids, test results, crash bugs, etc.)