Bugzilla:QA: Difference between revisions

Bugzilla:QA (view source)

Revision as of 19:31, 31 July 2008

616 bytes removed , 31 July 2008

m

→‎Writing Selenium scripts

LpSolit

Confirmed users

683

edits

@@ Line 15: / Line 15: @@
 === Scripts running from a web browser ===
-This is the easiest way to use Selenium. After having downloaded and untar'ed the tarball (we still use version 0.6.0 despite 0.8.1 is out, for compatibility issues), scripts simply consist of a table with three columns (command, field, value). A template is available in [https://bugzilla.mozilla.org/show_bug.cgi?id=317695 bug 317695] (template.html), as well as a useful Javascript file for most common actions (user-extensions.js).
+Till Bugzilla 3.0.x, Selenium tests were all written in HTML. It has been decided for Bugzilla 3.2 RC1 and newer to convert them to Perl, giving us more flexibility and control. We no longer write test scripts in HTML.
-[http://openqa.org/selenium-ide/ selenium-IDE] ([https://addons.mozilla.org/extensions/moreinfo.php?application=firefox&category=Newest&numpg=10&id=2079 amo], formerly [http://seleniumrecorder.mozdev.org/ Selenium Recorder]) is a Firefox extension which writes scripts for you. It records your actions and converts them into a valid Selenium script. If you decide to install this extension, you don't need to install Selenium separately; everything is included in the XPI package (samples and docs are not included though).
+=== Perl Selenium scripts ===
+The fastest way to write Selenium scripts is to use [http://openqa.org/selenium-ide/ selenium-IDE] ([https://addons.mozilla.org/extensions/moreinfo.php?application=firefox&category=Newest&numpg=10&id=2079 amo], formerly [http://seleniumrecorder.mozdev.org/ Selenium Recorder]). Selenium-IDE is a Firefox extension which writes scripts for you. It records your actions and converts them into a valid Selenium script. If you decide to install this extension, you don't need to install Selenium separately; everything is included in the XPI package (samples and docs are not included though). You can also write Selenium scripts with a text editor, but this is longer and can be pretty painful.
-=== Scripts called by a Perl program ===
+In order to run these Perl scripts, you first have to install 2 Perl modules, both of which are available on CPAN:
-The installation and configuration are a bit harder. First download and install [http://search.cpan.org/~lukec/Test-WWW-Selenium/ Test::WWW::Selenium]. In case you still use version 0.03, the following modules are required too:
+ [http://search.cpan.org/~lukec/Alien-SeleniumRC/ Alien::SeleniumRC]
+ [http://search.cpan.org/~lukec/Test-WWW-Selenium/ Test::WWW::Selenium]
-requires:
+Each command is then of the form $sel->command_name_ok('field', 'value', 'description'), where $sel is the test object created by Test::WWW::Selenium and which will do the interface between your test script and your Bugzilla installation. The description is optional, but gives very useful information. A typical output is of the form:
-  Alien::Selenium
-  Frontier::Client
-  Frontier::RPC2
-  LWP v5.8
-  POE v0.29
-  POE::Component::Client::UserAgent
-  POE::Component::Server::HTTP
-  Test::LongString
-build_requires:
-  HTTP::Daemon
-  Test::More v0.47
-When all these modules are installed, you will also need the SeleniumTest.pm module available in [https://bugzilla.mozilla.org/show_bug.cgi?id=317695 bug 317695] which is a simplified version of the one given with the Test-WWW-Selenium tarball. An example of a test script - 012qa.t - is also provided, which can e.g. be executed with runtests.pl, a Perl script available in the Bugzilla distribution.
+ #perl test_enter_new_bug.t
+ ok 1 - open, /bugzilla/
+ ok 2 - Enter admin login name
+ ok 3 - Enter admin password
+ ok 4 - Submit credentials
+ ok 5 - open, /bugzilla/enter_bug.cgi?product=TestProduct
+ ok 6 - Display enter_bug.cgi for the selected product (bypass classifications)
+ ok 7 - Enter bug summary
+ ok 8 - Enter bug description
+ ok 9 - Submit bug data to post_bug.cgi
+ ok 10 - Bug created
+..10
-For newer versions of Test::WWW::Selenium, requirements are different and SeleniumTest.pm is no longer required. Note that your old scripts running on 0.03 won't run on newer versions anymore.
+What you can read here are the descriptions given for each command of the script. This makes debugging much easier!
-As you can see, the syntax is different between HTML and Perl scripts, but the commands remain mostly the same. Make sure to end all your commands by "_ok" to generate an output on your screen. The format is now $test->command_name_ok('field', 'value', 'description'), where $test is the test object created by SeleniumTest.pm and which will do the interface between your test script and the web installation.
+Existing Selenium scripts can be found in bugs depending on [http://landfill.bugzilla.org/bugzillaqa/show_bug.cgi?id=3065 bug 3065]. Members of the QA team can use CVS to get them all at once using:
-The description is optional, but gives very useful information. A typical output is of the form:
+ cvs -d my_login@landfill.bugzilla.org:/cvsroot co selenium
- t/012qa....1..7
+where my_login is your user account name on landfill.
- ok 1 - Load query.cgi
- ok 2 - Check title
- ok 3 - Enter and check input in the short_desc field
- ok 4 - Recheck the input (using a different method)
- ok 5 - Submit request (-> buglist.cgi)
- ok 6 - Check title
- ok 7 - Make sure that no bug is returned (0 bug found)
- ok
- All tests successful.
-What you can read here are the descriptions given for each command of the script. This makes debugging much easier!
 [[category:Bugzilla|QA]]
 [http://www.bugzilla.jp/bzwiki/bz/Bugzilla:QA Ja]