Skip to content

Canon Best Practices

2 min read

Get better AI test cases by keeping Canon small, current and limited to documents your team agrees are correct.


Ask one question about each document: if a test case cited this, would you accept it as proof of how the product should behave?

Add to CanonLeave in Files
Product requirement documentsMeeting notes and brainstorms
Feature specs and design docsDraft specs still being discussed
API contractsBug reports and support tickets
Acceptance and exit criteriaScreenshots and recordings
Standards you must followOld versions kept for history

The AI treats everything in Canon as correct. An old or draft spec gets cited just as confidently as the current one.


The AI can only test what your document actually says. A spec that lists features without saying what should happen gives it nothing to check.

  • Weak: “Users may edit shared steps.”
  • Strong: “The Create Shared Step button stays disabled until the name is filled in.”

The strong sentence becomes a test case with a clear expected result. The weak one becomes a test case that just repeats the requirement.

If a spec is light on outcomes, the quickest fix is usually to add numbered steps and the exact error messages. Those turn directly into test steps and expected results.