Common Scenario Stress with IO

  • Article

Note  This content applies to the Windows Logo Kit (WLK). For the latest information using the new Windows Hardware Certification Kit (HCK), see Windows HCK User's Guide on the Windows Hardware Dev Center.

Type: Automated Test

Overview

The Common Scenario Stress with IO job ensures that the device that you are testing accepts and correctly handles numerous Plug and Play (PnP) and power management state change scenarios, including disable/enable and suspend/hibernate/wake scenarios. Additionally, this job ensures that the device is still functional after these state changes through SimpleIO stress testing.

Details

The Common Scenario Stress with IO job is the "Driver Reliability" version of the Common_Scenario_Stress_with_IO automated scenario.

The job directs the underlying scenario to target the device that you are testing through its service name or device instance identifier (ID). Additionally, the underlying scenario can run only disable/enable scenarios on disableable devices. A disableable device is a device that has the Disable option available in Windows Device Manager and is not class "LegacyDriver". If the scenario is targeted at a non-disableable device, it will revert to just the power management scenarios.

If the driver is a UMDF driver, then AppVerifier will be enabled on the host process for the following checks:

  • Handles
  • Locks
  • Memory
  • Exceptions
  • TLS

UMDF Object tracking will be enabled for the UMDF driver. If there is a UMDF object leak, then a DriverStop will occur. You can use UMDF debugger extension !wudfext.dumpobjects <objecttrackeraddress> to analyze the problem.

For KMDF drivers, WDF Verifier will be enabled along with KMDF Enhanced Verifier and KMDF Handle Tracking for all objects.

Run Time: 3 hours

Log File:

System Restart Required: No

Test Category:

Supported operating systems for Logo or Signature testing:

  • Windows 7

  • Windows Server 2008 R2

  • Windows Vista

  • Windows Server 2003

  • Windows XP

Program:

Requirements

Software Requirements

The test tool requires the following software:

  • Supported operating system (see list above)

  • Software components included with the device that is being tested

Hardware Requirements

The test tool requires the following hardware:

  • Device to be tested

  • Computer that meets the minimum software requirements

  • Windows keyboard

  • Two-button pointing device

  • Color display monitor capable of at least 1024 by 768 resolution, 32-bits per pixel, 60 Hz

  • Hard drive with a minimum of 20 GB available on partition C:

Processor

The test tool runs on the following processor architectures:

  • x86

  • x64

  • Itanium

Running Common Scenario Stress with IO

Prerequisite Before you can run the Common Scenario Stress with IO job, you must install the device and driver on the test client computer. Next, install and configure Driver Test Manager (DTM).

To run Common Scenario Stress with IO, do the following:

  1. Open DTM Studio.

  2. Open or switch to the Device Console window, and then select the machine pool that contains the computer where you want to run the test.

  3. In the Available Devices pane, expand the type of device that is associated with your driver, and then select the specific device to run the test on.

  4. In the Available Jobs pane, click the Common Scenario Stress with IO job.

  5. Click Add Selected in the lower-left corner of the Device Console window to add the jobs to the schedule of jobs to be run.

  6. Click Schedule Jobs.

  7. Follow the progress of the Common Scenario Stress with IO job by using Job Monitor. Use the Result Explorer to examine the results of jobs that have completed. The test creates additional log files that contain detailed information about what the test is doing. You can use these log files to help you determine why a test failed.

Troubleshooting

The underlying scenario is based on the new Microsoft Windows Device Testing Framework (WDTF). The Windows Driver Kit (WDK) contains extensive documentation about using and extending this framework in your own driver development process. For more information, search the WDK documentation for "Windows Device Testing Framework". For details about the specific operation of this scenario, open the WDK documentation, expand Windows Driver Kit, expand Other Tools, expand Windows Device Testing Framework, and click Automated Scenarios.

You may receive an error message similar to the following: "SimpleIOStress Failed! -> IcmpSendEcho() had too many consecutive timeouts. Win32=1214 - The format of the specified network name is invalid." This failure can be caused by network latency, which can be improved by trying one or more of the following steps:

  • Disable DHCP and use static IP addressing.

  • Place a router or switch directly between the controller and client.

  • For redundant network paths, add an additional NIC connected to the network.

Some machines will go into standby mode at the end of the test on Windows XP. If this occurs, you must wake the machine manually to complete the test. This is acceptable for Logo submission. If automation is required, you can wake the system by calling PoSetSystemState(ES_USER_PRESENT) from kernel mode.

 

 

Build date: 9/14/2012