arcuri82
commented
8 years ago Hi,
- "How does EvoSuite mock static methods and final classes?"
it does not (and will not) mock static methods, but it can mock final classes (as long as they are not loaded by the bootstrap classloader, eg "java.*"). Mocking static methods would have far too many negative consequences / complications for automated test generation
- "Should another mocking framework, such as JMockit, which can mock final classes and static methods, be used instead of Mockito?".
Nope :) there would be no advantage (EvoSuite strip out the "final" when loading classes, so Mockito can still be used on those types of classes)
- "Is there a workaround (property, command line switch), that I can use to get past this situation?"
unfortunately no :(
From you description/logs, it looks like class loading fails due to wrong static state in other classes (ie, exception during static initializer). This is a very special case, which so far I have seen it only once in my whole career :( Handling it in EvoSuite (or any other test generation tool) would be very complicated (ie, set static state of JVM in the right way even before some classes are loaded).
Unless more people will have the same kind of issue, unfortunately there would not be much ROI in trying to handle it now :(
cheers
JavaJimFl
Good Afternoon,
I've run into an issue while trying to generate test cases for a class (let's call it
MyClass) using the command line. The class relies heavily on collaborators that use static factory methods. Unit test generation failed with the following stack trace:MyClassrelies on a factory calledMyFactorythat in turn has a static method calledgetContext().getContext()throws aRuntimeExceptionwhen it hasn't been initialized, which is the case here. I think this problem may be caused by the call togetContext(), because it behaves as if it were not mocked. I noticed that Mockito classes are used for mocking, but as far as I know, the Mockito framework can't mock static methods or final classes. Another thing about this situation that's really interesting is the factory class is actually a transitive collaborator. The primary collaborator of the CUT is actually another class with static methods, and I think that would have been mocked instead.I have three questions:
My environment:
My configuraton is a stock evosuite.properties file with the following changes:
use_separate_classloader=false(JMockit and JaCoCo are used by the project)junit_suffix=EsTestshow_progress=falseThanks for tackling such a difficult problem!