Storing testcases as ontology annotation is causing too many ontology change events
Saving the test cases as ontology annotation can be optimized such that
- first not every store operation in a bunch of test case store operations should cause an ontology change event but only after all these test cases have been saved a ontology change event should be fired and
- second it should be evaluated (and implemented if possible) if an ontology change event is necessary at all since the save operation only affects the ontology annotation.