程序问答   发布时间:2022-06-01  发布网站:大佬教程  code.js-code.com
大佬教程收集整理的这篇文章主要介绍了在 Visual Studio 2015 中调试 nunit 测试时出错大佬教程大佬觉得挺不错的,现在分享给大家,也给大家做个参考。

如何解决在 Visual studio 2015 中调试 nunit 测试时出错?

开发过程中遇到在 Visual studio 2015 中调试 nunit 测试时出错的问题如何解决?下面主要结合日常开发的经验,给出你关于在 Visual studio 2015 中调试 nunit 测试时出错的解决方法建议,希望对你解决在 Visual studio 2015 中调试 nunit 测试时出错有所启发或帮助;

我正在尝试在 Visual studio 2015 中调试单元测试,但是当我尝试调试测试方法或测试类时,输出包含以下错误:

System.Reflection.TargeTinvocationException:调用目标抛出异常。 ---> System.Argumentexception:ID 为 -1 的进程未运行。

我所有的测试都基于 nunit。

当我在没有调试的情况下运行测试时,一切正常。 我使用 DeBUG / x64 平台来构建我的解决方案,默认的测试处理器架构是 x64。我尝试更改为 DeBUG / Anycpu 并针对 x64 或 x86,但它没有改变任何内容。

目前,我调试测试的解决方案是在 VS 外运行测试并附加到 Visual studio 中的测试运行器,但这不是很方便

欢迎提供任何线索。

提前致谢

问候

下面是输出窗口中显示的完整跟踪:

Enqueue operation 'RunSELEcteDWithDeBUGOperation',hashcode:12843996 
Operation left in the the queue: 1
    'RunSELEcteDWithDeBUGOperation',hashcode:12843996


