Walkthrough: Creating and Running Unit Tests for Windows Store Apps
Microsoft Visual Studio 2012 includes support for unit testing managed Windows Store apps and includes unit test library templates for Visual C#, Visual Basic and Visual C++.
For more information about developing Windows Store apps, see Getting started with Windows Store apps.
Microsoft Visual Studio 2012 provides the following unit testing functionality:
The following procedures describe the steps to create, run and debug unit tests for managed Windows 8 Windows Store app.
To create a unit test project for a Windows Store app
From the File menu, choose New Project.
The New Project dialog displays.
Under Templates, choose the programming language you want to create unit test in and then choose the associated Windows Store unit test library. For example, choose Visual C# , then choose Windows Store, and then choose Unit Test Library (Windows Store apps).
Microsoft Visual Studio 2012 includes unit test library templates for Visual C#, Visual Basic and Visual C++.
(Optional) In the Name textbox, enter the name you want to use for the Windows Storeunit test project.
(Optional) Modify the path where you want to create the project by entering it in the Location textbox, or choosing the Browse button.
(Optional) In the Solution name textbox, enter that name you want to use for your solution.
Leave the Create directory for solution option selected and choose the OK button.
Solution Explorer is populated with your new Windows Storeunit test project and the code editor displays the default unit test titled UnitTest1.
It may be necessary to edit the manifest for the unit test project to provide required capabilities to run the app.
To edit the unit test project’s Windows Store application manifest file
In Solution Explorer, in the new Windows Store unit test project, right-click the Package.appxmanifest file and choose Open.
The Manifest Designer displays for editing.
In the Manifest Designer, choose the Capabilities tab.
In the list under Capabilities, select the capabilities that you need your unit test and the code that it testing to have. For example, select the Internet checkbox if the unit test needs and the code it is testing need to have the capability to access the internet.
The capabilities you select should only include capabilities that are necessary for the Windows Store unit test to function correctly. The capabilities should never have to include capabilities that are not part of the Windows Store app being tested and generally should be a subset of the capabilities specified for the Windows Storeapp under test.
For more information about the Manifest Designer, see Using the Manifest Designer (Windows Store apps).
To code the unit test for a Windows Store app
In the Code Editor, edit the unit test and add the asserts and logic required for your test.
For more information, see in Using the Assert Classes in the MSDN library.
To build the solution and run the unit test using Test Explorer
From the View menu, choose Other Windows, and then choose Test Explorer.
Test Explorer displays without your test being listed.
From the Build menu, choose Build Solution.
Your unit test is now listed.
You must build the solution to update the list of unit tests in Test Explorer.
Microsoft Visual Studio 2012 known issue: You must open Test Explorer prior to building the test project.
In Test Explorer, choose the unit test you created.
Test Explorer provides a link to the source code next to Source:.
Choose Run All.
You can select one or more unit tests listed in Explorer and then right-click and choose Run Selected Tests.
Additionally, you can choose to Debug Selected Tests, Open Test, and use the Properties option.
The unit test runs. Upon completion, Test Explorer displays the test status, elapsed time and provides a link to the source.