[riot-notifications] [RIOT-OS/RIOT] [RFC] tests: add 'test-manual' targets (#11954)

Francisco notifications at github.com
Fri Sep 27 10:13:11 CEST 2019


> The problem with going to test-auto and the others in make test and test-all is that these will mostly not be run with make test anyway but make flash; sudo make test, connect hardware; edit the periph_conf.h; make flash test. And cannot be 100% automated if you do not have a dedicated board and environment for that application. And if you have a board with the hardware connected and the Makefile.local for it, then you are also at a point where you can call make manual-test in your script.

The only `auto` for you would be `native` then. I think making the distinction because of board setup makes no sense in this case. We are at a point where we only make a distinction between `unit-tests` and all other tests. `native` is still a board and although there is no "flashing" the compiled code is still bootstrapped and executed, the same thing is happening in hardware. Also the opposite of "manual" is "automatic", so having the duality makes a lot of sense to me ;) .

I would actually like having:

- `test`: all tests
- `test-manual`: all tests that do not require configuration except plugin in a board
- `test-auto`: `test` minus `test-manual`

The special case for native you are mentioning I don't know how to handle, or in general cases where for some boards the test ins manual and for others automatic.. Maybe native should be an exception where all tests are run no matter what? 



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/11954#issuecomment-535840317
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190927/a6862072/attachment.htm>


More information about the notifications mailing list