Skip to content

Commit 8d01446

Browse files
author
Andy Adamczak
committed
Added SmartPhone as a PureMVC target.
1 parent 48b2552 commit 8d01446

11 files changed

+2213
-0
lines changed

‎PureMVC.DotNET.VS2008.SmartPhone.Tests/AuthoringTests.txt

Lines changed: 136 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,136 @@
1+
==========================================================================
2+
Visual Studio Team System: Overview of Authoring and Running Tests
3+
==========================================================================
4+
5+
This overview describes the features for authoring and running tests in
6+
Visual Studio Team System and Visual Studio Team Edition for Software Testers.
7+
8+
Opening Tests
9+
-------------
10+
To open a test, open a test project or a test metadata file (a file with
11+
extension .vsmdi) that contains the definition of the test. You can find
12+
test projects and metadata files in Solution Explorer.
13+
14+
Viewing Tests
15+
-------------
16+
To see which tests are available to you, open the Test View window. Or,
17+
if you have installed Team Edition for Software Testers, you can also open
18+
the Test List Editor window to view tests.
19+
20+
To open the Test View window, click the Test menu, point to Windows, and
21+
then click Test View. To open the Test List Editor window (if you have
22+
installed Team Edition for Software Testers), click Test, point to Windows,
23+
and then click Test List Editor.
24+
25+
Running Tests
26+
-------------
27+
You can run tests from the Test View window and the Test List Editor window.
28+
See Viewing Tests to learn how to open these windows. To run one or more
29+
tests displayed in the Test View window, first select the tests in that
30+
window; to select multiple tests, hold either the Shift or CTRL key while
31+
clicking tests. Then click the Run Tests button in the Test View window
32+
toolbar.
33+
34+
If you have installed Visual Studio Team Edition for Software Testers, you can
35+
also use the Test List Editor window to run tests. To run tests in Test List Editor,
36+
select the check box next to each test that you want to run. Then click the
37+
Run Tests button in the Test List Editor window toolbar.
38+
39+
Viewing Test Results
40+
--------------------
41+
When you run a test or a series of tests, the results of the test run will be
42+
shown in the Test Results window. Each individual test in the run is shown on
43+
a separate line so that you can see its status. The window contains an
44+
embedded status bar in the top half of the window that provides you with
45+
summary details of the complete test run.
46+
47+
To see more detailed results for a particular test result, double-click it in
48+
the Test Results window. This opens a window that provides more information
49+
about the particular test result, such as any specific error messages returned
50+
by the test.
51+
52+
Changing the way that tests are run
53+
-----------------------------------
54+
Each time you run one or more tests, a collection of settings is used to
55+
determine how those tests are run. These settings are contained in a “test
56+
run configuration” file.
57+
58+
Here is a partial list of the changes you can make with a test run
59+
configuration file:
60+
61+
- Change the naming scheme for each test run.
62+
- Change the test controller that the tests are run on so that you can run
63+
tests remotely.
64+
- Gather code coverage data for the code being tested so that you can see
65+
which lines of code are covered by your tests.
66+
- Enable and disable test deployment.
67+
- Specify additional files to deploy before tests are run.
68+
- Select a different host, ASP.NET, for running ASP.NET unit tests.
69+
- Select a different host, the smart device test host, for running smart device unit tests.
70+
- Set various properties for the test agents that run your tests.
71+
- Run custom scripts at the start and end of each test run so that you can
72+
set up the test environment exactly as required each time tests are run.
73+
- Set time limits for tests and test runs.
74+
- Set the browser mix and the number of times to repeat Web tests in the
75+
test run.
76+
77+
By default, a test run configuration file is created whenever you create a
78+
new test project. You make changes to this file by double-clicking it in
79+
Solution Explorer and then changing its settings. (Test run configuration
80+
files have the extension .testrunconfig.)
81+
82+
A solution can contain multiple test run configuration files. Only one of
83+
those files, known as the “Active” test run configuration file, is used to
84+
determine the settings that are currently used for test runs. You select
85+
the active test run configuration by clicking Select Active Test Run
86+
Configuration on the Test menu.
87+
88+
-------------------------------------------------------------------------------
89+
90+
Test Types
91+
----------
92+
Using Visual Studio Team Edition for Software Testers, you can create a number
93+
of different test types:
94+
95+
Unit test: Use a unit test to create a programmatic test in C++, Visual C# or
96+
Visual Basic that exercises source code. A unit test calls the methods of a
97+
class, passing suitable parameters, and verifies that the returned value is
98+
what you expect.
99+
There are three specialized variants of unit tests:
100+
- Data-driven unit tests are created when you configure a unit test to be
101+
called repeatedly for each row of a data source. The data from each row
102+
is used by the unit test as input data.
103+
- ASP.NET unit tests are unit tests that exercise code in an ASP.NET Web
104+
application.
105+
- Smart device unit tests are unit tests that are deployed to a smart device
106+
or emulator and then executed by the smart device test host.
107+
108+
Web Test: Web tests consist of an ordered series of HTTP requests that you
109+
record in a browser session using Microsoft Internet Explorer. You can have
110+
the test report specific details about the pages or sites it requests, such
111+
as whether a particular page contains a specified string.
112+
113+
Load Test: You use a load test to encapsulate non-manual tests, such as
114+
unit, Web, and generic tests, and then run them simultaneously by using
115+
virtual users. Running these tests under load generates test results,
116+
including performance and other counters, in tables and in graphs.
117+
118+
Generic test: A generic test is an existing program wrapped to function as a
119+
test in Visual Studio. The following are examples of tests or programs that
120+
you can turn into generic tests:
121+
- An existing test that uses process exit codes to communicate whether the
122+
test passed or failed. 0 indicates passing and any other value indicates
123+
a failure.
124+
- A general program to obtain specific functionality during a test scenario.
125+
- A test or program that uses a special XML file (called a “summary results
126+
file”), to communicate detailed results.
127+
128+
Manual test: The manual test type is used when the test tasks are to be
129+
completed by a test engineer as opposed to an automated script.
130+
131+
Ordered test: Use an ordered test to execute a set of tests in an order you
132+
specify.
133+
134+
-------------------------------------------------------------------------------
135+
136+

