|
|
Windows Embedded CE 6.0 Test Kit, windows ce嵌入式驱动测试工具里面的帮助文档，集合了CETK的测试方法和测试项，虽然是针对ce写的测试工具帮助文档，但是对许多嵌入式设备都是通用的，cetk test case里面针对各种外围设别和设别驱动的测试项作了比较完整的测试用例，针对目前手机黑盒测试有很大的帮助作用，虽然是英文的，但是用词还是比较简单的，仔细点看还是能看懂的。
截一断可以看看是不是要下载：）
蓝牙测试部分针对基本功能的测试项和test case
The following table shows the test cases for the Bluetooth Test.
Test Case Description
101Opens a Bluetooth socket and then closes the socket. This test case fails if a call to the socket or closesocket functions fails on the Bluetooth address family.
102Binds a Bluetooth socket to a valid address. This test case fails if the bind function call fails.
103Binds a Bluetooth socket to a valid address. The test case then attempts to bind the same socket to the same address to verify that a second attempt to bind fails. This test case fails if the second bind function call succeeds.
104Executes a call to the listen function with a backlog value set to 0. This test case fails if the listen function call fails.
105Executes a call to the listen function with a backlog value set to 1. This test case fails if the listen function call fails.
106Executes a call to the listen function with a backlog value set to 5. This test case fails if the listen function call fails.
107Executes a call to the listen function with a backlog value set to 8. This test case fails if the listen function call fails.
108Executes a call to the listen function with a backlog value set to SOMAXCONN. This test case fails if the listen function call fails.
109Executes a call to the listen function with a backlog value set to SOMAXCONN+1. This test case fails if the listen function call fails.
110Runs only on server tests
Creates a Bluetooth connection from the client to the server. This test case fails if the connection fails.
112Runs only on server tests
Creates a Bluetooth connection from the server to the client. This test case fails if the connection fails.
113Runs only on server tests
Creates a Bluetooth connection from the client to the server, terminates the connection, and then establishes a new connection to the same port on the server. This test case fails if one of the two connections fails.
114Runs only on server tests
Creates two Bluetooth connections on different ports simultaneously. This test case fails if the two connections cannot exist simultaneously.
115Runs only on server tests
Creates two Bluetooth connections from client to server simultaneously. The client closes the first connection immediately after the connection is established. The server then closes the second connection. This test fails if the two connections cannot be made or if they fail to close in the specified order.
116Runs only on server tests
Transfers 10 bytes of data from the client to the server by sending 1 byte of data at a time. This test case fails if the data transfer fails.
117Runs only on server tests
Transfers 100 bytes of data from the client to the server by sending 10 bytes of data at a time. This test case fails if the data transfer fails.
118Runs only on server tests
Transfers 1000 bytes of data from the client to the server by sending 100 bytes of data at a time. This test case fails if the data transfer fails.
119Runs only on server tests
Transfers 10000 bytes of data from the client to the server by sending 1000 bytes of data at a time. This test case fails if the data transfer fails.
124Runs only on server tests
Attempts to transfer 0 bytes of data from the client to the server. This test case fails if the data transfer fails.
125Runs only on server tests
Attempts to send and receive data simultaneously. This test case fails if the data transfer fails.
126Runs only on server tests
Creates a connection, transfers data, and then shuts down the connection with the value of the how parameter of the shutdown function set to SD_RECEIVE. The test case then attempts to receive data on the same socket. The recv function call is expected to fail. This test case fails if the recv function call succeeds.
127Runs only on server tests
Creates a connection, transfers data, and then shuts down the connection with the value of the how parameter of the shutdown function set to SD_SEND. The test case then attempts to send data on the same socket. The send function call is expected to fail. This test case fails if the send function call succeeds.
128Runs only on server tests
Creates a connection, transfers data, and then shuts down the connection with the value of the how parameter of the shutdown function set to SD_BOTH. The test case then attempts to send and receive on the same socket. The send and recv function calls are expected to fail. This test case fails if the send or recv calls succeed.
201Tests the socket function call with various legal and illegal parameters. This test case fails if the socket function call fails in the legal cases or succeeds in the illegal cases.
202Tests the WSASocket function call with various legal and illegal parameters. This test case fails if the WSASocket function call fails in legal cases or succeeds in illegal cases.
203Tests the bind function call with various legal and illegal parameters. This test case fails if the bind function call fails in legal cases or succeeds in illegal cases.
301Runs only on server tests
Creates a listen function call with the backlog value set to 0 and then connects. This test case fails if the listen function call fails or the connection fails.
302Runs only on server tests
Creates a listen function call with the backlog value set to SOMAXCONN and then connects. This test case fails if the listen function call fails or the connection fails.
303Runs only on server tests
Creates a listen function call with the backlog value set to 8 and then connects. This test case fails if the listen function call fails or the connection fails.
304Runs only on server tests
Creates a listen function call with the backlog value set to SOMAXCONN+1 and then connects. This test case fails if the listen function call fails or the connection fails.
305Runs only on server tests
Tests the getpeername function. This test case fails if the getpeername function call fails.
306Runs only on server tests
Tests the getsockname function. This test case fails if the getsockname function call fails.
309Tests the SO_ACCEPTCONN option of the getsockopt function on a listening socket. This test case fails if the getsockopt function call fails.
310Tests the SO_ACCEPTCONN option of the getsockopt function on a socket that is not listening. This test case fails if the getsockopt function call fails.
311Tests the SO_TYPE option of the getsockopt function. This test case fails if the getsockname function call fails.
312Runs only on server tests
Tests the SO_LINGER option of the getsockopt function. This test case fails if the getsockname function call fails.
313Runs only on server tests
Tests the SO_LINGER option of the setsockopt function. This test case fails if the setsockname function call fails.
402Attempts to enumerate any SD service record with L2CAP_PROTOCOL on the local device. This test case fails if no SD service record is found on the local device.
403Runs only on server tests
Attempts to enumerate any SD service record with L2CAP_PROTOCOL on the remote device. This test case fails if no SD service record is found on the remote device.
404Registers a new SD service record and then attempts to enumerate the server locally. This test case fails if a newly added SD service record is not found on the local device.
405Attempts to modify an existing SD service record. This test case fails if it is not possible to modify the existing SD service record.
406Attempts to delete an existing SD service record. This test case fails if it is not possible to delete the SD service record.
407Runs only on server tests
The server registers a new SD service record and the client queries the newly registered record. This test case fails if the client does not find an SD service record.
408Runs only on server tests
Tests the service attribute search. This test case fails if the service attribute search fails.
409Attempts to register a new service record with the SERVICE_MULTIPLE flag. The attempt to create a new service record is expected to fail. This test case fails if a new service record is created.
410Attempts to register an invalid SD service record. This test case fails if a new service record is created.
411Attempts to update an existing SD service record with an invalid one. This test case fails if the service record is updated.
412Attempts to delete an existing SD service record that does not exist. This test case fails if no error is returned.
413Attempts to delete an existing SD record two times. This test case fails if the first delete fails or the second delete succeeds.
414Attempts to look up an SD service record using the lpServiceClassId parameter instead of the lpBlob parameter. This test case fails if the attempt to look up the service record fails.
415Attempts to look up an SD service record on a device that does not exist. This test case fails if the attempt to look up the device succeeds.
当然，还有其他嵌入式系统中其他各个部分的测试方法和测试用例，横向参考，还是有一定借鉴价值的，所以，便宜啦，1RD币，大家不要鄙视我啊，因为我也老要下载，但是我很多时候都潜水呀~~还有我也是做测试的：）大家有兴趣的可以讨论讨论。
另外就是，这是CETK测试工具里面的帮助文档，大家可以自己去microsof或者msdn上找到的就不要下了喊亏本啊。。。。嘿嘿。
[em01][em01]
【文件名】:0721@52RD_wcetk(1).chm
【格 式】:chm
【大 小】:1320K
【简 介】:
【目 录】:
|
本帖子中包含更多资源
您需要 登录 才可以下载或查看，没有账号？注册
×
|
IP卡
狗仔卡
发表于 2007-2-1 23:53:21
提升卡
置顶卡
沉默卡
喧嚣卡
变色卡
显身卡