test: Add unit tests for led-controller, config-manager, and wifi-utils

[marcodejongh]

Added comprehensive unit tests for the next 3 firmware modules:

• led-controller: 29 tests covering LED initialization, individual/batch
  control, brightness, clear/show operations, blink feedback, and bounds
  checking

• config-manager: 37 tests covering string/int/bool/bytes storage,
  key existence, removal, clear all, and default value handling

• wifi-utils: 27 tests covering connection state machine, credential
  storage, timeout handling, auto-reconnect, state callbacks, and
  status reporting

Also added:

• WiFi.h mock for simulating ESP32 WiFi functionality in native tests
• Library symlinks for led-controller, config-manager, and wifi-utils
• Updated FIRMWARE_TESTING.md to mark these modules as complete

https://claude.ai/code/session_01AKoYRwbDkprP13GwgKA8dt

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
boardsesh	Building	Preview, Comment	Feb 3, 2026 0:34am

[claude]

Claude Review

✅ Ready to merge - No significant issues found.

This PR adds comprehensive unit tests for three firmware modules (led-controller, config-manager, wifi-utils) with good coverage of happy paths, edge cases, and error handling. The WiFi mock implementation is well-designed, and the documentation in FIRMWARE_TESTING.md is properly updated.

[claude]

Claude Review

✅ Ready to merge - No significant issues found.

The PR adds comprehensive unit tests (93 total) for three firmware modules with appropriate mocking infrastructure. Tests cover happy paths, edge cases, and boundary conditions. Documentation is updated correctly.

[claude]

Claude Review

✅ Ready to merge - Comprehensive test coverage for embedded firmware modules with good edge case handling.

Minor observations (non-blocking):

• LED controller tests (test_led_controller.cpp:1012-1019): Many tests only assert true after operations, verifying "no crash" rather than actual behavior. While acceptable for a mock environment where internal state inspection isn't possible, consider adding observable state verification where feasible (e.g., verifying LED array state through exposed getters).

• Unused parameters in main(): All three test files have int argc, char **argv parameters that are unused. Minor, but could use (void)argc; (void)argv; to suppress compiler warnings on stricter settings.