hathach 3e5e1f70bf more shorten name 8 lat temu
..
lpc175x_6x 5f26c57b28 shorten descriptor type 8 lat temu
lpc18xx_43xx 3e5e1f70bf more shorten name 8 lat temu
support 3e5e1f70bf more shorten name 8 lat temu
vendor 4239e1390e delete some pdf docs 12 lat temu
.cproject 88f1291c09 replacing RF1GHZNODE with LPCXPRESSO11U68 (not yet implement the actual board) 11 lat temu
.project 2c9ecb300a get all tests passed with lpc18xx_43xx. Need to disable some though 12 lat temu
readme.md d70decf27f update md 12 lat temu

readme.md

Test-Driven Development

Test-Driven Development (TDD) is a development process that relies on the repetition of a very short development cycle: first the developer writes an (initially failing) automated test case that defines a desired improvement or new function, then produces the minimum amount of code to pass that test, and finally refactors the new code to acceptable standards.

In this project, TDD is performed by the help of Ceedling, Unity & CMock as a testing framework. However, due to my limited time, not all the code base is tested yet, and it will be indeed an challenging to keep the test up to the code.

More detail on TDD can be found at

Continuous Integration

Continuous Integration (CI) is used to automatically run all the tests whenever there is a change in the code base. This makes sure that a modification of a file won't break any tests or functionality of others, verifying they all passed.

As many other open source project, tinyusb uses Travis-CI server (free for OOS). You can find my project on Travis here https://travis-ci.org/hathach/tinyusb

Build Status