Hey all, Yes, I’ve been working on a framework that will make it easy(er) to develop tests that can run on native HW as well as a simulated environment (ie “newt test …”). There’s actually a fair amount of good functional test code but it's not not easy to package to run on target devices. I’m modifying the existing frameworks to allow tests to be allow control over pre and post setups for various environments as well as reporting results. The tests will be split up in a way so that one can pick and choose which tests to run in a given test application. Stay tuned, I’ll have something ready shortly and I’ll look for comments to make it more usable.
- peter > On Oct 5, 2016, at 7:24 PM, Sterling Hughes <[email protected]> wrote: > > Indeed - Peter has been working on making this a little easier to do for the > various hardware platforms that Mynewt runs on (breaking up unit tests to > make sure they run well on physical hardware, making it easier to include > only specific tests on given platforms, etc.) > > Peter: can you chime in on some of the changes that are pending to develop? > > On 5 Oct 2016, at 18:47, Kevin Townsend wrote: > >> Sorry, to answer my own question the 'test' app in apache-mynewt-core show >> how tests can be run on native HW. >> >> On 06/10/16 00:16, Kevin Townsend wrote: >>> Hi Sterling, >>> >>> Are you able to run the unit tests on real HW via newt to pipe the results >>> back to the console? That would probably remove the need to 'mock' >>> peripherals in most cases, and be a significantly easier way to run a set >>> of tests that have specific HW requirements, such as BLE which isn't >>> available in the simulator today (understandably). Or are the unit tests >>> currently limited to the simulator running as a native binary? The latter >>> was my understanding but I haven't dug very deeply into it either. >>> >>> Using the native BLE HW on OS X or via Bluez with the simulator would of >>> course be /amazing/, but I think there are a WHOLE LOT of other higher >>> priority features to add before that. :) >>> >>> K. >>> >>
