304
edits
Thunderbird:Testing: Difference between revisions
formatting
No edit summary |
(formatting) |
||
| (31 intermediate revisions by 7 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 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:''' == | |||
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 [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. | |||
== | === 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 [https://mozilla.github.io/mozregression/ 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. [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. | |||
<!-- == '''Challenging:''' Writing automated tests == | |||
[[category:Thunderbird | This is the most technical item. It requires a good amount of technical knowledge. But if you do not have the knowledge this is a good way to learn a lot of technical stuff. This involves understanding programming or learning about it. | ||
More information on writing tests is available here.-->__NOTOC__ | |||
== Ask questions on Matrix == | |||
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: | |||
<sup>[[#number1|1]]</sup> | |||
#<div id="number1"> this is the #tb−qa channel on </div> | |||
--> | |||
<small>Backup (for service): [[User:Tsk/bckup|Old Content]]</small> | |||
[[category:Thunderbird]] | |||