‎PureMVC.DotNET.VS2008.SmartPhone.Tests/Properties/AssemblyInfo.cs

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
using System.Reflection;
2+
using System.Runtime.CompilerServices;
3+
using System.Runtime.InteropServices;
4+
5+
// General Information about an assembly is controlled through the following
6+
// set of attributes. Change these attribute values to modify the information
7+
// associated with an assembly.
8+
[assembly: AssemblyTitle("PureMVC.DotNET.VS2008.SmartPhone.Tests")]
9+
[assembly: AssemblyDescription("")]
10+
[assembly: AssemblyConfiguration("")]
11+
[assembly: AssemblyCompany("")]
12+
[assembly: AssemblyProduct("PureMVC.DotNET.VS2008.SmartPhone.Tests")]
13+
[assembly: AssemblyCopyright("Copyright © 2009")]
14+
[assembly: AssemblyTrademark("")]
15+
[assembly: AssemblyCulture("")]
16+
17+
// Setting ComVisible to false makes the types in this assembly not visible
18+
// to COM componenets. If you need to access a type in this assembly from
19+
// COM, set the ComVisible attribute to true on that type.
20+
[assembly: ComVisible(false)]
21+
22+
// The following GUID is for the ID of the typelib if this project is exposed to COM
23+
[assembly: Guid("b059f593-f455-44de-9265-b634580c356e")]
24+
25+
// Version information for an assembly consists of the following four values:
26+
//
27+
// Major Version
28+
// Minor Version
29+
// Build Number
30+
// Revision
31+
//
32+
// You can specify all the values or you can default the Revision and Build Numbers
33+
// by using the '*' as shown below:
34+
[assembly: AssemblyVersion("1.0.0.0")]

‎PureMVC.DotNET.VS2008.SmartPhone.Tests/PureMVC.DotNET.VS2008.SmartPhone.Tests.csproj

