Formal Verification Constraints trigger
Constraint triggering seems to be buggy in both OCRA and TL spec constraints
Parent component - pc and its component - sc
Following cases arise:
Case 1: You have an OCRA contract on both pc and sc. Now make change to
behaviour of sc
Expected: verification of contract for only sc should be triggered
Current state: verification is triggered for both sc and pc
(from redmine: issue id 3162, created on 2017-11-14, closed on 2019-03-01)