Does AskYourDatabase report totals that match what actually happened?
AskYourDatabase's reported counts matched what was run in the two accounts. The first account showed 3 conversations and the second showed 2, and the messages list showed the five questions with timestamps; each count included an unanswered chat.
1 of 1 test case passed
Every test case in this scenario has a result.
The test case
Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above is based on this test case.
Reported totals include the unansweredPassEvidence
Input 1 · Person 1 account, 2026-10-07: “As of September 2, 2026, what's our total revenue in the last 30 days?”
Before each of Inputs 2–5: A separate chat was used for this question.
Input 2 · Person 1 account, 2026-10-07: “What's our most common payment method?”
Input 3 · Person 1 account, 2026-10-07: “How many complaints have we received on social media this month?”
Input 4 · Person 2 account, 2026-10-07: “How many customers currently have an active subscription?”
Input 5 · Person 2 account, 2026-10-07: “What's our net promoter score for last quarter?”
Response 1 answers Input 1.
Response 2 answers Input 2.
Response 3 answers Input 3.
Response 4 answers Input 4.
Response 5, the final response, answers Input 5.
I don't have access to any Net Promoter Score (NPS) data in this database
Quoted from Research submission
Every message the tool sent, in order (5)
- Revenue answer
the total revenue in the last 30 days (August 3 – September 2, 2026) was $8,828.82. This figure excludes cancelled orders.
- Payment-method answer
Your most common payment method is card, used in 162 orders
- Social-media complaints reply
I don't have access to social media data in this database. The database contains tables for customers, orders, products, subscriptions, returns, tickets, and related records — but nothing tracking social media mentions or complaints. If you're looking for customer complaints, the closest match would be the tickets table, which tracks support issues. Would you like me to check how many support tickets were opened this month instead?
- Active-subscription answer
4 customers currently have an active subscription.
- Net promoter score reply
The final response, printed above.
| ✓ | Expected: Reported counts should match what was run, including unanswered chats.Found: The first account shows 3 conversations and the second shows 2, and each count includes the unanswered chat on that account. |
The product had to count what was run on each account, including unanswered chats. The first account shows 3 conversations and the second 2, and the messages list shows the five questions with timestamps.
Conversation reporting scope. The History counters count conversations rather than questions and do not separate answered from unanswered chats.
Configuration and setup
How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.
- Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
- Fail: at least one expected behaviour clearly didn't happen; the test case's result says which one and quotes the tool.
- Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the test case's result says what's missing.
Where this sits in the benchmark
This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.
| Level | Name | Scope |
|---|---|---|
| Benchmark | AI Database Agents → | 28 scenarios · 11 tools |
| Capability | Analytics & Observability → | |
| Scenario | Reported analytics match what actually happened → | |
| Tool | AskYourDatabase → |
Global scenario definition → · Global capability definition → · AskYourDatabase product page →
History of this result
What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.
Act on this result
Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.
Verify the proof files
These files support this result. Open a file to inspect the original evidence.
File fingerprints (SHA-256)
A fingerprint identifies the exact file used for this result.