Connected Standby IO Stress

This test verifies that Connected Standby is functioning in the presence of IO events and that data corruptions do not occur across Connected Standby transitions.

Test details

Associated requirements

System.Fundamentals.StorageAndBoot.BootPerformance

See the system hardware requirements.

Platforms

Windows RT (ARM-based) Windows 8 (x86) Windows RT 8.1 Windows 8.1 x64 Windows 8.1 x86

Expected run time

~480 minutes

Categories

Certification Reliability

Type

Automated

Running the test

Before you run the test, complete the test setup as described in the test requirements: WDTF System Fundamentals Testing Prerequisites.

Before running the test, ensure that the system is able to enter and exit Connected Standby reliably. The test will stress its Connected Standby support. Also, ensure that there is greater than 2GB of free space on the boot volume to ensure that RapidFile is able to write to the disk.

Troubleshooting

For troubleshooting information, see Troubleshooting the Windows HCK Environment.

If the Check Configuration section fails, look at the log from the “Run ParseTrace.exe” task to determine why it failed. It may be caused by the system not entering in Connected Standby in response to the test issuing that command.

If the test fails on the Long Haul section then you can look into the last wtl logs generated by SCSI Compliance, RapidFile, and the Connected Standby script to determine what the cause of the error was.

More information

The test consists of three parts: setup, check configuration, and long haul.

The setup part copies the files to the system, exempts processes from the DAM, and enables test signing. Failures in this section are straightforward and the cause can be determined by viewing the error codes returned from the task.

The check configuration part runs Connected Standby, RapidFile, and SCSI Compliance tests in parallel for a few minutes while tracing the disk activity and the power states of the devices. This is to ensure that the devices are entering the proper power states in response to the test. Most commonly, a failure will be seen in the “Run ParseTrace.exe” task which evaluates the results from the ETW traces and determines if the devices entered the proper states. Viewing the task log for this task should reveal the cause of failure.

If the first two parts passed, the test enters into the long haul part where the same three files are run in parallel as in the check configuration part, but this time without the ETW tracing. The tasks run for 8 hours and passes as long as the system is able to continue running for that time and data integrity is maintained.

Command syntax

Command option Description

/Process

Process to run: ConnectedStandby, RapidFile, RapidFileVerify, or SCSICompliance.

/Duration

Duration to run the test (seconds).

/Device

Drive letter or physical drive number of device to test.

/Scenario

Scenario type to test: CheckConfiguration, Stress, LongHaul, or SelectiveSuspend.

Default value: LongHaul

Note

For command line help for this test binary, type /h.

Command usage

Command Description

cscript.exe ConnectedStandbyIOStress.wsf /Process:ConnectedStandby /Duration:[RunDurationSeconds] /Scenario:[Scenario]

Runs the Connected Standby test.

cscript.exe ConnectedStandbyIOStress.wsf /Process:RapidFile /Duration:[RunDurationSeconds] /Device:[StorageDriveLetter] /Scenario:[Scenario]

Runs the RapidFile test.

cscript.exe ConnectedStandbyIOStress.wsf /Process:SCSICompliance /Duration:[RunDurationSeconds] /Device:[StorageDriveNumber] /Scenario:[Scenario]

Runs the SCSI Compliance test.

Note

For command line help for this test binary, type /h.

File list

File Location

ntlog.dll

<osbinroot>\nttest\commontest\ntlog\

ntlogger.ini

<osbinroot>\nttest\commontest\ntlog\

Damx.exe

<testbinroot>\cstools\dam\

Stresslog.dll

<testbinroot>\nttest\basetest\core_file_services\shared_libs\

Fbslog.dll

<testbinroot>\nttest\basetest\core_file_services\shared_libs\fbslog\

Rapidfile.exe

<testbinroot>\nttest\basetest\core_file_services\shared_tests\wdk

ParseTrace.exe

<testbinroot>\nttest\driverstest\storage\sd\lowpower\

ConnectedStandbyIOStress.wsf

<testbinroot>\nttest\driverstest\storage\wdk\connectedstandy\

Wttlog_obj.js

<testbinroot>\nttest\driverstest\storage\wdk\

Scsicompliance.exe

<testbinroot>\nttest\driverstest\storage\wdk\

Send comments about this topic to Microsoft