Test Cycles

The Testcase Execution Assignment and Scheduling application can be found in the Test Lead's Desktop. This application - the third one to start using in a Release - is used to plan execution schedules and make testcase execution assignments to testers. It allows for visually setting up a testing scheduling, picking phases and testcases that need to be executed and assigning them to testers. This must be set up before testers can start executing test cases in their Testcase Execution application and Metrics are collected.

The concept is of high level Test Cycles that have multiple Test Phases (corresponding to the root level nodes of the Local Tree in the Repository Setup or Testcase Creation applications) which in turn contain all the testcases that need to be executed and hence need to be assigned to testers.

This application allows the Test Lead to:

• Set up various different execution cycles/runs

• Assign areas to testers (and themselves) to execute test cases

• Modify a schedule as needed based on changes in the project/release

• Reassign or load balance unexecuted testcases to other testers

This application does not allow:

• The selection of an explicit system/sub-system (i.e. sub node) for execution assignment. The top level Phase has to be selected but only the testcases that need to be executed can be assigned. The Testcase Execution, Metrics and Dashboards will only show and track the ones that have been set up for execution

A calendar based on month and week views is shown and can be toggled between these two views. < and > buttons allow months and weeks on either side of the currently displayed view to be shown.

Add New Cycle

To get started quickly, click on "Add New" that allows the creation of a new test execution cycle or a test run. All of the fields are mandatory.

1. Name: This is the name of the test cycle/test run that will be displayed in the schedule ("Cycle 1" in this example)

2. Build: This is an informational field for Testers to know which build/version/patch of the software they need to be testing

3. Environment: This is an informational field for Testers to know which environment they need to be running these tests in

4. Start Date: The start date of this test execution cycle

5. End Date: The end date of this test execution cycle

Once the above information is entered and saved, the cycle shows up in the upper pane of this application. Note that the Start Date and End Date of the cycle has to be within the Start Date and End Date of that particular Release (see Release Setup)

Edit Cycle

By selecting a test execution cycle and clicking on the "Edit" button, the Edit windows pops up that allows all of the above data to be modified. This is very useful especially in situations where schedule slippages are occurring or dates have to be reset for other reasons.

Copy Cycle

By selecting a test execution cycle and clicking on the "Copy" button, the entire cycle is copied including all its Test Phases. The "Copy Testcase assignments" checkbox allows you to copy over all the tester assignments while resetting the execution status.

Delete Cycle

By selecting a test execution cycle and clicking on the "Delete" button, the entire cycle is deleted after a confirmation, including its Test Phases, Assignments and Execution status (Metrics). Extreme caution should be exercised in deleting a cycle as this operation cannot be undone.

Export Cycle

On selecting a Cycle and clicking on the "Export" button, the entire Cycle can be exported to an Excel spreadsheet. This includes details such as Testcases, Assignments, Schedules and Execution Statuses.