Litmus

Litmus is the new integrated testcase management and 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 Documentation and Notes

• Litmus Roadmap
• Litmus To-Do List
• Litmus Developers' Notes
• Litmus Requirements
• Litmus Design
• Test Result Format (DTD)
• Test case management ideas

• View a list of recent checkins to Litmus in CVS (Bonsai)

Goals for Litmus

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.

Litmus will not:

• be released as a standalone product such as, e.g., Bugzilla, at least not in the 1.0 timeframe. We are trying not to paint ourselves into a corner where this is concerned, but many of the decisions and tradeoffs we're making are necessarily Mozilla-centric at this point. Still, the code is in CVS if you want to try your luck or help out.

Further Reading

• Mozilla QA