MailNews:Automated Testing: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎Automated Tests: TUnit are now run on Thunderbird as well)
(Content moved to devmo)
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<small>[[MailNews:Home Page|<< Back to MailNews:Home Page]]</small>
Content moved to the Mozilla Developer Center [https://developer.mozilla.org/en/MailNews/MailNews_Automated_Testing https://developer.mozilla.org/en/MailNews/MailNews_Automated_Testing]
 
__TOC__
 
== Introduction ==
 
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.
 
Tests are not only useful for checking for regressions, but they can help developing and testing of patches. For example, xpcshell tests are very good at checking interfaces, and are very quick to run as they only require a "make check" - you don't have to start up the application, and all the tests happen automatically in a consistent manner.
 
See also [[MailNews:Performance Testing]].
 
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.
 
Thunderbird brainstorm on unit test ideas is [[Thunderbird:Unit_Test_Ideas|also available]].
 
== Rules and Review Policy ==
 
See the following pages:
 
* [http://www.mozilla.org/mailnews/review.html mailnews/ review policies]
* [http://www.mozilla.org/mailnews/review-mail.html mail/ review policies]
* [http://www.mozilla.org/projects/toolkit/review.html toolkit/ review policies].
 
== Useful Documentation and notes ==
 
The [http://developer.mozilla.org/ devmo] pages have some good descriptions on how to start writing [http://developer.mozilla.org/en/docs/Mozilla_automated_testing automated tests].
 
Not all the [http://developer.mozilla.org/en/docs/Mozilla_automated_testing 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 report as TUnit and are run on both Thunderbird and SeaMonkey.
 
== Notes for running on Trunk Builds ==
 
These apply to trunk builds of SeaMonkey and Thunderbird. They may also apply to other applications.
 
=== xpcshell tests ===
 
Some of the non-mailnews tests may currently fail in various places due to the following reasons:
 
{|border="1"
!Test !! Debug-only? !! Bug Reference !! Notes
|-
| test_default_index_handler.js ||align="center"| No ||align="center"| {{bug|427831}} ||align="left"| Broken if CVS directory doesn't exist
|-
| test_bug299716.js ||align="center" rowspan=4| Yes ||align="center" rowspan=4| {{bug|431139}} ||rowspan=4| &nbsp;
|-
| test_bug378216.js
|-
| test_bug394300.js
|-
| test_download_manager.js
|-
| test_bug356370.js ||align="center"| Yes ||align="center"| {{bug|428078}} ||
|-
| test_bug394717.js ||align="center"| Yes ||align="center"| {{bug|431147}} ||
|}
 
* Thunderbird builds will also fail in various places in core, see the dependencies of {{bug|406227}}.
* Mac tests will leak memory and complain about it on 1.9 branch (CVS) due to {{bug|435853}}

Latest revision as of 13:20, 17 July 2009

Content moved to the Mozilla Developer Center https://developer.mozilla.org/en/MailNews/MailNews_Automated_Testing

Retrieved from "https://wiki.mozilla.org/index.php?title=MailNews:Automated_Testing&oldid=155973"