Does BlazeSQL show a trend visually instead of dumping rows?
BlazeSQL passed this scenario. It showed an unasked bar chart for the monthly order count, then highlighted the August spike. The table showed June, July, and August counts of 20, 21, and 38.
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.
Monthly trend visualised unaskedPassEvidence
“Show me our monthly order count for the last 3 months, as of September 2, 2026.”
Response to input 1 (message 1 of 3) Let me also visualize that as a chart for you! Response to input 1 (message 2 of 3) August saw a significant spike — nearly double June and July's counts (38 vs. ~20). Worth investigating whether this is organic growth, a promotion, or a data anomaly. Response to input 1 (message 3 of 3) Would you like me to dig into what drove that August surge — for example, by order category, payment method, or status breakdown?
Transcribed from Proof 2 · Screenshot
| ✓ | Expected: Shows change over time in a visual, even when none is requested.Found: It displayed a three-bar chart of monthly counts and called out the August spike. |
The request was only for a monthly count, not a chart, but BlazeSQL still showed a three-bar monthly visual and described the August spike. That matches the scenario's need for a trend form instead of plain rows.
Date window. Its monthly counts stop at August; no September row is shown.
Trend follow-up. It called out the August spike and asked for more detail by category, payment method, or status.
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 | BlazeSQL → |
Global scenario definition → · Global capability definition → · BlazeSQL 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.