2.2 KiB
2.2 KiB
Quick Start - E2E Collector Test
The Fastest Way to Run the Test
Option 1: Interactive Setup (Easiest)
cd /Users/markhenderson/ai-proxy/vibn-frontend
./setup-e2e-test.sh
This script will:
- ✅ Check if server is running
- ✅ Guide you through getting credentials
- ✅ Test the connection
- ✅ Run the E2E test automatically
Just follow the prompts!
Option 2: Manual Setup (If You Know What You're Doing)
cd /Users/markhenderson/ai-proxy/vibn-frontend
# 1. Get your auth token from DevTools Network tab
# 2. Get your project ID from the URL
# 3. Run:
AUTH_TOKEN='Bearer eyJhbGciOiJSUzI1NiIsImtpZCI6Ij...' \
PROJECT_ID='your-project-id' \
./test-e2e-collector.sh
What the Test Does
Welcome Message
↓
Upload 8 Documents (programmatically)
↓
AI: "I see you've uploaded 8 documents"
↓
User: "I have a GitHub repo"
↓
AI: "Great! Let me help you connect it"
↓
User: "I want the extension"
↓
AI: "Here's how to install it"
↓
User: "That's everything"
↓
AI: "Perfect! Let me analyze..." (auto-transition)
↓
User: "What do you need?"
↓
AI: Uses extraction prompt (mode switched!)
Expected Results
Console Output:
✅ Welcome message contains: 'Step 1', 'Step 2', 'Step 3'
✅ Uploaded: project-overview.md
✅ Uploaded: user-stories.md
... (8 total)
✅ AI acknowledges documents
✅ AI responds to GitHub
✅ AI explains extension
✅ AI triggers auto-transition
✅ Mode switches to extraction
Passed: 15/15
Failed: 0/15
Browser Verification:
- Open the project in browser
- Check AI Chat left sidebar:
- ✅ Documents uploaded (8)
- ✅ GitHub connected
- ⭕ Extension linked
- Verify conversation flows naturally
- Check mode badge shows "Extraction Review"
Troubleshooting
"Command not found: jq"
brew install jq
"Server not running"
npm run dev
"Unauthorized"
Get a fresh token - they expire after 1 hour
"No reply received"
Check server logs for errors
Ready? Run This:
cd /Users/markhenderson/ai-proxy/vibn-frontend
./setup-e2e-test.sh
That's it!