Symptoms:
- Extension icon is grayed out
- Extension not appearing in Chrome
- "Error loading extension" message
Solutions:
- Verify Chrome version (88+ required)
- Check extension installation:
1. Open chrome://extensions/ 2. Locate Testron 3. Verify "Enabled" is checked 4. Click "Reload" if needed
- Reinstall extension if problems persist
Symptoms:
- Inspector not highlighting elements
- Cannot select page elements
- Inspector freezes
Solutions:
- Refresh the page
- Check console for errors:
1. Open DevTools (F12) 2. Check Console tab 3. Look for inspector-related errors - Ensure page is fully loaded
- Disable other similar extensions temporarily
Symptoms:
- "Cannot connect to AI provider" error
- Timeout errors
- Authentication failures
- 529 "Overloaded" error (Claude specific)
Solutions:
- Verify API key:
// Check API key format Claude: "sk-ant-xxx..." OpenAI: "sk-xxx..." Groq: "gsk_xxx..."
- Check provider status pages
- Verify internet connection
- Try alternative provider
Symptoms:
- 529 error with message "Overloaded"
- Request timeouts
- Slow response times
Solutions:
- Immediate Actions:
- Wait a few minutes and retry
- Switch to another provider temporarily:
# Alternative providers: - Groq (Free tier available) - OpenAI - Ollama (Local, completely free)
- Long-term Solutions:
- Use Ollama as fallback for development/testing
- Implement automatic provider failover
- Schedule high-volume testing during off-peak hours
Symptoms:
- Cannot connect to Ollama
- Model loading failures
- CORS errors
- localhost:11434 not accessible
Solutions:
- Check Ollama service:
# Mac/Linux ps aux | grep ollama # Windows tasklist | findstr ollama
- Verify CORS settings:
# Mac/Linux OLLAMA_ORIGINS='chrome-extension://*' ollama serve # Windows set OLLAMA_ORIGINS=chrome-extension://* ollama serve
- Check model installation:
ollama list
- Verify localhost access:
# Test Ollama API curl http://localhost:11434/api/tags
Symptoms:
- Incorrect cost calculations
- Missing usage data
- Reset failures
- Unexpected token usage
Solutions:
- Review usage logs
- Reset counters if needed
- Verify provider pricing
- Check token calculations
- Cost optimization strategies:
# Free alternatives: 1. Use Groq's free tier 2. Switch to Ollama for testing 3. Enable token usage warnings 4. Set conservative thresholds
Symptoms:
- Frequent token limit warnings
- Cost threshold alerts
- Generation failures
Solutions:
- Adjust token limits in settings
- Monitor usage patterns
- Consider upgrading plan
- Use local Ollama option
Symptoms:
- Invalid TypeScript code
- Missing dependencies
- Selector errors
Solutions:
- Update Playwright installation:
npm install -g @playwright/test npx playwright install
- Verify TypeScript configuration
- Check element selectors
- Review generated code structure
Symptoms:
- Syntax errors
- Command failures
- Configuration problems
Solutions:
- Update Cypress:
npm install cypress@latest npx cypress verify
- Check Cypress configuration
- Verify test structure
- Review selector strategy
Symptoms:
- Java compilation errors
- WebDriver connection issues
- Page Object errors
Solutions:
- Update dependencies:
# Update WebDriver brew upgrade chromedriver # Update Selenium brew upgrade selenium-server
- Check Java version compatibility
- Verify WebDriver setup
- Review Page Object structure
Symptoms:
- Cannot connect to Ollama
- Model loading failures
- CORS errors
Solutions:
- Check Ollama service:
# Mac/Linux ps aux | grep ollama # Windows tasklist | findstr ollama
- Verify CORS settings:
# Mac/Linux OLLAMA_ORIGINS='chrome-extension://*' ollama serve # Windows set OLLAMA_ORIGINS=chrome-extension://* ollama serve
- Check model installation:
ollama list
Symptoms:
- Slow response times
- High CPU usage
- Memory warnings
Solutions:
- Check system resources
- Optimize model settings
- Clear cache if needed
- Consider hardware requirements
Symptoms:
- Incorrect cost calculations
- Missing usage data
- Reset failures
Solutions:
- Review usage logs
- Reset counters if needed
- Verify provider pricing
- Check token calculations
- Extension health check
- API connection test
- Framework compatibility check
- Resource usage monitor
// Available log levels
DEBUG // Detailed debugging information
INFO // General operational information
WARN // Warning messages for potential issues
ERROR // Error messages for serious problems
FATAL // Critical errors requiring immediate attention# Enable debug mode
1. Open extension settings
2. Enable "Debug Mode"
3. Check DevTools console
4. Review debug logs| Code | Description | Solution |
|---|---|---|
| E001 | API Connection Failed | Check API key and internet connection |
| E002 | Token Limit Exceeded | Adjust usage settings or upgrade plan |
| E003 | Model Loading Error | Verify model installation and requirements |
| E004 | Generation Failed | Check input parameters and try again |
| E005 | Framework Error | Update framework installation |
- Connection Errors
- Authentication Errors
- Generation Errors
- Framework Errors
- Resource Errors
- Clear extension cache
- Monitor memory usage
- Close unused tabs
- Restart browser if needed
- Use appropriate models
- Optimize selectors
- Cache common operations
- Monitor network latency
- Check Documentation
- Contact (Via Email:
testronai.com@gmail.com)