Windows Phone 7 Continuous Integration Testing Framework

New Post: Integrating with TFS Build

dbau56789 — Wed, 14 Mar 2012 04:37:59 GMT

This project looks like it has exactly what I was looking for. However, I am having trouble integrating the Continuous Integration Testing Framework with a TFS 2010 build server.

My first issue was that the Unit Test project couldn't find several Silverlight Assemblies when executing the unit tests (see below). I tried doing a Copy Local == true but then the System.Core Assembly still had issues.

I am building the project using the x86 processor architecture msbuild switch on a 64 bit machine as is necessary for silverlight assemblies.

Error details: System.IO.FileNotFoundException: Could not load file or assembly 'System.Windows, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e' or one of its dependencies.

The system cannot find the file specified.System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Phone, Version=7.0.0.0, Culture=neutral, PublicKeyToken=24eec0d8c86cda1e' or one of its dependencies. The system cannot find the file specified.

Reviewed: 1.1 (Nov 15, 2011)

andrew_khmylov — Tue, 15 Nov 2011 10:43:42 GMT

Rated 5 Stars (out of 5) - I've been searching for a good testing solution for my WP7 projects, and this framework does simply everything I need. Great work!

Updated Wiki: Home

richard_szalay — Sun, 21 Aug 2011 19:58:53 GMT

Project Description
WP7 CI is a port of the Silverlight Toolkit Test Framework with added CI support, allowing tests to be run in the emulator from the command line

NOTE: WP7-CI 1.1 (now with Mango support!) has a breaking change with 1.0 in that the MSBuild task is now called "Test" instead of "RunUnitTests". See the download page for a complete changelist.

Installation

Don't have NuGet? A manual installation package is now available. Read the readme.txt!

If you have NuGet, simply add the WP7-CI package from NuGet, which will do the following:

