Documentation Index
Fetch the complete documentation index at: https://docs.veval.dev/llms.txt
Use this file to discover all available pages before exploring further.
What is a scenario?
A scenario is a named set of test cases for your agent. Each run posts pass/fail results to the dashboard so you can track quality over time. Scenarios have two item types:| Type | How it works | Cost |
|---|---|---|
| Synthetic | Live LLM, fresh input you define | Real API cost |
| Trace-backed | Mocked LLM, replays a recorded production trace | Zero |
RunScenarioAsync
| Parameter | Description |
|---|---|
scenarioName | Identifies the scenario in the dashboard |
agent | Your agent — same signature as RunAsync |
scenarioAssertions | Assertions that apply to every item |
items | List of ScenarioItem — inline or fetched from dashboard |
Synthetic items
Use these for new inputs you want to test with a live LLM.Trace-backed items
Use these to replay a recorded production trace with mocked LLM responses — no API cost.The trace must have recorded steps. If it has none, Veval throws rather than silently calling the live LLM.
Per-item assertions
EachScenarioItem can carry its own assertions on top of the scenario-level ones:
Fetching items from the dashboard
Ifitems is null, Veval fetches items for the scenario from the API automatically. This lets you manage test cases in the dashboard without redeploying code.
ScenarioRunResult
| Member | Description |
|---|---|
Passed | True if all items passed |
PassCount | Number of passing items |
FailCount | Number of failing items |
Results | List of ItemRunResult |