Skip to main content

Visual Studio 2012 RTM: Async tests are not found when using .NET Framework 4.0

For a project I created some async unit tests inside Visual Studio 2012 RC. 
[TestMethod]  
public async Task AsyncTest()   
{   
 var result = await MyOperationAsync();   
 Assert.IsTrue(result);   
}

Last week I took the opportunity to upgrade to the VS 2012 RTM version. But when I tried to run my async tests again, no tests were executed and the MsTest engine reported that no tests were found?! When I removed the async and await keywords, MsTest found my tests again… What has changed in Visual Studio that this no longer works?

It took me some time to figure out the root cause. What happened?

As the projects I wanted to test were .NET 4.0 projects, I decided to set the Unit Test project also to .NET 4.0. Of course in .NET 4.0, you don’t have async support out-of-the-box. So I installed the “Async targeting pack for Visual Studio 2012”.

The "Async Targeting Pack for Visual Studio 2012" enables projects targeting .NET Framework 4.0 or Silverlight 5 to use the Async language feature in C# 5 and Visual Basic 11. This pack requires Visual Studio 2012 and will not work with Visual Studio 2010.

The pack contains the API support necessary to use the 'async' and 'await' keywords in C# 5.0 and Visual Basic 11, as well as a set of Task-based adapter APIs that allow using some of the existing asynchronous APIs with the new language keywords.
 
This worked fine in Visual Studio 2012 RC. MsTest was able to discover and run my tests without a problem. The moment I upgraded to the RTM version, it no longer worked.
How did I fix it?
After changing the target framework for my Test project to .NET 4.5, my tests were discovered again. Anyone with a better solution?
Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more