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.
Before You Schedule
Before scheduling a run, check the following details:
All plans used in the run have an associated execution time.
All plans used in the run have at least one test.
The Testing date range is correct.
Testers have enough time to respond to invitations. Example: if your run starts in 3 hours and ends 4 hours after that, ensure the invite expiry time allows you to compose the team. An invite expiry time of 12 hours does not work in this example.
You are confident in the build availability and readiness. The build has passed any smoke tests.
Schedule a Run
To schedule a run, follow these steps:
Navigate to the run you want to schedule.
Click Schedule.
Click Confirm.
The run is now scheduled and will take place during the selected testing date range.
Utilization Warnings
When scheduling tasks for testers, it’s important to not schedule more hours than clients have agreed to or is remaining within the period.
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.
Do not proceed unless the client has preapproved the hours. Please contact the engagement’s EM to ensure you have approval to proceed.
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 Community Freelancers as testers in your run, work invitations are 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.