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 tests
The VisualEditor JavaScript qunit tests are in test subdirectories of some modules. They need to run in a browser. You can visit Special:JavaScriptTest/qunit and run all tests (e.g. on test2wiki) including the ve modules (which will take a long time to complete in your browser), or choose individual modules from the dropdown. You can also 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.

Browser tests
 is a set of browser tests that perform some VE actions.

You can run these tests yourself by installing the necessary software, see Quality Assurance/Browser testing/Running and writing tests; the easiest setup is to run a MediaWiki-Vagrant virtual machine and enable the roles  and.

Continuous integration tests
When developers submit changes to VisualEditor, and later when other developers approve ("+2") them in gerrit, Jenkins runs a subset of VE tests: jshint, PHPcs, qunit tests.
 * last failed lint check

WMF QA regularly runs browser tests in multiple browser at https://wmf.ci.cloudbees.com, visiting pages on wikis, including beta labs] (which is running master) and test2wiki (which is running the most current wmf branch). Click the [r-ve] tab to see all VisualEditor runs.

Other

 * Fail, (historical)