All videos
Workflows · 2:02
Test a workflow, and know what a test does
Run a test, and see what it reads, holds back, and still runs.
Transcript
0:01Welcome
This video shows how to test a workflow with an example, and what a test does and does not do.
0:07Choose an example
A test runs your draft with one example event. Open the menu beside Run workflow, and choose Change event. Pick an event that looks like real work, such as a customer email about a damaged order.
0:21Run the test
Select Run workflow. Each job runs in turn, and its card shows how it went. Then open Logs, and select the run, to see what came in and what came out of each job. Check that the request is sorted correctly, and that the reply follows your policy.
0:41What a test does
A test is safe by default, but it is not a pretend run. Read is on, so steps that look things up in your tools get real data. This workflow looks nothing up, so its list is empty. Write is off. The draft is not created, the reply is not sent, and nothing is posted to team chat. Write also covers webhook requests, database writes and changes to knowledge documents. With Write off, none of them happen for real. Publish Events is off, so events from the test stay inside the test. Approval steps do not wait for a person. A test run approves them automatically. Model calls always run. Here a model sorts the request. OAIZ calls this an LLM call, and it uses your model in every test. Turn on Write only when you are sure what the workflow will send.
1:41Try different cases
One good test is not enough. Try an ordinary case, then an unusual one. A message with no order number. A message in another language. An upset customer. When a result is wrong, change the instructions or the knowledge, and test again with the same event, so you can compare.
