Windows Embedded CE Stress Tool
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
The Windows Embedded CE Stress tool provides an environment where functional units of a Windows Embedded CE–based run-time image are exercised for an extended period of time. You can use the Windows Embedded CE Stress tool to verify that these functional units are stable after prolonged use. The Windows Embedded CE Stress tool can help you identify whether a functional unit leaks memory, crashes, hangs, or fails to function after extended continuous operation.
In addition, the Windows Embedded CE Stress tool verifies that functional units of a run-time image interact appropriately with one another in arbitrary combinations. It can also help you identify whether functional units deadlock, time out, or fail to operate when competing for resources.
The Windows Embedded CE Stress tool includes a client/server harness and a collection of test modules. The harness runs the test modules in random sequence in a loop for an arbitrary duration. For information about the harness, see Windows Embedded CE Stress Tool Harness.
The test modules perform functional testing. Each test module performs a number of tests on the functional part of the operating system (OS). The tests might include simple calls to an application programming interface (API) or might simulate a more complex scenario. You can add a test module to the Windows Embedded CE Stress tool. For information about developing a test module, see Custom Module Creation for the Windows Embedded CE Stress Tool.
In addition, Microsoft provides a set of test modules that exercise specific functional units of the OS such as the Graphics Device Interface (GDI) or Winsock. The modules that Microsoft provides broadly cover the OS but do not provide an exhaustive test of stability. The Windows Embedded CE Stress tool is most effective when you create test modules that target specific functional units and then run the test modules in combination with the test modules that Microsoft provides.
The following table shows the software requirements for the Windows Embedded CE Stress tool.
| Required software | Description |
|---|---|
sServer.exe |
The desktop computer part of the Windows Embedded CE Stress tool harness. You can use this application to set parameters for the test and collect results. |
sClient.exe |
The target device side of the Windows Embedded CE Stress tool harness. This application runs test modules and reports results. |
Regmod.xml |
Initialization file for the test harness. This file contains the attributes of the test modules. |
StressUtils.dll |
Module that exports utility functions that are called by the test modules. |
Stressmod.exe |
Container that manages command-line parsing, module duration, and results recoding and reporting for test modules. |
Test modules |
A collection of test modules to be run by the harness. |
Microsoft Internet Explorer 6.0 for Windows Embedded CE |
Internet browser. |
Toolhelp.dll |
Optional. Include this module in the CE 6.0 OS for the target device if you want to run the kernel debugger while running the Windows Embedded CE Stress tool. |
Note
When you run the Windows Embedded CE Stress tool, the Windows Embedded CE 6.0 Test Kit (CETK) temporarily copies files to the root directory of the target device. While the test runs, the test dynamically consumes program memory on the target device. Before running the test, verify that there is at least 3.0 megabytes (MB) of free storage memory on the target device. Verify that there is 0.5 MB of free program memory to run the harness. Verify that there is also enough free program memory on the target device to run the test modules. The test modules provided by Microsoft use as much as 10 MB of program memory on an average overnight run with four random concurrent test modules. These memory requirements are estimates. The amount of memory required on the target device depends largely on the behavior of the test modules that you choose to run.
In This Section
- Windows Embedded CE Stress Tool Harness
Describes the harness for the Windows Embedded CE Stress Tool.
- Running the Windows Embedded CE Stress Tool
Tells how to run the Windows Embedded CE Stress Tool.
- Options for the Windows Embedded CE Stress Tool
Lists the options available for the Windows Embedded CE Stress Tool.
- Interpretation of Windows Embedded CE Stress Tool Results
Describes how to interpret the results of the Windows Embedded CE Stress Tool.
- Logged Information for the Windows Embedded CE Stress Tool
Explains how to view results logs generated by the Windows Embedded CE Stress Tool.
- Creating and Modifying a Module Mix for the Windows Embedded CE Stress Tool
Tells how to create and modify modules and module mixes for the Windows Embedded CE Stress Tool.
- Test Modules for the Windows Embedded CE Stress Tool
Lists and describes the test modules provided with the Windows Embedded CE Stress Tool.
- Custom Module Creation for the Windows Embedded CE Stress Tool
Describes the creation of custom modules for the Windows Embedded CE Stress Tool.