Changes

You can help improve Thunderbird and other users, or help make Thunderbird better and enjoy the satisfaction that you have contributed to improving Thunderbird - no prior experience is necessary. Below are just a few ways you can contribute to the Quality of Thunderbird. Each item has a specific page with more details.

== '''Easy:''' Testing == This activity is simple, takes the least amount of time, and doesn't require any special skill.  <small>The text below was moved from [[Thunderbird:Testing/Testing]]</small><!-- Moved from testing/testing -><!-- More information [[Thunderbird:Testing/Testing|here]] if you want to help with the testing activity. --><!-- <center>Quality through testing 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>=== Keywords ===* testace<ref>[https://en.wikipedia.org/wiki/Test_case]</ref>-->=== Punctual testing ===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 1-2 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.

Once on These activities are simple, takes the mailing list just read the emails coming in. Theyleast amount of time, and doesn'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 coveraget require any special skill. When we ask for volunteers we'll usually use the following tools for testing :

Having accounts on both on these systems Before Thunderbird is needed released to the general public, it goes through beta testing. To participate in order this effort you'll need to participaterun a [https://www.thunderbird.net/download/beta/ Beta version] which is different from the standard release version of Thunderbird. The [https://www.thunderbird.net/download/beta/ Beta web page] has advice and links to many helpful resources.

While testing or searching bugzilla you might find some portions of Thunderbird that used to work, previously worked but do not work anymore. These are called [[ Thunderbird:Testing/Regression|regressions]]Bug reports will have the '''regression''' keyword.

To participate in this effortWe can find the regression range using a wonderful semiautomated tool called [https://mozilla.github.io/mozregression/ mozregression], you'll need to run a version different from and hopefully identify the standard release version of Thunderbird linked on code which caused the mozilla.com websiteregression behavior.

Daily testing is can be done with [https== '''Moderate://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.''' ==

When doing daily testingBugs which are performance related, you will want to have an account on with the "perf" keyword, can be profiled using a tool which traces the code being used. [https://bugzillasupport.mozilla.org Bugzilla/en-US/kb/profiling-thunderbird-performance This page], so you can report has details on running the issues you findtool. More information to come.

=== Maintaining the Test cases Thunderbird's bug reports ===

A main part of our manual and community driven testing relies on test cases .<ref name="testcase">[https://securebugzilla.wikimediamozilla.org/wikipedia/en/wiki/Test_case<Bugzilla] is the database /ref>tool that tracks reported defects. What we do is we publish a call for help from volunteers Working in this area requires some experience using Thunderbird, and then split the test cases between those volunteersability to determine what the user reporting a problem might be seeing. You don't need great technical skill. It just takes a little time.

This means More information on this activity can be found [[Thunderbird:Testing/bugzilla|here]].

<!This requires running [https://www.mozilla.org/en-- == References ==<referencesUS/thunderbird/channel/> -->Daily version] which is different from the standard release version of Thunderbird. Daily is a difficult environment, because you get a new version almost every day, with updated code. Sometimes the daily build is broken by bugs. Otherwise, the challenges are similar to running a beta version.