VisualEditor/Planning and testing

This is a directory of pages related to the planning and testing process of the VisualEditor extension. Some pages document deprecated aspects of the software, and are kept for historical purposes.

Planning

 * "Forward-look" documents:
 * 2012-13 Q1
 * 2012-13 Q2
 * 2012-13 Q3


 * Agendas, meeting agendas for the development team
 * Roadmap, plan for VisualEditor as of August 21, 2012
 * Phase 2, description of the second phase of the VisualEditor development
 * Todo list
 * Todo later list, list of tasks de-scoped for the June 2013 release of the VisualEditor
 * FAQs from the June 2012 release
 * Undo and redo, planning for these functions (historical)

Testing

 * Test, a general test page
 * Template test, a test page for templates
 * References test, a test page for references
 * Typing, testing for languages requiring input methods
 * Indic, testing for Indic language characters
 * Right-to-left, testing for languages using right-to-left character placement
 * Testing Non-Latin Characters Input and Behavior, for non-Latin characters

JavaScript browser tests
The VisualEditor JavaScript qunit tests need to run in a browser. You can run them from the commandline using the Grunt JavaScript task runner, which will start up a PhantomJS headless browser to run them. Grunt can also run the JSHint code checker. See Gruntfile.js.

These tests are part of the browsertests-test2 suite that runs on https://wmf.ci.cloudbees.com/ on multiple browsers.

Browser tests
The suite includes some QA tests for VE WMF QA regularly runs these against multiple browser at https://wmf.ci.cloudbees.com, as of 2013-08 they report in the browsertests-test2 run. You can run these tests yourself by installing the necessary software, see QA/Browser_testing/Running_tests

You can also run a MediaWiki-Vagrant virtual machine, enabling the roles  and , to test the code locally and run tests against it.

Other

 * Fail, (historical)