Litmus: Difference between revisions
Jump to navigation
Jump to search
ChrisCooper (talk | contribs) No edit summary |
|||
| 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 | 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 == | == Work in Progress == | ||
* | * [[Litmus:Extension|QA Extension Project]] | ||
* [[Litmus:Todo|Litmus To-Do List]] | |||
== Goals for Litmus == | == Goals for Litmus == | ||
Litmus | 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 15: | Line 16: | ||
* 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 | 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:Requirements|Requirements]] | * [[Litmus:Requirements|Requirements]] | ||
* [[Litmus:Design|Design]] | * [[Litmus:Design|Design]] | ||
| Line 35: | Line 31: | ||
** Testcase Retrieval Service: | ** Testcase Retrieval Service: | ||
*** [[Litmus:Test_Format_DTD|Test Format DTD]] | *** [[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=== | ===Installation=== | ||
| Line 56: | Line 60: | ||
===Miscellaneous=== | ===Miscellaneous=== | ||
* | * [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) | ||
* [[2005Offsite/LitmusFutures|Notes from the Litmus BOF session]] | * 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] | |||
Revision as of 20:38, 22 August 2008
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 check out Litmus from mozilla.org CVS
- INSTALL doc (from mxr)
- Litmus Install FAQ
- Verifying Your Litmus Install
Using Litmus
- For Users:
- For Admins:
Miscellaneous
- recent checkins to Litmus in CVS (Bonsai)
- Litmus Session Notes