Unit Test Strategy

[ahmetalncak]

Following issues must be solved to clear unit test strategy;

• Place Unity to the project tree,
• Create the unit test file tree,
• Decide on how the unit test to be performed.

[ir-os]

In my mind,

• Place Unity to the project tree, We will have several tools and they should be just helper object so we need to seperate them under a directory. Let's collect all 3rd part tools under "tools" or "misc" folder for now in the main directory.

• Create the unit test file tree, Let's denote each logical piece as a module and let's assume that each module should provide complete solution so we can locate Unit Test under Module itself.

  <Module>
    ->Source
    ->Include
    ->Unittest
           -- TestFiles.c
           -- TestData.h
           -- UnitTest.mk
    module.mk

• Decide on how the unit test to be performed. We need two different interface for unit tests.
  • First is module interface : While one is developing module, he/she should be able to run unit test from module directory to find issues earlier. By that way, naturally, module development can be seperated from rest of development as expected. So, each module should provide a unittest.mk file for unit testing.
  • Second is general system check (will be implemented later) should be able to trigger all unit tests from root directory.

[ir-os]

As a first phase, structure in the previous comment is implemented and it works well. We can re-open this ticket when new ideas are appeared.

All new ideas are welcome!