Processing Queue .....
Operation Dequeue : 'RunSELEcteDWithDeBUGOperation'
VirtualReadonlyTestDataStore.operationStateChanged State=OperationSetStarted,operationInProgress=false
TestdiscoveryStats.OperationStateChanged State=OperationSetStarted,InProgress=false
VirtualReadonlyTestDataStore.operationStateChanged State=ChangeDetectionStarTing,operationInProgress=True
TestdiscoveryStats.OperationStateChanged State=ChangeDetectionStarTing,InProgress=false
We progrAMMatically start the build in TestwindowHost.updateContainer... 
After we await the build that progrAMMatically started in TestwindowHost.updateContainer... 
TESTContainer update (build) complete : 638 ms
Containers from 'Microsoft.Visualstudio.Testwindow.VsAdapters.VsProjectOutputContainerdiscoverer' :
    C:\dev\workspaces\PFM\89c3_app_meniga_cs\Meniga.bPCE.Common.CustomExtensions.Aggregation.Tests\bin\x64\DeBUG\Meniga.bPCE.Common.CustomExtensions.Aggregation.Tests.dll:executor://vsprojectoutputcontainerdiscoverer/v1
    C:\dev\workspaces\PFM\89c3_app_meniga_cs\Meniga.bPCE.Common.CustomExtensions.Aggregation\bin\x64\DeBUG\Meniga.bPCE.Common.CustomExtensions.Aggregation.dll:executor://vsprojectoutputcontainerdiscoverer/v1
    C:\dev\workspaces\PFM\89c3_app_meniga_cs\Meniga.bPCE.Common.CustomExtensions.Cache.Tests\bin\x64\DeBUG\Meniga.bPCE.Common.CustomExtensions.Cache.Tests.dll:executor://vsprojectoutputcontainerdiscoverer/v1
    C:\dev\workspaces\PFM\89c3_app_meniga_cs\Meniga.bPCE.Common.CustomExtensions.Cache\bin\x64\DeBUG\Meniga.bPCE.Common.CustomExtensions.Cache.dll:executor://vsprojectoutputcontainerdiscoverer/v1
    C:\dev\workspaces\PFM\89c3_app_meniga_cs\Meniga.bPCE.Common.CustomExtensions.DataInserters.Tests\bin\x64\DeBUG\Meniga.bPCE.Common.CustomExtensions.DataInserters.Tests.dll:executor://vsprojectoutputcontainerdiscoverer/v1
    C:\dev\workspaces\PFM\89c3_app_meniga_cs\Meniga.bPCE.Common.CustomExtensions.DataInserters\bin\x64\DeBUG\Meniga.bPCE.Common.CustomExtensions.DataInserters.dll:executor://vsprojectoutputcontainerdiscoverer/v1
    C:\dev\workspaces\PFM\89c3_app_meniga_cs\Meniga.bPCE.Common.CustomExtensions.DataModels\bin\x64\DeBUG\Meniga.bPCE.Common.CustomExtensions.DataModels.dll:executor://vsprojectoutputcontainerdiscoverer/v1
    C:\dev\workspaces\PFM\89c3_app_meniga_cs\Meniga.bPCE.Common.CustomExtensions.MQ.Tests\bin\x64\DeBUG\Meniga.bPCE.Common.CustomExtensions.MQ.Tests.dll:executor://vsprojectoutputcontainerdiscoverer/v1
    C:\dev\workspaces\PFM\89c3_app_meniga_cs\Meniga.bPCE.Common.CustomExtensions.MQ\bin\x64\DeBUG\Meniga.bPCE.Common.CustomExtensions.MQ.dll:executor://vsprojectoutputcontainerdiscoverer/v1
    C:\dev\workspaces\PFM\89c3_app_meniga_cs\Meniga.bPCE.Common.CustomExtensions.@R_616_10906@duledPayments.Tests\bin\x64\DeBUG\Meniga.bPCE.Common.CustomExtensions.@R_616_10906@duledPayments.Tests.dll:executor://vsprojectoutputcontainerdiscoverer/v1
    C:\dev\workspaces\PFM\89c3_app_meniga_cs\Meniga.bPCE.Common.CustomExtensions.@R_616_10906@duledPayments\bin\x64\DeBUG\Meniga.bPCE.Common.CustomExtensions.@R_616_10906@duledPayments.dll:executor://vsprojectoutputcontainerdiscoverer/v1
    C:\dev\workspaces\PFM\89c3_app_meniga_cs\Meniga.bPCE.Common.CustomExtensions.serviceExtensions.Tests\bin\x64\DeBUG\Meniga.bPCE.Common.CustomExtensions.serviceExtensions.Tests.dll:executor://vsprojectoutputcontainerdiscoverer/v1
    C:\dev\workspaces\PFM\89c3_app_meniga_cs\Meniga.bPCE.Common.CustomExtensions.serviceExtensions\bin\x64\DeBUG\Meniga.bPCE.Common.CustomExtensions.serviceExtensions.dll:executor://vsprojectoutputcontainerdiscoverer/v1
    C:\dev\workspaces\PFM\89c3_app_meniga_cs\Meniga.bPCE.Common.CustomExtensions.TextParsers.Tests\bin\x64\DeBUG\Meniga.bPCE.Common.CustomExtensions.TextParsers.Tests.dll:executor://vsprojectoutputcontainerdiscoverer/v1
    C:\dev\workspaces\PFM\89c3_app_meniga_cs\Meniga.bPCE.Common.CustomExtensions.TextParsers\bin\x64\DeBUG\Meniga.bPCE.Common.CustomExtensions.TextParsers.dll:executor://vsprojectoutputcontainerdiscoverer/v1
    C:\dev\workspaces\PFM\89c3_app_meniga_cs\Meniga.bPCE.Common.CustomExtensionS.UserEvents.test\bin\x64\DeBUG\Meniga.bPCE.Common.CustomExtensionS.UserEvents.Tests.dll:executor://vsprojectoutputcontainerdiscoverer/v1
    C:\dev\workspaces\PFM\89c3_app_meniga_cs\Meniga.bPCE.Common.CustomExtensionS.UserEvents\bin\x64\DeBUG\Meniga.bPCE.Common.CustomExtensionS.UserEvents.dll:executor://vsprojectoutputcontainerdiscoverer/v1
    C:\dev\workspaces\PFM\89c3_app_meniga_cs\Meniga.CustomExtension.bpceSpecific.Tests\bin\x64\DeBUG\Meniga.CustomExtension.bpceSpecific.Tests.dll:executor://vsprojectoutputcontainerdiscoverer/v1
    C:\dev\workspaces\PFM\89c3_app_meniga_cs\Meniga.CustomExtension.bpceSpecific\bin\x64\DeBUG\Meniga.CustomExtension.bpceSpecific.dll:executor://vsprojectoutputcontainerdiscoverer/v1
