For QA teams that keep manual test cases in TestRail.
Your setup
- Test cases in TestRail, grouped in suites.
- A web app on a test environment that Certyn can reach.
- A test account for the app.
- You want results in TestRail, every night or after each deploy.
Say this to Certyn
Connect TestRail and run our Regression suite against staging every night at 2am. Write the results back to TestRail.
What Certyn does
- Opens the TestRail form. You enter the base URL, your user email and an API key (My Settings → API Keys; API access must be on under Administration → Site Settings → API).
- In the same form, you pick the suites. Each picked suite becomes a Certyn process. To fill a run you already opened in TestRail, give its number; Certyn finds it and uses that run.
- If the app needs a sign-in, opens the sign-in form for the test account.
- Sets the schedule (
app.process.trigger.set): a time with your time zone, and/or after each deploy. - Each run pulls the current cases from TestRail, runs them in a real browser, and writes each result back.
What you get
- A TestRail run with a result per case: Passed, Failed, Blocked, or left untested for aborted or skipped cases.
- A Certyn run report, and one Certyn issue per real product bug, with evidence.
- The suite can also run from CI, like any Certyn process.
Limits
- Cases without a numeric TestRail id are skipped when Certyn opens a run.
- Only the latest attempt per case is written back. A retry does not post twice.
- After each deploy fires when the environment gets a new version. Your pipeline sets it through the Environments API or a GitHub App deployment rule.
- Certyn does not edit cases in TestRail. Fix an out-of-date case there.