CN103218280A - Hardware general testing method of USB (Universal Serial Bus) equipment - Google Patents
Hardware general testing method of USB (Universal Serial Bus) equipment Download PDFInfo
- Publication number
- CN103218280A CN103218280A CN2013101285047A CN201310128504A CN103218280A CN 103218280 A CN103218280 A CN 103218280A CN 2013101285047 A CN2013101285047 A CN 2013101285047A CN 201310128504 A CN201310128504 A CN 201310128504A CN 103218280 A CN103218280 A CN 103218280A
- Authority
- CN
- China
- Prior art keywords
- execution
- test
- configuration file
- item
- tested
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 236
- 238000000034 method Methods 0.000 claims description 29
- 238000004891 communication Methods 0.000 claims description 14
- 238000011084 recovery Methods 0.000 claims description 11
- 238000009434 installation Methods 0.000 claims description 7
- 238000012956 testing procedure Methods 0.000 claims description 7
- 238000010224 classification analysis Methods 0.000 claims description 6
- 230000005611 electricity Effects 0.000 claims description 6
- 230000002618 waking effect Effects 0.000 claims description 3
- 238000012217 deletion Methods 0.000 claims description 2
- 230000037430 deletion Effects 0.000 claims description 2
- 238000007689 inspection Methods 0.000 claims description 2
- 238000004088 simulation Methods 0.000 claims description 2
- GNFTZDOKVXKIBK-UHFFFAOYSA-N 3-(2-methoxyethoxy)benzohydrazide Chemical compound COCCOC1=CC=CC(C(=O)NN)=C1 GNFTZDOKVXKIBK-UHFFFAOYSA-N 0.000 claims 2
- FGUUSXIOTUKUDN-IBGZPJMESA-N C1(=CC=CC=C1)N1C2=C(NC([C@H](C1)NC=1OC(=NN=1)C1=CC=CC=C1)=O)C=CC=C2 Chemical compound C1(=CC=CC=C1)N1C2=C(NC([C@H](C1)NC=1OC(=NN=1)C1=CC=CC=C1)=O)C=CC=C2 FGUUSXIOTUKUDN-IBGZPJMESA-N 0.000 claims 2
- 238000010998 test method Methods 0.000 claims 1
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 6
- 230000002950 deficient Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 230000000694 effects Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 239000000725 suspension Substances 0.000 description 2
- 101100225042 Arabidopsis thaliana ECI3 gene Proteins 0.000 description 1
- 101100274486 Mus musculus Cited2 gene Proteins 0.000 description 1
- 101100533725 Mus musculus Smr3a gene Proteins 0.000 description 1
- 101150096622 Smr2 gene Proteins 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000007730 finishing process Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 238000012797 qualification Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Abstract
The invention discloses a hardware general testing method of USB (Universal Serial Bus) equipment and relates to the field of hardware testing. The hardware general testing method comprises the steps of 1) reading a testing state item in a configuration file, judging operation which is needed to be executed, executing a step 2 if the operation is restoration of an operating system, and executing a step 3 if the operation is testing; 2) restoring the operating system according to operating system directing item in the configuration file, updating the testing state item in the configuration file, restarting the operating system and executing the step 1; and 3) enumerating USB equipment which is connected to a testing platform, testing equipment to be tested in the current operating system environment according to a generated list of the equipment to be tested, judging whether the current operating system is the last operating system in the configuration file, if so, ending the testing, and if not, updating the testing state item and the operating system directing item in the configuration file and returning to the step 1. The hardware general testing method of the USB equipment has the beneficial effects that the manpower in testing resources is saved, different PC (Personal Computer) system platforms can be covered and the firmware/hardware level compatibility problem can be found in time.
Description
Technical field
The invention belongs to field of hardware, particularly a kind of hardware universal testing method of USB device.
Background technology
Because the chipset of various computing machine uses different USB controllers, so difference can appear in the mode of visit USB device, be that compatibility exists defective, on these different chipsets, use whether have hidden danger or defective so need to check USB device, at present, above-mentioned inspection adopts the mode of manual test to carry out.
The applicant finds that in finishing process of the present invention there is following defective at least in prior art:
1, test process is more loaded down with trivial details, needs more manpower and other resource to support;
What 2, test was covered is limited in scope, and can omit some environment;
3, use manual test can cause the wearing and tearing of USB device interface bigger, and have the problem that causes owing to artificial error.
Summary of the invention
The objective of the invention is to propose a kind of hardware universal testing method of USB device in order to overcome the defective of prior art.
The invention provides a kind of hardware universal testing method of USB device, described method is automatically performed according to configuration file by test platform, specifically comprises:
Steps A, read the test mode item in the described configuration file, judge the operation that needs are carried out according to described test mode item, if the execution in step B then of recovery operation system, if test then execution in step F, if other then finish;
Step B, the operating system that reads in the described configuration file is pointed to item, point to item according to described operating system and search current operation system in the described configuration file, and read the status items corresponding with current operation system, judging whether to treat testing apparatus according to described status items tests under the current operation system environment, be execution in step C then, otherwise judge that whether current operation system is last operating system in the described configuration file, if last operating system in the described configuration file then finishes, point to item if then do not upgrade described operating system, continue execution in step B for last operating system in the described configuration file;
Step C, read backup file name item corresponding and backup file place path entry with current operation system, generate first autoexec according to described backup file name item and backup file place path entry, obtain the title and the patch title of the current operating system of described test platform, and according to corresponding operating system in the title of the current operating system of described test platform and the described configuration file of patch name lookup, read the Globally Unique Identifier item of corresponding operating system, generate second autoexec according to described Globally Unique Identifier item, carry out acquiescence that described second autoexec is provided with system and start the acquiescence startup delay time that starts and system is set for WinPE;
Test mode item in step D, the described configuration file of renewal, sign needs the test that is operating as of execution, and restarting operating systems returns execution in step A;
Step F, the USB device that connects on the described test platform is enumerated, generated list of devices to be tested, treat testing apparatus according to described list of devices to be tested and under the current operation system environment, test;
Step G, the operating system that reads in the described configuration file are pointed to item and operating system quantity item, judge that whether current operation system is last operating system in the described configuration file, be then to finish, otherwise upgrade the test mode item in the described configuration file, sign needs the recovery operation system that is operating as of execution, the operating system of upgrading in the described configuration file is pointed to item, returns execution in step A.
Further, the described operation of carrying out according to described test mode item judgement needs also comprises: drive then execution in step E if install;
Step e, read the driver name item in the described configuration file, generate the 3rd autoexec or script file according to described driver name item, carry out described the 3rd autoexec or script file and come install driver, upgrade the test mode item in the described configuration file, sign needs the test that is operating as of execution, restarting operating systems returns execution in step A;
Correspondingly, also comprise between described step C and the described step D:
Step 1., read the installation sign in the described configuration file, judge whether according to described installation sign that needs are installed and drive, be then execution in step 3., otherwise execution in step is 2.;
Step 2., read the device type item in the described configuration file, judge according to the value of described device type item whether equipment to be tested is USB chip intelligent card equipment, be then execution in step 3., otherwise execution in step D;
Step 3., judge whether according to the OS name item of the current operation system in the described configuration file that needs are installed and drive, be then execution in step 4., otherwise execution in step D;
Step 4., upgrade the test mode item in the described configuration file, sign needs to carry out is operating as to install and drives, restarting operating systems returns execution in step A.
The beneficial effect of the inventive method is: save the manpower in the test resource, can cover different PC system platforms, can find the compatibility issue of firmware/hardware level, can control the execution frequency in the test process, minimizing is got rid of the problem that causes owing to artificial error to the wearing and tearing of USB device interface.
Description of drawings
For the clearer explanation embodiment of the invention or technical scheme of the prior art, to do simple the introduction to the accompanying drawing of required use in embodiment or the description of the Prior Art below, apparently, accompanying drawing in describing below only is some embodiments of the present invention, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain other accompanying drawing according to these accompanying drawings.
The hardware universal testing method process flow diagram of a kind of USB device that Fig. 1 provides for the embodiment of the invention one;
Fig. 2 is the refinement process flow diagram of step 111 among Fig. 1;
Fig. 3 is the refinement process flow diagram of step s1 among Fig. 2;
Fig. 4 is the refinement process flow diagram of step s4 among Fig. 2;
Fig. 5 is the refinement process flow diagram of step G4-8 among Fig. 4;
The journal file that generates in a kind of test process that Fig. 6 provides for the embodiment of the invention two carries out the method flow diagram that classification analysis obtains test result file.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the invention, the technical scheme in the embodiment of the invention is clearly and completely described, obviously, described embodiment only is the present invention's part embodiment, rather than whole embodiment.Based on the embodiment among the present invention, those of ordinary skills belong to the scope of protection of the invention not making the every other embodiment that is obtained under the creative work prerequisite.
Embodiment one
The embodiment of the invention one provides a kind of hardware universal testing method of USB device, and described method is automatically performed according to configuration file by test platform;
Particularly, described configuration file comprises the test mode item, the driver name item, operating system quantity item, operating system is pointed to the specifying information item of item and each operating system, wherein, the specifying information item of described each operating system comprises the backup file name item of operating system, the name item of operating system, the patch name item of operating system, the WinPE(Windows Preinstall Environment of operating system correspondence, the Windows WindowsPE) GUID(Globally Unique Identifier, Globally Unique Identifier) the value item, the backup file place path entry of the status items of operating system and operating system;
Described WinPE is the software that is used to carry out system recovery and backup, it is the Windows subsystem that has the limit service, based on Windows XP Professional kernel and Vista kernel, comprise that operation Windows setup and script, connection network are shared, robotization basic process and carry out the required minimum function of hardware verification with protected mode operation;
Referring to Fig. 1, described method specifically may further comprise the steps:
Step 101: read the test mode item in the configuration file, judge the operation that needs are carried out according to described test mode item, if recovery operation system execution in step 102 then drives then execution in step 108 if install, if test then execution in step 111, otherwise finish;
Preferably, in the present embodiment, described configuration file is as follows:
;test?state,1:configer,2:Auto?Install,3:test
STATE=3
;Device?Driver?name
SDKNAME=ep2011auto.exe
;the?system?total
OSNUM=3
;the?current?system?id
CURROSID=0
BAKNAME0=WinXPProSP3.GHO
OSNAME0=Windows?XP?Professional
PATCH0=Service?Pack3
GUID0={7619dcc9-fafe-11d9-b411-000476eba25f}
FLAG0=0
DEV0=E:
BAKNAME1=Windows7ult.GHO
OSNAME1=Windows7?Ultimate
PATCH1=NULL
GUID1={7619dcc9-fafe-11d9-b411-000476eba25f}
FLAG1=0
DEV1=E:
BAKNAME2=Windows7ultsp1.GHO
OSNAME2=Windows7?Ultimate
PATCH2=Service?Pack1
GUID2={7619dcc9-fafe-11d9-b411-000476eba25f}
FLAG2=0
DEV2=E:
Wherein, the STATE item is the test mode item, and the STATE=1 sign needs the recovery operation system that is operating as of execution, and STATE=2 identifies being operating as of need carrying out driving is installed, and STATE=3 identifies the test that is operating as that need carry out; The SDKNAME item is the driver name item, the title of sign driver; The OSNUM item is an operating system quantity item, the number of operating system in the sign configuration file; The CURROSID item is that operating system is pointed to item, the numbering of the current operation system in the sign configuration file; BAKNAME, OSNAME, PATCH, GUID, FLAG and DEV item are the specifying information item of each operating system, wherein the BAKNAME item is the backup file name item, the backup file title of sign operating system, the OSNAME item is the name item of operating system, the title of sign operating system, the PATCH item is the patch name item of operating system, the title of the patch of sign operating system, the GUID item is the GUID value item of the WinPE of operating system correspondence, the GUID value of the WinPE of sign operating system correspondence, the FLAG item is the status items of operating system, FLAG=0 identifies this operating system needs test, FLAG=1 identifies this operating system and tests, FLAG=2 identifies this operating system and has finished test, FLAG=3 identifies this operating system does not need test, the DEV item is the backup file place path entry of operating system, the path at the backup file place of sign operating system; Attribute every of operating system has a numbering in the sign configuration file, and described numbering is consistent with the numbering of operating system, and convenient value when the CURROSID item finds the every of the attribute that identifies this operating system when equaling the numbering of this operating system;
Correspondingly, according to above-mentioned configuration file example, step 101 is specially: read STATE item in the configuration file, judge the value of described STATE item, if 1 execution in step 102, if 2 execution in step 108, if the 3rd execution in step 111, otherwise finish;
Step 102: the operating system that reads in the configuration file is pointed to item, points to item according to described operating system and searches current operation system;
According to above-mentioned configuration file example, step 102 is specially: read the CURROSID item in the configuration file, search configuration file according to the value of described CURROSID item and obtain current operation system in the configuration file;
Step 103: reading the status items of current operation system correspondence, judge whether to treat testing apparatus according to described status items and test under the current operation system environment, is execution in step 105 then, otherwise execution in step 104;
According to above-mentioned configuration file example, step 103 is specially: reading the FLAG item of current operation system in the configuration file, judge whether the value of described FLAG item is 0, is execution in step 105 then, otherwise execution in step 104;
Step 104: judging that whether current operation system in the configuration file is last operating system in the configuration file, is then to finish, and points to otherwise upgrade described operating system, makes it to point to next operating system in the configuration file, returns execution in step 102;
According to above-mentioned configuration file example, step 104 is specially: the value of revising the CURROSID item in the configuration file adds 1 for its currency, returns execution in step 102;
Step 105: read the backup file name item and the backup file place path entry of current operation system correspondence in the configuration file, generate first autoexec according to the path entry at described backup file name item and backup file place;
According to above-mentioned configuration file example, step 105 is specially: read the value of BAKNAME item of current operation system in the configuration file and the value of DEV item, generate first autoexec according to the value of described BAKNAME item and the value of DEV item, be provided with and return to WinPE next time, enter the current operation system in the configuration file after system restarts automatically;
For example, the value of the BAKNAME item of the current operation system in the described configuration file is WinXPProSP3.GHO, the value of DEV item is E:, first autoexec that generates is e: ghost32.exe-clone, mode=pload, src=E: WinXPProSP3.GHO:1, dst=1:1/sure/rb;
Step 106: obtain current OS name of test platform and patch title, according to corresponding operating system in current OS name of described test platform and the patch name lookup configuration file and read the GUID item of its corresponding WinPE, generate second autoexec and carry out according to described GUID item;
Particularly, describedly obtain the current OS name of test platform and the patch title can realize by the following method: open registration table HLM SOFTWARE Microsoft Windows NT CurrentVersion, the value of obtaining ProductName obtains OS name, the value of obtaining CSDVersion obtains the title of the patch of operating system, closes described registration table;
According to above-mentioned configuration file example, describedly be specially according to corresponding operating system in current OS name of described test platform and the patch name lookup configuration file and the GUID item that reads its corresponding WinPE: the value of obtaining the value of OSNAME item in the configuration file and PATCH item respectively with the GUID item of the title and the patch title identical operations system of test platform current operation system;
For example, the name of test platform current operation system is called Windows 7 Ultimate, the patch name is called Service Pack 1, in the configuration file value of the value of OSNAME item and PATCH item with the value of the GUID item of the title of test platform current operation system and patch title identical operations system be respectively 7619dcc9-fafe-11d9-b411-000476eba25f} generates second autoexec that comprises following two instructions and is:
d:\system32\bcdedit?/store?c:\boot\bcd?/default?{7619dcc9-fafe-11d9-b411-000476eba25f}
d:\system32\bcdedit?/store?c:\boot\bcd?/timeout?5；
Wherein the effect of article one instruction is that the acquiescence of system starts item and is set to WinPE and starts, and the effect of second instruction is that the acquiescence of system starts delay time and is set to 5 seconds;
BCDEdit is a command execution instrument in the NT60 series operating system (Windows 7/Vista/2008/8/2012), is used for setting up and reconfiguring boot loader.So-called boot loader, at the one section small routine that refers to before the kernel operation, carry out, system comes initiating hardware equipment, sets up the mapping graph of memory headroom etc. by it, the hardware environment of system is arranged to a proper state, for final call operation system kernel is ready to correct environment;
Step 107: the test mode item in the new configuration file more, sign need to carry out is operating as to install and drives, and restarting operating systems returns execution in step 101;
According to above-mentioned configuration file example, step 107 is specially: the value of revising the STATE item in the configuration file is second preset value, and restarting operating systems returns execution in step 101;
Further, can comprise before the step 107:
Step a, reading the installation sign in the described configuration file, judge whether according to described installation sign that needs are installed and drive, is execution in step 107 then, otherwise execution in step b;
Step b, reading the device type item in the described configuration file, judge according to the value of described device type item whether equipment to be tested is USB chip intelligent card equipment, is execution in step c then, otherwise execution in step d;
Step c, judging whether according to the OS name item of the current operation system in the described configuration file that needs are installed and drive, is execution in step 107 then, otherwise execution in step d;
Test mode item in steps d, the described configuration file of renewal, sign needs the test that is operating as of execution, and restarting operating systems returns execution in step 101;
Particularly, comprise behind the restarting operating systems in step 107 and the steps d: enter WinPE after the time delay that test platform is provided with in second autoexec, automatically perform described first autoexec, executing the described first autoexec back operation system resets automatically, treat to enter after operating system starts once more described first and handle the fixed operating system of document, i.e. current operation system in the configuration file;
In step 107 and the steps d after the restarting operating systems, can comprise before the execution in step 101: whether successfully judge the recovery operation system operation, be execution in step 101 then, otherwise carry out abnormality processing;
Step 108: read the driver name item in the configuration file, generate the 3rd autoexec/script file and execution according to described driver name item;
According to above-mentioned configuration file example, step 108 is specially: read SDKNAME item in the configuration file, generate batch the 3rd processing file/script file, carry out described the 3rd autoexec/script file;
For example, the value of described SDKNAME item is ep2011auto .exe, generates the 3rd autoexec:
start?/wait?E:\FeiTianAutoTestOut\eP2Kauto.exe?/S
Perhaps generate the vbs script file:
Set.WshShell=CreateObject
("Wscript.Shell")
strCommandLine?=?"eP2011Auto.exe"
WshShell.Run(strCommandLine)
WScript.Sleep?3000
WshShell.SendKeys?"{ENTER}"
WScript.Sleep?3000
Step 109: upgrade the status items of current operation system, the sign current operation system is tested;
According to above-mentioned configuration file example, step 109 is specially: the value of revising the FLAG item of current operation system in the configuration file is 1, and sign is being treated testing apparatus and tested under the current operation system environment;
Step 110: the test mode item in the new configuration file more, sign need the test that is operating as carried out, and restarting operating systems returns execution in step 101;
According to above-mentioned configuration file example, step 110 is specially: the value of revising STATE item in the configuration file is the 3rd preset value, and restarting operating systems returns execution in step 101;
Step 111: the USB device that connects on the test platform is enumerated, generated list of devices to be tested, each equipment to be tested is tested under the current operation system environment according to described list of devices to be tested;
When test imperfect tense comprises: carry out aborted and handle; Wherein, described test is not finished and is meant in whole testing process, and test is not complete according to the process that pre-sets, but has ended for a certain reason halfway, perhaps can't continue to carry out;
When test is finished, comprise: if test result for test by execution in step 112 then or USB controller title, CPU title and the mainboard title obtaining the IP of test platform and obtain test platform, logging software test environment and testing procedure, generate journal file, execution in step 112; If test result is USB controller title, CPU title and the mainboard title by then finishing or obtaining the IP of test platform and obtain test platform not, information such as logging software test environment, testing procedure and error description, generate journal file, execution in step 112; Wherein, the described IP that obtains test platform is to use the api interface of Windows Sock2 to realize, specifically comprises: to the initialization of Winsock service, obtain the local host title, obtain the address information of main frame and the character string that an IP is converted to an internet standard point cellular; The described USB controller title of obtaining test platform, CPU title and mainboard title adopt the WMI com component to carry out, specifically comprise: initialization WMI com component, creating a WMI NameSpace connects, use m_pWbemloc to be connected to " root cimv2 " and the pointer of m_pWbemSvc is set, the security that WMI connects is set, use the value of the Caption of Win32_USBController to obtain USB controller title, use the value of the Name of Win32_Processor to obtain the CPU title, use the Manufacturer value of Win32_BaseBoard to obtain the mainboard title, discharge the WIM com component;
Preferably, referring to Fig. 2, step 111 comprises:
S0, distribution and initialization apparatus array;
S1, enumerate USB HCD(Host Controller Driver, master controller), obtain the Root Hub(Root Hub of number He each the USB HCD correspondence of USB HCD) title, the title of the Root Hub that gets access to is deposited in the described equipment array, it is 0 that first index value is set;
S2, judge that first index value whether less than the number of described USB HCD, is then to carry out s4, otherwise carry out s3;
S3, each equipment to be tested is tested execution in step 112 according to described list of devices to be tested under the current operation system environment;
Particularly, comprise in the described list of devices to be tested: the PID(Product Identity of equipment to be tested, product coding), VID(Vendor Identity, the operator code coding), handle and connected mode, if the connected mode of equipment to be tested is not for there being utility appliance, then described equipment to be tested is carried out first test operation and second test operation, if the connected mode of equipment to be tested is then carried out first test operation to described equipment to be tested for connecting by Hub1.1/Hub 2.0/ Hub 3.0; Wherein, described first test operation comprises:
1. treat testing apparatus and carry out PNP(Plug-and-Play, plug and play) identification and communication test;
Preferably, in the present embodiment, treating testing apparatus carries out PNP identification and be specially: the api interface that the call operation system provides sends to equipment to be tested and obtains PID and VID order, judge whether to receive PID and the VID that equipment to be tested returns, be that equipment then to be tested can be discerned, otherwise generate corresponding journal file, wherein said journal file can comprise: command name, error code, current operation system title and USB controller title etc.;
Treat testing apparatus communicate the test be specially: the api interface that the call operation system provides is to transmission read write command to be tested, judge whether to receive the response that data that read command that equipment to be tested returns reads or write order run succeeded, be that devices communicating then to be tested is normal, otherwise generate corresponding journal file misregistration log information, wherein said error log information can comprise: command name, error code, current that OS name and USB controller title etc.;
2. treat and carry out PNP identification and communication test again after operation is forbidden/enabled to testing apparatus;
Preferably, described electricity is forbidden/enabled to tested USB device is the power management instrument that provides by operating system, forms corresponding script data or autoexec, carries out described script data or autoexec; The api function that also can calling system provides carries out;
3. treat and carry out PNP identification and communication test again after testing apparatus is descended the electricity/operation that powers on;
Preferably, in the present embodiment, the described testing apparatus for the treatment of descends the electricity/operation that powers on to be specially: by the power management instrument that operating system provides, form corresponding script data or autoexec, carry out described script data or autoexec; The api function that also can calling system provides carries out.
4. treating testing apparatus carries out continuously carrying out PNP identification and communication test again after default the electric down/operation that powers on;
Wherein, described default time is 50 times;
Preferably, in the present embodiment, the described testing apparatus for the treatment of descends the electricity/operation that powers on to be specially: by the power management instrument that operating system provides, form corresponding script data or autoexec, carry out described script data or autoexec; The api function that also can calling system provides carries out.
5. treat and carry out PNP identification and communication test again after testing apparatus is preset time reset operation;
Preferably, describedly tested USB device is preset time reset operation be specially: the api interface that the call operation system provides sends the RESET order to equipment to be tested;
Wherein, described default time is 150 times;
6. simulate the power source change of notebook and treat testing apparatus and carry out PNP identification and communication test;
Preferably, the power source change of described simulation notebook is specially: to operating system broadcasting power management message;
Described power management message as:
Msg1:?PBT_APMQUERYSUSPEND
The?PBT_APMQUERYSUSPEND?event?is?broadcast?to?request?permission?to?suspend?the?computer.
An?application?that?grants?permission?should?carry?out?preparations?for?the?suspension?before?returning.Msg2:?PBT_APMRESUMECRITICAL
The?PBT_APMRESUMECRITICAL?event?is?broadcast?as?a?notification?that?the?system?has?resumed?operation.
This?event?can?indicate?that?some?or?all?applications?did?not?receive?a?PBT_APMSUSPEND?event.
For?example,?this?event?can?be?broadcast?after?a?critical?suspension?caused?by?a?failing?battery.
Msg3:PBT_APMRESUMEAUTOMATIC
The?PBT_APMRESUMEAUTOMATIC?event?is?broadcast?when?the?computer?wakes?up?automatically?to?handle?an?event.
An?application?will?not?generally?respond?unless?it?is?handling?the?event,?because?the?user?is?not?present.Msg4:?PBT_APMSUSPEND
The?PBT_APMSUSPEND?event?is?broadcast?immediately?before?the?computer?enters?a?suspended?state.
This?event?is?typically?broadcast?when?all?applications?and?installable?drivers?have?returned?TRUE
to?a?previous?PBT_APMQUERYSUSPEND?event.Msg5:PBT_APMPOWERSTATUSCHANGE
The?PBT_APMPOWERSTATUSCHANGE?event?is?broadcast?when?a?change?in?the?power?status?of
the?computer?is?detected,?such?as?a?switch?from?battery?power?to?A/C.
The?system?also?broadcasts?this?event?when?remaining?battery?power?slips
below?the?threshold?specified?by?the?user?or?if?the?battery?power?changes?by?a?specified?percentage.
Described second test operation is specially: treat testing apparatus and carry out carrying out PNP identification and communication test again after the sleeping/waking operation;
Preferably, in the present embodiment, the described testing apparatus for the treatment of is carried out sleeping/waking operation and is specially to operating system and sends the SLEEP order, specifically can realize by the api interface that the call operation system provides, perhaps by calling the instrument realization of test platform itself;
Need to prove that described first test operation and second test operation can be carried out or carry out simultaneously by predefined procedure, each operation in described first test operation also can be carried out or carry out simultaneously by predefined procedure, does not do qualification at this;
S4, enumerate the Root Hub that specifies USB HCD correspondence, obtain the information of the equipment to be tested of connection current Root Hub on, store in the list of devices to be tested according to first index value;
Particularly, the information of described equipment to be tested comprises equipment to be tested: PID, VID, handle and connected mode;
S5, renewal first index value return execution in step s2;
Particularly, upgrade first index value and add 1 for its currency;
Further, referring to Fig. 3, step s1 specifically comprises:
Step G2-1: distribute and the initialization apparatus array, second index value and maximal value are set;
In the present embodiment, it is 0 that second index value is set, and it is 16 that maximal value is set;
Step G2-2: whether judging second index value less than maximal value, is execution in step G2-3 then, otherwise execution in step s2;
Step G2-3: the device name that makes up USB HCD according to second index value, use the mode of attempting opening to enumerate, judge and attempt opening whether the handle that returns is invalid value, be execution in step s2 then, otherwise obtain the title of the Root Hub of current USB HCD correspondence, the title of the Root Hub that gets access to is deposited in the described equipment array, close the USB HCD equipment of opening, execution in step G2-4;
Particularly, the title shape of the USB HCD of structure such as. HCD1;
Step G2-4: upgrade second index value, return execution in step G2-2;
Particularly, upgrade second index value and add 1 for its currency;
Referring to Fig. 4, step s4 specifically comprises:
Step G4-1: construct the device name of current Root Hub, open current Root Hub equipment, obtain the link information of current each node of Root Hub;
Particularly, construct device name shape such as the. Root Hub title of current Root Hub;
Step G4-2: judging on current each node of Root Hub whether be connected with USB device, is execution in step G4-3 then, otherwise execution in step s5;
Step G4-3: obtain the number of the node that is connected with USB device, it is 0 that the 3rd index value is set;
Step G4-4: judging the 3rd index value whether less than the number of the node of the described USB device that is connected with, is execution in step G4-5 then, otherwise execution in step s5;
Step G4-5: inquire about the specified node of current Root Hub according to the 3rd index value, obtain PID and VID, handle and the connected mode of the USB device that connects on the described specified node;
Step G4-6: the type of judging the USB device that is connected on the described specified node according to PID that gets access to and VID, if equipment to be tested is execution in step G4-7 then, if Hub1.1/ Hub2.0/ Hub3.0 is execution in step G4-8 then, if other execution in step G4-9 then;
Step G4-7: PID and VID, handle and the connected mode of described equipment to be tested are saved in the list of devices to be tested execution in step G4-9;
Step G4-8: enumerate described Hub1.1/ Hub2.0/ Hub3.0, obtain PID and VID, handle and the connected mode of the USB device that connects on the described Hub1.1/ Hub2.0/ Hub3.0, judge according to PID that gets access to and VID whether each USB device is equipment to be tested, be then to preserve its PID and VID, handle and connected mode in list of devices to be tested, execution in step G4-9, otherwise execution in step G4-9;
Step G4-9: upgrade the 3rd index value, return execution in step G4-4;
Particularly, upgrade the 3rd index value and add 1 for its currency;
Further, referring to Fig. 5, step G4-8 specifically comprises:
I constructs the device name of described Hub1.1/Hub2.0/Hub3.0, opens described Hub1.1/Hub2.0/Hub3.0 equipment, obtains the link information of described each node of Hub1.1/Hub2.0/Hub3.0;
Particularly, construct the device name shape of described Hub1.1/Hub2.0/Hub3.0 such as the device name of. Root Hub Ming Cheng Hub;
Ii judges on each node of described Hub1.1/Hub2.0/Hub3.0 whether be connected with USB device, is then to carry out iii, otherwise execution in step G4-9;
Iii obtains the number of the node that is connected with USB device, and it is 0 that the 4th index value is set;
Iv judges that the 4th index value whether less than the described node number that is connected with USB device, is then to carry out v, otherwise execution in step G4-9;
In the present embodiment, the initial value of the 4th index value is 0;
V inquires about the specified node of described Hub1.1/ Hub2.0/ Hub3.0 according to the 4th index value, obtains PID and VID, handle and the connected mode of the USB device that connects on the described specified node;
Vi judges with VID whether the USB device that is connected on the described specified node is equipment to be tested according to getting access to PID, is then to carry out vii, otherwise carries out viii;
Vii in list of devices to be tested, carries out viii with the PID of described equipment to be tested and VID, handle and connected mode;
Viii closes the Hub1.1/Hub2.0/Hub3.0 equipment of opening, and upgrades the 4th index value, returns and carries out iv;
Particularly, upgrade the 4th index value and add 1 for its currency;
Step 112: the operating system that reads in the configuration file is pointed to item and operating system quantity item, judge according to described operating system sensing item and operating system quantity item whether current operation system is last operating system in the configuration file, be then to finish, otherwise execution in step 113;
Example according to above-mentioned configuration file, step 112 is specially: read CURROSID item and OSNUM item in the configuration file, whether the value of judging described CURROSID item is identical with the value of described OSNUM item, be that then the current operation system in the configuration file is last operating system in the configuration file, otherwise the current operation system in the configuration file is not last operating system in the configuration file;
Further, current operation system also comprises when being last operating system in the described configuration file: the STATE item of revising in the configuration file is the 4th preset value, and the journal file that generates in the test process is carried out classification analysis, obtains test result file;
For example, the journal file that generates in the test process is as follows, describedly the journal file that generates in the test process is carried out the method that classification analysis obtains test result file will set forth in embodiment two:
Journal file one:
Directly insert the mainboard USB interface, after using 0 end points to send to obtain the order of descriptor, do not have data among the Cdrom that scsi device ejects
STE: Windows 7 Ultimate, Service Pack 1
Windows?XP?Professional?Service?Pack?1
Hardware environment: IP:192.168.0.106, USB controller title: Intel (R) 82801G (ICH7 Family) USB Universal Host Controller-27CB, CPU title: Intel (R) Core (TM) 2 Quad CPU Q9500 2.83GHz, mainboard title: LENOVO ThinkCentre M6100T
Testing procedure: directly insert the mainboard USB interface, use 0 end points to send the order of obtaining descriptor
Error description: directly insert the mainboard USB interface, after using 0 end points to send to obtain the order of descriptor, do not have data among the Cdrom that scsi device ejects
Journal file two:
Directly insert the mainboard USB interface, after using 0 end points to send to obtain the order of descriptor, Get the crypt prov handle failed, internal error has appearred in err code:0x80090020.
STE: Windows 7 Ultimate, Service Pack 1
Windows?XP?Professional?Service?Pack?1
Hardware environment: IP:192.168.0.106, USB controller title: Intel (R) 82801G (ICH7 Family) USB Universal Host Controller-27CB, CPU title: Intel (R) Core (TM) 2 Quad CPU Q9500 2.83GHz, mainboard title: LENOVO ThinkCentre M6100T
Testing procedure: directly insert the mainboard USB interface, use 0 end points to send the order of obtaining descriptor
Error description: directly insert the mainboard USB interface, after using 0 end points to send to obtain the order of descriptor, Get the crypt prov handle failed, internal error has appearred in err code:0x80090020.
Journal file three:
Insert 1.5M USB extended line, after using 0 end points to send to obtain the order of descriptor, Get the crypt prov handle failed, internal error has appearred in err code:0x80090020.
STE: Windows 7 Ultimate, Service Pack 1
Windows?XP?Professional?Service?Pack?1
Hardware environment: IP:192.168.0.106, USB controller title: Intel (R) 82801G (ICH7 Family) USB Universal Host Controller-27CB, CPU title: Intel (R) Core (TM) 2 Quad CPU Q9500 2.83GHz, mainboard title: LENOVO ThinkCentre M6100T
Testing procedure: insert 1.5M USB extended line, after using 0 end points to send to obtain the order of descriptor
Error description: insert 1.5M USB extended line, use 0 end points to send to obtain use 0 end points to send after the order of descriptor to obtain the order of descriptor after, Get the crypt prov handle failed, internal error has appearred in err code:0x80090020.
Journal file four:
Insert 2.0 USB Hub, after using 0 end points to send to obtain the order of descriptor, do not have data among the Cdrom that scsi device ejects
STE: Windows 7 Ultimate, Service Pack 1
Windows?XP?Professional?Service?Pack?1
Hardware environment: IP:192.168.0.106, USB controller title: Intel (R) 82801G (ICH7 Family) USB Universal Host Controller-27CB, CPU title: Intel (R) Core (TM) 2 Quad CPU Q9500 2.83GHz, mainboard title: LENOVO ThinkCentre M6100T
Testing procedure: insert 2.0 USB Hub, after using 0 end points to send to obtain the order of descriptor
Error description: insert 2.0 USB Hub, use 0 end points to send to obtain use 0 end points to send after the order of descriptor to obtain the order of descriptor after, Get the crypt prov handle failed, internal error has appearred in err code:0x80090020.
Step 113: the test mode item in the new configuration file more, sign need the recovery operation system that is operating as that carries out, and more the operating system in the new configuration file is pointed to, makes it to point to next operating system in the configuration file, returns execution in step 101.
According to above-mentioned configuration file example, step 113 is specially: the value of revising the STATE item in the configuration file is first preset value, and the value of revising the CURROSID item adds 1 for its currency, returns execution in step 101.
Embodiment two
Referring to Fig. 6, the embodiment of the invention two provides a kind of the journal file that generates in the test process has been carried out the method that classification analysis obtains test result file, and described method specifically comprises:
Step 301: a journal file of not checking as current journal file, is checked in the current journal file whether wrong description, is execution in step 302 then, otherwise execution in step 303;
Step 302: read the error description in the current journal file, create chained list, described error log information is added in the described chained list to execution in step 303 as a node;
Step 303: judge the intact whole journal files of inspected, be execution in step 304 then, otherwise return execution in step 301;
Step 304: first compares the first node that index value points to described chained list;
Step 305: second compares the relatively next node of the node of index value sensing of index value sensing first;
Step 306: with first relatively index value point to node information key word and second relatively the index value key word that points to the information of node blur and compare, judge whether the two similar, be execution in step 307 then, otherwise execution in step 308;
Step 307: second information that compares index value sensing node is merged to first compare the node that index value points to, the node of index value sensing, execution in step 308 are compared in deletion second;
Step 308: judge second relatively the node that points to of index value whether be the tail node of described chained list, be execution in step 310 then, otherwise execution in step 309;
Step 309: second compares the next node that index value points to its current sensing node, returns execution in step 306;
Step 310: judge first relatively the next node of the current sensing node of index value whether be the tail node of described chained list, be execution in step 312 then, otherwise execution in step 311;
Step 311: first compares the next node that index value points to its current sensing node, returns execution in step 305;
Step 312: the information of described each node of chained list is written in the test result file, deletes described chained list.
Above-described embodiment is a more preferably embodiment of the present invention, and common variation that those skilled in the art carries out in the technical solution of the present invention scope and replacement all should be included in protection scope of the present invention.
Claims (24)
1. the hardware universal testing method of a USB device is characterized in that, described method is automatically performed according to configuration file by test platform, may further comprise the steps:
Steps A, read the test mode item in the described configuration file, judge the operation that needs are carried out according to described test mode item, if the execution in step B then of recovery operation system, if test then execution in step F, if other then finish;
Step B, the operating system that reads in the described configuration file is pointed to item, point to item according to described operating system and search current operation system in the described configuration file, and read the status items corresponding with current operation system, judging whether to treat testing apparatus according to described status items tests under the current operation system environment, be execution in step C then, otherwise judge that whether current operation system is last operating system in the described configuration file, if last operating system in the described configuration file then finishes, point to item if then do not upgrade described operating system, continue execution in step B for last operating system in the described configuration file;
Step C, read backup file name item corresponding and backup file place path entry with current operation system, generate first autoexec according to described backup file name item and backup file place path entry, obtain the title and the patch title of the current operating system of described test platform, and according to corresponding operating system in the title of the current operating system of described test platform and the described configuration file of patch name lookup, read the Globally Unique Identifier item of corresponding operating system, generate second autoexec according to described Globally Unique Identifier item, carry out acquiescence that described second autoexec is provided with system and start the acquiescence startup delay time that starts and system is set for WinPE;
Test mode item in step D, the described configuration file of renewal, sign needs the test that is operating as of execution, and restarting operating systems returns execution in step A;
Step F, the USB device that connects on the described test platform is enumerated, generated list of devices to be tested, treat testing apparatus according to described list of devices to be tested and under the current operation system environment, test;
Step G, the operating system that reads in the described configuration file are pointed to item and operating system quantity item, judge that whether current operation system is last operating system in the described configuration file, be then to finish, otherwise upgrade the test mode item in the described configuration file, sign needs the recovery operation system that is operating as of execution, the operating system of upgrading in the described configuration file is pointed to item, returns execution in step A.
2. the hardware universal testing method of USB device according to claim 1 is characterized in that, the described operation of carrying out according to described test mode item judgement needs also comprises: drive then execution in step E if install;
Step e, read the driver name item in the described configuration file, generate the 3rd autoexec or script file according to described driver name item, carry out described the 3rd autoexec or script file and come install driver, upgrade the test mode item in the described configuration file, sign needs the test that is operating as of execution, restarting operating systems returns execution in step A;
Correspondingly, also comprise between described step C and the described step D:
Step 1., read the installation sign in the described configuration file, judge whether according to described installation sign that needs are installed and drive, be then execution in step 4., otherwise execution in step is 2.;
Step 2., read the device type item in the described configuration file, judge according to the value of described device type item whether equipment to be tested is USB chip intelligent card equipment, be then execution in step 3., otherwise execution in step D;
Step 3., judge whether according to the OS name item of the current operation system in the described configuration file that needs are installed and drive, be then execution in step 4., otherwise execution in step D;
Step 4., upgrade the test mode item in the described configuration file, sign needs to carry out is operating as to install and drives, restarting operating systems returns execution in step A.
3. the hardware universal testing method of USB device according to claim 2 is characterized in that,
The described operation of carrying out according to described test mode item judgement needs comprises: the value of checking described test mode item, if first preset value then needs the recovery operation system that is operating as that carries out, if second preset value then needs to carry out is operating as to install and drives, if the 3rd preset value then needs the test that is operating as carried out;
Correspondingly, the test mode item in the described configuration file of described renewal, the installation driving that is operating as that sign needs to carry out is specially: the value of upgrading the test mode item in the described configuration file is second preset value; The test that is operating as that test mode item in the described configuration file of described renewal, sign need to carry out is specially: the value of upgrading the test mode item in the described configuration file is the 3rd preset value; Test mode item in the described configuration file of described renewal, the recovery operation system that is operating as that sign needs to carry out is specially: the value of upgrading the test item in the described configuration file is first preset value.
4. the hardware universal testing method of USB device according to claim 1 is characterized in that, describedly judges whether that according to described status items needs treat testing apparatus and test under the current operation system environment, comprising:
Whether the value of judging described status items is the 4th preset value, and being then needs to treat testing apparatus to test under the current operation system environment; Otherwise not needing to treat testing apparatus tests under the current operation system environment.
5. the hardware universal testing method of USB device according to claim 4 is characterized in that:
Describedly treat testing apparatus according to described list of devices to be tested and also comprise before testing under the current operation system environment: the value of upgrading the status items of current operation system correspondence in the described configuration file is the 5th preset value, and sign is being treated testing apparatus and tested under the current operation system environment;
Describedly treat testing apparatus according to described list of devices to be tested and also comprise after testing under the current operation system environment: the status items of upgrading current operation system correspondence in the described configuration file is the 6th preset value, and sign has been finished and treated the test of testing apparatus under the current operation system environment.
6. the hardware universal testing method of USB device according to claim 1, it is characterized in that, described in the described step C in the configuration file corresponding operating system be specially: current with the test platform that gets access to respectively OS name and the patch title identical operations system of the patch name item of the name item of operating system and operating system in the described configuration file.
7. the hardware universal testing method of USB device according to claim 1, it is characterized in that, comprise after the restarting operating systems among the described step D: test platform enters the Windows WindowsPE after the described acquiescence start delay time, automatically perform described first autoexec and come the setting operation system to enter described first after starting once more to handle the fixed operating system of document, operating system resets automatically.
8. the hardware universal testing method of USB device according to claim 2, it is characterized in that, comprise after the 4. middle restarting operating systems of described step: test platform enters the Windows WindowsPE after the described acquiescence start delay time, automatically perform described first autoexec and come the setting operation system to enter described first after starting once more to handle the fixed operating system of document, operating system resets automatically.
9. the hardware universal testing method of USB device according to claim 1 is characterized in that, comprises in the described list of devices to be tested: the product coding of equipment to be tested, operator code coding, handle and connected mode.
10. the hardware universal testing method of USB device according to claim 9 is characterized in that, described step F specifically comprises:
Step a, distribute and the initialization apparatus array, enumerate master controller, obtain the title of the Root Hub of the number of described master controller and each master controller correspondence, the described Root Hub title that gets access to is deposited in the described equipment array in initialization first index value;
Step b, judge first index value, be execution in step c then, otherwise each equipment to be tested tested under the current operation system environment according to described list of devices to be tested whether less than the number of described master controller;
Step c, enumerate the Root Hub of specifying the master controller correspondence according to described first index value, obtain product coding, operator code coding, handle and the connected mode of the equipment to be tested that connects on the current root hub, with the information stores that gets access in described list of devices to be tested;
Steps d, renewal first index value return execution in step b.
11. the hardware universal testing method of USB device according to claim 10 is characterized in that, described step a specifically comprises:
Step a1, the described equipment array of initialization are provided with second index value and maximal value;
Step a2, whether judging described second index value less than described maximal value, is execution in step a3 then, otherwise execution in step b;
Step a3, making up the device name of master controller according to described second index value, use the mode of attempting opening to enumerate, judge and attempt opening whether the handle that returns is invalid value, is execution in step b then, otherwise execution in step a4;
Step a4, obtain the title of the Root Hub of current master controller correspondence, the title of the Root Hub that gets access to is deposited in the described equipment array, close the host controller device of opening, upgrade second index value, return execution in step a2.
12. the hardware universal testing method of USB device according to claim 10 is characterized in that:
Described connected mode comprises: do not have the mode of utility appliance and pass through hub Hub1.1/Hub2.0/Hub3.0 ways of connecting;
Described step c specifically comprises:
The device name of step c1, structure current root hub is opened the current root hub device, obtains the link information of each node of current root hub;
Step c2, judging on each node of current root hub whether be connected with USB device, is the number of then obtaining the node that is connected with USB device, the 3rd index value is set, execution in step c3, otherwise execution in step d;
Step c3, whether judging described the 3rd index value less than the described node number that is connected with USB device, is then according to the specified node of described the 3rd index value inquiry current root hub, execution in step c4, otherwise execution in step d;
Step c4, the product coding that obtains the USB device that connects on the described specified node, operator code coding, handle and connected mode, judge the type of the USB device that is connected on the described specified node according to product coding that gets access to and operator code coding, if equipment to be tested is execution in step c5 then, if Hub1.1/Hub2.0/Hub3.0 is execution in step c6 then, if other execution in step c7 then;
Step c5, the product coding with described equipment to be tested, operator code coding, handle and connected mode are saved in the described list of devices to be tested, execution in step c7;
Step c6, enumerate described Hub1.1/Hub2.0/Hub3.0, obtain product coding, operator code coding, handle and connected mode that described Hub1.1/Hub2.0/Hub3.0 goes up the USB device that connects, type according to the product coding that gets access to and each USB device of operator code coding judgement, if equipment to be tested then is saved in product coding, operator code coding, handle and the connected mode of USB device to be tested in the described list of devices to be tested, execution in step c7, otherwise execution in step c7;
Step c7, close the Root Hub equipment of opening, upgrade the 3rd index value, return execution in step c3.
13. the hardware universal testing method of USB device according to claim 12 is characterized in that, described step c6 specifically comprises:
Step c6-1: construct the device name of described Hub1.1/Hub2.0/Hub3.0, open described Hub1.1/Hub2.0/Hub3.0 equipment, obtain the link information of described each node of Hub1.1/Hub2.0/Hub3.0;
Step c6-2: judging on each node of described Hub1.1/Hub2.0/Hub3.0 whether be connected with USB device, is the number of then obtaining the node that is connected with USB device, and the 4th index value is set, execution in step c6-3, otherwise execution in step c7;
Step c6-3, judge that described the 4th index value whether less than the described node number that is connected with USB device, is a specified node of then inquiring about described Hub1.1/Hub2.0/Hub3.0 according to described the 4th index value, execution in step c6-4, otherwise execution in step c7;
Step c6-4, the PID that obtains the USB device that connects on the described specified node, operator code coding, handle and connected mode, judge the type of the USB device that is connected on the described specified node according to product coding that gets access to and operator code coding, if equipment to be tested is execution in step c6-5 then, otherwise execution in step c6-6;
Step c6-5, the product coding with described equipment to be tested, operator code coding, handle and connected mode are saved in the described list of devices to be tested, execution in step c6-6;
Step c6-6, close the Hub1.1/Hub2.0/Hub3.0 equipment of opening, upgrade the 4th index value, return execution in step c6-3.
14. the hardware universal testing method of USB device according to claim 12, it is characterized in that, describedly treat testing apparatus according to described list of devices to be tested and under the current operation system environment, test and comprise: the connected mode of judging each equipment to be tested in the described list of devices to be tested, do not carry out first test and second test if there is utility appliance then to treat testing apparatus, carry out first test if then treat testing apparatus by the Hub1.1/Hub2.0/Hub3.0 connection.
15. the hardware universal testing method of USB device according to claim 14 is characterized in that,
The described testing apparatus for the treatment of is carried out first test and is comprised: treat testing apparatus and carry out plug and play identification and communication test, treat and carry out plug and play identification and communication test again after operation is forbidden and enabled to testing apparatus, treat that testing apparatus is descended electricity and the operation that powers on after carry out plug and play identification and communication test again, treating testing apparatus carries out continuously default time and carries out plug and play identification and communication test again after electricity and the operation that powers on down, treating testing apparatus presets and carries out the power source change of plug and play identification and communication test and simulation notebook again behind time reset operation and treat testing apparatus and carry out plug and play identification and communication test;
The described testing apparatus for the treatment of is carried out second test and is comprised: treat testing apparatus and carry out carrying out plug and play identification and communication test again after the sleeping/waking operation.
16. the hardware universal testing method of USB device according to claim 1, it is characterized in that, described according to described list of devices to be tested to each equipment to be tested test under the current operation system environment and described step G between also comprise: if test is finished and is not then carried out aborted and handle.
17. the hardware universal testing method of USB device according to claim 1, it is characterized in that, described according to described list of devices to be tested to each equipment to be tested test under the current operation system environment and described step G between also comprise: if the test finish and test by then generating journal file.
18. the hardware universal testing method of USB device according to claim 1, it is characterized in that, described according to described list of devices to be tested to each equipment to be tested test under the current operation system environment and described step G between also comprise: if test is finished and is tested not by then finishing.
19. the hardware universal testing method of USB device according to claim 17, it is characterized in that, described according to described list of devices to be tested to each equipment to be tested test under the current operation system environment and described step G between also comprise: if the test finish and test not by then generating journal file.
20. the hardware universal testing method of USB device according to claim 19, it is characterized in that, also comprise before the described generation journal file: obtain protocol IP address interconnected between the network of test platform, USB controller title, central processor CPU title and mainboard title, logging software test environment, testing procedure and error description.
21. the hardware universal testing method of USB device according to claim 1, it is characterized in that, describedly judge that whether current operation system is that last operating system in the described configuration file is specially: judge whether the value that described operating system points to is identical with the value of described operating system quantity item, be that then current operation system is last operating system in the described configuration file, otherwise current operation system is not last operating system in the described configuration file.
22. the hardware universal testing method of USB device according to claim 19, it is characterized in that, describedly judge that whether current operation system is that the judged result of last operating system in the described configuration file also comprises for after being: the journal file that generates in the test process is carried out classification analysis, obtain test result file.
23. the hardware universal testing method of USB device according to claim 22 is characterized in that, described all journal files that generate in the test process is carried out classification analysis, obtains test result file and comprises:
All journal files that generate in step e, the inspection test procedure read described error description during wrong description, and the information that reads are added in the chained list of establishment as a node in being checked through a journal file;
Step f, check the information of each node in the described chained list, will compare to determine the similar node of information key word and merge into a node, preserve the node after merging, delete all the other nodes through fuzzy;
Step g, the information of remaining node in the described chained list is write test result file, delete described chained list.
24. the hardware universal testing method of USB device according to claim 23 is characterized in that, described step f comprises:
Step f1, first compares the first node that index value points to described chained list;
Step f2, second compares the relatively next node of the node of index value sensing of index point sensing first;
Step f3, with first relatively the information of the node that points to of index value key word and second relatively the key word of the information of the node that points to of index value blur and compare, whether the information of judging the node that the first comparison index value points to is similar with the information of the node of second index value sensing, be execution in step f4 then, otherwise execution in step f5;
Step f4, with second relatively the information of the node that points to of index value merge to the node that first index value points to, deletion second is the node that points to of index value relatively, execution in step f5;
Step f5, judge second relatively the node that points to of index value whether be the tail node of described chained list, be execution in step f6 then, otherwise second relatively index value point to the next node of its current sensing node, return execution in step f3;
Step f6, judge first relatively the next node of the current sensing node of index value whether be the tail node of described chained list, be execution in step g then, otherwise first relatively index value point to the next node of its current sensing node, return execution in step f2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310128504.7A CN103218280B (en) | 2013-04-15 | 2013-04-15 | A kind of hardware universal testing method of USB device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310128504.7A CN103218280B (en) | 2013-04-15 | 2013-04-15 | A kind of hardware universal testing method of USB device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103218280A true CN103218280A (en) | 2013-07-24 |
| CN103218280B CN103218280B (en) | 2016-12-28 |
Family
ID=48816100
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310128504.7A Expired - Fee Related CN103218280B (en) | 2013-04-15 | 2013-04-15 | A kind of hardware universal testing method of USB device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103218280B (en) |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104267331A (en) * | 2014-09-16 | 2015-01-07 | 四川和芯微电子股份有限公司 | USB chip testing method |
| CN104714872A (en) * | 2015-04-10 | 2015-06-17 | 南车株洲电力机车研究所有限公司 | Performance test method for vehicle-mounted USB equipment |
| CN104869036A (en) * | 2015-06-05 | 2015-08-26 | 太仓市同维电子有限公司 | Method for testing plurality of portable USB (Universal Serial Bus) routers with mechanical arm |
| CN107168880A (en) * | 2017-05-31 | 2017-09-15 | 中标软件有限公司 | Virtual machine method of testing and instrument |
| CN107943702A (en) * | 2017-11-28 | 2018-04-20 | 中标软件有限公司 | Hardware compatibility test method and device |
| CN109218055A (en) * | 2017-07-04 | 2019-01-15 | 上海诺基亚贝尔股份有限公司 | A kind of method and apparatus that rapid configuration network element device carries out plug and play |
| CN109446013A (en) * | 2018-11-01 | 2019-03-08 | 深圳三地芯电子有限责任公司 | Store apparatus testing method, storage device testing system and storage medium |
| CN109634690A (en) * | 2018-12-24 | 2019-04-16 | 山东中孚安全技术有限公司 | Data clearing method, device, terminal and storage medium based on WinPE system |
| CN110910944A (en) * | 2018-09-17 | 2020-03-24 | 爱思开海力士有限公司 | Apparatus and method for maintaining firmware in a memory system |
| CN111200837A (en) * | 2019-12-20 | 2020-05-26 | 翱捷科技(上海)有限公司 | Wi-Fi software testing system and method |
| CN111341380A (en) * | 2020-02-25 | 2020-06-26 | 深圳忆联信息系统有限公司 | Test method and device for resetting SSD (solid State disk) controller and computer equipment |
| CN111708548A (en) * | 2020-06-18 | 2020-09-25 | 北京小米移动软件有限公司 | Software installation method, device, equipment and storage medium |
| CN111737066A (en) * | 2020-05-29 | 2020-10-02 | 浪潮电子信息产业股份有限公司 | USB signal testing system and method |
| CN112068998A (en) * | 2019-06-10 | 2020-12-11 | 山东华芯半导体有限公司 | Automatic solid state disk testing method based on USB (universal serial bus) flash disk PE (provider edge) system |
| CN112860498A (en) * | 2021-01-29 | 2021-05-28 | 紫光展讯通信(惠州)有限公司 | Test method, device, equipment and system for configuration channel |
| US20220244309A1 (en) * | 2021-01-30 | 2022-08-04 | Siliconch Systems Pvt Ltd | SINGLE PIN DFT ARCHITECTURE FOR USBPD ICs |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060195894A1 (en) * | 2005-02-25 | 2006-08-31 | Microsoft Corporation | Windows remote debugger service |
| CN101931477A (en) * | 2010-09-02 | 2010-12-29 | 湖北众友科技实业股份有限公司 | System and method for automatically testing performance of TD-LTE (Time Division-Long Term Evolution) terminal |
| CN102053900A (en) * | 2009-10-30 | 2011-05-11 | 鸿富锦精密工业（深圳）有限公司 | Method and system for testing USB (Universal Serial Bus) equipment of electronic device |
-
2013
- 2013-04-15 CN CN201310128504.7A patent/CN103218280B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060195894A1 (en) * | 2005-02-25 | 2006-08-31 | Microsoft Corporation | Windows remote debugger service |
| CN102053900A (en) * | 2009-10-30 | 2011-05-11 | 鸿富锦精密工业（深圳）有限公司 | Method and system for testing USB (Universal Serial Bus) equipment of electronic device |
| CN101931477A (en) * | 2010-09-02 | 2010-12-29 | 湖北众友科技实业股份有限公司 | System and method for automatically testing performance of TD-LTE (Time Division-Long Term Evolution) terminal |
Cited By (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104267331A (en) * | 2014-09-16 | 2015-01-07 | 四川和芯微电子股份有限公司 | USB chip testing method |
| CN104714872A (en) * | 2015-04-10 | 2015-06-17 | 南车株洲电力机车研究所有限公司 | Performance test method for vehicle-mounted USB equipment |
| CN104869036A (en) * | 2015-06-05 | 2015-08-26 | 太仓市同维电子有限公司 | Method for testing plurality of portable USB (Universal Serial Bus) routers with mechanical arm |
| CN107168880A (en) * | 2017-05-31 | 2017-09-15 | 中标软件有限公司 | Virtual machine method of testing and instrument |
| CN109218055B (en) * | 2017-07-04 | 2021-07-30 | 上海诺基亚贝尔软件有限公司 | Method and device for rapidly configuring network element equipment for plug and play |
| CN109218055A (en) * | 2017-07-04 | 2019-01-15 | 上海诺基亚贝尔股份有限公司 | A kind of method and apparatus that rapid configuration network element device carries out plug and play |
| CN107943702A (en) * | 2017-11-28 | 2018-04-20 | 中标软件有限公司 | Hardware compatibility test method and device |
| CN110910944A (en) * | 2018-09-17 | 2020-03-24 | 爱思开海力士有限公司 | Apparatus and method for maintaining firmware in a memory system |
| CN109446013B (en) * | 2018-11-01 | 2022-05-24 | 深圳三地一芯电子有限责任公司 | Storage device testing method, storage device testing system and storage medium |
| CN109446013A (en) * | 2018-11-01 | 2019-03-08 | 深圳三地芯电子有限责任公司 | Store apparatus testing method, storage device testing system and storage medium |
| CN109634690A (en) * | 2018-12-24 | 2019-04-16 | 山东中孚安全技术有限公司 | Data clearing method, device, terminal and storage medium based on WinPE system |
| CN112068998A (en) * | 2019-06-10 | 2020-12-11 | 山东华芯半导体有限公司 | Automatic solid state disk testing method based on USB (universal serial bus) flash disk PE (provider edge) system |
| CN111200837A (en) * | 2019-12-20 | 2020-05-26 | 翱捷科技(上海)有限公司 | Wi-Fi software testing system and method |
| CN111200837B (en) * | 2019-12-20 | 2023-12-22 | 翱捷科技股份有限公司 | Wi-Fi software testing system and method |
| CN111341380A (en) * | 2020-02-25 | 2020-06-26 | 深圳忆联信息系统有限公司 | Test method and device for resetting SSD (solid State disk) controller and computer equipment |
| CN111737066A (en) * | 2020-05-29 | 2020-10-02 | 浪潮电子信息产业股份有限公司 | USB signal testing system and method |
| CN111708548A (en) * | 2020-06-18 | 2020-09-25 | 北京小米移动软件有限公司 | Software installation method, device, equipment and storage medium |
| CN112860498A (en) * | 2021-01-29 | 2021-05-28 | 紫光展讯通信(惠州)有限公司 | Test method, device, equipment and system for configuration channel |
| US20220244309A1 (en) * | 2021-01-30 | 2022-08-04 | Siliconch Systems Pvt Ltd | SINGLE PIN DFT ARCHITECTURE FOR USBPD ICs |
| US11933841B2 (en) * | 2021-01-30 | 2024-03-19 | Siliconch Systems Pvt Ltd | Single pin DFT architecture for USBPD ICs |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103218280B (en) | 2016-12-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103218280A (en) | Hardware general testing method of USB (Universal Serial Bus) equipment | |
| US6725178B2 (en) | Use of hidden partitions in a storage device for storing BIOS extension files | |
| US10303458B2 (en) | Multi-platform installer | |
| CN103412769A (en) | External card parameter configuration method, equipment and system | |
| CN110135130B (en) | Method and system for preventing embedded equipment software from being modified | |
| CN104572387A (en) | Method and device for debugging terminal in engineering mode | |
| US20070168905A1 (en) | Networked linux machine and windows software development system | |
| CN107766084A (en) | Bootload and installation method and its computing system | |
| CN110119623A (en) | A kind of credible main board implementation method for realizing that firmware is actively measured using TPCM | |
| CN111338698A (en) | Method and system for accurately booting server by BIOS (basic input output System) | |
| US9965292B2 (en) | Method of bluetooth pairing with UEFI firmware and computer system thereof | |
| US8214825B2 (en) | Electronic device and method for installing software | |
| CN107315607B (en) | Drive self-adaptation loading system | |
| US20090198988A1 (en) | Method for verifying refreshed bios content | |
| CN110688235A (en) | System and method for sharing wireless connection information between UEFI firmware and OS | |
| US10379872B1 (en) | Method for creation of a device driver for a peripheral device | |
| TW528950B (en) | Permanent open firmware PCI host bridge (PHB) unit addressing to support dynamic memory mapping and swapping of I/O drawers | |
| CN112214413A (en) | Application program testing method, device, equipment and storage medium | |
| CN110825421A (en) | Firmware upgrading method and system and readable storage medium | |
| CN108052337A (en) | A kind of firmware upgrade method and device of eMMC production tools | |
| CN113900693A (en) | Firmware upgrading method, device and system, electronic equipment and storage medium | |
| CN113703914A (en) | Test method and test system | |
| CN109491947B (en) | Method and related device for sending heat removal information of PCIE (peripheral component interface express) external card | |
| TWI554876B (en) | Method for processing node replacement and server system using the same | |
| CN116028100B (en) | Software version upgrading method and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20161228 |