Add references to the Microsoft.Silverlight.Testing and Microsoft.VisualStudio.QualityTools.UnitTesting.Silverlight assemblies that ship with the package (removing existing references if they exist)
Add an MSBuild task called "Test" to the project that can be called from the command line (it's configured by default to fail build if the tests fail)
Add a TestsPage.xaml and set it as the startup page (you're free to remove this file)
Add a SampleTest.cs which contains three tests (one pass, one fail, one error)

You can then run the tests:

In Visual Studio by setting the tests project as startup and hitting F5
At the command line by running msbuild against the project and setting the target to "Test" (it will automatically build your project if required)

The log will be written to TestResult.trx in the same directory as the XAML output. See Build Properties for properties that you can override at the command line.

If your CI server is run by a windows service, you will need to enable "Allow service to interact with desktop" in the service's "Logon" options.

Features

MSBuild task for executing tests in the WP7 OS from the command line
- Basic options for emulator vs device
- Adanced options for selecting emulator images
Updated Microsoft.Silverlight.Testing assembly that enables service-callback support for WP7

Project Lifespan and Scope

This project will be terminated once there is official support for running in-emulator unit tests in a CI environment. Bug fixes and features will be limited to the automation of running unit tests on the WP7 operating system.

Known Issues

The emulator is not closed after execution completes

Updated Release: 1.1 (Aug 21, 2011)

richard_szalay — Sun, 21 Aug 2011 19:56:49 GMT

Change Log

BREAKING CHANGE Test task name is now "Test" (was "RunUnitTests")
Windows Phone 7.1 (Mango) support
Fixed display bug for ExpectedException tests

Installation

Using NuGet, install "WP7-CI" to the Windows Phone Silverlight Application that is being used for unit tests (create one if you haven't already).

NOTE: The package will change the startup page to "TestsPage.xaml", but you can revert it to "MainPage.xaml" by editing Properties/WMAppManifest.xaml. You can then delete the TestsPage.xaml file.

Manual Installation

Don't have NuGet?

Create a Windows Phone Silverlight Application for your tests if you haven't already
Download the manual installation archive and extract it to a folder called "WP7-CI" under your application project folder.
Add a reference to Microsoft.Silverlight.Testing.dll and Microsoft.VisualStudio.QualityTools.UnitTesting.Silverlight.dll in lib/sl3-wp. Remove any references to previous versions of these assemblies.
Manually edit your project file (csproj/vbproj) and place the following before the </Project> at the end of the file:

<Import Project="WP7-CI\tools\WP7CI.targets" />

Also, as is required by the standard testing framework, the following code should be placed in the Loaded event of your startup page:

var testPage = UnitTestSystem.CreateTestPage() as IMobileTestPage;

BackKeyPress += (x, xe) => xe.Cancel = testPage.NavigateBack();
(Application.Current.RootVisual as PhoneApplicationFrame).Content = testPage;

Released: 1.1 (Aug 21, 2011)

Sun, 21 Aug 2011 19:56:49 GMT

Change Log

BREAKING CHANGE Test task name is now "Test" (was "RunUnitTests")
Windows Phone 7.1 (Mango) support
Fixed display bug for ExpectedException tests

Installation

Manual Installation

Don't have NuGet?

Create a Windows Phone Silverlight Application for your tests if you haven't already
Download the manual installation archive and extract it to a folder called "WP7-CI" under your application project folder.
Add a reference to Microsoft.Silverlight.Testing.dll and Microsoft.VisualStudio.QualityTools.UnitTesting.Silverlight.dll in lib/sl3-wp. Remove any references to previous versions of these assemblies.
Manually edit your project file (csproj/vbproj) and place the following before the </Project> at the end of the file:

<Import Project="WP7-CI\tools\WP7CI.targets" />

Also, as is required by the standard testing framework, the following code should be placed in the Loaded event of your startup page:

var testPage = UnitTestSystem.CreateTestPage() as IMobileTestPage;

BackKeyPress += (x, xe) => xe.Cancel = testPage.NavigateBack();
(Application.Current.RootVisual as PhoneApplicationFrame).Content = testPage;

Updated Wiki: Home

richard_szalay — Sun, 21 Aug 2011 19:53:31 GMT

Installation

Don't have NuGet? A manual installation package is now available. Read the readme.txt!

If you have NuGet, simply add the WP7-CI package from NuGet, which will do the following:

Add references to the Microsoft.Silverlight.Testing and Microsoft.VisualStudio.QualityTools.UnitTesting.Silverlight assemblies that ship with the package (removing existing references if they exist)
Add an MSBuild task called "RunUnitTests" to the project that can be called from the command line (it's configured by default to fail build if the tests fail)
Add a TestsPage.xaml and set it as the startup page (you're free to remove this file)
Add a SampleTest.cs which contains three tests (one pass, one fail, one error)

You can then run the tests:

In Visual Studio by setting the tests project as startup and hitting F5
At the command line by running msbuild against the project and setting the target to "Test" (it will automatically build your project if required)

Features

MSBuild task for executing tests in the WP7 OS from the command line
- Basic options for emulator vs device
- Adanced options for selecting emulator images
Updated Microsoft.Silverlight.Testing assembly that enables service-callback support for WP7

Project Lifespan and Scope

Known Issues

The emulator is not closed after execution completes

Updated Wiki: Home

richard_szalay — Sun, 21 Aug 2011 19:53:12 GMT

Installation

Don't have NuGet? A manual installation package is now available. Read the readme.txt!

If you have NuGet, simply add the WP7-CI package from NuGet, which will do the following:

Add references to the Microsoft.Silverlight.Testing and Microsoft.VisualStudio.QualityTools.UnitTesting.Silverlight assemblies that ship with the package (removing existing references if they exist)
Add an MSBuild task called "RunUnitTests" to the project that can be called from the command line (it's configured by default to fail build if the tests fail)
Add a TestsPage.xaml and set it as the startup page (you're free to remove this file)
Add a SampleTest.cs which contains three tests (one pass, one fail, one error)

You can then run the tests:

In Visual Studio by setting the tests project as startup and hitting F5
At the command line by running msbuild against the project and setting the target to "Test" (it will automatically build your project if required)

Features

MSBuild task for executing tests in the WP7 OS from the command line
- Basic options for emulator vs device
- Adanced options for selecting emulator images
Updated Microsoft.Silverlight.Testing assembly that enables service-callback support for WP7

Project Lifespan and Scope

Known Issues

The emulator is not closed after execution completes

Updated Release: 1.1 (Aug 21, 2011)

richard_szalay — Sun, 21 Aug 2011 19:50:32 GMT

Change Log

BREAKING CHANGE Test task name is now "Test" (was "RunUnitTests")
Windows Phone 7.1 (Mango) support
Fixed display bug for ExpectedException tests

Installation

Manual Installation

Don't have NuGet?

Create a Windows Phone Silverlight Application for your tests if you haven't already
Download the manual installation archive and extract it to a folder called "WP7-CI" under your application project folder.
Manually edit your project file (csproj/vbproj) and place the following before the </Project> at the end of the file:

<Import Project="WP7-CI\tools\WP7CI.targets" />

Also, as is required by the standard testing framework, the following code should be placed in the Loaded event of your startup page:

var testPage = UnitTestSystem.CreateTestPage() as IMobileTestPage;

BackKeyPress += (x, xe) => xe.Cancel = testPage.NavigateBack();
(Application.Current.RootVisual as PhoneApplicationFrame).Content = testPage;

Updated Release: 1.1 (Aug 21, 2011)

richard_szalay — Sun, 21 Aug 2011 19:46:58 GMT

Change Log

BREAKING CHANGE Test task name is now "Test" (was "RunUnitTests")
Windows Phone 7.1 (Mango) support
Fixed display bug for ExpectedException tests

Installation

Manual Installation

Don't have NuGet?

Create a Windows Phone Silverlight Application for your tests if you haven't already
Download the manual installation archive and extract it to a folder called "WP7-CI" under your application project folder.
Manually edit your project file (csproj/vbproj) and place the following before the </Project> at the end of the file:

<Import Project="WP7-CI\tools\WP7CI.targets" />

Also, as is required by the standard testing framework, the following code should be placed in the Loaded event of your startup page:

var testPage = UnitTestSystem.CreateTestPage() as IMobileTestPage;

BackKeyPress += (x, xe) => xe.Cancel = testPage.NavigateBack();
(Application.Current.RootVisual as PhoneApplicationFrame).Content = testPage;

Updated Release: 1.1 (Aug 21, 2011)

richard_szalay — Sun, 21 Aug 2011 19:45:17 GMT

Change Log

BREAKING CHANGE Test task name is now "Test" (was "RunUnitTests")
Windows Phone 7.1 (Mango) support
Fixed display bug for ExpectedException tests

Installation

Using NuGet:http://nuget.org/, install "WP7-CI" to the Windows Phone Silverlight Application that is being used for unit tests (create one if you haven't already).

NOTE: The package will change the startup page to "TestsPage.xaml", but you can revert it to "MainPage.xaml" by editing Properties/WMAppManifest.xaml. You can then delete the TestsPage.xaml file.

Manual Installation

Don't have NuGet?

Create a Windows Phone Silverlight Application for your tests if you haven't already
Download the manual installation archive and extract it to a folder called "WP7-CI" under your application project folder.
Manually edit your project file (csproj/vbproj) and place the following before the </Project> at the end of the file:

<Import Project="WP7-CI\tools\WP7CI.targets" />

Also, as is required by the standard testing framework, the following code should be placed in the Loaded event of your startup page:

var testPage = UnitTestSystem.CreateTestPage() as IMobileTestPage;

BackKeyPress += (x, xe) => xe.Cancel = testPage.NavigateBack();
(Application.Current.RootVisual as PhoneApplicationFrame).Content = testPage;

Created Release: 1.1 (Aug 21, 2011)

richard_szalay — Sun, 21 Aug 2011 19:45:06 GMT

Change Log

BREAKING CHANGE Test task name is now "Test" (was "RunUnitTests")
Windows Phone 7.1 (Mango) support
Fixed display bug for ExpectedException tests

Installation

Manual Installation

Don't have NuGet?

Create a Windows Phone Silverlight Application for your tests if you haven't already
Download the manual installation archive and extract it to a folder called "WP7-CI" under your application project folder.
Manually edit your project file (csproj/vbproj) and place the following before the </Project> at the end of the file:

<Import Project="WP7-CI\tools\WP7CI.targets" />

Also, as is required by the standard testing framework, the following code should be placed in the Loaded event of your startup page:

var testPage = UnitTestSystem.CreateTestPage() as IMobileTestPage;

BackKeyPress += (x, xe) => xe.Cancel = testPage.NavigateBack();
(Application.Current.RootVisual as PhoneApplicationFrame).Content = testPage;

Source code checked in, #039f9d34ae77

Richard — Sun, 21 Aug 2011 19:06:24 GMT

Moved tag 1.1 to changeset c4a9cc2a05d1 (from changeset ab220f3cd817)

Source code checked in, #c4a9cc2a05d1

Richard — Sun, 21 Aug 2011 19:05:12 GMT

Breaking Change: Changed test target name to "Test" Added a DependsOn property for "Test"

Source code checked in, #73712d7bf062

Richard — Sun, 21 Aug 2011 18:33:50 GMT

Added tag 1.1 for changeset ab220f3cd817

Source code checked in, #ab220f3cd817

Richard — Sun, 21 Aug 2011 18:31:08 GMT

Fixed bugs preventing execution under Mango Fixed a visual bug related to the display of expected exceptions Updated NuSpec details

Updated Wiki: Home

richard_szalay — Thu, 11 Aug 2011 14:21:56 GMT

Project Description
WP7 CI is a port of the Silverlight Toolkit Test Framework with added CI support, allowing tests to be run in the emulator from the command line

Installation

NOTE: NuGet is not currently available for Visual Studio Express for Windows Phone, but it will be supported as of the WP71 ("Mango") release. Until then, either configure the package manually or hold tight!

Simply add the WP7-CI package from NuGet, which will do the following:

Add references to the Microsoft.Silverlight.Testing and Microsoft.VisualStudio.QualityTools.UnitTesting.Silverlight assemblies that ship with the package (removing existing references if they exist)
Add an MSBuild task called "RunUnitTests" to the project that can be called from the command line (it's configured by default to fail build if the tests fail)
Add a TestsPage.xaml and set it as the startup page (you're free to remove this file)
Add a SampleTest.cs which contains three tests (one pass, one fail, one error)

You can then run the tests:

In Visual Studio by setting the tests project as startup and hitting F5
At the command line by running msbuild against the project and setting the target to "RunUnitTests" (it will automatically build your project if required)

Features

MSBuild task for executing tests in the WP7 OS from the command line
- Basic options for emulator vs device
- Adanced options for selecting emulator images
Updated Microsoft.Silverlight.Testing assembly that enables service-callback support for WP7

Project Lifespan and Scope

Known Issues

The emulator is not closed after execution completes

New Post: Integration in Hudson

richard_szalay — Thu, 11 Aug 2011 14:13:09 GMT

Have you configured the service with "Allow service to interact with desktop" rights?

New Post: Integration in Hudson

Paab72 — Tue, 02 Aug 2011 06:09:51 GMT

I have set up Hudson to build and perform testing, but it will not detect when the tests are done. Anyone that have any suggestion on how to solve this?

Source code checked in, #306d85c85033

richard_szalay — Thu, 19 May 2011 16:48:10 GMT

Initial commit