-
Notifications
You must be signed in to change notification settings - Fork 0
Add build validation unit tests for CLI packages #364
Copy link
Copy link
Open
Labels
priority:mediumMedium priorityMedium priorityreliabilitySystem reliability and robustnessSystem reliability and robustnessscope:cliIssues related to the CLI packageIssues related to the CLI packagescope:device-profilerIssues related to the device-profiler packageIssues related to the device-profiler packagescope:emulatorIssues related to the emulator packageIssues related to the emulator packagescope:mqtt-bridgeIssues related to the MQTT bridge packageIssues related to the MQTT bridge packagetype:testingTesting improvements or additionsTesting improvements or additionsvalidationInput validation and configuration checksInput validation and configuration checks
Metadata
Metadata
Assignees
Labels
priority:mediumMedium priorityMedium priorityreliabilitySystem reliability and robustnessSystem reliability and robustnessscope:cliIssues related to the CLI packageIssues related to the CLI packagescope:device-profilerIssues related to the device-profiler packageIssues related to the device-profiler packagescope:emulatorIssues related to the emulator packageIssues related to the emulator packagescope:mqtt-bridgeIssues related to the MQTT bridge packageIssues related to the MQTT bridge packagetype:testingTesting improvements or additionsTesting improvements or additionsvalidationInput validation and configuration checksInput validation and configuration checks
Problem
CLI packages (emulator, cli, device-profiler, mqtt-bridge) have no unit tests that validate their build outputs. This includes:
Context
Proposed Solution
Add build validation tests to each CLI package:
packages/emulator/src/build.test.ts:
Apply similar tests to:
Benefits
Effort
~2-3 hours (4 packages × ~30-45 min each)
Implementation Notes
npm run buildin CItest.eachfor DRY test code (see docs/TESTING.md)Related