Thunderbird:Testing: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎IRC: Other title for heading)
(formatting)
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<small>[[Thunderbird:Home|<< Back to Thunderbird Home Page]]</small>
<small>[[Thunderbird:Home|<< Back to Thunderbird Home Page]]</small>


You can help, even if you have no prior experience helping. You help another user, or help make Thunderbird better and enjoy the satisfaction that you have contributed to improving Thunderbird.
You can help improve Thunderbird and other users - no prior experience is necessary.
Below are just a few ways you can contribute to the Quality of Thunderbird.  
__FORCETOC__
== '''Easy:''' ==


Below are just a few ways you can contribute to the Quality of Thunderbird. Each item has a specific page with more details.
These activities are simple, takes the least amount of time, and doesn't require any special skill.  


== '''Easy:''' Testing ==
=== Beta testing ===


This activity is simple, takes the least amount of time, and doesn't require any special skill.  
Before Thunderbird is released to the general public, it goes through beta testing. To participate in this effort you'll need to run 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, including a beta topicbox group for advice and assistance.


More information [[Thunderbird:Testing/Testing|here]] if you want to help with the testing activity.
=== Finding regressions ===
While testing or searching bugzilla you might find some portions of Thunderbird that previously worked but do not work anymore. Bug reports will have the '''regression''' keyword.  


== '''Moderate:''' Maintaining the bug database ==
For these bugs it is very helpful to know the "regression range", the 1-day range of changes that broke Thunderbird.  A bug whose regression range has not been determined also has a bugzilla keyword '''regressionrange-wanted'''.


The bug database aka [https://bugzilla.mozilla.org bugzilla] is the tool used track defects.  The bug database is open to anyone who wants to help developers know about issues with Thunderbird.
You can find the regression range using a wonderful semiautomated tool called [https://mozilla.github.io/mozregression/ mozregression], and hopefully identify the code which caused the regression behavior.


Work in this area requires some experience just using Thunderbird (just a few months), and the ability to determine what the user reporting a problem might be seeing. You don't need great technical skill. It just takes a little time.
== '''Moderate:''' ==
 
=== Performance Profiles ===
 
Bugs which are performance related, with the "perf" keyword, can be profiled using a tool which traces the code being used.  [https://support.mozilla.org/en-US/kb/profiling-thunderbird-performance This page] has details on running the tool.  More information to come.
 
=== Maintaining Thunderbird's bug reports ===
[https://bugzilla.mozilla.org/ Bugzilla] is the database / tool that tracks reported defects. Working in this area requires some experience using Thunderbird, and the ability to determine what the user reporting a problem might be seeing. You don't need great technical skill. It just takes a little time. More information on this activity can be found [[Thunderbird:Testing/bugzilla|here]].
 
== '''Difficult:''' ==
 
=== Daily build testing ===
 
This requires running [https://www.mozilla.org/en-US/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. The [https://thunderbird.topicbox.com/groups/daily daily topicbox group] is available for advice and assistance.


More information on this activity can be found [[Thunderbird:Testing/bugzilla|here]].
<!-- == '''Challenging:''' Writing automated tests ==
<!-- == '''Challenging:''' Writing automated tests ==


Line 23: Line 40:


More information on writing tests is available here.-->__NOTOC__
More information on writing tests is available here.-->__NOTOC__
== Find us by IRC ==
== Ask questions on Matrix ==
If you want to know more, just type '''/join [http://www.mibbit.com/chat/?server=irc.mozilla.org&channel=%23tb-qa #tb-qa]''' at IRC chat on [http://irc.mozilla.org/ irc.mozilla.org] and ask us all sorts of questions. Bear in mind that we might take a few minutes to answer - so please be patient.
If you want to know more, ask in the Thunderbird support topic ''#thunderbird:mozilla.org'' on [https://wiki.mozilla.org/Matrix Matrix]. Bear in mind volunteers may not respond immediately, so please be patient.


<!-- Backup. I don't think that we need it:
<!-- Backup. I don't think that we need it:

Latest revision as of 16:25, 15 January 2024

<< Back to Thunderbird Home Page

You can help improve Thunderbird and other users - no prior experience is necessary. Below are just a few ways you can contribute to the Quality of Thunderbird.

Easy:

These activities are simple, takes the least amount of time, and doesn't require any special skill.

Beta testing

Before Thunderbird is released to the general public, it goes through beta testing. To participate in this effort you'll need to run a Beta version which is different from the standard release version of Thunderbird. The Beta web page has advice and links to many helpful resources, including a beta topicbox group for advice and assistance.

Finding regressions

While testing or searching bugzilla you might find some portions of Thunderbird that previously worked but do not work anymore. Bug reports will have the regression keyword.

For these bugs it is very helpful to know the "regression range", the 1-day range of changes that broke Thunderbird. A bug whose regression range has not been determined also has a bugzilla keyword regressionrange-wanted.

You can find the regression range using a wonderful semiautomated tool called mozregression, and hopefully identify the code which caused the regression behavior.

Moderate:

Performance Profiles

Bugs which are performance related, with the "perf" keyword, can be profiled using a tool which traces the code being used. This page has details on running the tool. More information to come.

Maintaining Thunderbird's bug reports

Bugzilla is the database / tool that tracks reported defects. Working in this area requires some experience using Thunderbird, and the ability to determine what the user reporting a problem might be seeing. You don't need great technical skill. It just takes a little time. More information on this activity can be found here.

Difficult:

Daily build testing

This requires running 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. The daily topicbox group is available for advice and assistance.


Ask questions on Matrix

If you want to know more, ask in the Thunderbird support topic #thunderbird:mozilla.org on Matrix. Bear in mind volunteers may not respond immediately, so please be patient.


Backup (for service): Old Content