edgexfoundry / edgexfoundry/device-bacnet-c
Add .md pages describing how to test (with real hardware)
- Dominant language
- C
- Stars
- 16
- Forks
- 22
- Avg merge
- 21h 15m
- Merged PRs (30d)
- 1
Description
Per Kamakura planning meeting (Nov 21), each device service should provide a HOWTOTEST.md page that describe how to check the base functionality of the device service with real hardware. These tests should be run manually before each release.
Each device service should also provide a WORKSWITH.md page that lists the actual hardware (make, model, web site link, etc.) that the device service has been tested with and known to work with. Provide enough details on the device/sensor so that an adopter would know where to go to get the same device.
Contributor guide
Research direction
Start by inspecting the device service and identifying the real hardware available for testing. Add HOWTOTEST.md with manual base-function checks to run before releases, and WORKSWITH.md with make, model, website, and adopter-relevant details for hardware known to work. Done means both pages document the service's real hardware testing process and supported devices.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- documentation, embedded-iot
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100