Test Driven Development for Embedded C

Test Execution Order

Tests run backward in CppUTest. Other test harnesses might run in some other order. Test order should not matter, and you should not count on any particular order. Tests should be independent of each other, each one its own little experiment. One test might logically precede another in the design or as documentation, but when it comes time to run them, unit tests must be designed to be independent of each other. Prefer tests that depend only on setup and teardown.