恒定场仅在Junit5下初始化一次
我们正在迁移到Junit5并删除PowerMockito，因为Mockito现在支持Mockstatic。之前，PowerMockito提供了Whitebox.SetInternalState（..），使设置值最终字段（常数）
我有一个类似的课程
public class MyClass {
private static final String myField = Props.getString("myField");
public boolean myMethod() {
//uses my field
}
}
，我的测试看起来像这样的
class MyClassTest {
@Test
void myTest() {
try (MockedStatic<Props> propsMockedStatic = Mockito.mock(Props.class)) {
propsMockedStatic.when(() -> Props.getString("myField")).thenReturn("Hello!!");
MyClass myClass = new MyClass();
//more code
}
}
}
问题是，当我引入更多测试时，我会看到myfield在运行测试时仅一次模拟一次，尽管我每次都使用新实例。这会导致制动测试，因为在其他情况下，我希望myfield具有不同的值，但是当我单独运行它们时，一切都成功完成
We are migrating to JUnit5 and removing PowerMockito since Mockito now supports mockStatic. Before, PowerMockito offered Whitebox.setInternalState(..) making it possible to set values final fields (constants)
I have a class like
public class MyClass {
private static final String myField = Props.getString("myField");
public boolean myMethod() {
//uses my field
}
}
and my Test looks like this
class MyClassTest {
@Test
void myTest() {
try (MockedStatic<Props> propsMockedStatic = Mockito.mock(Props.class)) {
propsMockedStatic.when(() -> Props.getString("myField")).thenReturn("Hello!!");
MyClass myClass = new MyClass();
//more code
}
}
}
The problem is that when I introduce more tests I see that the myField gets mocked only once when I run the Tests although I use a new instance every time. This results in braking tests since on other cases I want myField to have different values but when I run them separately everything completes successfully
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我在堆栈溢出帖子上发现的临时解决方法是 >。它与JDK17，Junit5和Mockito 4.6一起使用。在这里回答，如果有人搜索同一问题，对我来说，花了很多时间才能碰到这个答案。这可能是暂时的，但就目前而言，它
可以综上所述，对我来说有用的是打开对某些软件包的访问，可以看出Bellow。要查找此处需要包含哪些软件包
A temporary workaround that I found on a Stack overflow post is this one https://stackoverflow.com/a/56043252/17984773. It works with JDK17, Junit5, and Mockito 4.6. Answering that here in case someone searches for the same issue, for me it took a lot of time to bump into this answer. It may be temporary but for now it works
To sum up, what worked for me was opening access to some of the packages as can be seen bellow. To find exact what packages need to be included here, I just run the test each time and error by error I created this array