CN100349134C - Method and system for testing drive software - Google Patents
Method and system for testing drive software Download PDFInfo
- Publication number
- CN100349134C CN100349134C CNB2005100588194A CN200510058819A CN100349134C CN 100349134 C CN100349134 C CN 100349134C CN B2005100588194 A CNB2005100588194 A CN B2005100588194A CN 200510058819 A CN200510058819 A CN 200510058819A CN 100349134 C CN100349134 C CN 100349134C
- Authority
- CN
- China
- Prior art keywords
- test
- script
- drive software
- interface
- function
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The present invention discloses a test method of driving software, which comprises the steps: a background generates a test case which is used for describing the test process of driving software; the background generates a test script which is used for describing the test case by using a script language according to the test case, and the test script comprises a spread command script; the background is used for transmitting the test script to a single plate; the single plate is used for receiving the test script which is used for analyzing the single plate, and the corresponding spread function is obtained and executed according to the spread command script. The execution of the spread function comprises the steps: the universal function is singly realized, or an interface sealing function which is used for sealing an interface of tested driving software into a standard interface is triggered; the interface sealing function starts an interface function of the tested driving software so as to realize the date exchange between the spread function and the tested driving software. The present invention also discloses a test system of driving software.
Description
Technical field
The present invention relates to the measuring technology of drive software, particularly relate to a kind of method of testing and test macro of drive software.
Background technology
As everyone knows, drive software provides the driving function to physical equipment, to the realization details of upper strata shielding device driving.At present, the operation-interface that makes progress of drive software does not also form a unified interface between each product.As MD 5500 products and ESR product, use similar FLASH chip, the function of using is also basic identical, but but difference is very big for the interface of drive software, and number of parameters, the parameter position of interface all are not quite similar.
When realizing the Test Design of drive software,, reuse so on the testing scheme rank, can reach substantially because the function that the object that will test is finished is (for example send data, receive data, configuration, verification, loopback etc.) of fixing basically.Yet, because the interface difference that different drive softwares provides, so can't realize reusing aspect the test blocks such as test event, test case, test script, test code.
See also Fig. 1, in the prior art, in the test process of drive software, test block mainly comprises following components or level: test case 110, be used for the description of test process, and comprise prerequisite, testing procedure, expected results, can not carry out; Test script 120 is described test case with script, finishes the explanation of whole test process and carries out, by explosion command script and spread function interface; Spread function 130 is finished the execution of explosion command script, calls the interface function of tested drive software 901.
Because test script 120 exists coupling with the interface (figure does not show) of drive software 901, therefore, just can not realize reusing of correlative measurement test specimen as long as the drive software interface is different.The interface of the similar drive software between each product is to be designed to duplicate (masking environmental difference) in theory, but never accomplishes under the reality.
Correspondingly, after the tester receives the test assignment of new drive software at every turn, all need to carry out again Test Design and realize with test; And in measuring executing process,, often to revise Test Design and test realization owing to design and the realization defective.
At present, when the tester carries out Test Design and realizes, basically judge the case as it stands, do not consider reusing of test job, the payment part of finishing, comprise that test event, test case, test script, test code all can only use, and can not reuse substantially on the driver module of finishing identical function of other products on certain driver module of this product; Cause most of achievement not inherited by Related product, correlation module; Perhaps promptly allow to part and reuse, also will drop into more workload in addition and carry out adaptability revision.
Owing to seldom consider the problem that Test Design is reused, the tester only tests towards certain module of certain product, does not possess the experience of reusing Related product, correlation module.And, the restriction of tested person personnel's testing level and measuring technology accumulation, the completeness difference of Test Design is considered not comprehensive, tends to omit test point.
In addition, when the tester carried out Test Design and realizes, random big, process was difficult to constraint.
In sum, existing test job exist that drive software Test Design reuse capability is low, the test completeness is poor, not comprehensively, the defective of process conformity difference.
In the prior art, test for drive software, basically be to adopt the mode of test command to finish, in application program, do not embed TCL (Tool Command Language, TCL) interpreter, the shortcoming of this mode is that test process is solidificated in the implementation of order, is difficult for expansion, and the degree that automatic test is supported is not enough.
Summary of the invention
At the above-mentioned defective of prior art, the invention provides a kind of method of testing and test macro of drive software, the technical matters of its solution is that the Test Design that realizes drive software reuses, improves the standardization of test process.
For this reason, the technical scheme of technical solution problem of the present invention is: a kind of method of testing of drive software is provided, comprises step:
1) backstage generates test case, is used for the test process of drive software is described; According to described test case, the backstage generates test script, is used to adopt script to describe described test case, comprises the explosion command script;
2) described backstage issues described test script to veneer;
3) described veneer receives described test script, and it is resolved, and obtains and carry out corresponding spread function according to wherein explosion command script; The execution of described spread function comprises: realize that separately general utility functions or triggering are used for the interface of tested drive software is packaged into the interface encapsulation function of standard interface;
4) described interface encapsulation function starts the interface function of tested drive software, realizes the data interaction between spread function and the tested drive software.
Preferably, the single plate interactive interface that issues by the backstage described step 2) carries out.
Preferably, also comprise: the backstage is by the reception of single plate interactive interface, Query Board status information; Type information when receiving the spread function execution.
Preferably, the parsing of described step 3) realizes by the script resolution unit of veneer.
Preferably, also comprise: the backstage issues the testing meter and instrument control command to instrument and meter; Send test data to instrument and meter; Frame that the receiving instrument instruments and meters is caught and statistical information.
Preferably, described test script is a TCL TCL script.
Preferably, described test case, test script and spread function are standardized test blocks.
The present invention also provides a kind of test macro of drive software, comprises backstage, veneer and testing meter and instrument;
The backstage is used to store test use cases and test script, issues test script to veneer; Described test script comprises the explosion command script;
Veneer is used to store spread function, receives and resolve the aforementioned test script that issues, according to explosion command script executing spread function wherein;
Described veneer also stores interface encapsulation function; Described interface encapsulation function is used for the interface of tested drive software is packaged into standard interface; In test process, start the interface function of tested drive software, realize the data interaction between spread function and the tested drive software.
Preferably, described test script is a TCL TCL script.
Preferably, described test case, test script and spread function are standardized test blocks.
With respect to prior art, the invention has the beneficial effects as follows: owing to adopt interface encapsulation function to shield the otherness of drive software in the method and system of the present invention, that is to say, interface encapsulation function provides one group of unified interface to the upper strata, the information of shielding different operating system, different phy chips, intercepting associative operation function and information under operating system and drive software are coupled closely situation, thus make spread function, test script and test case can easily realize design reuse.
In addition, in the test macro of the present invention, the form that test script adopts the TCL script can realize automatic test better, thereby improves the efficient of test process.
In addition, the invention provides the test suite of standard, can provide a unified test Solution at standard component, thereby effectively reduce the lack of standard of test process, further improve the Test Design of drive software in conjunction with the package interface unit and reuse; Can also guarantee the test completeness by the complete test block of definition drive software.
In a word, use the present invention, can realize drive software interface and test block standardization, realize the drive software automatically testing platform.Present technique is applied in the drive software test of ESR product, INET product, MD5500 product, the serial ports of drive software, network interface, FLASH etc. have been carried out actual test, test result shows that this drive software of employing automated testing method has improved the drive software testing efficiency greatly, realized that the drive software Test Design reuses, guarantee the test mass of drive software, obtained drive software Test Engineer's consistent favorable comment.
Description of drawings
Fig. 1 is the synoptic diagram of Test Design layering of the drive software of prior art;
Fig. 2 is the synoptic diagram of the Test Design layering of drive software of the present invention;
Fig. 3 is the block diagram of drive software automatically testing platform of the present invention;
Fig. 4 is the process flow diagram of drive software method of testing of the present invention.
Embodiment
Main design of the present invention is: the operation-interface to drive software carries out standardized packages, and the difference on shielding running environment, the application specific details makes that adopting general test case, trial function and test script to test becomes possibility.And,, test block can be promoted the use of in the test of product as standard component by standardization to these test blocks.
See also Fig. 2, the part or the level of the test block that comprises in the test macro of the present invention are: test case 210, be used for the description of test process, and comprise prerequisite, testing procedure and expected results, can not carry out; Test script 220 is described test case 210 with script, finishes the explanation of whole test process and carries out, by explosion command script and spread function interface; Spread function 230 is finished the execution of explosion command script, is called calling interface encapsulation function 240 by script; Interface encapsulation function 240 is packaged into standard interface with the drive software interface, calls tested drive software interface function.
Wherein, test case 210, test script 220 and spread function 230 belong to normalization layer 201, and interface encapsulation function 240 belongs to interface encapsulated layer 202.
That is to say that interface encapsulation function 240 is finished the shielding to the drive software 901 of bottom, makes top normalization layer can't see the drive software 901 of measurand layer 900 fully.
On this basis, it is conspicuous test case, test script, spread function being realized reusing.Further analyze and find, if extensively collect the test experience of each product drive software, test case, test script, spread function are carried out standardization, it only is coupled with the interface encapsulation function 240 that interface encapsulated layer 202 provides, with the drive software 901 of measurand layer 900 direct relation not taking place, can reach reusing fully of test case, test script spread function.
For testing through standardized drive software, the tester only need revise the content overwhelming majority work of interface encapsulation function 240 and can directly reuse, and testing efficiency, test completeness and standardization are guaranteed.Because interface encapsulation function 240 is finished the shielding to drive software 901, makes top normalization layer 201 can't see the drive software 901 of bottom fully; Therefore, interface encapsulation function 240 is relevant with concrete drive software 901, needs a modification, adaptive work.
In a word, by increasing an interface encapsulated layer drive software is carried out standardized packages, extensively collect each product drive software test experience test case, test script, spread function are carried out standardization, thereby realize that the drive software Test Design reuses, Here it is overall design philosophy of the present invention.By this design, can improve testing efficiency, test completeness and standardization significantly.
The present invention carries out standardized encapsulation to the drive software interface, thereby, be duplicate at the test of the drive software behind the nuclear interface standardizing.About the standardized packages of drive software interface, through several products be studies confirm that it is feasible.
The present invention states on the basis of test block in realization, further develops the test macro of drive software, perhaps is referred to as the drive software automatically testing platform, makes the tester directly to utilize platform to test, and reduces the time of integration testing environment.
As everyone knows, along with the development of measuring technology, behavioral test progressively is converted into stored program control system and implements, also i.e. test automatically.That is to say, to behavioral tests such as the operation of instrument and meter and equipment under test, test result differentiations, can realize in the test process, no longer need manual operations and monitoring by programming Control.The popular automatic test of industry at present, thus be to adopt the TCL script to describe and implement the robotization that behavioral test is realized test process.TCL is a kind of script, be characterized in directly explaining carrying out and reducing complicated compiling connection procedure, and the command analysis device can easily easily be embedded in the application program and goes.Support the software of autorun to adopt such framework usually: in application program, to embed the TCL interpreter and increase relevant explosion command, issue the control script by control desk in the time of test, carry out script command by the TCL interpreter interprets that embeds and finish corresponding test process.The benefit of this mode is to be combined into the high test case of coverage rate in many ways, and extensibility is good, and the automaticity of test is higher.
Adopt the tool software ScriptCenter of Sprient company exploitation in one embodiment of the present of invention, this tool software is the integrated environment of a TCL exploitation, the strong functions characteristic that provides support and test automatically provides convenience for building unified and open automatically testing platform.
The drive software test macro, promptly the drive software automatically testing platform is based upon on the basis of ScriptCenter, controls tested single board and testing meter and instrument by script, thereby realizes test automation and modularization.By script control, script is used for realizing control flow to test process fully, promptly the initialization port, when the opening/closing port, how configured port, when start operation such as transceive data and operating result carried out analysis and judgement to start corresponding processing.The thinking of test is real, directly embodiment is exactly a script.
See also Fig. 3, automatically testing platform comprises backstage (PC) 310, veneer 320 and 330 3 parts of testing meter and instrument.The editor of test case is mainly finished on backstage 310, functions such as the editor of script, management and execution; Veneer 320 is the support sections on backstage 310, finishes the function of explosion command and execution result is fed back to ScriptCenter; In addition, veneer 320 also will be handled test, business datum.
Backstage 310 has ScriptCenter, store test case 311 and test script 312, comprise with instrument and meter interactive unit 314, with tested single board interactive unit 315.Have the explosion command script in the described test script 312, wherein include explosion command 313.
Veneer 320 has operating system, drive software and application software, comprises script resolution unit 321, stores spread function 322, interface encapsulation function 323.
Testing meter and instrument 330 has control interface and business interface, realizes data interaction with backstage 310 and veneer 320 respectively.
Wherein, the design process of test case 311 is: collect each product drive software test case and integrate, test case conversion that can be public is that the public test case of standard is described; Can not public test case analyze its reason, provide support at the interface encapsulated layer in the time of necessary, improve the standard drive software interface that the interface encapsulated layer provides, make the test case can be public, finally export complete test case, and can be constantly perfect; The design of test case does not have new specific (special) requirements, and unique constraint condition is to take all factors into consideration, analyze the actual conditions of a plurality of products, with the facility that guarantees subsequent design and clear.
The editor of TCL test script 312, management and execution rely on the function of ScriptCenter self.
The instrument and meter interactive interface (figure does not show) that provides by ScriptCenter with instrument and meter interactive unit 314 issues the TCL script command, the duty of configuration testing instrument and meter 330, comprise the form that sends data, receive the trigger condition of data capture, counting etc.; Send test data to testing meter and instrument 330; Frame that receiving instrument instruments and meters 330 is caught and statistical information etc.
Assign the configuration script order with the single plate interactive interface (figure does not show) that tested single board interactive unit 315 provides by ScriptCenter to tested single board; Reception, Query Board status information; As the passage of explosion command, send to the script resolution unit 321 of veneer; As information channel, the type information when receiving the execution of TCL spread function is printed in the graphic interface median surface module (figure does not show) that ScriptCenter provides.
The sub-fraction function (refers to general, not relying on the interface encapsulated layer provides the function of interface) in the inner realization of spread function, most of function needs interface encapsulation function 323, promptly once encapsulation (virtual unit) realizes, after function is classified, is integrated, which is analyzed is general function, and which is to call the function that virtual unit provides, and designs spread function and the interface of encapsulation between (virtual unit) once.
Once encapsulation (virtual unit) requires tested software to satisfy certain interface, this interface is accomplished generally to be suitable for as far as possible, if in tested software, exist (under most of situation, having greatly, interface is like this, this also is the basis that the drive software test platform can be transplanted between different product), then do not need the tester to realize; Otherwise, should realize (in " once encapsulation ") by the tester.
Once encapsulate the function that (virtual unit) provides function to realize the spread function requirement according to tested software, spread function 322 is designed grammer, the form of explosion command on this basis.
In addition, test employed instrument and equipment and also will control by ordering, its grammatical form defines in ScriptCenter.
For relevant with operating system, with the phy chip function associated, in the TCL spread function parameter is analyzed, call once encapsulation (virtual unit) layer functions then.
323 pairs of TCL spread functions 322 of interface encapsulation function provide one group of unified interface, shielding different operating system, different phy chip information, and being coupled at operating system and drive software intercepts associative operation function and information under the situation closely.
In addition,, need to realize interface encapsulated layer software in order can on different products, to transplant, with the masking operation system information, phy chip information etc.For each device driver, all devices correlation properties, operating system correlation properties all terminate in interface encapsulated layer software, and this one deck needs to revise in conjunction with the product of oneself in the transplanting work of different product.
Seeing also Fig. 4, is the process flow diagram of drive software method of testing of the present invention.
Step S1, the backstage generates test case, is used for the test process of drive software is described; According to described test case, the backstage generates test script, is used to adopt script to describe described test case, comprises the explosion command script;
Step S2, described backstage issues described test script to veneer;
Step S3, described veneer receives described test script, and it is resolved, and obtains and carry out corresponding spread function according to wherein explosion command script; The execution of described spread function comprises: realize that separately general utility functions or triggering are used for the interface of tested drive software is packaged into the interface encapsulation function of standard interface;
Step S4, described interface encapsulation function starts the interface function of tested drive software, realizes the data interaction between spread function and the tested drive software.
In a word, the interface that the present invention is based on the similar drive software of each product carries out standardized packages, masking operation system, mutual resource and application specific details, by collecting the Related product experience test event, test case, test script, test code are carried out providing general standard testing part after the standardization, thereby realized that the height between product reuses, improve testing efficiency and test mass, reduce the lack of standard of test process.
For increasing work efficiency to greatest extent, further develop the drive software automatically testing platform in view of the above, platform provides all standardized test blocks to use for the drive software tester.The drive software tester directly utilizes test platform to test like this, has reduced the time of integration testing environment.
The above only is a preferred implementation of the present invention; should be pointed out that for those skilled in the art, under the prerequisite that does not break away from the principle of the invention; can also make some improvements and modifications, these improvements and modifications also should be considered as protection scope of the present invention.
Claims (10)
1. the method for testing of a drive software is characterized in that, comprises step:
1) backstage generates test case, is used for the test process of drive software is described; According to described test case, the backstage generates test script, is used to adopt script to describe described test case, comprises the explosion command script;
2) described backstage issues described test script to veneer;
3) described veneer receives described test script, and it is resolved, and obtains and carry out corresponding spread function according to wherein explosion command script; The execution of described spread function comprises: realize that separately general utility functions or triggering are used for the interface of tested drive software is packaged into the interface encapsulation function of standard interface;
4) described interface encapsulation function starts the interface function of tested drive software, realizes the data interaction between spread function and the tested drive software.
2. the method for testing of drive software according to claim 1 is characterized in that, described step 2) the single plate interactive interface that issues by the backstage carry out.
3. the method for testing of drive software according to claim 2 is characterized in that, also comprises: the backstage is by the reception of single plate interactive interface, Query Board status information; Type information when receiving the spread function execution.
4. the method for testing of drive software according to claim 1 is characterized in that, the parsing of described step 3) realizes by the script resolution unit of veneer.
5. the method for testing of drive software according to claim 1 is characterized in that, also comprises: the backstage issues the testing meter and instrument control command to instrument and meter; Send test data to instrument and meter; Frame that the receiving instrument instruments and meters is caught and statistical information.
6. the method for testing of drive software according to claim 1 is characterized in that, described test script is a TCL TCL script.
7. according to the method for testing of each described drive software of claim 1 to 6, it is characterized in that described test case, test script and spread function are standardized test blocks.
8. the test macro of a drive software comprises backstage, veneer and testing meter and instrument;
The backstage is used to store test use cases and test script, issues test script to veneer; Described test script comprises the explosion command script;
Veneer is used to store spread function, receives and resolve the aforementioned test script that issues, according to explosion command script executing spread function wherein;
It is characterized in that: described veneer also stores interface encapsulation function; Described interface encapsulation function is used for the interface of tested drive software is packaged into standard interface; In test process, start the interface function of tested drive software, realize the data interaction between spread function and the tested drive software.
9. the test macro of drive software according to claim 8 is characterized in that, described test script is a TCL TCL script.
10. according to Claim 8 or the test macro of 9 described drive softwares, it is characterized in that described test case, test script and spread function are standardized test blocks.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100588194A CN100349134C (en) | 2005-03-28 | 2005-03-28 | Method and system for testing drive software |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100588194A CN100349134C (en) | 2005-03-28 | 2005-03-28 | Method and system for testing drive software |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1841340A CN1841340A (en) | 2006-10-04 |
| CN100349134C true CN100349134C (en) | 2007-11-14 |
Family
ID=37030377
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005100588194A Expired - Fee Related CN100349134C (en) | 2005-03-28 | 2005-03-28 | Method and system for testing drive software |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100349134C (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101799506A (en) * | 2010-04-21 | 2010-08-11 | 广州市广晟微电子有限公司 | Chip test method, device and system based on script control |
Families Citing this family (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101150463B (en) * | 2007-11-14 | 2010-08-25 | 华为技术有限公司 | Testing method and system |
| CN102375778B (en) * | 2010-08-17 | 2014-12-31 | 中兴通讯股份有限公司 | Method and system for automatically testing digital signal processor (DSP) |
| CN102354200A (en) * | 2011-06-10 | 2012-02-15 | 大唐移动通信设备有限公司 | Method and device for automatic test through control instrument |
| CN102420722A (en) * | 2011-12-01 | 2012-04-18 | 盛科网络（苏州）有限公司 | Comprehensive networking automation testing method and system |
| CN102591780B (en) * | 2012-01-13 | 2015-04-15 | 广州广电运通金融电子股份有限公司 | Device driver software test method and test system |
| CN102609356B (en) * | 2012-01-19 | 2014-12-10 | 福建升腾资讯有限公司 | Terminal product driver loading stability testing method |
| CN103559114B (en) * | 2013-11-12 | 2015-08-19 | 福建联迪商用设备有限公司 | Flush bonding module drives function test system and method |
| CN111314538A (en) * | 2015-07-14 | 2020-06-19 | 苹果公司 | Mobile phone and instrument control method and system using same |
| CN109218271A (en) * | 2017-07-07 | 2019-01-15 | 中兴通讯股份有限公司 | Drive implementation method, device, equipment and computer readable storage medium |
| CN108462614A (en) * | 2018-01-09 | 2018-08-28 | 深圳市亿道数码技术有限公司 | Automatization test system |
| CN111930031B (en) * | 2019-12-26 | 2023-02-14 | 南京南瑞继保电气有限公司 | Relay protection single board debugging system and implementation method thereof |
| CN112148611B (en) * | 2020-09-28 | 2023-08-04 | 深圳信息通信研究院 | Cloud architecture-based automatic test intermediate interface method and platform |
| CN112732533B (en) * | 2021-01-27 | 2024-05-03 | 西门子工厂自动化工程有限公司 | Method, device and readable medium for running script program of industrial monitoring software |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPS58222357A (en) * | 1982-06-21 | 1983-12-24 | Hitachi Ltd | Debug system of drive control program |
| CN1402132A (en) * | 2001-08-28 | 2003-03-12 | 华为技术有限公司 | Method for carrying out instrument module drive of automatic test system |
| US20030070119A1 (en) * | 2001-10-10 | 2003-04-10 | Dallin Michael Dean | Method and system for testing a software product |
| CN1503136A (en) * | 2002-11-21 | 2004-06-09 | 深圳市中兴通讯股份有限公司 | Embedded software test method |
-
2005
- 2005-03-28 CN CNB2005100588194A patent/CN100349134C/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPS58222357A (en) * | 1982-06-21 | 1983-12-24 | Hitachi Ltd | Debug system of drive control program |
| CN1402132A (en) * | 2001-08-28 | 2003-03-12 | 华为技术有限公司 | Method for carrying out instrument module drive of automatic test system |
| US20030070119A1 (en) * | 2001-10-10 | 2003-04-10 | Dallin Michael Dean | Method and system for testing a software product |
| CN1503136A (en) * | 2002-11-21 | 2004-06-09 | 深圳市中兴通讯股份有限公司 | Embedded software test method |
Non-Patent Citations (1)
| Title |
|---|
| TCL命令扩展在产品测试系统开发中的应用 关红州，杨洁.江南大学学报(自然科学板)，第3卷第3期 2004 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101799506A (en) * | 2010-04-21 | 2010-08-11 | 广州市广晟微电子有限公司 | Chip test method, device and system based on script control |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1841340A (en) | 2006-10-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100349134C (en) | Method and system for testing drive software | |
| CN109933522B (en) | Test method, test system and storage medium for automatic case | |
| CN100589420C (en) | Function operation packaging based automatization test script implementing method and apparatus | |
| CN105260315B (en) | A kind of method of the debugging log in embedded system process | |
| CN103995777A (en) | Automatic embedded software block box testing system and method | |
| CN110134400A (en) | Data capture method, device, electronic equipment and computer readable storage medium | |
| CN107315679A (en) | A kind of embedded software automation exact p-value method and test system | |
| CN1503136A (en) | Embedded software test method | |
| CN102222041A (en) | Test analysis system and method based on embedded software | |
| CN106201882A (en) | Automated operating system method of testing based on Jenkins and system | |
| CN105678169A (en) | Binary program vulnerability discovery method and system | |
| CN102243609A (en) | Embedded software-based test analysis method and system | |
| CN110275833B (en) | Universal test equipment and use method | |
| CN100555219C (en) | Atom manipulation encapsulation apparatus and method | |
| CN106649073A (en) | Test method and device based on dynamic script template | |
| CN105740142A (en) | SSR centralized management platform pressure test management system | |
| CN101145970B (en) | System and method for online location of communication system device failures | |
| CN111930078A (en) | Network testing device for core control system | |
| CN105550103B (en) | A kind of automated testing method based on self-defined test script | |
| CN106445810A (en) | Interactive software and device compatibility test method and system | |
| Fabre et al. | Building dependable COTS microkernel-based systems using MAFALDA | |
| CN206476130U (en) | A kind of JL9 aircrafts function modoularization comprehensive automation detecting system | |
| CN109739760B (en) | Code debugging test method and device and storage medium | |
| CN104038388A (en) | Distributed automatic testing system and automatic testing method for Internet of Things | |
| CN105117332B (en) | A kind of detection method of stack overflow position |
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: 20071114 Termination date: 20150328 |
|
| EXPY | Termination of patent right or utility model |