Home is where you talk to Certyn. The chat is at the top, and your project's dashboard sits under it: what needs you today, the release in progress, and how your suites are doing.
You can ask Certyn for almost anything in the chat: run a test, explore a new feature, explain a failed run, write test cases from a spec, set up an environment, or plan the week.
Writing a message
- Voice input: press the mic and speak. Your words are added to the draft, so you can edit them before you send.
- Improve: rewrites a rough draft into a clear task, in place. It never sends; you check it and send it yourself.
- @-mentions: type
@to point at a test case, a finding, a suite, or a connection. Certyn then knows exactly which one you mean. - / commands: type
/for shortcuts to common jobs.
/ commands
| Command | What it is for |
|---|---|
/test | Test a pull request, ticket, build, or area: run the saved tests that cover it, explore the rest, give one result |
/repro | Reproduce a bug from a tracker ticket, a support message, or your own words, with steps and evidence |
/retest | Check whether a finding still happens after a fix |
/bug | Write up a bug from the conversation, saved once you agree |
/triage | Group failures by likely shared cause and say what to do next |
/cases | Draft test cases from a ticket, spec, or feature, saved once you approve them |
/coverage | Compare what should work with saved tests and run evidence, to find gaps |
/flaky | Look into tests that fail now and then, and propose fixes |
/automate | Turn a saved test case into a Playwright test in your repo, run it, and open a pull request |
/a11y | Check a page or flow against WCAG 2.2 and list the problems by severity |
/release | Check a release against its evidence and rules: blockers and missing checks |
Commands come from skills. Your team can add its own procedures under Knowledge → Skills.
Secrets go into forms
When Certyn needs a password, an API key, or another secret, it opens a small form in the chat. You type the value there. It goes straight into the environment's variables and never into the conversation. See Test accounts and secrets.
Machines
The chat can use a Machine: a browser Certyn drives while you watch. Pick or start one from the chat box. You can take over on its screen for a 2FA code, a captcha, or SSO.
Changes need your yes
Before Certyn changes something in your project, such as saving a URL or a plan, it asks you first. Plans for the week and for a release are drafted in the chat and saved only once you agree.
Usage
Chat answers use some of your plan time, by what the model costs. Runs you start from the chat use QA hours like any other run.