Can AskYourDatabase show the same answer in a different form?
AskYourDatabase changed the answer from a table to a chart without changing the values. The earlier reply shows a seven-category revenue table for August 2026. The charted reply prints the same seven category amounts beside the bars, and the code shown in the chat fetches saved data instead of running new SQL.
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.
Same answer, different representationPassEvidence
Input 1: “As of September 2, 2026, how did our revenue do last month, and what drove it?”
Input 2: “Can you show that as a chart instead?”
The tool's reply is shown in the screenshots under Proofs.
| ✓ | Expected: The form changes; the values do not.Found: The answer changed from a table to a bar chart, and the seven category amounts stayed the same. |
It was checked whether the reply could switch from table to chart without changing values. The charted turn shows the same seven category amounts as the earlier table, and the shown code fetches saved data instead of running new SQL.
Static chart image. The chart appears as an image with a download link. The numbers are printed next to the bars, so hover is unnecessary.
Code before result. The reply shows Python code above the chart, so technical text appears before the result.
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 · 4 tools |
| Capability | Answer Presentation → | |
| Scenario | The user asks to see the same answer a different way → | |
| 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.