Confirm
683
edits
Changes
m
→Writing Selenium scripts
The fastest way to write new Selenium scripts is to use the [http://seleniumhq.org/download/ Selenium IDE] extension for Firefox. It records all your actions and converts them into a valid Selenium script. You can also write Selenium scripts manually with a text editor, but this is longer and can be pretty painful.
Each command is of the form $sel->command_name_ok('field', 'value', 'description'), where $sel is the test object created by Test::WWW::Selenium. The description is optional, but may give some useful information. All available commands are listed [http://search.cpan.org/~lukec/Test-WWW-Selenium/lib/WWW/Selenium.pm here], and are fully documented.
Selenium scripts being under development/review can be found in open bugs depending on [http://landfill.bugzilla.org/bugzillaqa/show_bug.cgi?id=3065 bug 3065]. Those shouldn't be considered as "safe" till they are available via bzr. There are also many other bugs which need a test. You can [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=FIXED+testcase%3F pick one of them] and write a test, either by improving one of the existing tests, or by writing a completely new one. If you want to submit a script, please file it [http://landfill.bugzilla.org/bugzillaqa/enter_bug.cgi?product=QA%20tests&component=Selenium%20scripts here], which is the Bugzilla installation used by the QA team.
