模拟 Javaenum 以添加一个值来测试失败案例

我有一个 枚举开关或多或少像这样:

public static enum MyEnum {A, B}


public int foo(MyEnum value) {
switch(value) {
case(A): return calculateSomething();
case(B): return calculateSomethingElse();
}
throw new IllegalArgumentException("Do not know how to handle " + value);
}

我希望测试覆盖所有的行，但是由于代码需要处理所有的可能性，因此如果开关中没有相应的 case 语句，我就不能提供一个值。

扩展枚举来添加额外的值是不可能的，而且仅仅模仿 equals 方法来返回 false也不会起作用，因为生成的字节码使用窗帘后面的一个跳转表来进入正确的大小写... ... 所以我想也许 PowerMock 或者其他什么东西可以实现一些黑魔法。

谢谢！

编辑 :

因为我拥有这个枚举，所以我认为我可以向这些值添加一个方法，从而完全避免开关问题; 但是我留下了这个问题，因为它仍然很有趣。

101289 次浏览
小开

I would put the default case with one of enum cases:

  public static enum MyEnum {A, B}


public int foo(MyEnum value) {
if (value == null) throw new IllegalArgumentException("Do not know how to handle " + value);


switch(value) {
case(A):
return calculateSomething();
case(B):
default:
return calculateSomethingElse();
}
}
小开

Rather than using some radical bytecode manipulation to enable a test to hit the last line in foo, I would remove it and rely on static code analysis instead. For example, IntelliJ IDEA has the "Enum switch statement that misses case" code inspection, which would produce a warning for the foo method if it lacked a case.

小开

As you indicated in your edit, you can add the functionaliy in the enum itself. However, this might not be the best option, since it can violate the "One Responsibility" principle. Another way to achieve this is to create a static map which contains enum values as key and the functionality as value. This way, you can easily test if for any enum value you have a valid behavior by looping over all the values. It might be a bit far fetched on this example, but this is a technique I use often to map resource ids to enum values.

小开

Here is a complete example.

The code is almost like your original (just simplified better test validation):

public enum MyEnum {A, B}


public class Bar {


public int foo(MyEnum value) {
switch (value) {
case A: return 1;
case B: return 2;
}
throw new IllegalArgumentException("Do not know how to handle " + value);
}
}

And here is the unit test with full code coverage, the test works with Powermock (1.4.10), Mockito (1.8.5) and JUnit (4.8.2):

@RunWith(PowerMockRunner.class)
public class BarTest {


private Bar bar;


@Before
public void createBar() {
bar = new Bar();
}


@Test(expected = IllegalArgumentException.class)
@PrepareForTest(MyEnum.class)
public void unknownValueShouldThrowException() throws Exception {
MyEnum C = mock(MyEnum.class);
when(C.ordinal()).thenReturn(2);


PowerMockito.mockStatic(MyEnum.class);
PowerMockito.when(MyEnum.values()).thenReturn(new MyEnum[]{MyEnum.A, MyEnum.B, C});


bar.foo(C);
}


@Test
public void AShouldReturn1() {
assertEquals(1, bar.foo(MyEnum.A));
}


@Test
public void BShouldReturn2() {
assertEquals(2, bar.foo(MyEnum.B));
}
}

Result:

Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.628 sec
小开

