MailNews:Automated Testing

<< Back to MailNews:Home Page

Please do not edit this page unless you are on the Thunderbird or SeaMonkey MailNews team. Your feedback and comments are welcomed on the discussion page.

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.

xpcshell unit tests

The xpcshell unit tests are probably the easiest test to write, requiring no UI and being written in javascript. They are very useful for testing interfaces and back-end functionality.

Useful links:

• devmo documentation for writing xpcshell-based unit tests
• Current MailNews unit tests