Serial Port Driver Test Cases
The Serial Port Driver Test executes the tux –o –d serdrvbvt command line on default execution.
The following table shows the test cases for the Serial Port Driver Test.
| Test case | Description |
|---|---|
| 1001 | Configures the port and writes data to the port at all possible baud rates, data bits, parities, and stop bits. This test fails if it cannot send data on the port with a particular configuration. The output log shows details of a failure. |
| 1002 | Tests the SetCommEvent and GetCommEvent functions. This test fails if the driver does not properly support the SetCommEvent or GetCommEvent functions. The output log shows details of a failure. |
| 1003 | Tests the EscapeCommFunction function. This test fails if the driver does not support one of the Microsoft® Win32® EscapeCommFunction functions. The output log shows details of a failure. |
| 1004 | Tests the WaitCommEvent function on the EV_TXEMPTY event. The test creates a thread to send data and waits for the EV_TXEMPTY event to occur when the thread finishes sending data. This test fails if the WaitCommEvent function behaves improperly or if the EV_TXEMPTY event does not signal appropriately. The output log shows details of a failure. |
| 1005 | Tests the SetCommBreak and ClearCommBreak functions. This test fails if the driver does not properly support the SetCommBreak or ClearCommBreak functions. The output log shows details of a failure. |
| 1006 | Makes the WaitCommEvent function return a value when the handle for the current COM port is cleared. This test fails if the WaitCommEvent function behaves improperly. The output log shows details of a failure. |
| 1007 | Makes the WaitCommEvent function return a value when the handle for the current COM port is closed. This test fails if the WaitCommEvent function behaves improperly. The output log shows details of a failure. |
| 1008 | Tests the SetCommTimeouts function and verifies that the ReadFile function properly times out when no data is received. This test fails if the COM timeouts do not function correctly. The output log shows details of a failure. |
| 1009 | Verifies that previous Device Control Block (DCB) settings are preserved when the SetCommState function call fails with DCB settings that are not valid. This test fails if the serial port driver does not keep previous DCB settings when DCB settings that are not valid are passed to the driver. |
Remarks
This test library can have one or more optional command-line entries to change the behavior of the test. To specify one or more optional command-line entries to the test library, you must use the –c command-line option. This option forces Tux to pass the specified string into the test library.
See Also
Last updated on Friday, October 08, 2004
© 1992-2003 Microsoft Corporation. All rights reserved.