“…Type of Oracles Problems [13], [14], [15], [16], [17], [18] manual-based oracles error-pone and labor-intensive [2], [19], [20], [21], [22], [23] implicit test oracles limited faulty types and testing scenarios [24], [25], [26], [27], [28], [29] specified oracles requiring of full specification and heavy reliance on the test expertise [30], [31], [32], [33], [34], [35] correct version as oracles the existence of a correct version may not hold in CT, including so-called implicit test oracles [12] which can be directly observed by the behaviors of the SUT, like crashes [2], exceptions [19], memory leaks [20], buffer overflow [22]. When the full specification of the SUT is available, embedded assertions [24] or pre and post conditions [25] or a model-checker [26], [27] can also be utilized as the so-called specified oracles for the CT test cases.…”