How to: Configure Network Emulation Using Test Settings

  • Article

You can configure the diagnostic data adapter to test your application under various network environments from Microsoft Test Manager and Microsoft Visual Studio 2010. It can also be configured to test an artificial network load, or bottleneck, when you run your tests.

Warning

If you run your tests on a real network that is a slower type than the network you are emulating, the test will still run at the slower network speed. The emulation can only slow down the network environment, not speed it up.

The following procedure describes how to configure network emulation from the configuration editor. These steps apply to both the configuration editor in Microsoft Test Manager and Microsoft Visual Studio 2010.

Note

This network emulation can be used with either manual or automated tests.

An account that has administrator privileges must be used for network emulation. If you have selected network emulation for a local role that runs manual tests, you must start Microsoft Test Manager by using administrator privileges. If you have selected network emulation for any other role, you must verify that the test agent on the machine for that role uses a user account that is a member of the administrators group. For more information about how to set up the account for your test agent, see Installing and Configuring Visual Studio Agents and Test and Build Controllers.

Note

The Network Service account, which is the default account for the test agent, is not a member of the administrators group.

The network setting offers the following network emulation types:

  • LAN (default)

  • 3G

  • Cable-DSL-1.5Mbps

  • Cable-DSL-768k

  • Cable/DSL-384k

  • CDMA

  • Dial-up 56k

  • Intercontinental slow WAN 300 Kbps

  • Intercontinental WAN 1.5 Mbps

  • Intracontinental WAN 1.5 Mbps

True Network Emulation

Microsoft Visual Studio 2010 uses software-based true network emulation for all test types. This includes load tests. True network emulation simulates network conditions by direct manipulation of the network packets. The true network emulator can emulate the behavior of both wired and wireless networks by using a reliable physical link, such as an Ethernet. The following network attributes are incorporated into true network emulation:

  • Round-trip time across the network (latency)

  • The amount of available bandwidth

  • Queuing behavior

  • Packet loss

  • Reordering of packets

  • Error propagations.

True network emulation also provides flexibility in filtering network packets based on IP addresses or protocols such as TCP, UDP, and ICMP.

True network emulation can be used by network-based developers and testers to emulate a desired test environment, assess performance, predict the effect of change, or make decisions about technology optimization. When compared to hardware test beds, true network emulation is a much cheaper and more flexible solution.

Configure Network Emulation for Your Test Settings

Before you perform the steps in this procedure, you must open your test settings from either Microsoft Test Manager or Microsoft Visual Studio 2010, and then select the Data and Diagnostics page.

To configure network emulation for your test settings

  1. Select the role to use to emulate a specific network.

    Note

    You have to configure the Network Emulation adapter only on either the client role or the server role. You do not have to use the adapter on both roles. The adapter emulates network noise that affects communication between both roles, so that you do not have to use it on both. Unless it is necessary, you should pick a client role for the Network Emulation adapter to avoid extra overhead on the server role.

  2. Select Network Emulation and then click Configure.

    The dialog box to configure network emulation is displayed.

  3. Click the arrow next to Select the network profile to use, and select the network type that you want to emulate when you run a test (for example, Cable-DSL 768Kps).

    Warning

    If you run your tests on a real network that is a slower type than the network that you are emulating, the test will still run at the slower network speed. The emulation can only slow down the network environment, not speed it up.

  4. If you include the network emulation diagnostic data adapter in the test settings and you intend to use it on your local machine, then you must also bind the network emulation driver to one of your machine’s network adapters. The network emulation driver is required for the network emulation diagnostic data adapter to function. The network emulation driver is installed and bound to your adapter in two ways:

    • Network emulation driver installed with Microsoft Visual Studio Test Agent 2010: The Microsoft Visual Studio Test Agent 2010 can be used on both remote machines and your local machine. When you install a Microsoft Visual Studio Test Agent, the installation process includes a configuration step that binds the network emulation driver to your network card. For more information, see Installing and Configuring Visual Studio Agents and Test and Build Controllers.

    • Network emulation driver installed with Microsoft Visual Studio Test Professional 2010: When you use network emulation for the first time, you are prompted to bind the network emulation driver to a network card.

    Tip

    You can also install the network emulation driver from the command line on your local machine without installing the Visual Studio test agent by using the following command: VSTestConfig NETWORKEMULATION /install

See Also

Tasks

Create Test Settings for Manual Tests

Create Test Settings for Automated Tests as Part of a Test Plan

Create Test Settings to Run Automated Tests from Visual Studio

Concepts

Setting Up Machines and Collecting Diagnostic Information Using Test Settings

Running Manual Tests Using Test Runner

Recording and Playing Back Manual Tests