Geek Answers Handbook

Unit Test Sessions failed to complete

I am using VS2015 professional with the final version and I started getting the following error in the unit test session window when I execute my unit tests.

2016.09.21 14: 16: 54.745 ERROR System.AggregateException: One or more errors occurred. ---> System.Threading.Tasks.TaskCanceledException: the task has been canceled. --- End of internal check of the exception stack --- in System.Threading.Tasks.Task.ThrowIfExceptional (Boolean includeTaskCanceledExceptions) in System.Threading.Tasks.Task.Wait (Int32 millisecondsTimeout, CancellationToken cancelationToken) on JetBrains.ReSharperrameLestTestunchunch .Stages.DiscoveryStage.Run (CancellationToken token) on JetBrains.ReSharper.UnitTestFramework.Launch.UnitTestLaunch.RunStage (Object stageObject) ---> (Internal exception # 0) System.Threading.Tasks.TaskCanceledException: The task was canceled. <---

tests of other projects work fine in VS2013, but not in VS2015. Yesterday I installed a couple of packages on my computer: vs14-kb3165756.exe and OpenCover.UI.vsix

I tried to remove the OpenCover package, which did not solve the problem.

+8
c # unit-testing visual-studio-2015 resharper
source share
3 answers

I had the same problem, in my configuration the solution was set to "Release". Make sure your entire project is set to Debug and try again. Worked for me

+4
source share

For those who are experiencing this problem, after re-adding the UWP Unit Test project several times, I found that after creating a new Unit Test project (Universal Windows) in the Solution Configuration Manager for some reason, the Build CheckBox was not checked, and when I checked it and performed my unit tests, everything was performed as expected.

Right-click Solution> Configuration Manager ...

+6
source share

This is most likely due to katit answer, but it also happens when the configuration is in debug mode, but is deployed using the Release version.

Runner does not start after deployment (Release), probably because it tries to start using the last assembly output, which consists of assembly assemblies (optimized) , so you need to perform a complete rebuild with the Debug configuration.

+1
source share

More articles:


All Articles