Skip to content

Creating a Test Cycle

← Managing Test Cycles

Before you read this you may want to see:

Main Article


There are two ways in Worksoft SaaS to create a Test Cycle:
  • Manually using the Worksoft SaaS application
  • Using QaCONNECT REST API. To know how to create through QaCONNECT REST API, click here
Follow the instructions provided below to manually create a Test Cycle within the Worksoft SaaS application.

When on the Test Cycles' home screen, click on the 'Create' button on the top right-hand side of the screen.

To create a Test Cycle you are expected to key in the following values:
  • a unique Identifier for your Test Cycle [Mandatory] (This identifier is referred to as 'Test Cycle Identifier' in Worksoft SaaS)
  • a brief 'Description' [Optional]
  • Status [Mandatory], defaulted to 'Open' (you can leave it as is)
  • Planned Test Cycle Window [Mandatory]
  • Execution Asset Log Capture mode preferences for the Test Cycle [Optional]
  • Label assignments [Optional]
Once you enter the information for your Test Cycle, click 'Save' button.


Planned Time Window:
 
"Planned Time Window" of a Test Cycle is the window of time within which you want all tests (that you want to execute within that cycle) triggered/scheduled and execution completed. The value you enter can be considered the test design/goal for your test cycle.

When the tests start executing, the actual window can be wider than the planned window. For example, if some of your tests take more time than normal/expected, this may create a backlog of tests to be executed within your cycle which in turn may cause the actual test execution window to exceed the test cycle's planned window.

Your inputs for the planned window must meet the following conditions:
  • 'End DateTime' cannot be equal to or prior to the 'Start DateTime' for a Test Cycle.
  • When you specify the Planned Window for a Test Cycle, you must enter values for both the Minutes field as well as the Seconds field.
  • When you specify the Planned Window for a Test Cycle, you must enter values for both the Date field as well as the Time fields (Hours and Minutes).
  • The Planned Window for a Test Cycle cannot exceed 4 calendar weeks.

Execution Asset Log Capture mode preferences:

Worksoft SaaS allows you to configure what type(s) of assets/logs are captured when an automated test executes within the Worksoft SaaS Cloud.

For screenshot capture, you can configure whether or not you want screenshots captured and under what circumstances screenshots have to be captured (only where there is a failure or for all instructions in your test, and whether the screenshots have to be displayed real time or post test execution completion).

For video capture and Webdriver/Appium/Selendroid driver log capture or the Cloud log capture, you have the option to configure them to be either ON or OFF.

Worksoft SaaS allows you to define/configure these at various levels:
  • You can do this as part of the Testing Contexts you create for a Run Definition using Worksoft SaaS application
  • You can override the values that are set at the Run Definition's Testing Context level via QaCONNECT REST API that you use to schedule/trigger an automated test or a set of tests (aka Run Definitions)
  • Instead of overriding the execution asset log capture modes at the time of scheduling or triggering the execution of individual tests, you can instead define them at the Test Cycle level and let all tests that get executed within that cycle automatically inherit the Execution Asset Log Capture modes.
If you specify the 'Execution Asset Log Capture mode(s)' at the Test Cycle level, then, you don't have to go edit the modes individually/manually for each of the Run Definitions. 


Label Assignments to a Test Cycle:

Worksoft SaaS allows you to attach/assign one or more Labels to Run Definitions or the constituent Scenarios and Test Scripts. Some of these labels are usually assigned by the test automation authors/creators at the design time or automated test authoring time. An example of such a label is the 'Application Module' which is assigned to Test Scripts when the Scripts themselves are authored.

Then there are other categories of labels that ideally should be assigned at run-time (execution-time) of a Run Definition (aka test run). Usually, such labels are System-defined labels like the following:
  • Automation State (Development-Mode or Production-Ready Mode, which specify whether or not the test execution is being done to certify the automated test itself during development OR if the test is being executed to assess the quality of a particular release/build of your application under test)
  • Testing Purpose (Smoke Test, Regression Test, etc)
Worksoft SaaS allows you to define/configure the labels at various levels:
  • You can assign labels to the Run Definition and/or its constituent Scenarios and Test Scripts using Worksoft SaaS application
  • You can assign/override the labels that are set at the Run Definition (or its constituent Scenarios and Test Scripts) level via QaCONNECT REST API that you use to schedule/trigger an automated test or a set of tests (aka Run Definitions)
  • Instead of assigning/overriding the labels at the time of scheduling or triggering the execution of individual tests, you can instead define them at the Test Cycle level and let all tests that get executed within that cycle automatically inherit the labels.


After you read this article you may want to see:

Feedback and Knowledge Base

(thinking…)