Socket Connection Test Module (Windows CE 5.0)
The socket connection test module, Wsx_conn.exe, uses multiple threads to create connections, exchange a small amount of data over them, and then tear down the connections. This test module exercises the Winsock layer, the underlying Winsock providers, and the networking stack. You can run this test module on both Internet Protocol version 6 (IPv6) and Internet Protocol version 4 (IPv4).
To maximize the thoroughness of the test module, you can set up the test module across a client and a server. The test module acts as the client, initiating all actions. The server acts only as an echo service, accepting data from the client and echoing back the data verbatim on the same connection. On the server, you can use Echosrv.exe from a command prompt to perform this action, by using a command such as echosrv -p12678.
The following table shows the command-line options for the Wsx_bind.exe test module.
| Command-line option | Description |
|---|---|
|
Time, in ms, to wait between binds. You can use this option to reduce the chance that multiple, concurrent bind tests interfere with one another. You can also use this option to prevent the test module from cycling through ports too quickly. |
|
Number of concurrent threads to use. |
|
Port with which to connect. |
The Wsx_conn.exe test module uses the server specified by the -server option for the Windows CE Stress tool harness as a remote echo server. In the command line for the harness, if you do not specify a value for the -server option, the default value of localhost instructs this test module to spin its own echo thread on the local device to use for communications. For more information, see Options for the Windows CE Stress Tool.
See Also
Test Modules for the Windows CE Stress Tool
Send Feedback on this topic to the authors