Litmus: Difference between revisions
Jump to navigation
Jump to search
ChrisCooper (talk | contribs) |
ChrisCooper (talk | contribs) |
||
| Line 14: | Line 14: | ||
== Litmus Documentation and Notes == | == Litmus Documentation and Notes == | ||
===Designing and Planning=== | ===Designing and Planning=== | ||
* [[Litmus:Roadmap| | * [[Litmus:Roadmap|Roadmap]] | ||
* [[Litmus:Todo| | ** [[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:Future Directions|Future Directions | ** [[Litmus:Future Directions|Future Directions]] | ||
* [[Litmus:Wishlist|Feature Wishlist]] | ** [[Litmus:Wishlist|Feature Wishlist]] | ||
* [[Litmus:DevelopersNotes| | ** [[Litmus:DevelopersNotes|Developers' Notes]]: Interested in helping with Litmus? Start here. | ||
** [[Litmus:mod_perl|mod_perl Notes]] | ** [[Litmus:mod_perl|mod_perl Notes]] | ||
* [[Litmus:Requirements| | * [[Litmus:Requirements|Requirements]] | ||
* [[Litmus:Design|Litmus Design]] | * [[Litmus:Design|Litmus Design]] | ||
** [[Litmus:Design/Auth|Authentication System Design]] | ** [[Litmus:Design/Auth|Authentication System Design]] | ||
| Line 29: | Line 29: | ||
*** [[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]] | ||
===Installation=== | ===Installation=== | ||
Revision as of 16:57, 15 January 2007
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.
Goals for Litmus
Litmus will:
- 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 will 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
- 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.
- Future Directions
- Feature Wishlist
- Developers' Notes: Interested in helping with Litmus? Start here.
- mod_perl Notes
- Requirements
- Litmus Design
- Litmus:Web Services
- Result Submission Service:
- Testcase Retrieval Service:
Installation
Using Litmus
Miscellaneous
- View a list of recent checkins to Litmus in CVS (Bonsai)
- Notes from the Litmus BOF session held at the Mozilla 2005 offsite