Testing and Contributing

A connector is done when it has been proven to work and can be maintained by others. This section walks through that path, in order:

1. Run and Debug Locally^[1] — the core development loop: run your connector with the metricshub CLI against the real device or an emulator, force it with -pd/-c +Id, and inspect detection, discovered instances, and metric values with -vvv.
2. Integration Testing^[2] — freeze the behavior: record the protocol exchanges, build the config/emulation/expected resources, and register the connector in the replay integration tests so mvn verify guards it forever.
3. Contributing^[3] — ship it: what a connector pull request must contain, the CI gates it must pass, and the review checklist maintainers apply.

For connectors migrated from older formats, Legacy and Compatibility^[4] lists the legacy syntax you may encounter and its canonical replacements.