Litmus: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 9: Line 9:
* provide a request interface whereby developers can queue testing requests for patches, fixes, and regressions;
* provide a request interface whereby developers can queue testing requests for patches, fixes, and regressions;
* manage the automation of testing requests — one-time, and recurring (e.g. from [http://tinderbox.mozilla.org/showbuilds.cgi tinderbox]) — on a new group of dedicated testing servers, managing request priorities appropriately;
* manage the automation of testing requests — one-time, and recurring (e.g. from [http://tinderbox.mozilla.org/showbuilds.cgi tinderbox]) — on a new group of dedicated testing servers, managing request priorities appropriately;
* expose an API to allow developers to work with the various tools easily outside of a graphical environment.
* expose an API to allow developers to work with the various tools easily outside of a graphical environment;
* make it easier for casual testers to assist with testing Mozilla products.
</div>
</div>



Revision as of 17:56, 7 July 2005

Litmus is the new integrated QA tool that is designed to improve workflow and turnaround time in the Mozilla QA process. It is first and foremost designed as a replacement for Testrunner, but will also have additional functionality.

Litmus will:

  • serve as a repository for test cases, with all the inherent management abilities that implies;
  • serve as a repository for test results, carrying over the best features of Testrunner, e.g. test lists, division of labor, etc.;
  • provide a query interface for viewing, reporting on, and comparing test results;
  • provide a request interface whereby developers can queue testing requests for patches, fixes, and regressions;
  • manage the automation of testing requests — one-time, and recurring (e.g. from tinderbox) — on a new group of dedicated testing servers, managing request priorities appropriately;
  • expose an API to allow developers to work with the various tools easily outside of a graphical environment;
  • make it easier for casual testers to assist with testing Mozilla products.

Further Reading