Test an automation

1. 01

   Write your brief

   1. Describe the event or input, the action, expected output and when a person must approve it.
   2. Gather the notes or assets you can use. Remove private information you cannot share and confirm permission for any source material.

   Example brief

   Using sample data only, accept a list of tasks, keep items marked overdue and return a summary. Include an empty-list case. Do not send messages, connect live accounts, deploy or add a schedule.

   Start with

   The objective and proposed source material.

   You’ll have

   An approved brief and authorised inputs.

   CheckThe brief says what to make, who it is for and how you will judge the result.
2. 02

   Create a first version

   1. No reviewed product recipe is available for the tool assigned to this step. Open its profile and follow the cited official instructions for this exact task.
   2. Use the brief above and make a small draft before committing time, money or live data.

   Open Kestra (opens in a new tab)

   Start with

   The approved brief and authorised inputs.

   You’ll have

   A tested automation draft with an execution log.

   CheckThe draft handles the sample input correctly without live side effects.

   Official instructions (opens in a new tab) · Checked 2026-11-11

3. 03

   Check the finished result

   1. Test a normal input, an empty input and a failure case. Check retries will not create duplicate actions.
   2. Confirm credentials, permissions and any approval step. Decide separately whether to Deploy, schedule or connect live accounts.

   Start with

   A tested automation draft with an execution log.

   You’ll have

   An accepted output or a clear list of corrections.

   CheckSample and failure tests pass, and live activation has a separate reviewed plan.

0 of 3 step checks complete. A person has checked the output against the brief and accepted the result.