espressif_tinyusb/tests
hathach d70decf27f update md 2014-03-28 17:50:30 +07:00
..
lpc18xx_43xx able to get connect status change interrupt occured 2013-12-13 12:26:37 +07:00
lpc175x_6x change MCU to TUSB_CFG_MCU 2013-11-25 12:48:27 +07:00
support change TUSB_CFG_CONTROLLER0/1_MODE to TUSB_CFG_CONTROLLER_0/1_MODE for clearance 2013-10-24 15:32:54 +07:00
vendor/ceedling delete some pdf docs 2013-06-04 11:47:37 +07:00
.cproject change MCU to TUSB_CFG_MCU 2013-11-25 12:48:27 +07:00
.project change TUSB_CFG_CONTROLLER0/1_MODE to TUSB_CFG_CONTROLLER_0/1_MODE for clearance 2013-10-24 15:32:54 +07:00
readme.md update md 2014-03-28 17:50:30 +07:00

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