[Refactoring] Test suite cleanup and organization #166

New issue

Closed

opened 2025-12-29 03:54:51 +00:00 by john · 0 comments

john commented

2025-12-29 03:54:51 +00:00

Owner

Summary

The test suite in tests/ is functional but could use organization before public release.

Current State

tests/unit/ - 123 unit tests
tests/demo/screens/ - 10 demo screens
tests/regression/ - Bug regression tests
tests/vllm_demo/ - LLM agent demos

Tasks

Organization

Ensure no tests leak into build/ directory (it ships to users)
Review test naming consistency
Remove any obsolete or duplicate tests

Documentation

Add README to tests/ explaining structure
Document how to run specific test categories
Add comments to complex tests explaining what they verify

Coverage

Identify any untested public API
Prioritize tests for commonly-used features
Add tests for recent features (Line, Circle, Arc, focus system)

CI Readiness

Ensure all tests can run headless
Add timeout handling for stuck tests
Create test summary output format

Tests serve as API usage examples for documentation
Demo screens could become tutorial material

## Summary The test suite in `tests/` is functional but could use organization before public release. ## Current State - `tests/unit/` - 123 unit tests - `tests/demo/screens/` - 10 demo screens - `tests/regression/` - Bug regression tests - `tests/vllm_demo/` - LLM agent demos ## Tasks ### Organization 1. Ensure no tests leak into `build/` directory (it ships to users) 2. Review test naming consistency 3. Remove any obsolete or duplicate tests ### Documentation 1. Add README to `tests/` explaining structure 2. Document how to run specific test categories 3. Add comments to complex tests explaining what they verify ### Coverage 1. Identify any untested public API 2. Prioritize tests for commonly-used features 3. Add tests for recent features (Line, Circle, Arc, focus system) ### CI Readiness 1. Ensure all tests can run headless 2. Add timeout handling for stuck tests 3. Create test summary output format ## Related - Tests serve as API usage examples for documentation - Demo screens could become tutorial material