Skip to content

Commit 6281bad

Browse files
author
Andy Adamczak
committed
Tests are now running in 2008 on the Microsoft testing framework.
1 parent d89f9ac commit 6281bad

29 files changed

+1333
-488
lines changed

‎LocalTestRun.testrunconfig

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
<?xml version="1.0" encoding="UTF-8"?>
2+
<TestRunConfiguration name="Local Test Run" id="53d09980-bf26-41f8-9460-13336cc5522d" xmlns="http://microsoft.com/schemas/VisualStudio/TeamTest/2006">
3+
<Description>This is a default test run configuration for a local test run.</Description>
4+
<TestTypeSpecific />
5+
</TestRunConfiguration>

‎PureMVC.DotNET.2008.Tests.Old/PureMVC.DotNET.2008.Tests.Old.csproj

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,10 @@
1616
<SignAssembly>false</SignAssembly>
1717
<AssemblyOriginatorKeyFile>
1818
</AssemblyOriginatorKeyFile>
19+
<SccProjectName>Svn</SccProjectName>
20+
<SccLocalPath>Svn</SccLocalPath>
21+
<SccAuxPath>Svn</SccAuxPath>
22+
<SccProvider>SubversionScc</SccProvider>
1923
</PropertyGroup>
2024
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
2125
<DebugSymbols>true</DebugSymbols>

‎PureMVC.DotNET.2008.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.2008.Tests/Properties/AssemblyInfo.cs

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
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.2008.Tests")]
9+
[assembly: AssemblyDescription("")]
10+
[assembly: AssemblyConfiguration("")]
11+
[assembly: AssemblyCompany("")]
12+
[assembly: AssemblyProduct("PureMVC.DotNET.2008.Tests")]
13+
[assembly: AssemblyCopyright("Copyright © 2008")]
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("f79b85c0-9b33-49ee-adbf-7b71c3633280")]
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("3.0.0.0")]
35+
[assembly: AssemblyFileVersion("3.0.0.0")]

‎PureMVC.DotNET.2008.Tests/PureMVC.DotNET.2008.Tests.csproj

