Does AskYourDatabase show a trend visually instead of dumping rows?
AskYourDatabase returned monthly order counts without volunteering a visual to show the trend. Its answer used a text table and described the increase in words.
1 of 1 test case failed
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.
Monthly trend visualised unaskedFailEvidence
“Show me our monthly order count for the last 3 months, as of September 2, 2026.”
Here are the monthly order counts for the last 3 months (as of September 2, 2026): Month | Order Count June 2026 | 9 July 2026 | 23 August 2026 | 26 (Note: September shows 1 order, but that's only for the first day of the month before the September 2 cutoff.) The last three full months show a steady upward trend, from 9 orders in June to 26 in August.
Transcribed from Proof 1 · Screenshot
Every message the tool sent, in order (3)
- Progress
I'll query the monthly order counts for the last 3 months as of September 2, 2026.
- Generated SQL · not part of the answer
SELECT DATE_TRUNC('month', placed_at) AS month, COUNT(*) AS order_count FROM orders WHERE placed_at >= '2026-06-02' AND placed_at < '2026-09-02' GROUP BY DATE_TRUNC('month', placed_at) ORDER BY month; - Answer
The final response, printed above.
| ✗ | Expected: Show change over time visually without being asked for a visual.Found: The reply contained a three-row text table and written trend commentary; no chart, plot or other visual showed change over time. |
The database query completed and returned monthly counts, but the full exchange contained no trend visual. This was a failure to volunteer a visual in the default chat answer, not an execution failure or a conclusion that AskYourDatabase cannot produce charts on request.
Shifted June count. The table shows June as 9 instead of 10, and it presents June as a full month in the trend.
September note. September is missing from the table, and the note gives it 1 order instead of 2.
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 | Answer Presentation → | |
| Scenario | The answer is a trend or a comparison → | |
| 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.