I appreciate and agree with your thoughts and concerns cjpit and max_morais_dmm thanks
Probably max_morais_dmm you refer to ‘business use case’ tests - that capture end user scenario context requirements?
My rough thoughts are -
Initially to start, users will assume and grant quality to an extent. But to sustain ERPNext growth and favour, such control can’t be left to chance; due care must be paid to ensure quality and stability, and that is for the user community at large to recognize and support test driven process practice discipline.
A PR submission requires a validation test Pull Request Checklist · frappe/erpnext Wiki · GitHub
The appropriate tests can detect and define breaking changes, to point to unforeseen impacts of a developer’s changes or a refactoring that violates a public API.
For an urgent hot fix, a test to reproduce and mark the error would help learners to see for themselves otherwise forgotten problem cases.
At release time, regression tests are especially valuable and efficient to identify and isolate problems with proposed fixes.
To promote quality among users, one good way is to report test results and test coverage Help with Writing Tests - Foundation and community invite to help with 'do nothing' pass tests - #2 by revant_one