Litmus: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
No edit summary
 
(63 intermediate revisions by 11 users not shown)
Line 1: Line 1:
__NOTOC__
'''<span style="font-size:24px;color:red">NOTE: Litmus is no longer being maintained. It was replaced by [https://moztrap.readthedocs.org/en/latest/ MozTrap]</span>'''
<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 will:
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 was originally designed as a replacement for [[Testrunner]], but also has additional functionality.
 
== Work in Progress ==
 
* [[Litmus:Extension|QA Extension Project]]
* [[Litmus:Todo|Litmus To-Do List]]
 
== Goals for Litmus ==
Litmus does:
* 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 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.;
* 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 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;
* expose a web services interface for the mechanical batch submission of testing results.
* manage the automation of testing requests &mdash; one-time, and recurring (e.g. from [http://tinderbox.mozilla.org/showbuilds.cgi tinderbox]) &mdash; on a new group of dedicated testing servers, managing priorities appropriately;
 
* expose an API to allow developers to work with the various tools easily outside of a graphical environment.
Litmus does not:
</div>
* 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===
* [[Litmus:Requirements|Requirements]]
* [[Litmus:Design|Design]]
** [[Litmus:Design/Auth|Authentication System Design]]
* [[Litmus:Web Services|Web Services]]
** Result Submission Service:
*** [[Litmus:Test Result Format DTD|Test Result Format (DTD)]]
*** [[Litmus:bsmedbergWebServices|bsmedberg's notes on Litmus Web Services]]
*** [[Litmus:EggplantIntegration|Getting results from Eggplant into Litmus]]
** Testcase Retrieval Service:
*** [[Litmus:Test_Format_DTD|Test Format DTD]]
* [[Litmus:Roadmap|Roadmap]]
** [[Litmus:Todo|To-Do List]]: a list of what's in progress, and what remains to be done. Please check here before suggesting new features or filing new bugs.
** [[Litmus:Wishlist|Feature Wishlist]]
 
=== Development ===
Interested in helping with Litmus? Start here.
* [[Litmus:DevelopersNotes|Developers' Notes]]
** [[Litmus:mod_perl|mod_perl Notes]]
 
===Installation===
 
Litmus is released under the [http://www.mozilla.org/MPL/ MPL].
 
* [[Litmus:Hg|How to clone Litmus from hg.mozilla.org]]
* [http://mxr.mozilla.org/mozilla/source/webtools/litmus/INSTALL INSTALL doc] (from [http://mxr.mozilla.org/ mxr])
* [[Litmus:InstallFAQ|Litmus Install FAQ]]
* Verifying Your Litmus Install
** [[Litmus:Test Suite|Command-line verifications]]
** [[Litmus:Selenium|Selenium  Tests]]
 
===Using Litmus===
* For Users:
** [http://quality.mozilla.org/documents-home/test-docs/litmus-tutorial Litmus Tutorial]
* For Admins:
** [http://quality.mozilla.org/documents-home/test-docs/admin-tutorial Admin Tutorial]
** [[Litmus:Adding Testcases to Litmus|Adding Testcases to Litmus]]
** [[Litmus:Syncing testcases between subgroups|Syncing testcases between subgroups in Litmus]]
** [[Litmus:How to Triage Failed and Unclear test cases|How to Triage Failed and Unclear test cases]]
 
===Miscellaneous===
* [http://hg.mozilla.org/webtools/litmus recent commits to Litmus (hg)]
* Litmus Session Notes
** [[2005Offsite/LitmusFutures|Notes from the 2005 Litmus BOF session]]
** [[Summit2008/Session/Proposals/Litmus_QAC|Notes from the 2008 Litmus Summit session]]
 
== Further Reading ==
* [[Mozilla_QA|Mozilla QA]]
*[http://quality.mozilla.org QMO]

Latest revision as of 15:21, 27 April 2015

NOTE: Litmus is no longer being maintained. It was replaced by MozTrap

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 was originally designed as a replacement for Testrunner, but also has additional functionality.

Work in Progress

Goals for Litmus

Litmus does:

  • 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 does 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

Development

Interested in helping with Litmus? Start here.

Installation

Litmus is released under the MPL.

Using Litmus

Miscellaneous

Further Reading

Retrieved from "https://wiki.mozilla.org/index.php?title=Litmus&oldid=1070457"