Test incorrect inbound/outbound parameters -- failure due to the CETK's bug ?This is a discussion on Test incorrect inbound/outbound parameters -- failure due to the CETK's bug ? within the Software-Testing forums in Theory and Concepts category; Dear Sir/Madam, Recently, I'm doing the WinCE v6.0 CETK test on our new BSP for ARM9 processor, there is a OAL ioctl test item, iLtiming ioctl test, will fail due to the returned error code is wrong. however, I browsed the related information on internet and found someone in Microsoft said it's the bug of CETK test source code, so, the failure is correct, nevermind this problem, they will release the update in next release. My question is, when this update has been released ? or we just ignore this test case ? any response is very appreciated! the following ... | ||||||||
| | ||||||||
| ||||||||
| Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
|
#1
08-20-2008, 11:22 PM
| |||
| |||
 Test incorrect inbound/outbound parameters -- failure due to the CETK's bug ? Dear Sir/Madam, Recently, I'm doing the WinCE v6.0 CETK test on our new BSP for ARM9 processor, there is a OAL ioctl test item, iLtiming ioctl test, will fail due to the returned error code is wrong. however, I browsed the related information on internet and found someone in Microsoft said it's the bug of CETK test source code, so, the failure is correct, nevermind this problem, they will release the update in next release. My question is, when this update has been released ? or we just ignore this test case ? any response is very appreciated! the following is our CETK test log: <TESTCASE ID=1002> *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv vvvvvvvvvvvvvvvv *** TEST STARTING *** *** Test Name: Test incorrect inbound/outbound parameters *** Test ID: 1002 *** Library Path: oaltestiltiming.dll *** Command Line: *** Kernel Mode: Yes *** Random Seed: 10964 *** Thread Count: 0 *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv vvvvvvvvvvvvvvvv BEGIN TEST: "Test incorrect inbound/outbound parameters", Threads=0, Seed=10964 INFO: INFO: This test checks all the incorrect inbound/outbound parameters. INFO: All combinations of incorrect values are passed into the IOCTL INFO: function and the return values are verified. INFO: Any incorrect parameters should not crash the system. INFO: INFO: Calling the Ioctl with ILTIMING_MSG_ENABLE... INFO: The Ioctl is supported. INFO: INFO: Checking incorrect outbound parameters... INFO: INFO: The ILTIMING IOCTL does not use the outbound buffer. INFO: We will set the outbound parameters same as the inbound INFO: parameters and verify that this does not affect the Ioctl. INFO: INFO: Passing outbound parameters to IOCTL_HAL_ILTIMING did not INFO: have any effect on the KernelIoControl() call. INFO: INFO: Checking incorrect inbound parameters... INFO: INFO: Calling IOCTL_HAL_ILTIMING with invalid iltiming messages. INFO: INFO: Calling the ILTIMING Ioctl with incorrect inbound parameters. INFO: A total of 4 tests will be run on the Inbound parameters. INFO: INFO: This is test 1 INFO: Description: Inbound buffer is NULL and inbound buffer size is zero. INFO: Set up the inbound parameters... INFO: Call the IOCTL using KernelIoControl function now... INFO: Check the returned value... INFO: Check GetLastError... INFO: GetLastError is 6 ERROR: The error code returned is 6 while the expected value is 87. ERROR: The parameter checking test failed. INFO: INFO: This is test 2 INFO: Description: Inbound buffer is NULL and inbound buffer size is size of correct input. INFO: Set up the inbound parameters... INFO: Call the IOCTL using KernelIoControl function now... INFO: Check the returned value... INFO: Check GetLastError... INFO: GetLastError is 6 ERROR: The error code returned is 6 while the expected value is 87. ERROR: The parameter checking test failed. INFO: INFO: This is test 3 INFO: Description: Inbound buffer is correct but inbound buffer size is zero. INFO: Set up the inbound parameters... INFO: Call the IOCTL using KernelIoControl function now... INFO: Check the returned value... INFO: Check GetLastError... INFO: GetLastError is 6 ERROR: The error code returned is 6 while the expected value is 87. ERROR: The parameter checking test failed. INFO: INFO: This is test 4 INFO: Description: Inbound buffer is correct size minus one. INFO: Set up the inbound parameters... INFO: Call the IOCTL using KernelIoControl function now... INFO: Check the returned value... INFO: Check GetLastError... INFO: GetLastError is 6 ERROR: The error code returned is 6 while the expected value is 87. ERROR: The parameter checking test failed. ERROR: ERROR: The Ioctl did not handle incorrect inbound parameters correctly. INFO: END TEST: "Test incorrect inbound/outbound parameters", FAILED, Time=0.854 *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^ *** TEST COMPLETED *** *** Test Name: Test incorrect inbound/outbound parameters *** Test ID: 1002 *** Library Path: oaltestiltiming.dll *** Command Line: *** Kernel Mode: Yes *** Result: Failed *** Random Seed: 10964 *** Thread Count: 1 *** Execution Time: 0:00:00.854 *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^ </TESTCASE RESULT="FAILED"> -- Best Regards, -Zebra, MVP of Windows Embedded, Techware Technology Co., Ltd.  |
