As we make changes and implement A/B tests on the wikipedia.org portal, it's important to create tests to prevent regressions. Initially, integration tests will be created for event-logging across each section of the page and for each A/B testing scenario. Integration tests will also be created for new features as necessary.

Integration (end-to-end) Testing Framework
Integration tests will be decoupled from the implementation and carried out by a headless webkit browser (phantomjs).
The casperjs testing & navigation framework will be used to simulate user interaction on the page, and tests will pass or fail based on the expected outcomes of these interactions. Tests will be carried out on the development version of the page, so that event-logging events are not passed to the production servers.

Some integration tests that are common across each A/B test include:

• making sure an event-logging 'landing' event is sent on page load.
• an event-logging 'click-through' event is sent when a user clicks on a link.
• search form works when clicking the submit button or pressing enter.
• an event-logging event is sent when the search form is submitted.

limitations
Integration testing is not cross-browser testing. Cross browser testing will be done manually either in browserstack, on local machines and devices, or through virtual machines.