Content translation/QA

Persona based testing

 * New user
 * Existing user
 * Returning user testing.

Browser testing

 * Firefox
 * Chrome
 * CBT options can be used.

Language pairs

 * Group the language pairs to sensible sets and test a sample from each group- end to end testing.
 * Language pair with mixed directions.
 * Language pair without MT.
 * Language pair with MT (internal service).
 * Language pair with MT (external service).

Depth of testing

 * Ensuring something works vs. trying to break it vs. try every thinkable condition (clearly not possible at moment)
 * Prepare an end-to-end testing set - Define some common workflow paths
 * From entry point to draft save.
 * From entry point to draft save, resume and save again
 * From entry point to draft save, publish
 * Resume and Publish
 * Links related
 * Image
 * Tables
 * Maths or other commonly used tags
 * categories

Time/resource management ideas

 * Complete the whole test plan once in a week time- 5 days.
 * Focussed task based testing - one per each task.
 * Master stability testing - focussed on the features added and sanity testing prior to branching.

Resources

 * Labs:
 * CX (http://cx2.wmflabs.org/index.php/Special:ContentTranslation) is always on master (Delay 30 minutes).
 * cxserver (cxserver.wmflabs.org/v1) is always on master.


 * Beta:
 * CX (http://en.wikipedia.beta.wmflabs.org/wiki/Special:ContentTranslation) is always on master (Delay 30 minutes).
 * cxserver (https://cxserver-beta.wmflabs.org/v1) is manually updated by cxserver/deploy repo.


 * testwiki (https://test.wikipedia.org/wiki/Special:ContentTranslation) updated every Tuesday.


 * cawiki, hewiki in Production updated every Wednesday.


 * cxserver (https://cxserver.wikimedia.org/v1) is updated manually using cxserver/deploy repo.