For QA leads and developers who open Certyn once a day and want to know what needs a person.
Your setup
- Suites ran overnight or after a deploy. Maybe your CI pushed its results too.
- Some runs found possible bugs. Some tests failed.
- You have 10 minutes and want one list, in order, with links.
Say this to Certyn
What needs me today? Most urgent first.
What Certyn does
- Reads the project's inbox (
app.inbox.list):- actions: open critical or major issues, findings in review, test cases that need review or are quarantined, failed tests with no linked issue, environment errors, and the runs active now;
- notifications: recent suite runs (passed, failed, stopped) and new issues.
- Orders them: blocking bugs, then findings in review, then failed tests.
- Gives one line per item with a link and the decision it needs.
- Does the work you pick in the same chat. It asks before it changes a record or starts a run.
The same list is on Home, under the chat, in Needs you. The bell at the top shows the notifications.
The daily loop
- What needs me today?
- Findings in review: confirm the real bugs, close the rest with a reason.
- Deployed fixes: retest issue 12.
- Failed tests with no issue: why did this fail? Certyn reads the run and says: product bug, broken test, or setup problem.
- Release day: Can we ship staging?
What you get
- One ordered list instead of five pages.
- Decisions made in the chat: confirm, close with a reason, retest, run again.
- By email if you want: Email me what needs me every morning. After you approve, it comes at 08:00 in your time zone (UTC if none is set).
Limits
- The inbox shows only what Certyn knows: its runs, results your CI pushed, and its issues.
- Nothing closes by itself. A finding stays in review until a person decides, even if a later run passes.
- Needs you shows the first items. For all of them, ask, for example list every finding in review.
- The morning email goes to your account email, only when email notifications are on.