No containers found from 'Microsoft.Visualstudio.Web.ProjectSystem.UnitTest.KUnitTESTContainerdiscoverer' :
No containers found from 'Microsoft.Visualstudio.MSTest.Testwindow.orderedTESTContainerdiscoverer' :
No containers found from 'Microsoft.Visualstudio.MSTest.Testwindow.GenericTESTContainerdiscoverer' :
No containers found from 'Microsoft.Visualstudio.MSTest.Testwindow.WebTESTContainerdiscoverer' :
discoveryOperation<RunSELEcteDWithDeBUGOperation> FinishedChangedCotainers,changed container count is 0
VirtualReadonlyTestDataStore.operationStateChanged State=ChangeDetectionFinished,operationInProgress=false
TestdiscoveryStats.OperationStateChanged State=ChangeDetectionFinished,InProgress=false
VirtualReadonlyTestDataStore.operationStateChanged State=TestEXECUTIONStarTing,operationInProgress=false
TestdiscoveryStats.OperationStateChanged State=TestEXECUTIONStarTing,InProgress=false
------ Run test started ------
RunSetTings Content:
<RunSetTings>
  <runconfiguration>
    <ResultsDirectory>C:\dev\workspaces\PFM\89c3_app_meniga_cs\TestResults</ResultsDirectory>
    <SolutionDirectory>C:\dev\workspaces\PFM\89c3_app_meniga_cs\</SolutionDirectory>
    <TargetPlatform>X64</TargetPlatform>
    <TargetFrameworkVersion>Framework45</TargetFrameworkVersion>
  </runconfiguration>
