"Is there an economical way to test more frequently?
We currently only test manually before our most significant events such as release of a new product, or major changes to an existing product We’d like to test all productive changes to our product models, instead of waiting for our customers to discover problems?"
Yes, definitely. The cost of automatically running an existing library of test cases is negligible compared with equivalent manual testing. So you can run your tests a) more frequently: not only before a major release, but before a minor or patch release, b) after a single change or set of changes by a single modeler as a unit test of his or her changes. Catching defects earlier in your build and release process reduces the cost impact of each defect.
