Testing Guide
Testing Strategy
Manual Testing
Primary testing method for this project:
- Command Testing: Test each command with various inputs
- Error Cases: Test error handling and edge cases
- Integration: Test command interactions
- Browser Testing: Test across different browsers
- Responsive: Test on different screen sizes
Test Checklist
Core Functionality
Commands
Error Handling
Browser Compatibility
Responsive Design
Testing Commands
Test Command Execution
# Start Jekyll server
bundle exec jekyll serve
# Open browser
open http://localhost:4000/terminal/
Test Specific Commands
- Open browser console (F12)
- Execute commands in terminal
- Check console for errors
- Verify output format
Test Error Cases
- Invalid command:
invalid-command
- Missing file:
cat /nonexistent.txt
- Invalid path:
cd /invalid/path
- Missing data: Disable Jekyll data loading
Debugging
Browser Console
Check for:
- JavaScript errors
- Network errors
- Data loading issues
Jekyll Build
Check for:
- Plugin errors
- Data file generation
- Build warnings
Common Issues
Command not found
- Check registration in core.js
- Verify script loaded in layout
- Check appMap entry
Data not loading
- Verify
window.JEKYLL_DATA exists
- Check filesystem-loader.js
- Verify data files in
_data/
EcmaOS not working
- Check kernel.js loaded
- Verify import path
- Check console for errors
- Page load time
- Command execution speed
- Terminal rendering performance
- Memory usage
Accessibility Testing
- Keyboard navigation
- Screen reader compatibility
- High contrast themes
- Focus indicators