Visual Studio Team Edition for Software Testers
• Team Tester allows testers to create tests against the software within the same IDE used by the
developers.
- This allows QA to download and view all the projects checked into Team Foundation Source Control
by the developers.
- Testers can also retrieve the unit tests already created and checked in by the developers. These unit
tests can be added to ordered tests or regression tests.
- Testers can store their test project(s) in TFS and publish their results to their TFS database.
- Ultimately, bugs will be found by the QA and can be recorded and assigned as work items in TFS.
• In Team Tester, a solution can contain one or more test projects, with each containing one or more tests.
- Besides helping QA’s create, edit, manage and run tests, several types are exposed for custom test
development.
Adding a Test Project
• In Team Test edition, there are eight different types of tests that can be performed.
- Database Unit Test
- Generic Test
- Load Test
- Manual Test (text)
- Manual Test (Word)
- Ordered Test
- Unit Test
- Web Test
• In order to utilize any of the tests mentioned above, you need to add a Test Project to your current
solution.
- A test project is used as a container for one or more tests.
- Just right-click your current solution and add a new test project.
- For simplicity reasons, be sure to choose the same .NET language as your project(s), if possible.
• IMPORTANT: the language you choose defines the .NET language to be used by the tests you add!
- Don’t worry about not being able to choose a test type; that comes after you add the test project.
• As shown, a VB Test project has been added to a VB ASP.NET web application. Thus, there are now
two projects in the solution.
- The web application is called TeamTestWeb and the test project is called TeamTestWebTestProject.
• By default, when you add a new test project, it already includes a unit test and a manual (Word) test.
Bonus!
- Notice the MHTML file called ManualTest1.mht. It is used to outline the steps of a Manual test.
- Also, notice the unit testing file called UnitTest1.vb. This (obviously) can be used to unit test a .NET
project.
• Other important files …
- localtestrun.testrunconfig is an XML file configuration file that is used to configure the execution of the
tests.
• By double-clicking it, you can configure you test executions. More on this in a bit.
- TeamTestWeb.vsmdi is the Visual Studio Test Metadata file (an XML configuration file) for the Test
Manager, where its configuration settings are stored.
• AuthoringTests.txt, a simple text file, is a great overview of defining and running tests in Team
Test/Team Suite.
- If you get a chance to read it, however, you will soon realize it was written by someone who does not
write software documentation for a living.
Adding Tests
• You can add additional tests (either the same type or different) to the project by right-clicking the Test
project and choosing “Add - New Test…”
- Notice that each of the tests types provides a brief description.
- Also, notice that any additional unit tests added are created in the same .NET language (VB, in the
example above) as the test project!
• Each test type that can be added uses a unique file extension. Here are the default file names with a
description:
TEST TYPE DEFAULT NAME DESCRIPTION
Database Unit Test DatabaseUnitTest1.vb Available with Team DB Pro edition. Allows unit testing
of SPs, UDFs, triggers, etc.
Generic Test GenericTest1.GenericTest Wrap an existing test already created.
Load Test LoadTest1.loadtest Simulate a heavy number of requests from an application – often used
with web applications or web services.
Manual Test (text) ManualTest1.mtx Notepad is used to modify a text file that lists several manual
steps that must be performed by the tester.
Manual Test (Word) ManualTest2.mht Same as the test above, except uses Microsoft Word to
modify the document.
Ordered Test OrderedTest1.orderedtest Calls two or more tests in a specific order.
Unit Test UnitTest2.vb Adds a unit test to our test project. Why is the default name UnitTest2.vb?
Web Test WebTest1.webtest Tests the functionality of a web application or web service. When
used with a load test, can perform single, simulated and heavy web requests. Technically, these web
applications and services do not have to be written in .NET. Test your Java web apps!
- Unit testing was covered in the Team Developer chapter and database unit testing will be covered in the
Team DB Pro chapter.
- In the remaining sections of this chapter, the five other types of testing (web, load, generic, ordered and
manual) are examined.
Testing Windows - Test Manager and Test View
• The two primary windows in Visual Studio used for managing tests are Test Manager and Test View.
- To effectively work with these two windows, you must know how to work with their toolbars and
(right-click) context menus.
- Stating the obvious… these windows will not be available until you add a test project to your solution!
• Test Manager is exclusive to Team Tester (and Team Suite, of course).
- To open Test Manager in Team Tester, click: Test – Windows – Test Manager
• The Test Manager is viewed in the center code window.
- It offers a way to view, group, manage, debug and execute tests in the test project.
- Test Lists (test groups) are shown on the left side while all tests in the test project are shown on the
right.
• Test lists are a great to organize the tests, based on projects or test types.
- You can choose which columns you want viewed in the test list.
- This gives you different ways to sort the tests and set test properties in the Properties window.
- You can also import and export the Test Manager settings via its metadata (*.vsmdi) file.
• Test View is a lighter weight version of Test Manager and is available in both Team editions.
- To open Test View in Team Tester/Team Developer, click: Test – Windows - Test View
• It offers a simple user interface for starting, debugging and stopping one or more tests.
- The Test View window is “dock-able” and can be placed on any side of Visual Studio – left, right, top
or bottom.
- Like the Test Manager, columns can be selected for viewing and sorting the tests and test properties can
be changed.
- However, it doesn’t offer the ability to group tests into lists for easier test group execution; they have
to be manually selected.
- Team Developer uses the Test View window for unit testing exclusively.
• Other test windows include Test Results, Test Runs and Run Details.
- These windows can be opened manually from the Test dropdown menu. They also open automatically
during test runs.
- The next topic allows you to dive into the tests and get in greater detail of the windows you examined
here.
• Team Tester allows testers to create tests against the software within the same IDE used by the
developers.
- This allows QA to download and view all the projects checked into Team Foundation Source Control
by the developers.
- Testers can also retrieve the unit tests already created and checked in by the developers. These unit
tests can be added to ordered tests or regression tests.
- Testers can store their test project(s) in TFS and publish their results to their TFS database.
- Ultimately, bugs will be found by the QA and can be recorded and assigned as work items in TFS.
• In Team Tester, a solution can contain one or more test projects, with each containing one or more tests.
- Besides helping QA’s create, edit, manage and run tests, several types are exposed for custom test
development.
Adding a Test Project
• In Team Test edition, there are eight different types of tests that can be performed.
- Database Unit Test
- Generic Test
- Load Test
- Manual Test (text)
- Manual Test (Word)
- Ordered Test
- Unit Test
- Web Test
• In order to utilize any of the tests mentioned above, you need to add a Test Project to your current
solution.
- A test project is used as a container for one or more tests.
- Just right-click your current solution and add a new test project.
- For simplicity reasons, be sure to choose the same .NET language as your project(s), if possible.
• IMPORTANT: the language you choose defines the .NET language to be used by the tests you add!
- Don’t worry about not being able to choose a test type; that comes after you add the test project.
• As shown, a VB Test project has been added to a VB ASP.NET web application. Thus, there are now
two projects in the solution.
- The web application is called TeamTestWeb and the test project is called TeamTestWebTestProject.
• By default, when you add a new test project, it already includes a unit test and a manual (Word) test.
Bonus!
- Notice the MHTML file called ManualTest1.mht. It is used to outline the steps of a Manual test.
- Also, notice the unit testing file called UnitTest1.vb. This (obviously) can be used to unit test a .NET
project.
• Other important files …
- localtestrun.testrunconfig is an XML file configuration file that is used to configure the execution of the
tests.
• By double-clicking it, you can configure you test executions. More on this in a bit.
- TeamTestWeb.vsmdi is the Visual Studio Test Metadata file (an XML configuration file) for the Test
Manager, where its configuration settings are stored.
• AuthoringTests.txt, a simple text file, is a great overview of defining and running tests in Team
Test/Team Suite.
- If you get a chance to read it, however, you will soon realize it was written by someone who does not
write software documentation for a living.
Adding Tests
• You can add additional tests (either the same type or different) to the project by right-clicking the Test
project and choosing “Add - New Test…”
- Notice that each of the tests types provides a brief description.
- Also, notice that any additional unit tests added are created in the same .NET language (VB, in the
example above) as the test project!
• Each test type that can be added uses a unique file extension. Here are the default file names with a
description:
TEST TYPE DEFAULT NAME DESCRIPTION
Database Unit Test DatabaseUnitTest1.vb Available with Team DB Pro edition. Allows unit testing
of SPs, UDFs, triggers, etc.
Generic Test GenericTest1.GenericTest Wrap an existing test already created.
Load Test LoadTest1.loadtest Simulate a heavy number of requests from an application – often used
with web applications or web services.
Manual Test (text) ManualTest1.mtx Notepad is used to modify a text file that lists several manual
steps that must be performed by the tester.
Manual Test (Word) ManualTest2.mht Same as the test above, except uses Microsoft Word to
modify the document.
Ordered Test OrderedTest1.orderedtest Calls two or more tests in a specific order.
Unit Test UnitTest2.vb Adds a unit test to our test project. Why is the default name UnitTest2.vb?
Web Test WebTest1.webtest Tests the functionality of a web application or web service. When
used with a load test, can perform single, simulated and heavy web requests. Technically, these web
applications and services do not have to be written in .NET. Test your Java web apps!
- Unit testing was covered in the Team Developer chapter and database unit testing will be covered in the
Team DB Pro chapter.
- In the remaining sections of this chapter, the five other types of testing (web, load, generic, ordered and
manual) are examined.
Testing Windows - Test Manager and Test View
• The two primary windows in Visual Studio used for managing tests are Test Manager and Test View.
- To effectively work with these two windows, you must know how to work with their toolbars and
(right-click) context menus.
- Stating the obvious… these windows will not be available until you add a test project to your solution!
• Test Manager is exclusive to Team Tester (and Team Suite, of course).
- To open Test Manager in Team Tester, click: Test – Windows – Test Manager
• The Test Manager is viewed in the center code window.
- It offers a way to view, group, manage, debug and execute tests in the test project.
- Test Lists (test groups) are shown on the left side while all tests in the test project are shown on the
right.
• Test lists are a great to organize the tests, based on projects or test types.
- You can choose which columns you want viewed in the test list.
- This gives you different ways to sort the tests and set test properties in the Properties window.
- You can also import and export the Test Manager settings via its metadata (*.vsmdi) file.
• Test View is a lighter weight version of Test Manager and is available in both Team editions.
- To open Test View in Team Tester/Team Developer, click: Test – Windows - Test View
• It offers a simple user interface for starting, debugging and stopping one or more tests.
- The Test View window is “dock-able” and can be placed on any side of Visual Studio – left, right, top
or bottom.
- Like the Test Manager, columns can be selected for viewing and sorting the tests and test properties can
be changed.
- However, it doesn’t offer the ability to group tests into lists for easier test group execution; they have
to be manually selected.
- Team Developer uses the Test View window for unit testing exclusively.
• Other test windows include Test Results, Test Runs and Run Details.
- These windows can be opened manually from the Test dropdown menu. They also open automatically
during test runs.
- The next topic allows you to dive into the tests and get in greater detail of the windows you examined
here.
VSTS for Software Testers
Table of Contents
Copyright (c) 2008. Intertech, Inc. All Rights Reserved. This information is to be used exclusively as an
online learning aid. Any attempts to copy, reproduce, or use for training is strictly prohibited.
online learning aid. Any attempts to copy, reproduce, or use for training is strictly prohibited.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
Courseware
Training Resources
Tutorials