2013-08-02 42 views
4

每當我們推出一個FitNesse的測試時間,它結束一個例外:FitNesse的:說</p> <blockquote> <p>測試被中斷,結果是不完整</p> </blockquote> <p>而且我們有「無法檢測到命令行測試跑步者的死亡」

Could not detect death of command line test runner. 
java.lang.IllegalThreadStateException: process has not exited 
    at fitnesse.components.CommandRunner.join(CommandRunner.java:79) 
    at fitnesse.responders.run.slimResponder.SlimTestSystem.bye(SlimTestSystem.java:208) 
    at fitnesse.responders.run.MultipleTestsRunner.startTestSystemAndExecutePages(MultipleTestsRunner.java:118) 
    at fitnesse.responders.run.MultipleTestsRunner.internalExecuteTestPages(MultipleTestsRunner.java:88) 
    at fitnesse.responders.run.MultipleTestsRunner.executeTestPages(MultipleTestsRunner.java:60) 
    at fitnesse.responders.run.TestResponder.performExecution(TestResponder.java:190) 
    at fitnesse.responders.run.TestResponder.doExecuteTests(TestResponder.java:72) 
    at fitnesse.responders.run.TestResponder$TestExecutor.execute(TestResponder.java:106) 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) 
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
    at java.lang.reflect.Method.invoke(Method.java:600) 
    at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:395) 
    at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:384) 
    at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:173) 
    at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:280) 
    at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:369) 
    at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:342) 
    at org.apache.velocity.runtime.directive.Parse.render(Parse.java:260) 
    at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:207) 
    at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:342) 
    at org.apache.velocity.Template.merge(Template.java:356) 
    at org.apache.velocity.Template.merge(Template.java:260) 
    at fitnesse.responders.templateUtilities.HtmlPage.render(HtmlPage.java:80) 
    at fitnesse.responders.run.TestResponder.doSending(TestResponder.java:61) 
    at fitnesse.responders.ChunkingResponder.startSending(ChunkingResponder.java:66) 
    at fitnesse.http.ChunkedResponse.sendTo(ChunkedResponse.java:26) 
    at fitnesse.FitNesseExpediter.sendResponse(FitNesseExpediter.java:96) 
    at fitnesse.FitNesseExpediter.start(FitNesseExpediter.java:48) 
    at fitnesse.FitNesseServer.serve(FitNesseServer.java:24) 
    at fitnesse.FitNesseServer.serve(FitNesseServer.java:17) 
    at fitnesse.socketservice.SocketService$ServerRunner.run(SocketService.java:109) 
    at java.lang.Thread.run(Thread.java:736) 

您是否遇到同樣的問題?你是如何解決它的?

FitNesse的版本:20121220

回答

0

這很可能是你有被掛在那裏一類的引用和FitNesse的不敢靠近。或者是調用System.exit()。

第一個例子是Selenium WebDriver。您必須關閉()browserDriver以徹底結束測試。

第二個是我們過去無意中允許的,並且在更新的版本中已經更改。有可能更新到最新的EDGE可能會解決它。

但是,確實需要更多上下文,因爲這很可能是您的配置或夾具中的問題。

相關問題