测试挂起(Chutzpah TimeoutException)

时间:2012-10-30 19:15:50

标签: visual-studio-2010 chutzpah

我已经安装了Chutzpah并在我的计算机上运行了几次,然后我重新启动并在尝试从 Visual Studio 中的扩展程序运行时出现此类错误命令

>chutzpah.console /wait /path C:\Projects\CP\Testing\RESAAS.JavaScriptTestSuite\Specs

Chutzpah Error: Chutzpah.Exceptions.ChutzpahTimeoutException: Timeout occured when running C:\Projects\CP\Testing\RESAAS.JavaScriptTestSuite\Specs\User\RegistrationSpec.js
at Chutzpah.TestRunner.HandleTestProcessExitCode(Int32 exitCode, String inputTestFile) in c:\Dev\chutzpah\Chutzpah\TestRunner.cs:line 217
at Chutzpah.TestRunner.InvokeTestRunner(String headlessBrowserPath, TestOptions options, TestContext testContext, TestRunnerMode testRunnerMode, ITestMethodRunnerCallback callback) in c:\Dev\chutzpah\Chutzpah\TestRunner.cs:line 200
at Chutzpah.TestRunner.<>c__DisplayClass2.<ProcessTestPaths>b__1(PathInfo testFile) in c:\Dev\chutzpah\Chutzpah\TestRunner.cs:line 143
While Running:C:\Projects\CP\Testing\RESAAS.JavaScriptTestSuite\Specs\User\RegistrationSpec.js



Chutzpah Error: Chutzpah.Exceptions.ChutzpahTimeoutException: Timeout occured when running C:\Projects\CP\Testing\RESAAS.JavaScriptTestSuite\Specs\User\SendMessageSpec.js
at Chutzpah.TestRunner.HandleTestProcessExitCode(Int32 exitCode, String inputTestFile) in c:\Dev\chutzpah\Chutzpah\TestRunner.cs:line 217
at Chutzpah.TestRunner.InvokeTestRunner(String headlessBrowserPath, TestOptions options, TestContext testContext, TestRunnerMode testRunnerMode, ITestMethodRunnerCallback callback) in c:\Dev\chutzpah\Chutzpah\TestRunner.cs:line 200
at Chutzpah.TestRunner.<>c__DisplayClass2.<ProcessTestPaths>b__1(PathInfo testFile) in c:\Dev\chutzpah\Chutzpah\TestRunner.cs:line 143
While Running:C:\Projects\CP\Testing\RESAAS.JavaScriptTestSuite\Specs\User\SendMessageSpec.js

=== 0 total, 0 failed, took 0.00 seconds ===

如果我在Visual Studio中的一个文件上单击一个测试并要求它在浏览器中运行它实际上是正确执行的,但由于我们有100多个文件,因此无法对所有文件使用此方法。

任何见解都将不胜感激。在网上找到参考资料似乎很难。

2 个答案:

答案 0 :(得分:4)

在2.0版本中有/ timeoutMilliseconds选项。将此值设置为更高的值,默认值为5000(ms)

答案 1 :(得分:1)

刚刚回到版本1.4(以匹配我的同事)并且错误已经全部消失,因为我没有使用任何新功能,这很好。