Litmus: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 16: Line 16:
* [[Litmus:Roadmap|Litmus Roadmap]]
* [[Litmus:Roadmap|Litmus Roadmap]]
* [[Litmus:Todo|Litmus To-Do List]]
* [[Litmus:Todo|Litmus To-Do List]]
* [[Litmus:Future Directions|Future Directions for Litmus]]
* [[Litmus:Wishlist|Feature Wishlist]]
* [[Litmus:DevelopersNotes|Litmus Developers' Notes]]
* [[Litmus:DevelopersNotes|Litmus Developers' Notes]]
** [[Litmus:mod_perl|mod_perl Notes]]
** [[Litmus:mod_perl|mod_perl Notes]]

Revision as of 16:48, 15 January 2007

Litmus is the new integrated testcase management and QA tool that is designed to improve workflow, visibility, 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.

Goals for Litmus

Litmus will:

  • make it easier for casual testers to assist with testing Mozilla products;
  • 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;
  • expose a web services interface for the mechanical batch submission of testing results.

Litmus will not:

  • manage the automation of testing requests as a centralized test scheduler or daemon. The majority of testing we do, and all of the community testing that we know of, is still done by hand. This doesn't preclude such functionality in the future, but we need to figure out the intricacies of how to automate a larger proportion of our daily testing before it makes sense to spend too much time on scheduling those automated tests. Existing automation frameworks will be able to submit results via web services.

Litmus Documentation and Notes

Designing and Planning

Installation

Using Litmus

Miscellaneous

Further Reading