Test coverage

Test coverage is somewhat spotty right now. Plenty of the core pieces are covered, along with actual bugs that were discovered by usage, but there are plenty of obvious gaps in our current verification.

Any contribution to increase coverage of the pytest tests is welcome.

Note that these tests do not have a usable py command, and so need to be structured to not rely on that - plenty of mocks, monkey-patching and directly importing commands is intended!

(For tests that can only be run after the full app is compiled/installed, create a new issue describing the scenario and why you think it wouldn't be valid as a unit test.)

Commencez par examiner la suite de tests pytest existante et identifier une zone centrale non couverte pouvant faire l’objet de tests unitaires ; l’issue ne nomme aucun fichier ni point d’entrée spécifique. Structurez les tests sans dépendre d’une commande py utilisable, en utilisant si nécessaire des mocks, du monkey-patching ou des imports directs de commandes. C’est terminé lorsque vous avez ajouté une couverture ciblée pour une lacune sélectionnée et que les tests restent valides sans compiler ni installer l’application complète.