13

我有以下内容：

public class UnsetProperty extends Command {

    @Resource
    private SetProperty setProperty;

    public String parse(String[] args) {
        if (args.length != 4) {
            throw new RuntimeException("Incorrect number of arguments. Expected 4. Got " + args.length);
        }
        String publisher = args[0];
        String version = args[1];
        String mode = args[2];
        String property = args[3];

        /*
         * Unsetting a property is done by changing the current property to null.
         * Technically, the old property doesn't get changed, a new one is inserted with
         * a higher revision number, and it becomes the canonical one.
        */
        setProperty.setProperty(publisher, version, mode, property, null, false);
        return "";
    }
}

和以下测试：

public class UnsetPropertyTest extends CommandTest {
    @Configuration
    public static class Config {

        @Bean(name = "mockSetProperty")
        public SetProperty getSetProperty() {
            return mock(SetProperty.class);
        }

        @Bean
        public UnsetProperty getUnsetProperty() {
            return new UnsetProperty();
        }

    }

    @Resource
    @InjectMocks
    private UnsetProperty unsetProperty;

    @Resource(name = "mockSetProperty")
    private SetProperty setProperty;

    // ... SNIP ...

    @Test
    public void testCallsSetPropertyWithCorrectParameters() throws SQLException, TaboolaException {
        final String[] args = new String[]{"publisher", "version", "mode", "property"};
        final String output = unsetProperty.parse(args);
        verify(setProperty).setProperty("publisher", "version", "mode", "property", null, false);
        // The above line should have killed the mutation!
        verifyNoMoreInteractions(setProperty);
        assertThat(output).isEqualTo("");
    }
}

正如预期的那样，测试通过了。当我通过 PIT 运行它时，我得到以下结果

33   1. removed call to my/package/SetProperty::setProperty → SURVIVED

第 33 行在类代码中突出显示。

检查的测试如下：

  • my.package.UnsetPropertyTest.testCallsSetPropertyWithCorrectParameters(my.package.UnsetPropertyTest) （32 毫秒）
  • my.package.UnsetPropertyTest.testUnsetThrowsForIncorrectNumberOfParameters(my.package.UnsetPropertyTest) (3 毫秒)

现在：

  • 当我更改测试调用参数 ( args) 时，测试失败。正如预期的那样
  • 当我更改断言 ( verify(setProperty).setProperty(...)) 参数时，测试失败。正如预期的那样。
  • 当我手动注释掉第一个代码块中突出显示的函数调用时，测试失败。

为什么突变会存活？

我正在使用 Java 8、Mockito 1.9.5 和 PIT 1.1.4。

4

1 回答 1

1

多年后，但似乎没有人提到 (Spring)@Resource和 (Mockito)@InjectMocks是相互排斥的解决方案。你有多个生成的子类UnsetProperty在玩，所以 PIT 只是对正在发生的事情感到困惑。

于 2019-10-27T21:41:09.487 回答