|
#2
08-22-2008, 08:21 AM
| |||
| |||
| Re: Test incorrect inbound/outbound parameters -- failure due to the CETK's bug ? I'm sorry that if there is someone does the same test and get the fail test result ? please help and thank you very much! -Zebra @ TECHWARE eMVP "Zebra" <zebra_chen@techware.com.tw> wrote in message news:ueFTp0zAJHA.908@TK2MSFTNGP03.phx.gbl... > Dear Sir/Madam, > > Recently, I'm doing the WinCE v6.0 CETK test on our new BSP for ARM9 > processor, there is a OAL ioctl test item, > iLtiming ioctl test, will fail due to the returned error code is wrong. > however, I browsed the related information on internet and found someone > in Microsoft said it's the bug of CETK test source code, so, the failure > is correct, nevermind this problem, they will release the update in next > release. > > My question is, when this update has been released ? or we just ignore > this test case ? any response is very appreciated! > > the following is our CETK test log: > > <TESTCASE ID=1002> > *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv vvvvvvvvvvvvvvvv > *** TEST STARTING > *** > *** Test Name: Test incorrect inbound/outbound parameters > *** Test ID: 1002 > *** Library Path: oaltestiltiming.dll > *** Command Line: > *** Kernel Mode: Yes > *** Random Seed: 10964 > *** Thread Count: 0 > *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv vvvvvvvvvvvvvvvv > BEGIN TEST: "Test incorrect inbound/outbound parameters", Threads=0, > Seed=10964 > INFO: > INFO: This test checks all the incorrect inbound/outbound parameters. > INFO: All combinations of incorrect values are passed into the IOCTL > INFO: function and the return values are verified. > INFO: Any incorrect parameters should not crash the system. > INFO: > INFO: Calling the Ioctl with ILTIMING_MSG_ENABLE... > INFO: The Ioctl is supported. > INFO: > INFO: Checking incorrect outbound parameters... > INFO: > INFO: The ILTIMING IOCTL does not use the outbound buffer. > INFO: We will set the outbound parameters same as the inbound > INFO: parameters and verify that this does not affect the Ioctl. > INFO: > INFO: Passing outbound parameters to IOCTL_HAL_ILTIMING did not > INFO: have any effect on the KernelIoControl() call. > INFO: > INFO: Checking incorrect inbound parameters... > INFO: > INFO: Calling IOCTL_HAL_ILTIMING with invalid iltiming messages. > INFO: > INFO: Calling the ILTIMING Ioctl with incorrect inbound parameters. > INFO: A total of 4 tests will be run on the Inbound parameters. > INFO: > INFO: This is test 1 > INFO: Description: Inbound buffer is NULL and inbound buffer size is > zero. > INFO: Set up the inbound parameters... > INFO: Call the IOCTL using KernelIoControl function now... > INFO: Check the returned value... > INFO: Check GetLastError... > INFO: GetLastError is 6 > ERROR: The error code returned is 6 while the expected value is 87. > ERROR: The parameter checking test failed. > INFO: > INFO: This is test 2 > INFO: Description: Inbound buffer is NULL and inbound buffer size is > size of correct input. > INFO: Set up the inbound parameters... > INFO: Call the IOCTL using KernelIoControl function now... > INFO: Check the returned value... > INFO: Check GetLastError... > INFO: GetLastError is 6 > ERROR: The error code returned is 6 while the expected value is 87. > ERROR: The parameter checking test failed. > INFO: > INFO: This is test 3 > INFO: Description: Inbound buffer is correct but inbound buffer size > is zero. > INFO: Set up the inbound parameters... > INFO: Call the IOCTL using KernelIoControl function now... > INFO: Check the returned value... > INFO: Check GetLastError... > INFO: GetLastError is 6 > ERROR: The error code returned is 6 while the expected value is 87. > ERROR: The parameter checking test failed. > INFO: > INFO: This is test 4 > INFO: Description: Inbound buffer is correct size minus one. > INFO: Set up the inbound parameters... > INFO: Call the IOCTL using KernelIoControl function now... > INFO: Check the returned value... > INFO: Check GetLastError... > INFO: GetLastError is 6 > ERROR: The error code returned is 6 while the expected value is 87. > ERROR: The parameter checking test failed. > ERROR: > ERROR: The Ioctl did not handle incorrect inbound parameters > correctly. > INFO: > END TEST: "Test incorrect inbound/outbound parameters", FAILED, > Time=0.854 > *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^ > *** TEST COMPLETED > *** > *** Test Name: Test incorrect inbound/outbound parameters > *** Test ID: 1002 > *** Library Path: oaltestiltiming.dll > *** Command Line: > *** Kernel Mode: Yes > *** Result: Failed > *** Random Seed: 10964 > *** Thread Count: 1 > *** Execution Time: 0:00:00.854 > *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^ > > </TESTCASE RESULT="FAILED"> > > -- > Best Regards, > -Zebra, > MVP of Windows Embedded, > Techware Technology Co., Ltd. > |
|
#3
09-12-2008, 08:33 PM
| |||
| |||
| Re: Test incorrect inbound/outbound parameters -- failure due to the CETK's bug ? Yes, you are correct. There was a bug in the test that was fixed later. The updated test was released with the "Windows Embedded CE 6.0 R2" version. Sorry about the inconvenience this has caused. -Deepika -- deepikas@online.microsoft.com (remove "online" from reply-to address) __________________________________________________ ___________ This posting is provided "AS IS" with no warranties, and confers no rights. "Zebra" <zebra_chen@techware.com.tw> wrote in message news:ueFTp0zAJHA.908@TK2MSFTNGP03.phx.gbl... > Dear Sir/Madam, > > Recently, I'm doing the WinCE v6.0 CETK test on our new BSP for ARM9 > processor, there is a OAL ioctl test item, > iLtiming ioctl test, will fail due to the returned error code is wrong. > however, I browsed the related information on internet and found someone > in Microsoft said it's the bug of CETK test source code, so, the failure > is correct, nevermind this problem, they will release the update in next > release. > > My question is, when this update has been released ? or we just ignore > this test case ? any response is very appreciated! > > the following is our CETK test log: > > <TESTCASE ID=1002> > *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv vvvvvvvvvvvvvvvv > *** TEST STARTING > *** > *** Test Name: Test incorrect inbound/outbound parameters > *** Test ID: 1002 > *** Library Path: oaltestiltiming.dll > *** Command Line: > *** Kernel Mode: Yes > *** Random Seed: 10964 > *** Thread Count: 0 > *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv vvvvvvvvvvvvvvvv > BEGIN TEST: "Test incorrect inbound/outbound parameters", Threads=0, > Seed=10964 > INFO: > INFO: This test checks all the incorrect inbound/outbound parameters. > INFO: All combinations of incorrect values are passed into the IOCTL > INFO: function and the return values are verified. > INFO: Any incorrect parameters should not crash the system. > INFO: > INFO: Calling the Ioctl with ILTIMING_MSG_ENABLE... > INFO: The Ioctl is supported. > INFO: > INFO: Checking incorrect outbound parameters... > INFO: > INFO: The ILTIMING IOCTL does not use the outbound buffer. > INFO: We will set the outbound parameters same as the inbound > INFO: parameters and verify that this does not affect the Ioctl. > INFO: > INFO: Passing outbound parameters to IOCTL_HAL_ILTIMING did not > INFO: have any effect on the KernelIoControl() call. > INFO: > INFO: Checking incorrect inbound parameters... > INFO: > INFO: Calling IOCTL_HAL_ILTIMING with invalid iltiming messages. > INFO: > INFO: Calling the ILTIMING Ioctl with incorrect inbound parameters. > INFO: A total of 4 tests will be run on the Inbound parameters. > INFO: > INFO: This is test 1 > INFO: Description: Inbound buffer is NULL and inbound buffer size is > zero. > INFO: Set up the inbound parameters... > INFO: Call the IOCTL using KernelIoControl function now... > INFO: Check the returned value... > INFO: Check GetLastError... > INFO: GetLastError is 6 > ERROR: The error code returned is 6 while the expected value is 87. > ERROR: The parameter checking test failed. > INFO: > INFO: This is test 2 > INFO: Description: Inbound buffer is NULL and inbound buffer size is > size of correct input. > INFO: Set up the inbound parameters... > INFO: Call the IOCTL using KernelIoControl function now... > INFO: Check the returned value... > INFO: Check GetLastError... > INFO: GetLastError is 6 > ERROR: The error code returned is 6 while the expected value is 87. > ERROR: The parameter checking test failed. > INFO: > INFO: This is test 3 > INFO: Description: Inbound buffer is correct but inbound buffer size > is zero. > INFO: Set up the inbound parameters... > INFO: Call the IOCTL using KernelIoControl function now... > INFO: Check the returned value... > INFO: Check GetLastError... > INFO: GetLastError is 6 > ERROR: The error code returned is 6 while the expected value is 87. > ERROR: The parameter checking test failed. > INFO: > INFO: This is test 4 > INFO: Description: Inbound buffer is correct size minus one. > INFO: Set up the inbound parameters... > INFO: Call the IOCTL using KernelIoControl function now... > INFO: Check the returned value... > INFO: Check GetLastError... > INFO: GetLastError is 6 > ERROR: The error code returned is 6 while the expected value is 87. > ERROR: The parameter checking test failed. > ERROR: > ERROR: The Ioctl did not handle incorrect inbound parameters > correctly. > INFO: > END TEST: "Test incorrect inbound/outbound parameters", FAILED, > Time=0.854 > *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^ > *** TEST COMPLETED > *** > *** Test Name: Test incorrect inbound/outbound parameters > *** Test ID: 1002 > *** Library Path: oaltestiltiming.dll > *** Command Line: > *** Kernel Mode: Yes > *** Result: Failed > *** Random Seed: 10964 > *** Thread Count: 1 > *** Execution Time: 0:00:00.854 > *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^ > > </TESTCASE RESULT="FAILED"> > > -- > Best Regards, > -Zebra, > MVP of Windows Embedded, > Techware Technology Co., Ltd. > |
|
#4
09-13-2008, 01:12 PM
| |||
| |||
| Re: Test incorrect inbound/outbound parameters -- failure due to the CETK's bug ? Thanks a lot for your kindly feedback. b.r. -Zebra, "Deepika Sripathi" <deepikas@online.microsoft.com> wrote in message news:OVh2nhTFJHA.3392@TK2MSFTNGP06.phx.gbl... > Yes, you are correct. There was a bug in the test that was fixed later. > The updated test was released with the "Windows Embedded CE 6.0 R2" > version. > > Sorry about the inconvenience this has caused. > > -Deepika > -- > deepikas@online.microsoft.com (remove "online" from reply-to address) > __________________________________________________ ___________ > This posting is provided "AS IS" with no warranties, and confers no > rights. > > > "Zebra" <zebra_chen@techware.com.tw> wrote in message > news:ueFTp0zAJHA.908@TK2MSFTNGP03.phx.gbl... >> Dear Sir/Madam, >> >> Recently, I'm doing the WinCE v6.0 CETK test on our new BSP for ARM9 >> processor, there is a OAL ioctl test item, >> iLtiming ioctl test, will fail due to the returned error code is wrong. >> however, I browsed the related information on internet and found someone >> in Microsoft said it's the bug of CETK test source code, so, the failure >> is correct, nevermind this problem, they will release the update in next >> release. >> >> My question is, when this update has been released ? or we just ignore >> this test case ? any response is very appreciated! >> >> the following is our CETK test log: >> >> <TESTCASE ID=1002> >> *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv vvvvvvvvvvvvvvvv >> *** TEST STARTING >> *** >> *** Test Name: Test incorrect inbound/outbound parameters >> *** Test ID: 1002 >> *** Library Path: oaltestiltiming.dll >> *** Command Line: >> *** Kernel Mode: Yes >> *** Random Seed: 10964 >> *** Thread Count: 0 >> *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv vvvvvvvvvvvvvvvv >> BEGIN TEST: "Test incorrect inbound/outbound parameters", Threads=0, >> Seed=10964 >> INFO: >> INFO: This test checks all the incorrect inbound/outbound >> parameters. >> INFO: All combinations of incorrect values are passed into the IOCTL >> INFO: function and the return values are verified. >> INFO: Any incorrect parameters should not crash the system. >> INFO: >> INFO: Calling the Ioctl with ILTIMING_MSG_ENABLE... >> INFO: The Ioctl is supported. >> INFO: >> INFO: Checking incorrect outbound parameters... >> INFO: >> INFO: The ILTIMING IOCTL does not use the outbound buffer. >> INFO: We will set the outbound parameters same as the inbound >> INFO: parameters and verify that this does not affect the Ioctl. >> INFO: >> INFO: Passing outbound parameters to IOCTL_HAL_ILTIMING did not >> INFO: have any effect on the KernelIoControl() call. >> INFO: >> INFO: Checking incorrect inbound parameters... >> INFO: >> INFO: Calling IOCTL_HAL_ILTIMING with invalid iltiming messages. >> INFO: >> INFO: Calling the ILTIMING Ioctl with incorrect inbound parameters. >> INFO: A total of 4 tests will be run on the Inbound parameters. >> INFO: >> INFO: This is test 1 >> INFO: Description: Inbound buffer is NULL and inbound buffer size is >> zero. >> INFO: Set up the inbound parameters... >> INFO: Call the IOCTL using KernelIoControl function now... >> INFO: Check the returned value... >> INFO: Check GetLastError... >> INFO: GetLastError is 6 >> ERROR: The error code returned is 6 while the expected value is 87. >> ERROR: The parameter checking test failed. >> INFO: >> INFO: This is test 2 >> INFO: Description: Inbound buffer is NULL and inbound buffer size is >> size of correct input. >> INFO: Set up the inbound parameters... >> INFO: Call the IOCTL using KernelIoControl function now... >> INFO: Check the returned value... >> INFO: Check GetLastError... >> INFO: GetLastError is 6 >> ERROR: The error code returned is 6 while the expected value is 87. >> ERROR: The parameter checking test failed. >> INFO: >> INFO: This is test 3 >> INFO: Description: Inbound buffer is correct but inbound buffer size >> is zero. >> INFO: Set up the inbound parameters... >> INFO: Call the IOCTL using KernelIoControl function now... >> INFO: Check the returned value... >> INFO: Check GetLastError... >> INFO: GetLastError is 6 >> ERROR: The error code returned is 6 while the expected value is 87. >> ERROR: The parameter checking test failed. >> INFO: >> INFO: This is test 4 >> INFO: Description: Inbound buffer is correct size minus one. >> INFO: Set up the inbound parameters... >> INFO: Call the IOCTL using KernelIoControl function now... >> INFO: Check the returned value... >> INFO: Check GetLastError... >> INFO: GetLastError is 6 >> ERROR: The error code returned is 6 while the expected value is 87. >> ERROR: The parameter checking test failed. >> ERROR: >> ERROR: The Ioctl did not handle incorrect inbound parameters >> correctly. >> INFO: >> END TEST: "Test incorrect inbound/outbound parameters", FAILED, >> Time=0.854 >> *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^ >> *** TEST COMPLETED >> *** >> *** Test Name: Test incorrect inbound/outbound parameters >> *** Test ID: 1002 >> *** Library Path: oaltestiltiming.dll >> *** Command Line: >> *** Kernel Mode: Yes >> *** Result: Failed >> *** Random Seed: 10964 >> *** Thread Count: 1 >> *** Execution Time: 0:00:00.854 >> *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^ >> >> </TESTCASE RESULT="FAILED"> >> >> -- >> Best Regards, >> -Zebra, >> MVP of Windows Embedded, >> Techware Technology Co., Ltd. >> > > |
 |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
All times are GMT -5. The time now is 06:34 AM.