Lines changed: 172 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,172 @@
1+
<?xml version="1.0" encoding="utf-8"?>
2+
<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="3.5">
3+
<PropertyGroup>
4+
<Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
5+
<Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform>
6+
<ProductVersion>9.0.30729</ProductVersion>
7+
<SchemaVersion>2.0</SchemaVersion>
8+
<ProjectGuid>{4C97BCC4-3357-476F-A98F-8A3D356BD24D}</ProjectGuid>
9+
<OutputType>Library</OutputType>
10+
<RootNamespace>PureMVC.DotNET.VS2008.SmartPhone.Tests</RootNamespace>
11+
<AssemblyName>PureMVC.DotNET.VS2008.SmartPhone.Tests</AssemblyName>
12+
<PlatformFamilyName>Smartphone</PlatformFamilyName>
13+
<PlatformID>BD0CC567-F6FD-4ca3-99D2-063EFDFC0A39</PlatformID>
14+
<OSVersion>5.1</OSVersion>
15+
<DeployDirSuffix>PureMVC.DotNET.VS2008.SmartPhone.Tests</DeployDirSuffix>
16+
<TargetFrameworkVersion>v3.5</TargetFrameworkVersion>
17+
<FormFactorID>
18+
</FormFactorID>
19+
<WarningLevel>4</WarningLevel>
20+
<ProjectTypeGuids>{73A5A715-AF05-47af-9C33-47A864AF9AE7};{3AC096D0-A1C2-E12C-1390-A8335801FDAB};{4D628B5B-2FBC-4AA6-8C16-197242AEB884};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids>
21+
<NativePlatformName>Windows Mobile 5.0 Smartphone SDK</NativePlatformName>
22+
</PropertyGroup>
23+
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
24+
<DebugSymbols>true</DebugSymbols>
25+
<DebugType>full</DebugType>
26+
<Optimize>false</Optimize>
27+
<OutputPath>bin\Debug\</OutputPath>
28+
<NoStdLib>true</NoStdLib>
29+
<NoConfig>true</NoConfig>
30+
<ErrorReport>prompt</ErrorReport>
31+
<FileAlignment>512</FileAlignment>
32+
<WarningLevel>4</WarningLevel>
33+
<GenerateSerializationAssemblies>Off</GenerateSerializationAssemblies>
34+
<DefineConstants>DEBUG;TRACE;$(PlatformFamilyName)</DefineConstants>
35+
</PropertyGroup>
36+
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
37+
<DebugSymbols>false</DebugSymbols>
38+
<Optimize>true</Optimize>
39+
<OutputPath>bin\Release\</OutputPath>
40+
<DefineConstants>TRACE;$(PlatformFamilyName)</DefineConstants>
41+
<NoStdLib>true</NoStdLib>
42+
<NoConfig>true</NoConfig>
43+
<ErrorReport>prompt</ErrorReport>
44+
<FileAlignment>512</FileAlignment>
45+
<WarningLevel>4</WarningLevel>
46+
<GenerateSerializationAssemblies>Off</GenerateSerializationAssemblies>
47+
</PropertyGroup>
48+
<ItemGroup>
49+
<Reference Include="Microsoft.VisualStudio.SmartDevice.UnitTestFramework, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL">
50+
<Private>False</Private>
51+
</Reference>
52+
<Reference Include="mscorlib" />
53+
<Reference Include="System" />
54+
<Reference Include="System.Core" />
55+
<Reference Include="System.Data" />
56+
<Reference Include="System.Data.DataSetExtensions" />
57+
<Reference Include="System.Xml" />
58+
<Reference Include="System.Xml.Linq" />
59+
</ItemGroup>
60+
<ItemGroup>
61+
<Compile Include="..\PureMVC\Tests\Core\ControllerTest.cs">
62+
<Link>Core\ControllerTest.cs</Link>
63+
</Compile>
64+
<Compile Include="..\PureMVC\Tests\Core\ControllerTestCommand.cs">
65+
<Link>Core\ControllerTestCommand.cs</Link>
66+
</Compile>
67+
<Compile Include="..\PureMVC\Tests\Core\ControllerTestCommand2.cs">
68+
<Link>Core\ControllerTestCommand2.cs</Link>
69+
</Compile>
70+
<Compile Include="..\PureMVC\Tests\Core\ControllerTestVO.cs">
71+
<Link>Core\ControllerTestVO.cs</Link>
72+
</Compile>
73+
<Compile Include="..\PureMVC\Tests\Core\ModelTest.cs">
74+
<Link>Core\ModelTest.cs</Link>
75+
</Compile>
76+
<Compile Include="..\PureMVC\Tests\Core\ModelTestProxy.cs">
77+
<Link>Core\ModelTestProxy.cs</Link>
78+
</Compile>
79+
<Compile Include="..\PureMVC\Tests\Core\ViewTest.cs">
80+
<Link>Core\ViewTest.cs</Link>
81+
</Compile>
82+
<Compile Include="..\PureMVC\Tests\Core\ViewTestMediator.cs">
83+
<Link>Core\ViewTestMediator.cs</Link>
84+
</Compile>
85+
<Compile Include="..\PureMVC\Tests\Core\ViewTestMediator2.cs">
86+
<Link>Core\ViewTestMediator2.cs</Link>
87+
</Compile>
88+
<Compile Include="..\PureMVC\Tests\Core\ViewTestMediator3.cs">
89+
<Link>Core\ViewTestMediator3.cs</Link>
90+
</Compile>
91+
<Compile Include="..\PureMVC\Tests\Core\ViewTestMediator4.cs">
92+
<Link>Core\ViewTestMediator4.cs</Link>
93+
</Compile>
94+
<Compile Include="..\PureMVC\Tests\Core\ViewTestMediator5.cs">
95+
<Link>Core\ViewTestMediator5.cs</Link>
96+
</Compile>
97+
<Compile Include="..\PureMVC\Tests\Core\ViewTestMediator6.cs">
98+
<Link>Core\ViewTestMediator6.cs</Link>
99+
</Compile>
100+
<Compile Include="..\PureMVC\Tests\Core\ViewTestNote.cs">
101+
<Link>Core\ViewTestNote.cs</Link>
102+
</Compile>
103+
<Compile Include="..\PureMVC\Tests\Patterns\Command\MacroCommandTest.cs">
104+
<Link>Patterns\Command\MacroCommandTest.cs</Link>
105+
</Compile>
106+
<Compile Include="..\PureMVC\Tests\Patterns\Command\MacroCommandTestCommand.cs">
107+
<Link>Patterns\Command\MacroCommandTestCommand.cs</Link>
108+
</Compile>
109+
<Compile Include="..\PureMVC\Tests\Patterns\Command\MacroCommandTestSub1Command.cs">
110+
<Link>Patterns\Command\MacroCommandTestSub1Command.cs</Link>
111+
</Compile>
112+
<Compile Include="..\PureMVC\Tests\Patterns\Command\MacroCommandTestSub2Command.cs">
113+
<Link>Patterns\Command\MacroCommandTestSub2Command.cs</Link>
114+
</Compile>
115+
<Compile Include="..\PureMVC\Tests\Patterns\Command\MacroCommandTestVO.cs">
116+
<Link>Patterns\Command\MacroCommandTestVO.cs</Link>
117+
</Compile>
118+
<Compile Include="..\PureMVC\Tests\Patterns\Command\SimpleCommandTest.cs">
119+
<Link>Patterns\Command\SimpleCommandTest.cs</Link>
120+
</Compile>
121+
<Compile Include="..\PureMVC\Tests\Patterns\Command\SimpleCommandTestCommand.cs">
122+
<Link>Patterns\Command\SimpleCommandTestCommand.cs</Link>
123+
</Compile>
124+
<Compile Include="..\PureMVC\Tests\Patterns\Command\SimpleCommandTestVO.cs">
125+
<Link>Patterns\Command\SimpleCommandTestVO.cs</Link>
126+
</Compile>
127+
<Compile Include="..\PureMVC\Tests\Patterns\Facade\FacadeTest.cs">
128+
<Link>Patterns\Facade\FacadeTest.cs</Link>
129+
</Compile>
130+
<Compile Include="..\PureMVC\Tests\Patterns\Facade\FacadeTestCommand.cs">
131+
<Link>Patterns\Facade\FacadeTestCommand.cs</Link>
132+
</Compile>
133+
<Compile Include="..\PureMVC\Tests\Patterns\Facade\FacadeTestVO.cs">
134+
<Link>Patterns\Facade\FacadeTestVO.cs</Link>
135+
</Compile>
136+
<Compile Include="..\PureMVC\Tests\Patterns\Mediator\MediatorTest.cs">
137+
<Link>Patterns\Mediator\MediatorTest.cs</Link>
138+
</Compile>
139+
<Compile Include="..\PureMVC\Tests\Patterns\Observer\NotificationTest.cs">
140+
<Link>Patterns\Observer\NotificationTest.cs</Link>
141+
</Compile>
142+
<Compile Include="..\PureMVC\Tests\Patterns\Observer\ObserverTest.cs">
143+
<Link>Patterns\Observer\ObserverTest.cs</Link>
144+
</Compile>
145+
<Compile Include="..\PureMVC\Tests\Patterns\Proxy\ProxyTest.cs">
146+
<Link>Patterns\Proxy\ProxyTest.cs</Link>
147+
</Compile>
148+
<Compile Include="..\PureMVC\Tests\Util\BaseTest.cs">
149+
<Link>Util\BaseTest.cs</Link>
150+
</Compile>
151+
<Compile Include="Properties\AssemblyInfo.cs" />
152+
</ItemGroup>
153+
<ItemGroup>
154+
<Content Include="AuthoringTests.txt" />
155+
</ItemGroup>
156+
<ItemGroup>
157+
<Shadow Include="Test References\PureMVC.DotNET.35.SmartPhone.accessor" />
158+
</ItemGroup>
159+
<ItemGroup>
160+
<ProjectReference Include="..\PureMVC.DotNET.VS2008.SmartPhone\PureMVC.DotNET.VS2008.SmartPhone.csproj">
161+
<Project>{DE630FA6-F998-4F91-B884-22D50562F956}</Project>
162+
<Name>PureMVC.DotNET.VS2008.SmartPhone</Name>
163+
</ProjectReference>
164+
</ItemGroup>
165+
<Import Project="$(MSBuildBinPath)\Microsoft.CompactFramework.CSharp.targets" />
166+
<PropertyGroup Condition="'$(BuildingInsideVisualStudio)'=='true' ">
167+
<DeviceTestAssemblySearchPath>$(DevEnvDir)PublicAssemblies</DeviceTestAssemblySearchPath>
168+
</PropertyGroup>
169+
<PropertyGroup>
170+
<AssemblySearchPaths>$(DeviceTestAssemblySearchPath);$(AssemblySearchPaths)</AssemblySearchPaths>
171+
</PropertyGroup>
172+
</Project>

