0

我在windows环境下工作。

在我的tearDown()方法中，deleteSucceeded返回 false。

文件永远不会被删除，尽管它位于所需的位置。

奇怪的是：

在 unix 环境中，相同的代码运行良好。

见下课：

@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(locations = { "/ServiceMockTest-context.xml" })
public class ServiceMockTest { 

private File actualSerializedObjectFile;

 @Before
 public void setUp() throws InvalidDocumentException, 
 SAXException, IOException, 
 ParserConfigurationException,  InvalidGpecConfigurationException {
 actualSerializedObjectFile = new File(OUTPUT_DIR, 
 "ServiceMockTest-" + name.getMethodName() + ".json");
 System.out.println("actualSerializedObjectFile: " 
 +  actualSerializedObjectFile.getAbsolutePath());
 }


 @After
 public void tearDown() {
     boolean deleteSucceeded = actualSerializedObjectFile.delete();
     if (!deleteSucceeded) {
         throw new RuntimeException("Failed to delete temporary 
         output file for List<Map<String,Object>> serialized 
         object: " + actualSerializedObjectFile.getAbsolutePath());
     }
 }

}

更新：

我分析了这个错误，发现问题出在其他地方。

当我在调试模式下运行测试时，控件转到以下代码块：

/**
 * Constructs a InvocationTargetException with a target exception.
 *
 * @param target the target exception
 */
public InvocationTargetException(Throwable target) {
    super((Throwable)null);  // Disallow initCause
    this.target = target;
}

这发生在调用delete()方法之后。

笔记：

我的文件没有在其他任何地方打开，因此delete()调用不会像在 Windows 环境中那样删除它。

错误日志：

java.lang.RuntimeException: Failed to delete temporary output file for List<Map<String,Object>> serialized object: E:\git\userapp\services\serializedObjects\ServiceMockTest-getSchedule.json
    at com.userapp.services.ServiceMockTest.tearDown(ServiceMockTest.java:198)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
    at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:36)
    at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:83)
    at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:47)
    at org.junit.rules.RunRules.evaluate(RunRules.java:18)
    at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:72)
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:231)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
    at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
    at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
    at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:71)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:174)
    at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
    at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
4

2 回答 2

1

在 windows 环境下需要关闭inputStream，以便在需要时删除文件。

我刚刚inputStream.close();在调用删除之前添加了它，它起作用了。

这也意味着在 unix 环境中，inputStream一旦完成读取流的工作，它就会自行关闭。

于 2015-08-18T11:07:49.227 回答
1

Windows 不会让您删除应用程序仍然打开的文件，但 Unix 会。这可能是导致行为差异的原因。

于 2015-08-18T08:16:00.513 回答