org.evomaster.client.java.instrumentation.staticstate

Class MethodReplacementPreserveSemantics

java.lang.Object

org.evomaster.client.java.instrumentation.staticstate.MethodReplacementPreserveSemantics

public class MethodReplacementPreserveSemantics
extends Object

Field Summary

Fields

Modifier and Type	Field and Description
static boolean	shouldPreserveSemantics Most method replacements do preserve semantics.

Constructor Summary

Constructors

Constructor and Description
MethodReplacementPreserveSemantics()

Method Summary

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail

shouldPreserveSemantics

public static boolean shouldPreserveSemantics

Most method replacements do preserve semantics. So, when evaluating dynamically generated test cases in E2E tests, there is (should be) no issue. The problem is when some method replacements DO NOT preserve semantics... the generated tests will have no way to setup instrumentation info. In the ideal world, when evaluating dynamically generated tests, we should unload the instrumented classes. But this does not seem possible :-( Anyway, this is only needed for E2E tests, so must have no impact on running EM.

Constructor Detail

MethodReplacementPreserveSemantics

public MethodReplacementPreserveSemantics()