How to make sure updates do not silently break stuff: add a revision option to overwatcher and a revision parameter in each test. If the parameter does not match, warn and do not start the test except after user confirmation (lightly forces a review and an update of test).
NOTE: the revision will not be related to the actual version of the framework! It will only be incremented when major change are done to the behavior which can break old tests. Updating stuff transparently increases the version of the framework and keeps the revision unchanged! (example: refactoring the options implementation keeps the same options, so the tests do not care....removing options from triggers breaks tests)
How to make sure updates do not silently break stuff: add a revision option to overwatcher and a revision parameter in each test. If the parameter does not match, warn and do not start the test except after user confirmation (lightly forces a review and an update of test).
NOTE: the revision will not be related to the actual version of the framework! It will only be incremented when major change are done to the behavior which can break old tests. Updating stuff transparently increases the version of the framework and keeps the revision unchanged! (example: refactoring the options implementation keeps the same options, so the tests do not care....removing options from triggers breaks tests)