Confirm
683
edits
Changes
m
As we are We still doing do some tests manually, you can either do manual tests or choose one despite more and more of the two approaches described below them are converted to write automated testsSelenium scripts. In the latter case, and if If you don't want know how to install all the required modules or cannot get them workingwrite Selenium scripts, you can still help us either by writing HTML scripts is probably what new testcases, or by running existing ones manually. If you want prefer to do. One day, we will probably write a conversion toolSelenium scripts, allowing us to write scripts in HTML and convert them in Perl and vice versa.that's even better!
→How to contribute?
As Selenium cannot do everything, and because someone has to write these scripts anyway, we are always looking for new testers. If you are interested in helping us making Bugzilla better and more stable, feel free to join us. The best way to start is to join us in the [irc://irc.mozilla.org/qa-bugzilla #qa-bugzilla] channel on IRC, or to write to [mailto:qa@bugzilla.org qa@bugzilla.org] telling us that you are interested. Of course, you can also report bugs you discovered to [https://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla b.m.o] directly.
Since mid-2006, we use a [http://landfill.bugzilla.org/bugzillaqa Testopia installation] to track testing progress and to let us easily manage remaining tests to do. See e.g. [http://landfill.bugzilla.org/bugzillaqa/tr_list_runs.cgi?plan_id=3 4 tests we did on October 2006] when we released 2.18.6, 2.20.for Bugzilla 3, 2.22.1 and 2.23.30]. That's another way a great tool to help us work efficiently, avoiding testing what has already been (automatically) tested.
== Writing Selenium scripts ==
