Bug or feature...

[sschwarzman]

Let's suppose that a Schematron module contains 100 assert/report statements and that the test suite contains one NoGo test per each statement. Thus we have 100 NoGo tests for this Schematron module. Let's further suppose that we change one of those 100 assert/report statements, or that we added one more assert/report statement. The way Smehotron works, if the previously valid Expected SVRL files remain in place, all NoGo tests will fail. Thus one has to delete all 100 previously existed Expected SVRL files, generate them again, and then run NoGo tests. However, this kind-of defeats the purpose, because what if one of those 100 tests did actually fail because of the change? We would never know. Of course, prior to deleting all Expected SVRL, one could run all 100 NoGo tests to make sure they still generate the expected error messages but that's what I mean by "defeating the purpose" -- ideally, Smehotron should show us which NoGo tests no longer generate expected error messages because of the newly introduced change. However, this is only so for the tests in other Schematron modules, and not for the tests within the same Schematron module.