Name Why Nothing Arrived

Command note: "Nothing happened" is not a test result. "Nothing happened because the test lead has no phone" is.

Built Today: the latest Workflow Audit Pro release (3.92.2) changes how a failed check reads. When a test lead goes into a workflow and nothing arrives, the heading now names the cause instead of just saying nothing arrived. A text step skipped because the test lead has no phone is called out as exactly that. A failed step is reported as failed, not as "the workflows ran."

The takeaway for your own QA:

• A silent test teaches you nothing

• "Did not run" and "ran and failed" are different problems

• The cause belongs in the heading, not buried in a log

Do it now on one live workflow:

1) Create a test lead with every channel filled in: phone, email, name.

2) Push it through and write down what each step did: sent, skipped, or failed.

3) For every skip, write the reason in one plain sentence.

4) Fix the test lead first, then the workflow, in that order.

Half of "broken automation" is a test record that was never set up to receive anything.

A test that can't say why it failed isn't a test yet.

3 comments