Overview
LiteAgent creates a structured directory hierarchy to store all test results, making it easy to analyze agent behavior and debug issues. Each test run generates multiple types of data for comprehensive analysis.Directory Hierarchy
File Types Explained
Core Files
- Database File
- Site & Task Files
- Scratchpad
File: Contains every click, type, scroll, and navigation event with timestamps and element information.
{task}.db
Format: SQLite database
Purpose: Complete interaction logMedia Files
- Video Recording
- HTML Snapshots
- rrweb Recording
Directory:
video/
File: {task}.mp4
Purpose: Visual playback of the entire testHigh-quality screen recording showing exactly what the agent saw and did. Useful for:- Debugging failed tests
- Demonstrating agent behavior
- Understanding UI interactions
Debug Files
- Trace Files
- Commands
Directory:
trace/
File: {task}_trace.zip
Purpose: Playwright debuggingContains detailed browser traces for debugging:- Network requests
- JavaScript execution
- Performance metrics
- Error details
Example Output Structure
Successful Test Run
Failed Test Run
File Size Guidelines
Typical File Sizes
File Type | Small Test | Medium Test | Large Test |
---|---|---|---|
Database | 50-200 KB | 200-500 KB | 500KB-2MB |
Video | 5-15 MB | 15-50 MB | 50-200 MB |
HTML snapshots | 100-500 KB | 500KB-2MB | 2-10 MB |
rrweb events | 200KB-1MB | 1-5 MB | 5-20 MB |
Trace files | 5-50 MB | 50-200 MB | 200MB-1GB |
Storage Considerations
Accessing the Data
Quick File Access
Programmatic Access
Output Management
Cleanup Scripts
Backup Strategy
Parallel Test Organization
When running parallel tests, each gets a unique directory:Integration with Analysis Tools
Database Tools
Video Analysis
rrweb Replay
Next Steps
Database Schema
Detailed database structure and queries
Video Analysis
Working with video recordings
Trace Debugging
Using Playwright traces for debugging