tac0S
Template Affectional Command Operating System
**/!\ Do not PUSH on RELEASE-branch. ONLY the CI is allowed to push on RELEASE-branch. !!!!**

tacOS

Sauce blanche algérienne chef !

Project architecture:

Testing

How

All tests are perform by the CI

The test_unit.sh introspect all test_step<X> folder and launch tests. Each test script need to have a <testX>_result file in the results_test folder. If the test script need a input, store the input file in input_test folder (the script check automaticly if their are a input file or not). The input test file need to be call like <testX>_input.

Please make sure that your files architecture repect the Testing architecture according the following architecture schematic

Test Architecture schematic

1 test
2 │ README.md
3 | test_unit.sh
4 └───test_step2
5 │ │ test1.c
6 │ │ test2.c
7 │ │ ...
8 │ │
9 │ └───input_test
10 | │ │ test1_input
11 | │ │ test2_input
12 | │ │ ...
13 | └──results_test
14 | │ │ test1_result
15 | │ │ test2_input
16 | │ │ ...
17 │
18 └───test_step3
19 | │ ...
20 |
21 └─── ...