jMock (at least as of version 2.5.1 that I'm using) can do this out of the box. You will need to set your Mockery to use ClassImposterizer.

Mockery mockery = new Mockery();
mockery.setImposterizer(ClassImposterizer.INSTANCE);
MyEnum unexpectedValue = mockery.mock(MyEnum.class);
小开

First of all Mockito can create mock data which can be integer long etc It cannot create right enum as enum has specific number of ordinal name value etc so if i have an enum 

public enum HttpMethod {
GET, POST, PUT, DELETE, HEAD, PATCH;
}

so i have total 5 ordinal in enum HttpMethod but mockito does not know it .Mockito creates mock data and its null all the time and you will end up in passing a null value . So here is proposed solution that you randomize the ordinal and get a right enum which can be passed for other test 

import static org.mockito.Mockito.mock;


import java.util.Random;


import org.junit.Test;
import org.junit.runner.RunWith;
import org.mockito.Matchers;
import org.mockito.internal.util.reflection.Whitebox;
import org.powermock.api.mockito.PowerMockito;
import org.powermock.core.classloader.annotations.PrepareForTest;
import org.powermock.modules.junit4.PowerMockRunner;


import com.amazonaws.HttpMethod;








//@Test(expected = {"LoadableBuilderTestGroup"})
//@RunWith(PowerMockRunner.class)
public class testjava {
// private static final Class HttpMethod.getClass() = null;
private HttpMethod mockEnumerable;


@Test
public void setUpallpossible_value_of_enum () {
for ( int i=0 ;i<10;i++){
String name;
mockEnumerable=    Matchers.any(HttpMethod.class);
if(mockEnumerable!= null){
System.out.println(mockEnumerable.ordinal());
System.out.println(mockEnumerable.name());


System.out.println(mockEnumerable.name()+"mocking suceess");
}
else {
//Randomize all possible  value of  enum
Random rand = new Random();
int ordinal = rand.nextInt(HttpMethod.values().length);
// 0-9. mockEnumerable=
mockEnumerable= HttpMethod.values()[ordinal];
System.out.println(mockEnumerable.ordinal());
System.out.println(mockEnumerable.name());
}
}
}














@Test
public void setUpallpossible_value_of_enumwithintany () {
for ( int i=0 ;i<10;i++){
String name;
mockEnumerable=    Matchers.any(HttpMethod.class);
if(mockEnumerable!= null){
System.out.println(mockEnumerable.ordinal());
System.out.println(mockEnumerable.name());


System.out.println(mockEnumerable.name()+"mocking suceess");
} else {
int ordinal;
//Randomize all possible  value of  enum
Random rand = new Random();
int imatch =  Matchers.anyInt();
if(  imatch>HttpMethod.values().length)
ordinal = 0    ;
else
ordinal = rand.nextInt(HttpMethod.values().length);


// 0-9.  mockEnumerable=
mockEnumerable= HttpMethod.values()[ordinal];
System.out.println(mockEnumerable.ordinal());
System.out.println(mockEnumerable.name());
}
}
}
}

Output :

0
GET
0
GET
5
PATCH
5
PATCH
4
HEAD
5
PATCH
3
DELETE
0
GET
4
HEAD
2
PUT
小开

I think that the simplest way to reach the IllegalArgumentException is to pass null to the foo method and you will read "Do not know how to handle null"

小开

Just creating a fake enum value will not be enough, you eventually also need to manipulate an integer array that is created by the compiler.

Actually to create a fake enum value, you don't even need any mocking framework. You can just use Objenesis to create a new instance of the enum class (yes, this works) and then use plain old Java reflection to set the private fields name and ordinal and you already have your new enum instance.

Using Spock framework for testing, this would look something like:

given:
def getPrivateFinalFieldForSetting = { clazz, fieldName ->
def result = clazz.getDeclaredField(fieldName)
result.accessible = true
def modifiers = Field.getDeclaredFields0(false).find { it.name == 'modifiers' }
modifiers.accessible = true
modifiers.setInt(result, result.modifiers & ~FINAL)
result
}


and:
def originalEnumValues = MyEnum.values()
MyEnum NON_EXISTENT = ObjenesisHelper.newInstance(MyEnumy)
getPrivateFinalFieldForSetting.curry(Enum).with {
it('name').set(NON_EXISTENT, "NON_EXISTENT")
it('ordinal').setInt(NON_EXISTENT, originalEnumValues.size())
}

If you also want the MyEnum.values() method to return the new enum, you now can either use JMockit to mock the values() call like

new MockUp<MyEnum>() {
@Mock
MyEnum[] values() {
[*originalEnumValues, NON_EXISTENT] as MyEnum[]
}
}

or you can again use plain old reflection to manipulate the $VALUES field like:

given:
getPrivateFinalFieldForSetting.curry(MyEnum).with {
it('$VALUES').set(null, [*originalEnumValues, NON_EXISTENT] as MyEnum[])
}


expect:
true // your test here


cleanup:
getPrivateFinalFieldForSetting.curry(MyEnum).with {
it('$VALUES').set(null, originalEnumValues)
}

As long as you don't deal with a switch expression, but with some ifs or similar, either just the first part or the first and second part might be enough for you.

If you however are dealing with a switch expression, e. g. wanting 100% coverage for the default case that throws an exception in case the enum gets extended like in your example, things get a bit more complicated and at the same time a bit more easy.

A bit more complicated because you need to do some serious reflection to manipulate a synthetic field that the compiler generates in a synthetic anonymous innner class that the compiler generates, so it is not really obvious what you are doing and you are bound to the actual implementation of the compiler, so this could break anytime in any Java version or even if you use different compilers for the same Java version. It is actually already different between Java 6 and Java 8.

A bit more easy, because you can forget the first two parts of this answer, because you don't need to create a new enum instance at all, you just need to manipulate an int[], that you need to manipulate anyway to make the test you want.

I recently found a very good article regarding this at https://www.javaspecialists.eu/archive/Issue161.html.

Most of the information there is still valid, except that now the inner class containing the switch map is no longer a named inner class, but an anonymous class, so you cannot use getDeclaredClasses anymore but need to use a different approach shown below.

Basically summarized, switch on bytecode level does not work with enums, but only with integers. So what the compiler does is, it creates an anonymous inner class (previously a named inner class as per the article writing, this is Java 6 vs. Java 8) that holds one static final int[] field called $SwitchMap$net$kautler$MyEnum that is filled with integers 1, 2, 3, ... at the indices of MyEnum#ordinal() values.

This means when the code comes to the actual switch, it does

switch(<anonymous class here>.$SwitchMap$net$kautler$MyEnum[myEnumVariable.ordinal()]) {
case 1: break;
case 2: break;
default: throw new AssertionError("Missing switch case for: " + myEnumVariable);
}

If now myEnumVariable would have the value NON_EXISTENT created in the first step above, you would either get an ArrayIndexOutOfBoundsException if you set ordinal to some value greater than the array the compiler generated, or you would get one of the other switch-case values if not, in both cases this would not help to test the wanted default case.

You could now get this int[] field and fix it up to contain a mapping for the orinal of your NON_EXISTENT enum instance. But as I said earlier, for exactly this use-case, testing the default case, you don't need the first two steps at all. Instead you can simple give any of the existing enum instances to the code under test and simply manipulate the mapping int[], so that the default case is triggered.

So all that is necessary for this test case is actually this, again written in Spock (Groovy) code, but you can easily adapt it to Java too:

given:
def getPrivateFinalFieldForSetting = { clazz, fieldName ->
def result = clazz.getDeclaredField(fieldName)
result.accessible = true
def modifiers = Field.getDeclaredFields0(false).find { it.name == 'modifiers' }
modifiers.accessible = true
modifiers.setInt(result, result.modifiers & ~FINAL)
result
}


and:
def switchMapField
def originalSwitchMap
def namePrefix = ClassThatContainsTheSwitchExpression.name
def classLoader = ClassThatContainsTheSwitchExpression.classLoader
for (int i = 1; ; i++) {
def clazz = classLoader.loadClass("$namePrefix\$$i")
try {
switchMapField = getPrivateFinalFieldForSetting(clazz, '$SwitchMap$net$kautler$MyEnum')
if (switchMapField) {
originalSwitchMap = switchMapField.get(null)
def switchMap = new int[originalSwitchMap.size()]
Arrays.fill(switchMap, Integer.MAX_VALUE)
switchMapField.set(null, switchMap)
break
}
} catch (NoSuchFieldException ignore) {
// try next class
}
}


when:
testee.triggerSwitchExpression()


then:
AssertionError ae = thrown()
ae.message == "Unhandled switch case for enum value 'MY_ENUM_VALUE'"


cleanup:
switchMapField.set(null, originalSwitchMap)

In this case you don't need any mocking framework at all. Actually it would not help you anyway, as no mocking framework I'm aware of allows you to mock an array access. You could use JMockit or any mocking framework to mock the return value of ordinal(), but that would again simply result in a different switch-branch or an AIOOBE.

What this code I just shown does is:

  • it loops through the anonymous classes inside the class that contains the switch expression
  • in those it searches for the field with the switch map
  • if the field is not found, the next class is tried
  • if a ClassNotFoundException is thrown by Class.forName, the test fails, which is intended, because that means that you compiled the code with a compiler that follows a different strategy or naming pattern, so you need to add some more intelligence to cover different compiler strategies for switching on enum values. Because if the class with the field is found, the break leaves the for-loop and the test can continue. This whole strategy of course depends on anonymous classes being numbered starting from 1 and without gaps, but I hope this is a pretty safe assumption. If you are dealing with a compiler where this is not the case, the searching algorithm needs to be adapted accordingly.
  • if the switch map field is found, a new int array of the same size is created
  • the new array is filled with Integer.MAX_VALUE which usually should trigger the default case as long as you don't have an enum with 2,147,483,647 values
  • the new array is assigned to the switch map field
  • the for loop is left using break
  • now the actual test can be done, triggering the switch expression to be evaluated
  • finally (in a finally block if you are not using Spock, in a cleanup block if you are using Spock) to make sure this does not affect other tests on the same class, the original switch map is put back into the switch map field
小开
最佳答案

If you can use Maven as your build system, you can use a much simpler approach. Just define the same enum with an additional constant in your test classpath.

Let's say you have your enum declared under the sources directory (src/main/java) like this:

package my.package;


public enum MyEnum {
A,
B
}

Now you declare the exact same enum in the test sources directory (src/test/java) like this:

package my.package


public enum MyEnum {
A,
B,
C
}

The tests see the testclass path with the "overloaded" enum and you can test your code with the "C" enum constant. You should see your IllegalArgumentException then.

Tested under windows with maven 3.5.2, AdoptOpenJDK 11.0.3 and IntelliJ IDEA 2019.3.1

小开

I added an Unknown option to my enum, which I pass in during the test. Not ideal in every case, but simple.

小开

Here is my Mockito only version of the solution of @Jonny Heggheim. It has been tested with Mockito 3.9.0 and Java 11:

public class MyTestClass {


private static MockedStatic<MyEnum> myMockedEnum;
private static MyEnum mockedValue;


@BeforeClass
public void setUp() {
MyEnum[] newEnumValues = addNewEnumValue(MyEnum.class);
myMockedEnum = mockStatic(MyEnum.class);
myMockedEnum.when(MyEnum::values).thenReturn(newEnumValues);
mockedValue = newEnumValues[newEnumValues.length - 1];
}
 

@AfterClass
public void tearDown(){
myMockedEnum.close();
}


@Test
public void testCase(){
// Use mockedValue in your test case
...
}


private static <E extends Enum<E>> E[] addNewEnumValue(Class<E> enumClazz){
EnumSet<E> enumSet = EnumSet.allOf(enumClazz);
E[] newValues = (E[]) Array.newInstance(enumClazz, enumSet.size() + 1);
int i = 0;
for (E value : enumSet) {
newValues[i] = value;
i++;
}


E newEnumValue = mock(enumClazz);
newValues[newValues.length - 1] = newEnumValue;


when(newEnumValue.ordinal()).thenReturn(newValues.length - 1);


return newValues;
}
}

A few words of caution when using this:

  • It is crucial that you run the code in the setup() Method before any class is loaded by the JVM classloader that contains a switch statement for the mocked Enum. I recommend you read the article quoted in the answer of @Vampire if you want to know why.
  • The safest way to achieve this is to put the code in a static method annotated with @BeforeClass.
  • If you forget the code in the tearDown() method if can happen that the tests in the test class succeed but tests in other test classes fail when run afterwards in the same test run. This is because MyEnum stays extended until you call close() on MockedStatic.
  • If in the same test class some of your test cases use the mocked Enum and some don't and you have to pull the setUp() and tearDown() code into single test cases, I highly recommend running the tests with the Robolectric runner or any other test runner, that guarantees that each test case runs in a freshly started JVM. This way you can make sure, that all classes that contain switch statements for the Enum are newly loaded by the class loader for every test case.

提交答案