Changes

Jump to: navigation, search

Bugzilla:QA

No change in size, 16:11, 9 December 2006
no edit summary
As repeating the same tests manually again and again for each new release quickly became rather boring, we tried to automate the process as much as possible. To help us in this task, the QA team is now working on a [http://www.openqa.org/selenium/index.html Selenium] installation on [http://landfill.bugzilla.org/selenium/bugzilla/index.html landfill] which can either be run from a web browser or from a Perl script directly.
 
== 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 tests we did on October 2006] when we released 2.18.6, 2.20.3, 2.22.1 and 2.23.3. That's another way to help us efficiently, avoiding testing what has already been tested.
 
As we are still doing some tests manually as mentioned above, you can either do manual tests or choose one of the two approaches described previously to write automated tests. In the latter case, and if you don't want to install all the required modules or cannot get them working, writing HTML scripts is probably what you want to do. One day, we will probably write a conversion tool, allowing us to write scripts in HTML and convert them in Perl and vice versa.
== Writing Selenium scripts ==
What you can read here are the descriptions given for each command of the script. This makes debugging much easier!
 
== 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 tests we did on October 2006] when we released 2.18.6, 2.20.3, 2.22.1 and 2.23.3. That's another way to help us efficiently, avoiding testing what has already been tested.
 
As we are still doing some tests manually as mentioned above, you can either do manual tests or choose one of the two approaches described previously to write automated tests. In the latter case, and if you don't want to install all the required modules or cannot get them working, writing HTML scripts is probably what you want to do. One day, we will probably write a conversion tool, allowing us to write scripts in HTML and convert them in Perl and vice versa.
[[category:Bugzilla]]
[http://www.bugzilla.jp/bzwiki/bz/Bugzilla:QA Ja]
Confirm
683
edits

Navigation menu