Skip to content
certyn logoCertyn
Start Free
RecipesDoc

Teach Certyn Your Product with the Wiki, Testing Rules and Memory

Write your product overview, business rules and Definition of Ready in the wiki, keep small facts as memory, and roll back a bad wiki edit.

For QA leads who want every run and chat to know the product and the team's rules.

Your setup

  • A Certyn project. Its wiki still has the starter text.
  • A spec or notes that explain the product.
  • Release rules that differ from the default Definition of Ready.

Say this to Certyn

Here is our product brief. Fill in the wiki: what the app does, the checkout rules, and our Definition of Ready: no open critical bugs and a pass rate of at least 98%. Also remember that the staging coupon is TEST10.

What Certyn does

  1. Edits one part of a wiki section at a time (app.wiki.update) and keeps the rest. The sections:
    • Overview: what the app does, who uses it, areas to prioritise.
    • Business logic: rules that must always hold, key flows, edge cases.
    • Testing rules: Definition of Ready, bug severities, tags and suites. The default Definition of Ready: no open critical or major bugs, no real smoke failures, pass rate at least 95%, no unresolved Sentry regression, regression suite run on this version in the last 24 hours.
  2. Saves small facts as memory (app.memory.create): a title up to 50 characters, one fact up to 500. The same title updates it. Memory belongs to the project and all its environments. Secrets go in a form, never in memory.
  3. On "undo the last wiki change": lists the revisions (app.wiki.revision.list), shows the old text, asks, then restores it (app.wiki.revision.update). A restore replaces all sections and is saved as a new revision.

What runs and the chat read

  • At the start: overview up to 1,000 characters, business logic and testing rules up to 3,000 each. The full wiki when they need more. A section that still has the starter text is left out.
  • Memory: the 100 newest facts, one line each. Explore runs and the chat save memory; test-case runs only read it. Testing rules win over memory.

What you get

  • Runs that know your flows, rules and accounts.
  • Release go/no-go answers judged by your Definition of Ready.

Limits

  • Revisions are only in the chat. There is no history page, and the starter text cannot be restored.
  • The Knowledge page shows Overview and Rules only. Edit business logic and memory through the chat.
  • Explore runs can edit the wiki too. The revision list shows who changed it.
  • Chat edits do not complete the setup step "Give me your house rules". Save the wiki once on the Knowledge page.
PreviousTriage Findings in Review, Confirm or Close Each with a ReasonNextWrite a Team Skill, for Example "How We Test Checkout"