Litmus: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
__NOTOC__
<div>
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 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.
If your question isn't answered by this site, you can email [http://www.zachlipton.com/email.png Zach Lipton] or post a question on one of these WikiPages.
== Litmus Documentation and Notes ==
* [[Litmus:Todo|Litmus To-Do List]]
* [[Litmus:Requirements|Litmus Requirements]]
* [[Litmus:Test Result Format DTD|Test Result Format (DTD)]]
* [[TestcaseManagementIdeas|Test case management ideas]]
== Goals for Litmus ==
Litmus will:
Litmus will:
* serve as a repository for test cases, with all the inherent management abilities that implies;
* serve as a repository for test cases, with all the inherent management abilities that implies;
Line 11: Line 19:
* 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.
* make it easier for casual testers to assist with testing Mozilla products.
</div>


== Further Reading ==
== Further Reading ==
* [[Litmus:Requirements|Litmus Requirements]]
* [[Mozilla_QA|Mozilla QA]]
* [[Litmus:Test Result Format DTD|Test Result Format (DTD)]]
* [[TestcaseManagementIdeas|Test case management ideas]]

Revision as of 21:34, 27 July 2005

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.

If your question isn't answered by this site, you can email Zach Lipton or post a question on one of these WikiPages.

Litmus Documentation and Notes

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.

Further Reading