Before you start
A signed-in NodeFox workspace. Use synthetic data and prepare outputs before enabling external writes.
01Test input boundaries
Define required fields, allowed values and source freshness. Use normal, incomplete, conflicting and malicious-content fixtures. Decide which cases stop and which request a person’s decision.
02Review every side effect
Inventory external writes, messages, tool calls and downloaded artifacts. Confirm who can authorize them, how duplicates are prevented, and what happens when a response is uncertain.
03Assign operational ownership
Identify who reviews waiting cases, rotates credentials, investigates failures and changes policy. Confirm the actual runtime environment’s persistence and monitoring instead of assuming guarantees from the editor.
04Agree acceptance and rollback
Use a bounded initial population and compare results with the existing process. Record how to disable external actions and return work to people. Expand only after correctness and operating responsibilities are demonstrated.
If the result is wrong
A visually complete graph is not a production acceptance test.