What Assets Are For
When you write a verification assertion like “Does the shop screen match the expected layout?”, the evaluator needs something to compare against. That’s where assets come in — they provide the ground truth. Common uses:- Visual regression — Compare a screenshot from a run to a reference image of how the screen should look
- Layout validation — Check that UI elements are positioned correctly relative to a baseline
- Animation reference — Compare video clips to verify animations play as expected
Uploading Assets
Each asset can contain one or more files:| File type | Formats | Max size |
|---|---|---|
| Images | PNG, JPEG, GIF, WebP | 10 MB |
| Videos | MP4, WebM, MOV | 100 MB |
Using Assets in Verifications
Assets are linked to verification assertions through reference asset IDs. When setting up an assertion, you can attach one or more assets as references. The AI evaluator will use these references when answering the assertion’s query. For example:- Assertion: “Does the main menu match the expected design?”
- Reference asset: A screenshot of the approved main menu design
- Evaluator behavior: Compares the run’s actual main menu screenshot to the reference and reports any differences
Managing Assets
- Project-scoped — Assets belong to a project and are available across all scenarios and verifications within it
- Multi-file — A single asset can contain multiple files (e.g., several screenshots of the same screen at different states)
- Archive and restore — Deleted assets are soft-deleted and can be recovered from the Archive section if needed
Quick Reference
| Concept | What it is |
|---|---|
| Asset | A reference material (image or video) uploaded to a project |
| Reference asset | An asset linked to a verification assertion as a comparison baseline |
| Thumbnail | Auto-generated preview for quick browsing |