No test found. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again

buildtfstfs-2015unit testing

I am in the process of upgrading our existing solution to .Net 4.6.1 and have been unable to get our unit tests to run during a server build. Locally they run as expected and flipping the framework version back to .Net 4.5.1 makes them run again on the server.

I am getting the following error:

No test found. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again.

I have reproduced the problem in a simpler setup:

Solution with a single C# Unit Test project with two tests (one failing, one passing).
XAML build definition
using the Default Template (TfvcTemplate.12.xaml)
TFS 2015 Update 1
XAML build server with Visual Studio Enterprise 2015 Update 1
installed (have six similar servers and all produce the same result)

Best Answer

You can try to change your default processor architecture in your Test Setting from X86 to X64. In my case this was the problem.

This happens if the platform target of your project under test is set to x64.

Related Solutions

C# – Why does visual studio 2012 not find the tests

I had same symptoms, but under different circumstances.

I had to add one additional step to Peter Lamberg's solution — Clean your solution/project.

My unittest project targets x64. When I created the project it was originally targeting x86.

After switching to x64 all my unit tests disappeared.

I had to go to the Test Menu -> Test Setting -Default Processor Architecture -> x64.

They still didn't show up.

Did a build.

Still didn't show up.

Finally did a Clean

Then they showed up.

I find Clean Solution and Clean to be quite useful at getting the solutions to play ball when setting have changed. Sometimes I have to go to the extreme and delete the obj and bin directories and do a rebuild.

C# – Using Moq to mock an asynchronous method for a unit test

You're creating a task but never starting it, so it's never completing. However, don't just start the task - instead, change to using Task.FromResult<TResult> which will give you a task which has already completed:

...
.Returns(Task.FromResult(new HttpResponseMessage(System.Net.HttpStatusCode.OK)));

Note that you won't be testing the actual asynchrony this way - if you want to do that, you need to do a bit more work to create a Task<T> that you can control in a more fine-grained manner... but that's something for another day.

You might also want to consider using a fake for IHttpClient rather than mocking everything - it really depends on how often you need it.

Best Answer

Related Solutions

C# – Why does visual studio 2012 not find the tests

C# – Using Moq to mock an asynchronous method for a unit test

Related Topic