Can Draxlr change an answer's format on request without changing its information?
Draxlr redrew its revenue answer as a bar chart when asked, and the numbers stayed the same. The chart's seven category changes, from furniture down $6,562.19 to bedding and rugs up $1,129.47, are the first answer's figures and the reference figures to the cent, and the chart's own table and query are unchanged.
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 · Original revenue question: “As of September 2, 2026, how did our revenue do last month, and what drove it?”
Input 2 · Chart request: “Can you show that as a chart instead?”
Revenue answer
August 2026 revenue was $14,403.87, down $3,858.77 from July's $18,262.64. The drop was driven mainly by furniture (-$6,562.19), with outdoor and patio also down (-$448.84); gains in bedding and rugs (+$1,129.47) and kitchen and dining (+$803.14) partially offset it. This includes all order statuses and uses placed date.
Chart reply
Here it is as a bar chart.
Transcribed from Proof 1 · Screen recording at 0:00
Every message the tool sent, in order (2)
- Revenue answer
Printed above.
- Chart reply
The final response, printed above.
| ✓ | Expected: Asked to show the same answer another way, the product changes the form while every value stays the same.Found: A bar chart with seven values: furniture -$6,562.19, bedding and rugs $1,129.47, kitchen and dining $803.14, home decor $555.64, outdoor and patio -$448.84, lighting $409.64, storage and organization $254.37, as in the reference. |
It is a Pass: the form had to change and the values stay the same. The second request asked only for a chart; its seven printed values equal the first answer's seven revenue changes, and its table holds the same seven rows and the same query, so nothing was recomputed.
The chart plots the change. The bar chart, subtitled August 2026 Revenue Change by Category, plots each category's change against July 2026; the August and July revenue figures themselves stay in the chart's Result tab.
Axis labels partly hidden. The chart's x axis names only every other category and cuts off the last name at the panel edge; hovering the rightmost bar shows its full name, storage and organization, and its value.
The earlier table stays available. The chart arrived as a second step of the same result instead of replacing the first answer's seven-row table, which stays reachable as step one.
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 user asks to see the same answer a different way → | |
| Tool | Draxlr → |
Global scenario definition → · Global capability definition → · Draxlr 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.