Wiki & Context
Teach the autonomous QA team what your product is and what must always be true.
Certyn is most effective when it has stable, explicit context about your application. The Wiki is where you provide that context so the autonomous QA team can make better decisions, write better tests, and produce higher-signal issues.
What lives in the Wiki
In the app, open Wiki from the sidebar. You will see two main sections:
- Overview: what the product does, who uses it, critical flows, and what to ignore.
- Rules: non-negotiable statements that should always hold (security, workflows, validation rules, etc).
Keep these short, testable, and stable. Treat the wiki like the "ground truth" you would give a QA engineer on day one.
Documents (optional)
If you have product docs, runbooks, or specs, you can upload them in the Wiki under Documents. Certyn can use these as additional context during exploration and test writing.
Good document examples:
- public help center docs
- staging credentials and test data rules (non-sensitive)
- a "happy path" checklist for your release process
Avoid uploading secrets or personal data.
How context affects Runs and Issues
With better context, Certyn can:
- focus exploration on critical workflows
- avoid "false failures" caused by ambiguous expectations
- write tests that are aligned with real business rules
- produce issues with better reproduction steps and impact statements