ClarkeJ, totally agree. I’d like to propose a complete re-design of the testing framework, as it is not really usable from a testing perspective as mentioned [Bug] Testing framework commits to database · Issue #7126 · frappe/frappe · GitHub and [Bug] Testing Framework Commits to Database · Issue #7370 · frappe/frappe · GitHub
I’d like to propose moving to pytest as well, as it has so many extra features, is backwards compatible with unittest, and separating it out into a separate folder structure, so that the tests and the src code is not intermingled.
That way it can be built up side by side with the current testing, and not actually affect it. Moving to a XP/TDD ethos will really increase the quality of the code, as you mentioned, and a worthy task I think for the future of erpnext/frappe to really increase its uptake. I’m currently stuck with an ERP from a close sourced vendor which has exactly the same problems, because testing was not a first class citizen.