Can Basedash save an answer and reproduce it when reopened?
Basedash saved the monthly-order answer as a dashboard chart and reproduced it in another account's session. The counts remained 11 for June 2026, 18 for July 2026 and 27 for August 2026, totalling 56.
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.
Saved answer reopened in a new sessionPassEvidence
“Show me our monthly order count for the last 3 months, as of September 2, 2026.”
For the three complete months before September 2, 2026, monthly order counts were: June 2026 11, July 2026 18, August 2026 27
Transcribed from Proof 1 · Screen recording at 0:01
| ✓ | Expected: Reopening a saved answer reproduces the same answer and makes it identifiable as the same question.Found: The new session retained the chart's title and original counts: June 2026, 11; July 2026, 18; August 2026, 27; total, 56. |
Reopening had to preserve the answer and identify its question. Basedash's own dashboard feature reproduced the chart and values in a second account's new session, with a title naming the measure and period.
How orders were counted. The monthly-order chart's footnote says counts include cancelled orders, group orders by placement date in Calcutta local time, and exclude September's partial month.
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 | Reporting → | |
| Scenario | The user wants to keep an answer they just got → | |
| Tool | Basedash → |
Global scenario definition → · Global capability definition → · Basedash 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.