Scenario in benchmark · Version 1
A bad file in the upload
A bad file uploaded for ingestion cannot be processed.
How the tools performed
Every in-scope tool is visible. Outcomes come from current published Results for this scenario and benchmark version.
No published results for this scenario yet.
No published result does not tell you whether a tool has been tested. Test coverage is shown only for comparable published Results.
| Tool | Published outcomes | Test coverage | Result |
|---|---|---|---|
| No published result · alphabetical | |||
| Denser AI | — | — | No published result |
| Dify | — | — | No published result |
| FutureSmart Document Intelligence | — | — | No published result |
| Llama Cloud | — | — | No published result |
| Onyx | — | — | No published result |
| Vectara | — | — | No published result |
| Vectorize.io | — | — | No published result |
Assessed = Pass + Fail + Not gradable. Gradable = Pass + Fail. Both use the published Result’s pinned-test denominator. — means not publicly available.
Test design
- Pinned test cases
- 1
- Disclosure
- 0 public · 1 withheld
- Capabilities exercised here
- Data Ingestion
What this scenario evaluates
- Whether the service reports failure for the uploaded file.
- Whether the file is marked as not processed or not ingested.
- Whether the upload is presented as unsuccessful rather than successful.
Specific test-case inputs and grading live on the related test-case pages.
How the results are graded
- Pass: the test-case expectations hold.
- Fail: an expectation demonstrably does not hold.
- Not gradable: the evidence cannot establish the outcome.
Version 1 uses test-case expectations; no scenario rubric is pinned.
Benchmark methodology →