| ... | ... | @@ -50,6 +50,7 @@ This allows for 2 things : |
|
|
|
1. Factorize all the common setup & teardown required for tests.
|
|
|
|
2. Creating scenarios for your `TEST_CASE` and test each one separately.
|
|
|
|
> **Why sections names are important**
|
|
|
|
>
|
|
|
|
> Tests are a place in a codebase where people go to understand how to interact with a function or an object. To help them it is advised to have explicit and verbous tests.
|
|
|
|
> This can be done in 2 ways :
|
|
|
|
> 1. with a lot of comment
|
| ... | ... | |
