{"id":17145,"date":"2016-05-30T13:43:40","date_gmt":"2016-05-30T20:43:40","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/?p=17145"},"modified":"2019-02-14T17:33:59","modified_gmt":"2019-02-15T01:33:59","slug":"announcing-mstest-framework-support-for-net-core-rc2-asp-net-core-rc2","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/announcing-mstest-framework-support-for-net-core-rc2-asp-net-core-rc2\/","title":{"rendered":"Announcing MSTest Framework support for .NET Core RC2 \/ ASP.NET Core RC2"},"content":{"rendered":"

.NET Core RC2 and ASP.NET Core RC2 released just a couple of weeks back. They feature the introduction of the .NET CLI, major changes to the .NET Core SDK (formerly called DNX), the rebranding of ASP.NET 5 to ASP.NET Core, and more. You can read about these on the .NET team blog<\/a> and the .NET Web Development team blog<\/a>.<\/p>\n

We are now pleased to announce MSTest framework support for these releases! The framework and its allied packages are available on NuGet now. This is a preview release, and we are looking for your feedback to make this a robust rollout for RTM.<\/p>\n

In this post, we show you how to write and run your first set of MSTest based tests for this release. Here are the steps:<\/p>\n

    \n
  1. Installing the SDK<\/li>\n
  2. Creating a class library project<\/li>\n
  3. Adding references for MSTest<\/li>\n
  4. Writing the tests<\/li>\n
  5. Running the tests from Visual Studio<\/li>\n
  6. Running the tests from the console<\/li>\n
  7. Targetting desktop .NET<\/li>\n<\/ol>\n

    Installing the SDK<\/h3>\n

    Install the Visual Studio official MSI installer from https:\/\/www.microsoft.com\/net\/core<\/a><\/p>\n

    Creating a class library project<\/h3>\n

    Create a .NET Core Class Library application. Open Visual Studio, and choose File | New | Project:<\/p>\n

    \"img1\"<\/a><\/p>\n

    Adding references for MSTest<\/h3>\n

    From nuget.org, install the MSTest.TestFramework package (shown below).<\/p>\n

    \"img2\"<\/a><\/p>\n

    Now, install the runner \u2013 look for the dotnet-test-mstest package, and install it:<\/p>\n

    \"img3-new\"<\/a><\/p>\n

    [Editor\u2019s note<\/strong>: Thank you @IanGriffiths and @BenHysell for reporting an issue with the package we published earlier. We have since uploaded a fixed version, as shown in the updated image above.]<\/span><\/em><\/p>\n

    Open the project.json<\/code> file in the solution. You will already see the packages you just installed mentioned under “dependencies”. We need to add the “testRunner” property and set that to “mstest”. To make it easier, just replace the content of the project.json<\/code> file with the following:<\/p>\n

    {\n  \"version\"<\/span>: \"1.0.0-*\"<\/span>,\n\n  \"testRunner\"<\/span>: \"mstest\"<\/span>,\n\n  \"dependencies\"<\/span>: {\n    \"dotnet-test-mstest\"<\/span>: \"1.0.1-preview\"<\/span>,\n    \"MSTest.TestFramework\"<\/span>: \"1.0.0-preview\"<\/span>\n  },\n\n  \"frameworks\"<\/span>: {\n    \"netcoreapp1.0\"<\/span>: {\n      \"imports\"<\/span>: [\n        \"dnxcore50\"<\/span>,\n        \"portable-net45+win8\"<\/span>\n      ],\n  \n      \"dependencies\"<\/span>: {\n        \"Microsoft.NETCore.App\"<\/span>: {\n          \"version\"<\/span>: \"1.0.0-rc2-3002702\"<\/span>,\n          \"type\"<\/span>: \"platform\"<\/span>\n        }\n      }\n    }\n  }\n}\n<\/code><\/pre>\n
    Notice that the class library project we created is getting marked as an application (netcoreapp1.0<\/code>). That is because when using .NET CLI for testing, unit test projects are actually an application, not a class library. That application\u2019s Main<\/em> method is provided by the runner.<\/p>\n
    Writing the tests<\/h3>\n
    Visual Studio would have automatically created a file named Class1.cs<\/code>. Open that file and replace its content with the following:<\/p>\n
    using<\/span> Microsoft.VisualStudio.TestTools.UnitTesting;\n\nnamespace<\/span> SampleNetCoreUnitTests\n{\n  [TestClass<\/span>]\n  public class<\/span> TestClass<\/span>\n  {\n    [TestMethod<\/span>]\n    public void<\/span> TestMethodPassing()\n    {\n      Assert<\/span>.IsTrue(true<\/span>);\n    }\n\n    [TestMethod<\/span>]\n    public void<\/span> TestMethodFailing()\n    {\n      Assert<\/span>.IsTrue(false<\/span>);\n    }\n  }\n}\n<\/code><\/pre>\n
    Running tests from the console<\/h3>\n
    Open a command prompt and navigate to the folder containing the solution. Type dotnet test<\/code> to run the .NET CLI test runner:<\/p>\n
    D:SamplesdotNetCoreTestssrcdotNetCoreTests>dotnet test\nProject dotNetCoreTests (.NETFramework,Version=v4.5.1) was previously compiled. Skipping compilation.\nDiscovering Tests ...\nExecuting Tests ...\nPassed   TestMethodPassing\nFailed   TestMethodFailing\nError Message:\n   Assert.IsTrue failed.\nStack Trace:\n   at SampleNetCoreUnitTests.TestClass.TestMethodFailing() in D:SamplesdotNetCoreTestssrcdotNetCoreTestsClass1.cs:line 17\n============ Test Run Summary ============\nTotal tests: 2. Passed: 1. Failed: 1. Skipped: 0\nTest Run Failed.\nSUMMARY: Total: 1 targets, Passed: 1, Failed: 0.\n<\/code><\/span><\/pre>\n
    The tests are discovered and executed as expected.<\/p>\n
    Targeting the desktop .NET<\/h3>\n
    In addition to .NET Core, the .NET CLI runner can run tests targeting desktop .NET (minimum version 4.5.1) as well. To target desktop .NET, update the project.json<\/code> to use this frameworks section instead:<\/p>\n
    \"frameworks\"<\/span>: {\n  \"net451\"<\/span>: { }\n}\n<\/code><\/pre>\n
    Summary<\/h3>\n
    There, it is as simple as that – MSTest support for .NET Core 1.0 RC2 and ASP.NET Core 1.0 RC2, fully integrated with Visual Studio.<\/p>\n","protected":false},"excerpt":{"rendered":"
    .NET Core RC2 and ASP.NET Core RC2 released just a couple of weeks back. They feature the introduction of the .NET CLI, major changes to the .NET Core SDK (formerly called DNX), the rebranding of ASP.NET 5 to ASP.NET Core, and more. You can read about these on the .NET team blog and the .NET […]<\/p>\n","protected":false},"author":765,"featured_media":45953,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[226,1,252],"tags":[],"class_list":["post-17145","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ci","category-devops","category-testing"],"acf":[],"blog_post_summary":"
    .NET Core RC2 and ASP.NET Core RC2 released just a couple of weeks back. They feature the introduction of the .NET CLI, major changes to the .NET Core SDK (formerly called DNX), the rebranding of ASP.NET 5 to ASP.NET Core, and more. You can read about these on the .NET team blog and the .NET […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/17145","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/users\/765"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=17145"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/17145\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/45953"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=17145"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=17145"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=17145"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
    Running the tests from Visual Studio<\/h3>\n
    Open the Test Explorer window (Test | Windows | Test Explorer in Visual Studio).\nBuild the solution, and you should see the tests as follows:<\/p>\n
    \"img4\"<\/a><\/p>\n
    Click on “Run All” to run the tests.<\/p>\n
    \"img5\"<\/a><\/p>\n