</RunSetTings>
VirtualReadonlyTestDataStore.operationStateChanged State=TestEXECUTIONStarted,operationInProgress=false
TestdiscoveryStats.OperationStateChanged State=TestEXECUTIONStarted,InProgress=false
**  Launching deBUGger  **
.     Launched process      : C:\PROGRAM fileS (X86)\MICROSOFT VISUAL studio 14.0\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\TEStwindOW\vstest.executionENGIne.exe
.     Arguments             : /parentProcessID 28948 
.     Current directory     : C:\Program files (x86)\Microsoft Visual studio 14.0\Common7\IDE
.     Environment variables : 
.     ENGIne guID           : 92ef0900-2251-11d2-b72e-0000f87572ef
.     Other options         : 
.     AppPackageLaunchInfo  : 
VirtualReadonlyTestDataStore.operationStateChanged State=OperationSetFinished,operationInProgress=false
TestdiscoveryStats.OperationStateChanged State=OperationSetFinished,InProgress=false
***    Run finished using 'InMemoryUnitTestWriter' ***
System.Reflection.TargeTinvocationException: Exception has been thrown by the target of an invocation. ---> System.Argumentexception: Process with an ID of -1 is not running.
   at System.Diagnostics.process.GetProcessByID(Int32 processID,String machineName)
   at System.Diagnostics.process.GetProcessByID(Int32 processID)
   at Microsoft.Visualstudio.TestPlatform.ClIEnt.TestExecutorserviceClIEnt.Initialize_Nolock(Architecture targetPlatform,FrameworkVersion targetFramework)
   at Microsoft.Visualstudio.TestPlatform.ClIEnt.TestExecutorserviceClIEnt.EnsureInitialized(IDictionary`2 environmentvariables,TestExecutionContext context)
   at Microsoft.Visualstudio.TestPlatform.ClIEnt.TestExecutorserviceClIEnt.<>c__displayClass17_0.<StartTestRun>b__0()
   at Microsoft.Visualstudio.TestPlatform.ClIEnt.TestExecutorserviceClIEnt.InvokeTestExecutorserviceAction(Action action)
   at Microsoft.Visualstudio.TestPlatform.ClIEnt.TestExecutorserviceClIEnt.StartTestRun(IEnumerable`1 tests,TestExecutionContext executionContext,String runSetTings,IDictionary`2 environmentvariables,String dataCollectionserviceUri,ITESTCaseLog TESTCaseLog,ITestRunLog testRunLog,iframeworkHandleInternal frameworkHandlE)
   at Microsoft.Visualstudio.TestPlatform.ClIEnt.Rocksteady.RocksteadyExecutionManager.StartTestRun(Testruncriteria testruncriteria,@R_874_8487@an inisolation,DataCollectionParameters dataCollectionParameters,ITestRunEventsHandler runEventsHandler)
   at Microsoft.Visualstudio.TestPlatform.ClIEnt.TestRunrequest.ExecuteAsync()
   at Microsoft.Visualstudio.Testwindow.Controller.TestRunrequest.onStart(Irequest request)
   at Microsoft.Visualstudio.Testwindow.Controller.request.<>c__displayClass100_0.<<Runrequest>b__0>d.MoveNext()
--- End of stack trace from prevIoUs LOCATIOn where exception was thrown ---
   at System.Runtime.Compilerservices.TaskAwaiter.ThrowForNonsuccess(Task task)
   at System.Runtime.Compilerservices.TaskAwaiter.HandleNonsuccessAndDeBUGgerNotification(Task task)
   at Microsoft.Visualstudio.Testwindow.Data.UnitTestStorage.<ExecuteWhiLeopen>d__32.MoveNext()
--- End of stack trace from prevIoUs LOCATIOn where exception was thrown ---
   at System.Runtime.Compilerservices.TaskAwaiter.ThrowForNonsuccess(Task task)
   at System.Runtime.Compilerservices.TaskAwaiter.HandleNonsuccessAndDeBUGgerNotification(Task task)
   at Microsoft.Visualstudio.Testwindow.Controller.request.<Runrequest>d__100.MoveNext()
--- End of stack trace from prevIoUs LOCATIOn where exception was thrown ---
   at System.Runtime.Compilerservices.TaskAwaiter.ThrowForNonsuccess(Task task)
   at System.Runtime.Compilerservices.TaskAwaiter.HandleNonsuccessAndDeBUGgerNotification(Task task)
   at Microsoft.Visualstudio.Testwindow.Controller.request.<Runrequests>d__99.MoveNext()
   --- End of inner exception stack trace ---
   at Microsoft.Visualstudio.Testwindow.Controller.request.<Processrequest>d__98.MoveNext()
========== Run test finished: 0 run (0:00:00,8452663) ==========
VirtualReadonlyTestDataStore.operationStateChanged State=TestExecutionFinished,operationInProgress=false
TestdiscoveryStats.OperationStateChanged State=TestExecutionFinished,InProgress=false

解决方法

暂无找到可以解决该程序问题的有效方法,小编努力寻找整理中!

如果你已经找到好的解决方法,欢迎将解决方案带上本链接一起发送给小编。

小编邮箱:dio#foxmail.com (将#修改为@)

大佬总结

以上是大佬教程为你收集整理的在 Visual Studio 2015 中调试 nunit 测试时出错全部内容,希望文章能够帮你解决在 Visual Studio 2015 中调试 nunit 测试时出错所遇到的程序开发问题。

如果觉得大佬教程网站内容还不错,欢迎将大佬教程推荐给程序员好友。

本图文内容来源于网友网络收集整理提供,作为学习参考使用,版权属于原作者。
如您有任何意见或建议可联系处理。小编QQ:384754419,请注明来意。