Unit Testing guidelines

We like to ensure everyone using picoTCP that we take software quality very serious. As we have discussed in a previous post, there is a big collection of testing tools and scripts that are running continuously on our code base (TICS, Check, ...)

Since picoTCP is freely available and everyone can contribute to it, it is important to define a good and standardized way of testing bits and pieces of functionality before it ends up in the master branch on GitHub. With this in mind, we've written a short description on how parts should be tested when working on a feature or specific code change in your fork.

Like all the other guides, we've published this guide on the picoTCP GitHub wiki.