Litmus: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(25 intermediate revisions by 5 users not shown)
Line 1: Line 1:
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.  
'''<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>'''
 
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 ==
== Goals for Litmus ==
Litmus will:
Litmus does:
* make it easier for casual testers to assist with testing Mozilla products;
* 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;
Line 9: Line 18:
* expose a web services interface for the mechanical batch submission of testing results.
* expose a web services interface for the mechanical batch submission of testing results.


Litmus will not:
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.
* 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 ==
== Litmus Documentation and Notes ==
===Designing and Planning===
===Designing and Planning===
* [[Litmus:Roadmap|Litmus Roadmap]]
* [[Litmus:Requirements|Requirements]]
* [[Litmus:Todo|Litmus To-Do List]]
* [[Litmus:Design|Design]]
* [[Litmus:Future Directions|Future Directions for Litmus]]
* [[Litmus:Wishlist|Feature Wishlist]]
* [[Litmus:DevelopersNotes|Litmus Developers' Notes]]
** [[Litmus:mod_perl|mod_perl Notes]]
* [[Litmus:Requirements|Litmus Requirements]]
* [[Litmus:Design|Litmus Design]]
** [[Litmus:Design/Auth|Authentication System Design]]
** [[Litmus:Design/Auth|Authentication System Design]]
* [[Litmus:Web Services]]
* [[Litmus:Web Services|Web Services]]
** Result Submission Service:
** Result Submission Service:
*** [[Litmus:Test Result Format DTD|Test Result Format (DTD)]]
*** [[Litmus:Test Result Format DTD|Test Result Format (DTD)]]
Line 29: Line 32:
*** [[Litmus:EggplantIntegration|Getting results from Eggplant into Litmus]]
*** [[Litmus:EggplantIntegration|Getting results from Eggplant into Litmus]]
** Testcase Retrieval Service:
** Testcase Retrieval Service:
*** [[Litmus:Test_Format_DTD]]
*** [[Litmus:Test_Format_DTD|Test Format DTD]]
* [[Litmus:Future Directions|Future Directions for Litmus]]
* [[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===
===Installation===
* [[Litmus:Test Suite|Verifying Your Litmus Install]]
 
* [[Litmus:CVS|How to check out Litmus from mozilla.org CVS]]
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===
===Using Litmus===
* [[Litmus:Adding Testcases to Litmus|Adding Testcases to Litmus]]
* For Users:
* [[Litmus:Syncing testcases between subgroups|Syncing testcases between subgroups in Litmus]]
** [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===
===Miscellaneous===
* View a list of [http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=mozilla%2Fwebtools%2Flitmus&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=month&mindate=&maxdate=&cvsroot=%2Fcvsroot recent checkins to Litmus in CVS] (Bonsai)
* [http://hg.mozilla.org/webtools/litmus recent commits to Litmus (hg)]
* [[2005Offsite/LitmusFutures|Notes from the Litmus BOF session]] held at the Mozilla 2005 offsite
* 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 ==
== Further Reading ==
* [[Mozilla_QA|Mozilla QA]]
* [[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"