Lines changed: 150 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,150 @@
1+
<Project ToolsVersion="3.5" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
2+
<PropertyGroup>
3+
<Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
4+
<Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform>
5+
<ProductVersion>9.0.30729</ProductVersion>
6+
<SchemaVersion>2.0</SchemaVersion>
7+
<ProjectGuid>{0A42BFD1-6BA7-4219-A1A7-0643BF824F97}</ProjectGuid>
8+
<OutputType>Library</OutputType>
9+
<AppDesignerFolder>Properties</AppDesignerFolder>
10+
<RootNamespace>PureMVC.DotNET._2008.Tests</RootNamespace>
11+
<AssemblyName>PureMVC.DotNET.2008.Tests</AssemblyName>
12+
<TargetFrameworkVersion>v3.5</TargetFrameworkVersion>
13+
<FileAlignment>512</FileAlignment>
14+
<ProjectTypeGuids>{3AC096D0-A1C2-E12C-1390-A8335801FDAB};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids>
15+
</PropertyGroup>
16+
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
17+
<DebugSymbols>true</DebugSymbols>
18+
<DebugType>full</DebugType>
19+
<Optimize>false</Optimize>
20+
<OutputPath>bin\Debug\</OutputPath>
21+
<DefineConstants>DEBUG;TRACE</DefineConstants>
22+
<ErrorReport>prompt</ErrorReport>
23+
<WarningLevel>4</WarningLevel>
24+
</PropertyGroup>
25+
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
26+
<DebugType>pdbonly</DebugType>
27+
<Optimize>true</Optimize>
28+
<OutputPath>bin\Release\</OutputPath>
29+
<DefineConstants>TRACE</DefineConstants>
30+
<ErrorReport>prompt</ErrorReport>
31+
<WarningLevel>4</WarningLevel>
32+
</PropertyGroup>
33+
<ItemGroup>
34+
<Reference Include="Microsoft.VisualStudio.QualityTools.UnitTestFramework, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL" />
35+
<Reference Include="System" />
36+
<Reference Include="System.Core">
37+
<RequiredTargetFramework>3.5</RequiredTargetFramework>
38+
</Reference>
39+
</ItemGroup>
40+
<ItemGroup>
41+
<Compile Include="..\PureMVC\Tests\Core\ControllerTest.cs">
42+
<Link>Core\ControllerTest.cs</Link>
43+
</Compile>
44+
<Compile Include="..\PureMVC\Tests\Core\ControllerTestCommand.cs">
45+
<Link>Core\ControllerTestCommand.cs</Link>
46+
</Compile>
47+
<Compile Include="..\PureMVC\Tests\Core\ControllerTestCommand2.cs">
48+
<Link>Core\ControllerTestCommand2.cs</Link>
49+
</Compile>
50+
<Compile Include="..\PureMVC\Tests\Core\ControllerTestVO.cs">
51+
<Link>Core\ControllerTestVO.cs</Link>
52+
</Compile>
53+
<Compile Include="..\PureMVC\Tests\Core\ModelTest.cs">
54+
<Link>Core\ModelTest.cs</Link>
55+
</Compile>
56+
<Compile Include="..\PureMVC\Tests\Core\ModelTestProxy.cs">
57+
<Link>Core\ModelTestProxy.cs</Link>
58+
</Compile>
59+
<Compile Include="..\PureMVC\Tests\Core\ViewTest.cs">
60+
<Link>Core\ViewTest.cs</Link>
61+
</Compile>
62+
<Compile Include="..\PureMVC\Tests\Core\ViewTestMediator.cs">
63+
<Link>Core\ViewTestMediator.cs</Link>
64+
</Compile>
65+
<Compile Include="..\PureMVC\Tests\Core\ViewTestMediator2.cs">
66+
<Link>Core\ViewTestMediator2.cs</Link>
67+
</Compile>
68+
<Compile Include="..\PureMVC\Tests\Core\ViewTestMediator3.cs">
69+
<Link>Core\ViewTestMediator3.cs</Link>
70+
</Compile>
71+
<Compile Include="..\PureMVC\Tests\Core\ViewTestMediator4.cs">
72+
<Link>Core\ViewTestMediator4.cs</Link>
73+
</Compile>
74+
<Compile Include="..\PureMVC\Tests\Core\ViewTestMediator5.cs">
75+
<Link>Core\ViewTestMediator5.cs</Link>
76+
</Compile>
77+
<Compile Include="..\PureMVC\Tests\Core\ViewTestMediator6.cs">
78+
<Link>Core\ViewTestMediator6.cs</Link>
79+
</Compile>
80+
<Compile Include="..\PureMVC\Tests\Core\ViewTestNote.cs">
81+
<Link>Core\ViewTestNote.cs</Link>
82+
</Compile>
83+
<Compile Include="..\PureMVC\Tests\Patterns\Command\MacroCommandTest.cs">
84+
<Link>Patterns\Command\MacroCommandTest.cs</Link>
85+
</Compile>
86+
<Compile Include="..\PureMVC\Tests\Patterns\Command\MacroCommandTestCommand.cs">
87+
<Link>Patterns\Command\MacroCommandTestCommand.cs</Link>
88+
</Compile>
89+
<Compile Include="..\PureMVC\Tests\Patterns\Command\MacroCommandTestSub1Command.cs">
90+
<Link>Patterns\Command\MacroCommandTestSub1Command.cs</Link>
91+
</Compile>
92+
<Compile Include="..\PureMVC\Tests\Patterns\Command\MacroCommandTestSub2Command.cs">
93+
<Link>Patterns\Command\MacroCommandTestSub2Command.cs</Link>
94+
</Compile>
95+
<Compile Include="..\PureMVC\Tests\Patterns\Command\MacroCommandTestVO.cs">
96+
<Link>Patterns\Command\MacroCommandTestVO.cs</Link>
97+
</Compile>
98+
<Compile Include="..\PureMVC\Tests\Patterns\Command\SimpleCommandTest.cs">
99+
<Link>Patterns\Command\SimpleCommandTest.cs</Link>
100+
</Compile>
101+
<Compile Include="..\PureMVC\Tests\Patterns\Command\SimpleCommandTestCommand.cs">
102+
<Link>Patterns\Command\SimpleCommandTestCommand.cs</Link>
103+
</Compile>
104+
<Compile Include="..\PureMVC\Tests\Patterns\Command\SimpleCommandTestVO.cs">
105+
<Link>Patterns\Command\SimpleCommandTestVO.cs</Link>
106+
</Compile>
107+
<Compile Include="..\PureMVC\Tests\Patterns\Facade\FacadeTest.cs">
108+
<Link>Patterns\Facade\FacadeTest.cs</Link>
109+
</Compile>
110+
<Compile Include="..\PureMVC\Tests\Patterns\Facade\FacadeTestCommand.cs">
111+
<Link>Patterns\Facade\FacadeTestCommand.cs</Link>
112+
</Compile>
113+
<Compile Include="..\PureMVC\Tests\Patterns\Facade\FacadeTestVO.cs">
114+
<Link>Patterns\Facade\FacadeTestVO.cs</Link>
115+
</Compile>
116+
<Compile Include="..\PureMVC\Tests\Patterns\Mediator\MediatorTest.cs">
117+
<Link>Patterns\Mediator\MediatorTest.cs</Link>
118+
</Compile>
119+
<Compile Include="..\PureMVC\Tests\Patterns\Observer\NotificationTest.cs">
120+
<Link>Patterns\Observer\NotificationTest.cs</Link>
121+
</Compile>
122+
<Compile Include="..\PureMVC\Tests\Patterns\Observer\ObserverTest.cs">
123+
<Link>Patterns\Observer\ObserverTest.cs</Link>
124+
</Compile>
125+
<Compile Include="..\PureMVC\Tests\Patterns\Proxy\ProxyTest.cs">
126+
<Link>Patterns\Proxy\ProxyTest.cs</Link>
127+
</Compile>
128+
<Compile Include="..\PureMVC\Tests\Util\BaseTest.cs">
129+
<Link>Util\BaseTest.cs</Link>
130+
</Compile>
131+
<Compile Include="Properties\AssemblyInfo.cs" />
132+
</ItemGroup>
133+
<ItemGroup>
134+
<Content Include="AuthoringTests.txt" />
135+
</ItemGroup>
136+
<ItemGroup>
137+
<ProjectReference Include="..\PureMVC.DotNET.2008\PureMVC.DotNET.2008.csproj">
138+
<Project>{A1482CF1-5566-4636-8590-30ED9CF3D4D9}</Project>
139+
<Name>PureMVC.DotNET.2008</Name>
140+
</ProjectReference>
141+
</ItemGroup>
142+
<Import Project="$(MSBuildBinPath)\Microsoft.CSharp.targets" />
143+
<!-- To modify your build process, add your task inside one of the targets below and uncomment it.
144+
Other similar extension points exist, see Microsoft.Common.targets.
145+
<Target Name="BeforeBuild">
146+
</Target>
147+
<Target Name="AfterBuild">
148+
</Target>
149+
-->
150+
</Project>

0 commit comments

Comments
 (0)