Bugzilla:QA: Difference between revisions

Jump to navigation Jump to search
m
no edit summary
mNo edit summary
Line 22: Line 22:
This will download Selenium scripts for all branches, including Bugzilla 2.20, 2.22, 3.0, and 3.2. Do not expect HTML scripts to work as is. They were based on a given test installation on landfill having some given user accounts, products, components and parameters, and so they won't run on a fresh test installation. They are only available so that you can see what we did till Bugzilla 3.0. Note that the 3.0 branch has a t/ directory with test scripts related to WebService. As those point to the same test installations as above, they also won't run as is on a fresh test installation.
This will download Selenium scripts for all branches, including Bugzilla 2.20, 2.22, 3.0, and 3.2. Do not expect HTML scripts to work as is. They were based on a given test installation on landfill having some given user accounts, products, components and parameters, and so they won't run on a fresh test installation. They are only available so that you can see what we did till Bugzilla 3.0. Note that the 3.0 branch has a t/ directory with test scripts related to WebService. As those point to the same test installations as above, they also won't run as is on a fresh test installation.


To avoid this problem, we highly improved the QA process during the Bugzilla 3.2 cycle and decided to write a script which would populate your fresh new installation so that you could also run our Selenium and WebService tests. This script is located in bugzilla32/config/generate_test_data.pl, and requires that you first set parameters in bugzilla32/config/selenium_test.conf correctly. Note that generate_test_data.pl must be run against an existing Bugzilla installation, created by checksetup.pl! Once the DB is populated, you can start the Selenium server and run our scripts located in bugzilla32/t/.


=== Perl Selenium scripts ===
=== Perl Selenium scripts ===
To avoid the problem mentioned above, we highly improved the QA process during the Bugzilla 3.2 cycle and decided to write a script which would populate your fresh new installation so that you could also run our Selenium and WebService tests. This script is located in bugzilla32/config/generate_test_data.pl, and requires that you first set parameters in bugzilla32/config/selenium_test.conf correctly. Note that generate_test_data.pl must be run against an existing Bugzilla installation, created by checksetup.pl! Once the DB is populated, you can start the Selenium server and run our scripts located in bugzilla32/t/.
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.
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.


Confirmed users
683

edits

Navigation menu