==========================================================================
Visual Studio Team System: Overview of Authoring and Running Tests
==========================================================================
This overview describes the features for authoring and running tests in
Visual Studio Team System and Visual Studio Team Edition for Software Testers.
Opening Tests
-------------
To open a test, open a test project or a test metadata file (a file with
extension .vsmdi) that contains the definition of the test. You can find
test projects and metadata files in Solution Explorer.
Viewing Tests
-------------
To see which tests are available to you, open the Test View window. Or,
if you have installed Team Edition for Software Testers, you can also open
the Test List Editor window to view tests.
To open the Test View window, click the Test menu, point to Windows, and
then click Test View. To open the Test List Editor window (if you have
installed Team Edition for Software Testers), click Test, point to Windows,
and then click Test List Editor.
Running Tests
-------------
You can run tests from the Test View window and the Test List Editor window.
See Viewing Tests to learn how to open these windows. To run one or more
tests displayed in the Test View window, first select the tests in that
window; to select multiple tests, hold either the Shift or CTRL key while
clicking tests. Then click the Run Tests button in the Test View window
toolbar.
If you have installed Visual Studio Team Edition for Software Testers, you can
also use the Test List Editor window to run tests. To run tests in Test List Editor,
select the check box next to each test that you want to run. Then click the
Run Tests button in the Test List Editor window toolbar.
Viewing Test Results
--------------------
When you run a test or a series of tests, the results of the test run will be
shown in the Test Results window. Each individual test in the run is shown on
a separate line so that you can see its status. The window contains an
embedded status bar in the top half of the window that provides you with
summary details of the complete test run.
To see more detailed results for a particular test result, double-click it in
the Test Results window. This opens a window that provides more information
about the particular test result, such as any specific error messages returned
by the test.
Changing the way that tests are run
-----------------------------------
Each time you run one or more tests, a collection of settings is used to
determine how those tests are run. These settings are contained in a “test
run configuration” file.
Here is a partial list of the changes you can make with a test run
configuration file:
- Change the naming scheme for each test run.
- Change the test controller that the tests are run on so that you can run
tests remotely.
- Gather code coverage data for the code being tested so that you can see
which lines of code are covered by your tests.
- Enable and disable test deployment.
- Specify additional files to deploy before tests are run.
- Select a different host, ASP.NET, for running ASP.NET unit tests.
- Select a different host, the smart device test host, for running smart device unit tests.
- Set various properties for the test agents that run your tests.
- Run custom scripts at the start and end of each test run so that you can
set up the test environment exactly as required each time tests are run.
- Set time limits for tests and test runs.
- Set the browser mix and the number of times to repeat Web tests in the
test run.
By default, a test run configuration file is created whenever you create a
new test project. You make changes to this file by double-clicking it in
Solution Explorer and then changing its settings. (Test run configuration
files have the extension .testrunconfig.)
A solution can contain multiple test run configuration files. Only one of
those files, known as the “Active” test run configuration file, is used to
determine the settings that are currently used for test runs. You select
the active test run configuration by clicking Select Active Test Run
Configuration on the Test menu.
-------------------------------------------------------------------------------
Test Types
----------
Using Visual Studio Team Edition for Software Testers, you can create a number
of different test types:
Unit test: Use a unit test to create a programmatic test in C++, Visual C# or
Visual Basic that exercises source code. A unit test calls the methods of a
class, passing suitable parameters, and verifies that the returned value is
what you expect.
There are three specialized variants of unit tests:
- Data-driven unit tests are created when you configure a unit test to be
called repeatedly for each row of a data source. The data from each row
is used by the unit test as input data.
- ASP.NET unit tests are unit tests that exercise code in an ASP.NET Web
application.
- Smart device unit tests are unit tests that are deployed to a smart device
or emulator and then executed by the smart device test host.
Web Test: Web tests consist of an ordered series of HTTP requests that you
record in a browser session using Microsoft Internet Explorer. You can have
the test report specific details about the pages or sites it requests, such
as whether a particular page contains a specified string.
Load Test: You use a load test to encapsulate non-manual tests, such as
unit, Web, and generic tests, and then run them simultaneously by using
virtual users. Running these tests under load generates test results,
including performance and other counters, in tables and in graphs.
Generic test: A generic test is an existing program wrapped to function as a
test in Visual Studio. The following are examples of tests or programs that
you can turn into generic tests:
- An existing test that uses process exit codes to communicate whether the
test passed or failed. 0 indicates passing and any other value indicates
a failure.
- A general program to obtain specific functionality during a test scenario.
- A test or program that uses a special XML file (called a “summary results
file”), to communicate detailed results.
Manual test: The manual test type is used when the test tasks are to be
completed by a test engineer as opposed to an automated script.
Ordered test: Use an ordered test to execute a set of tests in an order you
specify.
-------------------------------------------------------------------------------
没有合适的资源?快使用搜索试试~ 我知道了~
实现一个类来代表不限制精度的小数
共96个文件
pdb:33个
exe:18个
dll:16个
需积分: 10 4 下载量 78 浏览量
2009-01-03
17:49:05
上传
评论
收藏 243KB RAR 举报
温馨提示
实现一个类来代表不限制精度的小数。这个类使用一个字符串来构造,它的对象之间应该具有加和乘操作的能力。 比如 MyNumber num1 = "1.23456781111111111111111111111111"; MyNumber num2 = "222"; MyNumber num3 = num1 * num2 + num1; Console.WriteLine(MyNumber); 然后为这个类实现一些单元测试。
资源推荐
资源详情
资源评论
收起资源包目录
Exercise Training.rar (96个子文件)
Exercise Training
LocalTestRun.testrunconfig 335B
Exercise Training.suo 24KB
MyNumberTest
bin
Debug
MyNumberTest.dll 6KB
Exercise Training.pdb 20KB
MyNumberTest.pdb 16KB
Exercise Training.exe 8KB
obj
Debug
MyNumberTest.dll 6KB
ResolveAssemblyReference.cache 7KB
MyNumberTest.pdb 16KB
TempPE
MyNumberTest.csproj.FileListAbsolute.txt 801B
Properties
AssemblyInfo.cs 1KB
MyNumberTest.csproj 3KB
AuthoringTests.txt 7KB
MyNumberTest.cs 4KB
Exercise Training.sln 2KB
TestResults
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_28_13.trx 9KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_43_09.trx 7KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_29_46.trx 7KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_48_56.trx 7KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_22_10
Out
Exercise Training.pdb 20KB
MyNumberTest.pdb 14KB
mynumbertest.dll 5KB
Exercise Training.exe 8KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_12_52.trx 10KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_16_21
Out
Exercise Training.pdb 20KB
MyNumberTest.pdb 14KB
mynumbertest.dll 5KB
Exercise Training.exe 8KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_14_24.trx 10KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_29_35.trx 7KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_16_21.trx 10KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_27_53
Out
Exercise Training.pdb 20KB
MyNumberTest.pdb 14KB
mynumbertest.dll 5KB
Exercise Training.exe 8KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_48_02.trx 7KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_48_56
Out
Exercise Training.pdb 20KB
MyNumberTest.pdb 16KB
mynumbertest.dll 6KB
Exercise Training.exe 8KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_26_03.trx 10KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_23_00.trx 10KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_43_09
Out
Exercise Training.pdb 20KB
MyNumberTest.pdb 16KB
mynumbertest.dll 6KB
Exercise Training.exe 8KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_43_04.trx 7KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_14_24
Out
Exercise Training.pdb 20KB
MyNumberTest.pdb 14KB
mynumbertest.dll 5KB
Exercise Training.exe 8KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_12_52
Out
Exercise Training.pdb 20KB
MyNumberTest.pdb 14KB
mynumbertest.dll 5KB
Exercise Training.exe 8KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_22_10.trx 10KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_23_00
Out
Exercise Training.pdb 20KB
MyNumberTest.pdb 14KB
mynumbertest.dll 5KB
Exercise Training.exe 8KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_26_03
Out
Exercise Training.pdb 20KB
MyNumberTest.pdb 14KB
mynumbertest.dll 5KB
Exercise Training.exe 8KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_29_46
Out
Exercise Training.pdb 20KB
MyNumberTest.pdb 16KB
mynumbertest.dll 6KB
Exercise Training.exe 8KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_43_04
Out
Exercise Training.pdb 20KB
MyNumberTest.pdb 16KB
mynumbertest.dll 6KB
Exercise Training.exe 8KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_48_02
Out
Exercise Training.pdb 20KB
MyNumberTest.pdb 16KB
mynumbertest.dll 6KB
Exercise Training.exe 8KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_27_53.trx 9KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_29_35
Out
Exercise Training.pdb 20KB
MyNumberTest.pdb 16KB
mynumbertest.dll 6KB
Exercise Training.exe 8KB
i-huijux_WS-I-HUIJUX-01 2009-01-01 12_28_13
Out
Exercise Training.pdb 20KB
MyNumberTest.pdb 14KB
mynumbertest.dll 5KB
Exercise Training.exe 8KB
Exercise Training
bin
Debug
Exercise Training.vshost.exe.manifest 490B
Exercise Training.pdb 20KB
Exercise Training.vshost.exe 14KB
Exercise Training.exe 8KB
Exercise Training.csproj 2KB
obj
Debug
Exercise Training.pdb 20KB
TempPE
Exercise Training.exe 8KB
Exercise Training.csproj.FileListAbsolute.txt 614B
Properties
AssemblyInfo.cs 1KB
Exercise Training.cs 9KB
Exercise Training.vsmdi 499B
共 96 条
- 1
资源评论
Rosalindx
- 粉丝: 6
- 资源: 6
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- Python 程序语言设计模式思路-创建型模式:原型模式:通过复制现有对象来创建新对象,面向对象编程
- 卸载软件geek卸载软件geek
- Python 程序语言设计模式思路-创建型模式:单例模式,确保一个类的唯一实例(装饰器)面向对象编程、继承
- skywalking-plugins.jar skywalking-alarm.jar
- 独栋别墅图纸D020-两层-10.00&11.00米- 施工图.dwg
- Python 程序语言设计模式思路-创建型模式:工厂模式,创建对象的统一接口,封装对象的创建逻辑
- python自学教程-05-json数据格式的介绍.ev4.rar
- python自学教程-04-自定义JavaScript.ev4.rar
- 《淘宝后台系统...》
- skywalking-plugins.jar
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功