Bug reports
Failed flows filed as issues in GitHub, Linear or Jira, one per bug, kept current.
A flow that fails is a bug someone has to look at. TestedOK files it where the team already looks — GitHub Issues, Linear or Jira — with everything a person needs to reproduce it, and keeps the issue current instead of filing it again.
Set it up
Under App settings → Bug reports, pick the tracker:
- GitHub Issues: the repository, one the TestedOK app is installed on. No token: the app files the issue.
- Linear: the team id (Settings → Teams → the team) and an API key (Settings → API). The key is encrypted under the project's secrets key and never shown again.
- Jira: your site URL (
https://acme.atlassian.net), the email of the account the token belongs to, the project key (APP), and an API token from id.atlassian.com → Security. Issues are created as type Bug.
One tracker per project. Remove it and nothing more is filed; issues already filed stay where they are.
What gets filed
When a blocking flow fails, TestedOK opens an issue titled after the flow, the step it failed at and the reason, with:
- the flow's goal;
- every step, its action and result, up to the failure;
- what was on screen at the failing step — the visible text and the controls;
- the environment, branch and commit, and a link to the run, where the screenshots, the tree and the video are.
Runs that errored (a driver restart, a lost connection) are not bugs in your app and file nothing. Informational suites file nothing either.
One issue per bug
A failure's identity is the flow, the step it failed at, and the screen it failed on (the same screen signature the app map uses, so counts and timestamps do not make it a new screen). The same failure on the next run, the next commit, the next night adds a comment to the issue it already has — "seen again in this run" — rather than a second issue. The run page shows the issue and how many times it has been seen.
When the flow passes again, TestedOK comments that too, with the run and the commit, and marks the report resolved on its side. It does not close the issue: whether the fix is really in is a person's call. If the same failure comes back later, the same issue gets the comment.