MailNews:Automated Testing: Difference between revisions
(Restructure slightly) |
|||
| Line 19: | Line 19: | ||
* [[MailNews:xpcshell tests]] | * [[MailNews:xpcshell tests]] | ||
** These currently run on the [http://tinderbox.mozilla.org/SeaMonkey/ SeaMonkey tinderboxes], and report as TUnit. Thunderbird hopes to pick running of these up soon ({{bug|422817}}. | ** These currently run on the [http://tinderbox.mozilla.org/SeaMonkey/ SeaMonkey tinderboxes], and report as TUnit. Thunderbird hopes to pick running of these up soon ({{bug|422817}}). | ||
Revision as of 15:09, 20 April 2008
Automated testing for MailNews (i.e. Thunderbird and the Mail/Newsgroups part of SeaMonkey) is becoming more important. We need to ensure that when we are fixing bugs we do not introduce regressions in other areas of the code. Automated testing is a vital part of this.
This page and its sub-pages are intended to describe and provide pointers to the available test mechanisms within MailNews and supporting information for developers and testers.
See also MailNews:Performance Testing.
General Notes
The devmo pages have some good descriptions on how to start writing automated tests.
Not all the automated tests will work at the moment, some of them require new support architectures, some of them require other issues fixing before they will pass/work correctly.
Automated Tests
- MailNews:xpcshell tests
- These currently run on the SeaMonkey tinderboxes, and report as TUnit. Thunderbird hopes to pick running of these up soon (bug 422817).