Does BlazeSQL report analytics that match what actually happened?
BlazeSQL did not report analytics that matched what happened. Its query review page listed only one of five questions and left out both deliberately unanswerable ones, with no answered-versus-unanswered breakdown.
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.
Reported totals include the unansweredFailEvidence
Input 1: “As of September 2, 2026, what's our total revenue in the last 30 days?”
Input 2: “What's our most common payment method?”
Input 3: “How many complaints have we received on social media this month?”
Input 4: “How many customers currently have an active subscription?”
Input 5: “What's our net promoter score for last quarter?”
The tool's response has no text to quote: it is what the evidence under Proofs shows.
Proof 4 · Screen recording · ▶ 0:13–0:14; ▶ 0:13–0:14
| ✗ | Expected: The reported counts match what was run, including unanswered questions, not just successful ones.Found: The page reported 1 query, showed only the active-subscription question, and omitted the other four, including both unanswered ones. |
It had to reflect the full mix of questions in the workspace. The review page showed only one active-subscription query, while four others were absent, including both unanswered ones, so the reported total did not match what was run.
Query mismatch. The only logged query is the active-subscription question from the user account, so the query log does not match either account's activity.
The answers themselves were not shown, so only the reported totals are established here.
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 | Reported analytics match what actually happened → | |
| 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.