Nicolas Cantu
425fb36dc9
Some checks failed
CI - 4NK Node / Code Quality (push) Failing after 30s
CI - 4NK Node / Unit Tests (push) Failing after 29s
CI - 4NK Node / Integration Tests (push) Successful in 27s
CI - 4NK Node / Security Tests (push) Failing after 28s
CI - 4NK Node / Docker Build & Test (push) Failing after 10s
CI - 4NK Node / Documentation Tests (push) Successful in 3s
CI - 4NK Node / Performance Tests (push) Successful in 28s
CI - 4NK Node / Notify (push) Failing after 2s
58 lines
1.8 KiB
Plaintext
58 lines
1.8 KiB
Plaintext
---
|
||
alwaysApply: true
|
||
---
|
||
|
||
# Tests et qualité
|
||
|
||
[portée]
|
||
Stratégie de tests, exécution locale, stabilité, non-régression.
|
||
|
||
[objectifs]
|
||
|
||
- Exiger des tests verts avant tout commit.
|
||
- Couvrir les axes unit, integration, connectivity, performance, external.
|
||
|
||
[directives]
|
||
|
||
- Ajouter/mettre à jour des tests dans tests/unit, tests/integration, tests/connectivity, tests/performance, tests/external selon l’impact.
|
||
- Consigner les journaux dans tests/logs et les rapports dans tests/reports.
|
||
- Maintenir tests/README.md (stratégie, outillage, seuils).
|
||
- Fournir un nettoyage reproductible via tests/cleanup.sh.
|
||
- Bloquer l’édition si des tests échouent tant que la correction n’est pas appliquée.
|
||
|
||
[validations]
|
||
|
||
- Refus d’un commit si tests en échec.
|
||
- Exiger justification et plan de test dans docs/TESTING.md pour toute refonte majeure.
|
||
|
||
[artefacts concernés]
|
||
|
||
- tests/**, docs/TESTING.md, CHANGELOG.md.
|
||
|
||
# Tests et qualité
|
||
|
||
[portée]
|
||
Stratégie de tests, exécution locale, stabilité, non-régression.
|
||
|
||
[objectifs]
|
||
|
||
- Exiger des tests verts avant tout commit.
|
||
- Couvrir les axes unit, integration, connectivity, performance, external.
|
||
|
||
[directives]
|
||
|
||
- Ajouter/mettre à jour des tests dans tests/unit, tests/integration, tests/connectivity, tests/performance, tests/external selon l’impact.
|
||
- Consigner les journaux dans tests/logs et les rapports dans tests/reports.
|
||
- Maintenir tests/README.md (stratégie, outillage, seuils).
|
||
- Fournir un nettoyage reproductible via tests/cleanup.sh.
|
||
- Bloquer l’édition si des tests échouent tant que la correction n’est pas appliquée.
|
||
|
||
[validations]
|
||
|
||
- Refus d’un commit si tests en échec.
|
||
- Exiger justification et plan de test dans docs/TESTING.md pour toute refonte majeure.
|
||
|
||
[artefacts concernés]
|
||
|
||
- tests/**, docs/TESTING.md, CHANGELOG.md.
|