Scheduling a run means that you commit to the work outlined in the run configuration. While you may later edit the scope of that work, this action serves as the trigger to commission work from testers.
Schedule a manual run
To schedule a run, follow these steps:
Navigate to the run you want to schedule or create a new one.
If you haven't already done so, configure your run by adding the plan, build, and devices.
All plans used in the run must have an associated execution time.
All plans used in the run must have at least one test within them.
Set the Testing date range to the period when you want the run to happen.
Click Schedule.
Click Confirm.
The run is now scheduled and will take place during the Testing date range you selected.
If the workspace you're trying to schedule the run in would have less than 10% of its contracted hours remaining after the run, you see a warning before confirming:
If the workspace you're trying to schedule the run in would have no hours remaining after the run, the button to save the task is disabled and you need to explicitly confirm client approval before you can continue:
What happens after scheduling
Scheduling triggers a number of important processes:
Your run changes status to In progress.
The act of scheduling commissions testing work to take place. Generally, hours are committed and billing can occur, depending on the run configuration. This commitment should not be taken lightly.
Allocation of your run team starts.
If you are using Testlio Network Freelancers as testers in your run, work offers will be sent out to them. These invites are agreements between Testlio and the freelancers.
The testers selected to take part in the run are given access to the specified build and any other artifacts such as info sheets that may be relevant during the run execution for the duration of the run.