OAL KITL (Stress) Tests (Compact 2013)


The OAL KITL (Stress) Tests verify that the Kernel-Independent Transport Layer (KITL) functions correctly under stress.

Test Prerequisites

Your device must meet the following requirements before you run this test.

The following table describes the software requirements for the test:




Tux test harness, required to execute the test.


Kato logging engine, required for logging test data.


Library containing the OAL IOCTL Test files.


Support library for running the OAL test.

Note: To run test case 1000, you must have the debugger enabled in your image (IMGNODEBUGGER environment variable unset), or have started the debugger manually by executing the following at the Platform Builder Target Control Command Prompt: s loaddbg.


The table below lists the subtests included in this test.

SubTest ID



KITL Test Usage Message:

This test prints out the usage message for the OAL KITL Tests. It tells the user what the tests perform and specifies the input, if any, that the user must provide for the tests.


Stress KITL - LoadUnload DLL:

This test keeps loading and unloading a DLL for a specified time. By default, this test case runs for 10 minutes.

Note that this test case requires that the debugger be enabled.


Stress KITL - Dump Debug Output:

This test outputs debug output for the specified time. It generates lots of debug output. By default, this test case runs for 10 minutes.

Setting Up the Test

This test has no additional requirements, beyond the standard test environment setup.

Running the Test

The Stress KITL Test executes the following command line on default execution: tux.exe -o -d oalTestKitl.dll

This test has an optional command line parameter to change the behavior of the test. To specify this entry, you must use the -c command line option. This option causes Tux to pass the specified string into the test library (ex: s tux -o -d oalTestKitl -c "-runTimeS 30").

The following table shows the optional command line parameter for the Stress KITL Test.



runTimeS seconds

Specifies the length of time in seconds that the test cases run (default is 600s).

Verifying the Test

When the test completes running, verify that "PASS" appears in the test log for all subtests.

Troubleshooting the Test

* Check device output for error messages indicating potential setup issues.

* If test case 1000 is failing, ensure that the debugger is enabled in the image (or you can also start the debugger by executing "s loaddbg" from the Platform Builder Target Control window).

* If source code for the test is available, find the point of failure and attempt to determine the cause of the failure.

See Also

Other Resources

OAL - KITL, Memory, RTC Tests