RIOT's new test system

This page acts as a hub for all wiki pages which are related to the new proposed test system for RIOT.

• Requirements and challenges
• Overview of the proposed architecture
• Current test coverage matrix for core and sys modules

#FAQ

Are any changes to the unit test system planed?

No. We therefore highly encourage you to write unit tests according to this howto.

What will change for me as a developer

• We will introduce means to test code which is currently only tested manually.
• You will be able to test hardware dependent code in our distributed test system. For example: right now our test system doesn't check whether a code change to a transceiver drivers which may make sense on one platform renders it unusable on another platform.
• Hopefully, it will be a system that also performs faster by allowing developers/reviewers to selectively run tests which are most relevant for the code change (e.g.: a comment change doesn't require build tests and a change to an application doesn't require driver tests etc.)

#TODO list

• Architecture -> in detail description of components missing
• Test coverage matrix -> sys modules missing