| ... | @@ -2,6 +2,8 @@ |
... | @@ -2,6 +2,8 @@ |
|
|
|
|
|
|
|
Unit-tests are an **ESSENTIAL** part of any codebase to assert the behaviour of a new feature and the consequences of any modification in the codebase. Any piece of production code that is not covered by a unit-test will probably later lead to a longer debug session or worse: undetected bad/undefined behaviours.
|
|
Unit-tests are an **ESSENTIAL** part of any codebase to assert the behaviour of a new feature and the consequences of any modification in the codebase. Any piece of production code that is not covered by a unit-test will probably later lead to a longer debug session or worse: undetected bad/undefined behaviours.
|
|
|
|
|
|
|
|
|
[TOC]
|
|
|
|
|
|
|
## Structure of unit_test folder
|
|
## Structure of unit_test folder
|
|
|
|
|
|
|
|
Each Aidge module can be supplemented by a test directory called ``unit_tests`` with the following hierarchy:
|
|
Each Aidge module can be supplemented by a test directory called ``unit_tests`` with the following hierarchy:
|
| ... | | ... | |
