Language Testing Plan/TCMS Guide

A test case management system can be used to organise numerous repetitive tests over several versions of a product release. It also provides simple interfaces to create, manage and execute tests for users with different permission levels. For the projects maintained by the WMF Language Engineering team, we are evaluating the use of Testlink as a test case management system. As a start we have the included the tests for the Universal Language Selector that are manually run prior to MLEB releases. The following sections document the workflow used to create and execute the tests. Users with admin rights can create and manage tests. Users with tester roles can execute tests assigned to them.

More information about using Testlink can be found in the official User Guide

Log-in and Roles
Create a new account at http://language-tcms.wmflabs.org/firstLogin.php by filling in the form. Registered users can then log into the TCMS system using http://language-tcms.wmflabs.org/login.php
 * Users can be assigned different roles depending on the extent of their work inside the TCMS system. For the sake of simplicity, in the Testlink instance on language-tcms, we use 2 roles: admin and tester.
 * The admin users prepare the tests, plan them and assign them to testers
 * The testers can execute the tests assigned to them
 * Test assignments are done after test plans for the extensions/features have been drawn up
 * Before tests can be assigned, they have to be created and planned

Test Creation
Tests within the TCMS system are organised as Test Projects with Test Specifications. Test Specifications include Test Suites which are used to group the invidual Test cases.

Replication

 * Test Projects, Test Suites, Test Cases, and Test Plans can all be replicated from the TCMS interface at the time of creation. The forms will provide options from existing sets that can be chosen as the base. These can also be exported/imported using XML files.
 * New sets are necessary not just for creating newer versions of tests, but also for creating duplicate sets of Test Plans if more testers join in later