Thunderbird:Testing/Testing: Difference between revisions

Jump to navigation Jump to search
m
tune, cut #1. and fix link
m (tune, cut #1. and fix link)
Line 1: Line 1:
<center>Quality through testing</center>
<center>Quality through testing


One of the easiest way to help make Thunderbird a great product is by testing it.  
One of the easiest way to help make Thunderbird a great product is by testing it.  
Here are several different ways you can help.</center>


== Punctual testing ==
== Punctual testing ==


This is the easiest way to participate, and learn how to do more - and get more confident about helping.
This may be the easiest way to participate, learn how to do more - and get more confident about helping. To help here, just subscribe yourself to the [https://mail.mozilla.org/listinfo/thunderbird-testers Thunderbird-testers] mailing list. This is a read-only mailing list with one or two messages per month. We usually send detailed instructions on what to do and test and how to get help when you sign up for one of those events.
 
To help there , just subscribe yourself to the [https://mail.mozilla.org/listinfo/thunderbird-testers Thunderbird-testers] mailing list. This is a read-only mailing list with one or two messages per month.


Once on the mailing list just read the emails coming in. They'll either ask for volunteers for a shared event or will give very specific instructions on how to test a new feature on which we want a lot of coverage. When we ask for volunteers we'll usually use the following tools for testing :
Once on the mailing list just read the emails coming in. They'll either ask for volunteers for a shared event or will give very specific instructions on how to test a new feature on which we want a lot of coverage. When we ask for volunteers we'll usually use the following tools for testing :
Line 14: Line 14:
* [https://bugzilla.mozilla.org Bugzilla] to manage our defects and [https://secure.wikimedia.org/wikipedia/en/wiki/Software_bug bugs]
* [https://bugzilla.mozilla.org Bugzilla] to manage our defects and [https://secure.wikimedia.org/wikipedia/en/wiki/Software_bug bugs]


Having accounts on both on these system is needed in order to participate.
Having accounts on both on these systems is needed in order to participate.
 
We usually send detailed instructions on what to do and test and how to get help when you sign up for one of those events.
 


== Daily testing ==
== Daily testing ==


To participate in this effort, you'll need to run different versions of Thunderbird than the one linked on the mozilla.com website.
To participate in this effort, you'll need to run a version different from the standard release version of Thunderbird linked on the mozilla.com website.


Daily testing is can be divided by [[https://www.mozilla.org/en-US/thunderbird/channel/ |versions of Thunderbird]] that needs testing. Mozilla produces versions of Thunderbird every night, with new fixes and sometimes new bugs.
Daily testing is can be done with [https://www.mozilla.org/en-US/thunderbird/channel/ "newer" versions of Thunderbird] that needs testing. Mozilla produces updates of these versions of Thunderbird every night, with new fixes, but also sometimes causing new bugs.


* We need a number of people on the stable branch - as its name implies, the stable branch only contains fixes and doesn't see any new features. But by using these builds, you'll help make sure that we don't introduce new bugs in the next security and stability release. To use these either:
* We need many people on the stable branch - as its name implies, the stable branch only contains fixes and doesn't see any new features. But by using these builds, you'll help make sure that we don't introduce new bugs in the next security and stability release. To use these, either:
*# Download one stable nightly build and update it regularly
*# Download one stable nightly build and update it regularly
*# Or switch your update channel to beta instead of release.
*# Or switch your update channel to beta instead of release.
* We need people to use Alphas and Betas of the next major release. To run these just download one when they are announced and just keep using them.
* We also need people to use Alphas and Betas of the next major release. To run these just download one when they are announced and just keep using them.
* And finally we also need people to run trunk builds. These builds will contain all the new features of the next major release of Thunderbird and you don't need to wait for the next beta to see them. These builds are less stable than the others and get broken once in a while (I would say maybe once or twice per calendar year).
* And finally we also need people to run trunk builds. These builds will contain all the new features of the next major release of Thunderbird and you don't need to wait for the next beta to see them. These builds are less stable than the others and get broken once in a while (I would say maybe once or twice per calendar year).
*# We also announce major issues when we are aware of them on [https://mail.mozilla.org/listinfo/tb-planning Tb-planning] - Some coverage about less critical issues is available on the [http://forums.mozillazine.org/viewforum.php?f=29 Daily build thread at Mozillazine]
*# We also announce major issues when we are aware of them on [https://mail.mozilla.org/listinfo/tb-planning Tb-planning] - Some coverage about less critical issues is available on the [http://forums.mozillazine.org/viewforum.php?f=29 Daily build thread at Mozillazine]
canmove, Confirmed users
2,190

edits

Navigation menu