For teams that track bugs in Linear or in GitHub Issues.
Your setup
- A Linear workspace with a team, or a GitHub repository with Issues on.
- Certyn already tests one of your environments.
- You want real bugs in your tracker, not every failed test.
Say this to Certyn
File the bugs you find in our Linear team WEB.
Or: File the bugs you find as GitHub issues in acme/shop.
What Certyn does
- Opens the connect form.
- Linear: Connect Linear workspace signs in once for the whole workspace. Certyn then works as its own app user. Or paste a personal API key.
- GitHub: install the Certyn GitHub App and pick the repository. Or use a personal access token.
- If there is more than one team or repository, asks which one gets the issues and saves it (
tracker.target.set). - For each real product bug, asks before it files it (
tracker.issue.create), then links the Certyn issue to it. An issue you already have can be linked instead (tracker.issue.link). - After a fix is deployed, you say retest issue 12. In Linear you can also mention @Certyn on the issue. Certyn runs the bug again on the environment where it was found.
What you get
- One issue per bug, with the write-up from the run.
- The Certyn issue keeps the screenshots and the session, and shows the tracker link.
- The retest result on the same Certyn issue.
Limits
- Certyn asks before it creates each issue. It does not file every finding on its own.
- GitHub Issues has no @Certyn mention. Ask for the retest in Ask Certyn.
- Retest needs a confirmed issue that is linked to a tracker issue or a test case.
- A passing retest does not close the tracker issue. Close it yourself, or ask Certyn to add a comment.