Can Dot show what people have been asking?
Dot's History listed every question with the account that asked it: six from the admin account and three from the standard account. Filtered to the standard account, the analysis footer read 3 chats for its 3 questions; its Messages tile read 5 because it also counts Root proposal sessions Dot created itself.
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.
Usage view across two accountsPassEvidence
A new chat was opened in the admin account.
Input 1 · Admin account, 18:06–18:09 IST: “As of September 2, 2026, what's our total revenue in the last 30 days?”
Before each of Inputs 2–6: A new chat was opened.
Input 2 · Admin account, 18:06–18:09 IST: “What's our most common payment method?”
Input 3 · Admin account, 18:08 IST: “How many complaints have we received on social media this month?”
Input 4 · Admin account, 18:06–18:09 IST: “How many customers currently have an active subscription?”
Input 5 · Admin account, 18:09 IST: “What's our net promoter score for last quarter?”
Input 6 · Admin account, 18:32 IST: “What membership tier is Alice Prosser on?”
The standard account was used, with a new chat opened for the question.
Input 7 · Standard account, 18:39 IST: “What membership tier is Alice Prosser on?”
Before each of Inputs 8–9: A new chat was opened.
Input 8 · Standard account, 18:40 IST: “How many customers currently have an active subscription?”
Input 9 · Standard account, 18:41 IST: “What's our net promoter score for last quarter?”
The tool's response has no text to quote: it is what the evidence under Proof shows.
Proof 1 · Screen recording · ▶ 5:40–5:50; ▶ 5:55–6:07
| ✓ | Expected: The questions appear, attributable to the account that asked them, and the total matches what we ran.Found: History attributed all 9 questions to their askers (6 admin account, 3 standard account). The standard account's analysis footer showed 3 chats for 3 questions; its Messages tile showed 5. |
The test asks for a question list that is complete and shows who asked each question. Dot's History chat rows and per-chat headers show that, and the standard account's filtered list held exactly its 3 chats. The Messages tile counts broader activity, so it does not decide the result.
Proposal sessions affect totals. The standard account's Messages tile also counts automatically generated proposal sessions, attributing them to the account whose questions prompted them.
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 | Someone needs to see what people have been asking → | |
| Tool | Dot → |
Global scenario definition → · Global capability definition → · Dot 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.