Hi folks, Given we do not have a sufficient regression tests to catch discovery and onboarding issues at this time, I'd like to request in the short term (especially as we close in on release date) that if you're working on an area that could affect discovery/onboarding, please take 2 minutes to run this smoke test before merging a change to 1.3-rel:
Verify discovery and onboarding are nominally functional: 1. $ cd <out>/resource/csdk/security/provisioning/sample 2. $ ./sampleserver_justworks 3. <open a second console in same dir> 4. $ ./provisioningclient 5. At provisioningclient app menu, choose "10" <enter> 6. after doing discovery, one deviceuuid should appear in "unowned" list 7. at app menu, choose "20" <enter> 8. after doing JustWorks OTM completes... 9. at app menu, choose "10" <enter> 10. after discovery, same deviceuuid should appear in "owned" list 11. Done! Note that it is much easier to see the application menu in a release build... debug build logging can obscure the app output. Note also that a subsequent run of the same steps requires copying the appropriate .dat file from /resource/csdk/security/provisioning/samples to the app directory, to revert to "unowned" state. Thanks for your help in keeping 1.3-rel from breaking during this time-critical phase! Sincerely, Nathan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170502/713f6581/attachment.html>
