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.)

Inizia ispezionando la suite di test pytest esistente e individuando un’area centrale non coperta, verificabile con unit test; l’issue non indica file o punti di ingresso specifici. Struttura i test senza dipendere da un comando py utilizzabile, usando mock, monkey-patching o importazioni dirette dei comandi secondo necessità. Il lavoro è completato quando hai aggiunto una copertura mirata per una lacuna selezionata e mantenuto validi i test senza compilare o installare l’applicazione completa.