Duku AI is now Antidote
The evidence
Here’s one bug, opened up
An example of what Antidote sends: what went wrong, how far it got, and how to make it happen again.
3 pages observed · Not checked is not passed.
Pages with errors first.
This run used none of your saved test logins. Any sign-in in its steps was part of the key flow itself.
Looking fine isn’t
the same as working
Reading code can’t tell you if sign-in still works. Antidote tries every new release like a customer and flags what broke.
Flows are every path discovery found or you added; key flows are the ones we check on every release.
4 of 6 key flows passed on 4.12 in production · 2 need review · 1 new issue.
Since 4.11: Checkout stopped passing; Export report passes again.
1 of 4 flow checks passed on 4.12 in production · 2 failed · 1 couldn’t be confirmed.
1 new in this release · 1 back again · 3 still seen · 24 no longer seen since 4.11.
The paths discovery found or you added, each with its newest result here. Key flows, above, are the ones we check on every release.
Antidote only counts what it saw work
Four checks: one passed, one failed, one was blocked, one didn’t run. That’s one pass, not three.
4 of 6 key flows passed on 4.12 in production · 2 need review · 1 new issue.
Since 4.11: Checkout stopped passing; Export report passes again.
1 of 4 flow checks passed on 4.12 in production · 2 failed · 1 couldn’t be confirmed.
1 new in this release · 1 back again · 3 still seen · 24 no longer seen since 4.11.
The paths discovery found or you added, each with its newest result here. Key flows, above, are the ones we check on every release.
Questions
What does a bug report look like?
+
Can I reproduce it?
+
How are issues prioritised?
+
Your team goes straight to the fix
Each bug comes with what should have happened, what did, and where it stopped. Nobody loses an afternoon recreating it.