User:Rachel99/proposal1

Browser Test Automation for VisualEditor
Name: Rachel Thomas

Email: rachelthomas_99@yahoo.com

IRC handle: rachel99

Location: Boston, MA (UTC -4:00 )

Background
As the major issues in VisualEditor have been fixed, the VisualEditor has recently been deployed to 14 non-English Wikipedias so that users can become familiar with the editor. It will eventually become the default editor for Wikipedia. The timing is good for a battery of tests of be constructed for the VisualEditor as the editor is stable enough to have automated tests written and run against it.

My background
I have been volunteering at Wikipedia for the past 3 months, prior to this application. I have been volunteering in the Browser web automation area, and helping to create test cases for the backlog and and code them in Ruby.

VisualEditor is a great target for tests because it matches the desired criteria exactly:  http://www.mediawiki.org/wiki/QA/Browser_testing#Rationale. VE should work in many browsers, is javascript-heavy; requires navigation to test properly; is likely to have regression issues, and is a critically important project.

Goals
To construct a battery of web automation tests for the thorough testing of VisualEditor. These would be Accepted Test Driven Development tests written in Cucumber and falling under the same framework as the currently running web automation tests. The Cucumber tests would be coded using Ruby Page Object Design, and then run under Jenkins.