You get one clear summary in Slack or email. It tells you first whether anything is broken, with the details underneath.
A pass rate on its own makes everyone open the dashboard to find out what it means. Cofactor tells you what happened, then shows the details.
The first line tells you whether anything is actually broken, before any numbers.
New failures are listed separately from known ones, so an old issue doesn’t look like an emergency.
Each failure is explained in terms of your product, with a link to the issue that was filed.
You can send each suite’s report to a different channel or person, so each team only sees what matters to them.
A message in the channel that owns that part of the product, with a thread so the discussion stays with the run.
The same summary as an email digest, for people who don’t use Slack much.
Send the raw result to your own endpoint if you want to handle routing yourself.
POST /your-endpointWill this be noisy?
By default, you only hear about failures and changes. A nightly run where everything passed can be a short digest or nothing at all.
Can the summary be wrong?
It can miss things, so every statement in it links to the run, video and trace behind it.
Who can see the reports?
Only the people and channels you send them to. Reports don’t contain credentials, and the videos and traces stay behind your login.