Litmus: Difference between revisions
Jump to navigation
Jump to search
m (point to correct documents due to QMO site update) |
ChrisCooper (talk | contribs) No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
'''<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. | 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. | ||
| Line 44: | Line 46: | ||
Litmus is released under the [http://www.mozilla.org/MPL/ MPL]. | Litmus is released under the [http://www.mozilla.org/MPL/ MPL]. | ||
* [[Litmus: | * [[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]) | * [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 | * Verifying Your Litmus Install | ||
** [[Litmus:Test Suite|Command-line verifications]] | ** [[Litmus:Test Suite|Command-line verifications]] | ||
| Line 61: | Line 63: | ||
===Miscellaneous=== | ===Miscellaneous=== | ||
* [http:// | * [http://hg.mozilla.org/webtools/litmus recent commits to Litmus (hg)] | ||
* Litmus Session Notes | * Litmus Session Notes | ||
** [[2005Offsite/LitmusFutures|Notes from the 2005 Litmus BOF session]] | ** [[2005Offsite/LitmusFutures|Notes from the 2005 Litmus BOF session]] | ||
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
- Requirements
- Design
- Web Services
- Result Submission Service:
- Testcase Retrieval Service:
- Roadmap
- 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.
- Feature Wishlist
Development
Interested in helping with Litmus? Start here.
Installation
Litmus is released under the MPL.
- How to clone Litmus from hg.mozilla.org
- INSTALL doc (from mxr)
- Litmus Install FAQ
- Verifying Your Litmus Install
Using Litmus
- For Users:
- For Admins:
Miscellaneous
- recent commits to Litmus (hg)
- Litmus Session Notes