I expect to have some real hardware in hand (CC2538 based boards of my own design, and possibly some MSP430 boards after that) in the coming weeks (months if I don't get into gear). I'd be more than willing to contribute some whatever time is needed to running tests on real hardware if it's helpful (assuming that I have the gear, my LA isn't the greatest but that could change).
On a related note, how much (if any) of RIOT's code base is covered by real unit tests? Has any thought been given to a TDD type of unit test battery? With the all the refactoring going on in the network stack this might be the perfect time to get serious about writing some tests. On Wed, Nov 5, 2014 at 10:58 PM, Teemu Hakala <[email protected]> wrote: > On 5.11.2014, at 17:42, Martine Lenders <[email protected]> wrote: > > 2014-11-05 16:24 GMT+01:00 Philipp Rosenkranz < > [email protected]>: > >> Dear RIOTers, >> >> in order to discuss possible enhancements to our current test >> setup I would like to invite you to a dedicated RIOT testing meeting. >> >> The main topics to discuss will be: >> >> * Automated hardware based regression testing. >> > > This is where we have existing code for Robot Framework. ELL-i is able to > run unit tests > in real hardware and apply tests with a logic analyser. > > > * CI systems: Jenkins / buildbot or both? >> * Simulations / Virtualization as part of our testing strategy. >> > > I'd like that whatever test system it is, an individual developer could > run it even offline. > For this goal, virtualization seems to be the easiest path. > > > We also should discuss robot framework [1] as suggested by ELL-i at the > workshop. I did not look into it too much, but from as much as I gathered > it might be helpful to automate a lot of already existing tests in our > `tests/` directory. It's also integratable into Jenkins if this is > important to you [2]. > > > RF is Python and its test cases are in wiki markdown format. This makes it > easy to separate test spec from the testing framework itself allows > nonprogrammers to participate in some of the generating of test cases. I'm > hoping Asif can join the meeting as he is the key RF person for ELL-i and > has written bidirectional Python<->C hooks for running unit tests against > the ELL-i emulator. The emulator itself is emulating a MCU including > register controlled peripherals so we have some interesting tests coming > up. It could be used in Riot OS context as well. > > - t > > > _______________________________________________ > devel mailing list > [email protected] > http://lists.riot-os.org/mailman/listinfo/devel > >
_______________________________________________ devel mailing list [email protected] http://lists.riot-os.org/mailman/listinfo/devel
