v1.0.11

What's new?

✨ Smarter test audits. Your AI now knows what's actually broken before it starts reviewing.

Ask your AI assistant for a TestDino audit on your Playwright tests and it
stops guessing. It walks in with the top failing tests, the top flaky
tests, and the top slow tests from your real test runs, for the branch
you're on, before it looks at a single line of your code. The audit that
comes out is grounded in what your test suite is actually doing, not the
AI's hunch.

🧭 The audit conversation, made honest

Before, when you said "audit my checkout flow tests", the AI would read
your files and improvise findings. Now:

1. Your AI pulls context from TestDino first. Which tests keep failing on your branch, which ones are flaky, which ones are getting slow, and how many runs have been recorded lately.
2. Then it reviews your code with that context in hand.
3. Then it files the audit report back to TestDino. Same as before, viewable in the dashboard alongside your test runs.

You'll notice the reports read more like "the checkout total-calculation
test has failed 8 out of the last 10 runs, here's why the assertion is
too loose" instead of generic "consider stronger assertions" advice.

🧩 Two focused tools now drive the audit flow

The audit runs on two tools:

• get_audit_report: fetches the audit context (prompt + branch signals) at the start of a new audit, or browses and retrieves past audit reports.
• submit_audit_report: hands in the completed audit with score, findings, recommendations, and markdown.

Regular conversational usage ("run a TestDino audit on my Playwright
tests") just works, no config changes needed for your Cursor or Claude
Desktop setup.

Heads up for custom automations and CI scripts: if you were calling
test_audit by name in your own scripts, update those references to
get_audit_report and submit_audit_report. The test_audit tool has
been replaced by these two.

Full Changelog

v1.0.10...v1.0.11