Reading/Web/QA

Browser tests

 * What are browser tests? Quality_Assurance/Browser_testing
 * Setup browser tests - Quality_Assurance/Browser_testing/Setup_instructions;
 * Run browser tests - Quality_Assurance/Browser_testing/Running_tests;
 * Have Jenkins execute browser tests for every patchset submitted to Gerrit - Continuous_integration/Browser_tests;
 * Write your own browser tests - Quality_Assurance/Browser_testing/Writing_tests
 * Useful links - Reading/Web/Selenium_tests;
 * Some tips on writing automation tests - Reading/Web/Automation CheatSheet.

Running browser tests on the beta cluster
Set the following variables, using an existing account for username and password: Note that certain tests may require your username to have certain permissions set.

Simulating browser test run on an unmerged patchset.
The way we test such change is to create a copy of the existing Jenkins job, disable all notifications and then add a shell step that fetch and checkout the patchset.

Steps:
 * Login at https://integration.wikimedia.org/ci/
 * Click [./Https://integration.wikimedia.org/ci/newJob New Item] link in the left sidebar
 * A form would show.
 * Item Name: `item-name`
 * [ ] Copy existing Item: `selenium-MobileFrontend`
 * Save form
 * Go to the job configuration
 * Delete the sections:
 * IRC Notification
 * Editable Notification
 * In the `build` section add in the first step `Execute shell` a command to fetch and checkout the patch:


 * Save and trigger a build of that `item-name` to run browser tests.

Current browser test results

 * MobileFrontend
 * Other tests