Checklist developed during Jakarta Release and used since.
Test | Owner/Actions |
Test any configuration not already handled by new TAF tests |
•Persistence on/off (running without core data and with persistence = false pass through) may be covered
•DS REST vs Message Bus (Redis) – test REST with Virtual DS
Test CORS support – check headers there if enabled (both ways secure/non secure. | |
Test reboot of the system. Make sure EdgeX can come back up | Containerized Snap reboot test |
Test device services (with real hardware where possible) |
Test something that uses C SDK
Bacnet update – simulator
Modbus, SNMP, GPIO – real deviceCoAP, RFID, Grove – in process of port to V2; address when ported
Working with service authors to identify minimal tests | Start requiring contributions of DS to include this |
Add MD page to each DS |
Test |
MQTT and HTTP export are important ones – covered TAF
Test on Windows Native
Kamakura Arch topic
running with multiple services of same type (device service and app services) | App service – done in TAF |
DS – should be done in all; not a blocker
Generic test – 2 DS running simultaneous
...
Ticket for adding the device service test to TAF: https://github.com/edgexfoundry/edgex-taf/issues/851 |
The following are now automated by TAF:
- Persistence on/off (persistence = false pass through) is covered
- Test different combinations/permutations of app functions in app services - MQTT and HTTP export functions are covered
- Test running of multiple app services