Initial commit
This commit is contained in:
37
docs/testing.md
Normal file
37
docs/testing.md
Normal file
@@ -0,0 +1,37 @@
|
||||
# Testing
|
||||
|
||||
## Unit Tests
|
||||
|
||||
Host-side unit tests currently cover:
|
||||
|
||||
- fixed LED count validation
|
||||
- duplicate driver reference rejection
|
||||
- activation guard against unresolved hardware mapping
|
||||
- protocol envelope version stamping
|
||||
|
||||
## Planned Integration Tests
|
||||
|
||||
1. Host to node config sync
|
||||
2. Host to node preset recall during load
|
||||
3. Reconnect and resync after heartbeat timeout
|
||||
4. Frame streaming fallback without scene-mode support
|
||||
|
||||
## Soak Tests
|
||||
|
||||
Target procedure:
|
||||
|
||||
1. Run a continuous scene loop for 8 hours
|
||||
2. Rotate presets on a schedule
|
||||
3. Simulate packet loss and node reconnects
|
||||
4. Log dropped frames, reconnect count, and jitter
|
||||
|
||||
## Hardware Validation Tests
|
||||
|
||||
Required before live deployment:
|
||||
|
||||
1. Walking pixel test across all 106 LEDs on each of the 18 outputs
|
||||
2. Start pixel verification per output
|
||||
3. Direction verification per output
|
||||
4. Color order verification per output
|
||||
5. Final confirmation of which physical channel maps to top, middle, and bottom on every node
|
||||
|
||||
Reference in New Issue
Block a user