‎PureMVC.DotNET.VS2008.SmartPhone.Tests/Test References/PureMVC.DotNET.35.SmartPhone.accessor

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
PureMVC.DotNET.35.SmartPhone.dll
2+
Device

‎PureMVC.DotNET.VS2008.SmartPhone.sln

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,34 @@
11

22
Microsoft Visual Studio Solution File, Format Version 10.00
33
# Visual Studio 2008
4+
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "PureMVC.DotNET.VS2008.SmartPhone", "PureMVC.DotNET.VS2008.SmartPhone\PureMVC.DotNET.VS2008.SmartPhone.csproj", "{DE630FA6-F998-4F91-B884-22D50562F956}"
5+
EndProject
6+
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "PureMVC.DotNET.VS2008.SmartPhone.Tests", "PureMVC.DotNET.VS2008.SmartPhone.Tests\PureMVC.DotNET.VS2008.SmartPhone.Tests.csproj", "{4C97BCC4-3357-476F-A98F-8A3D356BD24D}"
7+
EndProject
8+
Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Solution Items", "Solution Items", "{9270E851-DDF3-4229-A170-DC2C1148527B}"
9+
ProjectSection(SolutionItems) = preProject
10+
PureMVC.DotNET.VS2008.SmartPhone.vsmdi = PureMVC.DotNET.VS2008.SmartPhone.vsmdi
11+
SmartPhoneTestRun.testrunConfig = SmartPhoneTestRun.testrunConfig
12+
EndProjectSection
13+
EndProject
414
Global
15+
GlobalSection(TestCaseManagementSettings) = postSolution
16+
CategoryFile = PureMVC.DotNET.VS2008.SmartPhone.vsmdi
17+
EndGlobalSection
18+
GlobalSection(SolutionConfigurationPlatforms) = preSolution
19+
Debug|Any CPU = Debug|Any CPU
20+
Release|Any CPU = Release|Any CPU
21+
EndGlobalSection
22+
GlobalSection(ProjectConfigurationPlatforms) = postSolution
23+
{DE630FA6-F998-4F91-B884-22D50562F956}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
24+
{DE630FA6-F998-4F91-B884-22D50562F956}.Debug|Any CPU.Build.0 = Debug|Any CPU
25+
{DE630FA6-F998-4F91-B884-22D50562F956}.Release|Any CPU.ActiveCfg = Release|Any CPU
26+
{DE630FA6-F998-4F91-B884-22D50562F956}.Release|Any CPU.Build.0 = Release|Any CPU
27+
{4C97BCC4-3357-476F-A98F-8A3D356BD24D}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
28+
{4C97BCC4-3357-476F-A98F-8A3D356BD24D}.Debug|Any CPU.Build.0 = Debug|Any CPU
29+
{4C97BCC4-3357-476F-A98F-8A3D356BD24D}.Release|Any CPU.ActiveCfg = Release|Any CPU
30+
{4C97BCC4-3357-476F-A98F-8A3D356BD24D}.Release|Any CPU.Build.0 = Release|Any CPU
31+
EndGlobalSection
532
GlobalSection(SolutionProperties) = preSolution
633
HideSolutionNode = FALSE
734
EndGlobalSection

0 commit comments

Comments
 (0)