|
|
|
# Testing philosophy
|
|
|
|
|
|
|
|
When you develop new features in Alya, you should regularly add new tests to the testsuite to validate that such a feature works as expected, but also that nobody breaks this feature when contributing to Alya. We won't accept complaints from someone whose Alya features are not evaluated by the testsuite, because it is not reasonably possible to determine all the interweaving between Alya components and the impact of a modification on the whole code behavior without automatic testing. Nevertheless, regarding the developer, we don't validate either the following assertion: _because Alya passes the testsuite, my contribution is of good quality_. Any contribution should be thought, designed carefully without interfering with the normal behavior of Alya, and if possible mentioned to the design team through the issues, not relying only on the testsuite result.
|
|
|
|
The [code coverage](/Code-coverage) helps you to determine if your modifications or additions are tested by the testsuite. In absolute terms, you should design a test to evaluate all the contributions you submit.
|
|
|
|
|
|
|
|
# Git
|
|
|
|
|
| ... | ... | |
