CN1866221A - Software interface testing method and apparatus - Google Patents
Software interface testing method and apparatus Download PDFInfo
- Publication number
- CN1866221A CN1866221A CN 200610057811 CN200610057811A CN1866221A CN 1866221 A CN1866221 A CN 1866221A CN 200610057811 CN200610057811 CN 200610057811 CN 200610057811 A CN200610057811 A CN 200610057811A CN 1866221 A CN1866221 A CN 1866221A
- Authority
- CN
- China
- Prior art keywords
- software interface
- test
- input
- tested
- graphical interfaces
- 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
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The disclosed software interface testing method comprises: according to pre-set grammar format, describing the software interface to be tested, and dynamic generating the GUI for testing. Wherein, it just needs to modify description information and dynamic generate a GUI for testing when the target interface changes. This invention implements seamless transplantation, and improves testing tool expandability and portability fit to different testing request.
Description
Technical field
The present invention relates to the network communications technology field, be specifically related to a kind of software interface test approach and device.
Background technology
Communication terminal or other equipment generally all can provide the software interface of a secondary development or debugging diagnosis, as with the serial ports being AT command set of hardware interface etc., software interface can be controlled many behaviors of communication terminal, as audio call, by key control, fax, GPRS (GPRS) etc.
The test process of software interface is exactly the proof procedure of the interactive information of tester and tested software interface.At present, realize that at similar AT command set the method for software interface test mainly contains following three kinds:
Method one, the software interface test code by hand-coding carry out the software interface test.
This method require the tester to have stronger test code development ability and the test code development workload very big, be unfavorable for extensively carrying out of software interface test job, and, the testing cost height of software interface.Because it is the software interface that products such as communication terminal provide in the early stage can usually change, and causes the test code needs of software interface usually to be revised, and makes the maintenance workload of software interface test code big, maintainable poor.
Method two, the graphical interfaces that encapsulates out by special interface carry out the software interface test, and promptly the graphic interface by special use calls software interface, and carry out the software interface test.
Though this method effectively alleviated the tester the software interface test code write workload, but, when software interface changes, because the graphical interfaces in this method is a kind of graphical interfaces of static state, so, still there is the maintainable poor problem of software interface test code, and, special-purpose graphical interfaces need be made very significantly and revise on being transplanted to other tested systems the time.
Method three, by the dedicated graphics interface not only being provided, but also providing the software interface testing tool of test code hand-coding approach to carry out the software interface test.
This method is actually the combination of method one and method two, software interface testing tool in this method is equivalent to a user application, tested software interface carries out function package with the graphical interfaces form of static state, the tester just can call the corresponding software interface by operating this graphical interfaces, thereby realization is mutual with equipment under test, finishes the software interface test.The software interface testing tool the software interface with equipment under test carry out mutual in, can also export detailed interaction data.Software interface testing tool in this method also provides the function that is used for importing with executive software interface testing code, makes the tester can write the software interface test code according to actual needs, and carries out the software interface test.
Because the graphical interfaces design of this method staticize itself is pointed, make the test subscriber can not increase the element at the shape interface of changing plan and the description of interactive interfacing information without authorization, change at software interface, when perhaps the software interface testing tool need be applied to other new tested order set, need significantly revise the application code of software interface testing tool, so that finish function package to new interface or new tested order set, even if the software interface testing tool provides secondary to revise the package interface mechanism of graphical interfaces, when testing tool is transplanted on the new tested software interface, still need to go significantly to revise the package interface of graphical interfaces, make the software interface test lack dirigibility, can not satisfy Protean testing requirement in the software interface test, can not accomplish hardware and software platform, extensibility, portable poor, be difficult for promoting the use of.
Summary of the invention
The objective of the invention is to, a kind of software interface test approach and device are provided, dynamically generate graphical interfaces by descriptor, realized improving extensibility, the portability of software interface testing tool, satisfy the purpose of various software interface testing requirements according to software interface.
For achieving the above object, a kind of software interface test approach provided by the invention comprises:
A, each software interface of needs being tested according to predetermined syntax format are described;
B, dynamically generate the graphical interfaces of software interface test according to each software interface of described description;
C, carry out the software interface test according to the descriptor of the graphical interfaces correspondence that triggers.
Described step a is specially:
According to predetermined syntax format the description document of each software interface that needs test is set, and described description document is one or more, describes one or more software interfaces in the description document.
The description document of the software interface of described predetermined syntax format comprises: the parameter-definition item of the title of software interface, software interface, the functional description of software interface.
The description document of the software interface of described predetermined syntax format also comprises: one or more in coding before the span tabulation, default value, transmission, the decoding after receiving.
Described step c specifically comprises:
C1, generate corresponding software interface test script according to the graphical interfaces that triggers;
C2, by carrying out test script, corresponding software interface instruction is sent to the tested software interface, and shows the input/output information of tested software interface.
Described method also comprises:
D1, the software interface of importing with the form reception outside of script file instruct;
D2, the software interface in script file instruction is sent to the tested software interface, and shows the input/output information of tested software interface.
Described step b also comprises:
Dynamically generate the input and output rule of software interface instruction according to each software interface of described description;
And the step that shows the input/output information of tested software interface among described step c2 or the d2 is specially:
The information input and output of described tested software interface, that meet described input and output rule is resolved and show according to the descriptor of software interface.
The present invention also provides a kind of software interface proving installation, comprising:
Describing module: be used to store the descriptor that each software interface of needs being tested according to predetermined syntax format is described;
Generate the graphical interfaces module: the descriptor that is used for storing according to describing module dynamically generates graphical interfaces, and output shows;
Software interface test module: be used to trigger generating the graphical interfaces that the graphical interfaces module dynamically generates, and carry out the software interface test according to the descriptor of the graphical interfaces correspondence that is triggered of storing in the describing module.
Described software interface test module comprises:
The generation script submodule: the descriptor that is used for the graphical interfaces correspondence that is triggered of storing according to the graphical interfaces, the describing module that trigger generates and comprises software interface instruction software interface testing script, and test script is transferred to software interface test submodule;
Software interface test submodule: be used to carry out the script file of its reception, the instruction of the software interface in the script is sent to the tested software interface, and show the input/output information of tested software interface.
Described device also comprises:
Outside load module: be used for receiving the software interface instruction of outside input, and the instruction of the software interface in the described script file is transferred to software interface test submodule with the form of script file.
Described device also comprises: generate the input and output rule module;
Generate the input and output rule module: dynamically generate the input and output rule of software interface instruction according to the descriptor of each software interface of storing in the describing module, and with the input and output rale store that generates in describing module;
Software interface test submodule is resolved the information input and output of described tested software interface, that meet described input and output rule according to the input and output rule of storing in the describing module and is shown.
Description by technique scheme as can be known, by with software interface abstract be descriptor, make the software interface testing tool dynamically generate graphical interfaces, and the input and output rule of software interface testing tool and software interface interactive information according to descriptor, when the tested software interface changes, just can realize test by the descriptor of revising each tested software interface, avoid the dirigibility at static graphics interface not enough, shortcomings such as portable poor, poor expandability new similar software interface; When the suitable tested software interface system of software interface testing tool of the present invention changes, only revise or redefine the predetermined syntax format of description document, and regenerate the input and output rule of software interface testing tool and software interface interactive information according to description document, can realize test to new software interface system, realized seamless transplanting, promoted the hardware and software platform of software interface testing tool, strengthen the reusability of software interface testing tool, reduce the use complicacy of software interface testing tool, help carrying out smoothly of test job; Thereby realized improving extensibility, the portability of software interface testing tool by technical scheme provided by the invention, satisfied the purpose of various software interface testing requirements.
Description of drawings
Fig. 1 is the graphical interfaces synoptic diagram that the short message of the embodiment of the invention sends;
Fig. 2 is the information interaction synoptic diagram in the software interface test process of the embodiment of the invention;
Fig. 3 is the software interface test approach process flow diagram of the embodiment of the invention;
Fig. 4 is the software interface proving installation synoptic diagram of the embodiment of the invention.
Embodiment
The core of software interface test approach of the present invention and device all is: describe each software interface that needs are tested according to predetermined syntax format, each software interface according to described description dynamically generates the graphical interfaces that software interface is tested, by triggering graphical interfaces and carrying out the software interface test according to the descriptor of the graphical interfaces correspondence that triggers.
Based on core of the present invention technical scheme provided by the invention is further described below.
The present invention at first needs to determine each tested software interface, promptly definite each software interface that need test, then, the tested software interface is described, as the tested software interface being abstracted into simple software interface description document etc. according to predetermined syntax format according to predetermined syntax format.
Each tested software interface can be distinguished corresponding different description document, promptly a description document only is described a software interface, a plurality of tested software interfaces also can corresponding same description document, promptly comprises the descriptor to a plurality of software interfaces in description document.
The descriptor of tested software interface should mainly comprise: the parameter-definition item of software interface, the title of software interface, the functional description of software interface, descriptor can also comprise: one or more in the decoding after coding, software interface order and parameter received before the tabulation of default value, span, software interface order and parameter sent.
Predetermined syntax format among the present invention can according to actual needs or be accustomed to defining.
Being example with a concrete software interface below describes the descriptor of tested software interface of the present invention.
Descriptor to the instruction that sends SMS message is as follows:
NAME
AT$HSMSSS
FUNCTION
Send SMS message
SEND
AT$HSMSSS=<ack>,<prt>,<fmt>,<prv>,<msg>
SEND_DECODE
……
SEND_ENCODE
……
<ack>
DESCRIPTION
Whether need short message state report
DEFAULT_VALUE
0
VALUE_LIST
0 does not need short message state report
1 needs short message state report
<prt>
DESCRIPTION
Note priority
DEFAULT_VALUE
0
VALUE_LIST
0Normal
1Interactive
2Urgent
3Emergency
<fmt>
DESCRIPTION
Coded system
DEFAULT_VALUE
1
VALUE_LIST
The 1ASCII coding
The 2UNICODE coding
<prv>
DESCRIPTION
Security classification
DEFAULT_VALUE
0
VALUE_LIST
0Normal
1Restricted
2Confidential
3Secret
<msg>
DESCRIPTION
Short message content
ENCODE
……
DECODE
……
In foregoing description information, NAME is the title of software interface, and as the title of AT instruction etc., FUNCTION is the functional description of software interface, and SEND is predetermined syntax format, and NAME, FUNCTION and SEND are the essential key word in the descriptor.In above-mentioned example, the value of NAME is AT$HSMSSS, the instruction that the AT$HSMSSS representative sends SMS message, the value of FUNCTION is for sending SMS message, and the value of SEND is AT$HSMSSS=<ack 〉,<prt 〉,<fmt 〉,<prv 〉,<msg 〉, expression need be carried when sending SMS message<ack 〉,<prt 〉,<fmt 〉,<prv 〉,<msg〉and parameter.
DESCRIPTION is the descriptor of each parameter in the software interface syntax format, VALUE_LIST is that parameter value range list, DEFAULT_VALUE are the acquiescence value of parameter, it is the default value of parameter, ENCODE is the coding before the software interface detecting information sends, and DECODE is the decoding of software interface detecting information after receiving.DESCRIPTION, DEFAULT_VALUE, VALUE_LIST, ENCODE and DECODE etc. are optional keyword.
In the above-mentioned example, the promptly predetermined syntax format of the rules for writing of software interface description document is:
The software interface of NAME appointment is essential unique, must be unique as the AT instruction title of NAME appointment, NAME can with real AT instruction title is identical also can be different.Must use the TAB key to carry out indentation between key word such as NAME, FUNCTION and its value.Key word must be capitalized, and monopolize delegation, parameter name has been drawn together by a pair of angle brackets, and the content of ENCODE/DECODE should be legal scripted code, the normal content of reference parameter in the scripted code, and the end statement need return the final data of this parameter.The extension name of the description document of software interface can be text, i.e. * .txt.
After carrying out the software interface description, the present invention can dynamically generate the graphical interfaces of software interface test and input, the output rule of interactive interfacing information at the description of software interface, and the graphical interfaces that sends as the short message that generates according to the description document in the foregoing description as shown in Figure 1.
Among Fig. 1, user side is by activating " AT$HSMSSS ", the graphical interfaces that the present invention can dynamically generate the menu activation type according to the description document of this software interface in the menu item.
Graphical interfaces of the present invention can be menu activation type graphical interfaces or static window type graphical interfaces.
After generating graphical interfaces, when graphical interfaces is activated, triggering etc. operated, the present invention is the software interface instruction of generation script document form automatically, thereby realize that instruction inputs to the tested software interface intuitively, fast, flexibly as AT with the software interface instruction, select to test short message as user side by the graphical interfaces in the application drawing 1 and send order AT$HSMSSS.Software interface instruction in the script file of the present invention can be carried out edit-modify, and promptly this script file is for can edit executable script file.
The interface instruction that can comprise one or more graphical interfaces correspondences in the script file according to the graphical interfaces generation, be that the present invention can repeatedly activate, trigger same or different graphical interfaces, and add the software interface instruction of the graphical interfaces correspondence that at every turn activates in the current script file cursor place.
The present invention sends to tested interface by carrying out this test script with corresponding software interface instruction, and the present invention can also be from tested software interface receiving software interface instruction.And resolve according to the information of input, output rule to the software interface instruction that is sent to the tested software interface with from the software interface instruction that tested interface receives according to description document, realized the test of software interface.Provided by the invention to tested software interface transmission, meet the function that input, the regular information of output resolve and be equivalent to be provided with a virtual interface layer.
In the above-mentioned example, when test AT$HSMSSS instruction, the information after the virtual interface layer is resolved the information transmission of tested software interface, that meet input, output rule according to the description document of AT$HSMSSS is as follows:
[10:23:34] COM2:AT$HSMSSS=0,3,1,3,Hello?World!
[10:23:34] order: the AT$HSMSSS=<ack that sends SMS message 〉,<prt 〉,<fmt〉and,<prv 〉,<msg 〉
[10:23:34] ack=0 does not need short message state report
[10:23:34] prt=3?Emergency
[10:23:34] fmt=1 ASCII coding
[10:23:34] prv=3?Secret
[10:23:34] msg=Hello?World!
[10:23:34] COM2:AT$HSMSSS=0,3,1,3,Hello?World!
Software interface test approach of the present invention can support the software interface of using always based on AT command set to test, simultaneously, by increasing new interface description document, also can support other AT command interface test on this basis easily, even can also be by revising the predetermined syntax format that software interface is described, and support the test of other software interface of non-AT order according to the input and output rule that description document regenerates software interface testing tool and software interface interactive information.
For software interface test approach of the present invention can be realized flexibly, the present invention can also receive the software interface instruction of the script file form of user side input, and the script file here is for can edit executable script file.The present invention is by carrying out this test script, the software interface instruction of user's input is sent to tested interface, and the software interface instruction that is sent to tested interface is resolved according to the output Rule Information according to description document, simultaneously, the interface instruction that receives from tested interface is resolved according to input rule information, realized the test of software interface.
From top description as can be seen, the present invention only need write out corresponding software interface description document according to the descriptor format of software interface, just can be with the software interface graphical interfacesization, will with the resolving robotization of software interface interactive information, and can generate test script file automatically by graphical interfaces, avoided the process of hand-coding test code, greatly reduce the development amount of test code, reduced the test job amount of software interface, and the technical capability requirement to the tester is low, helps carrying out smoothly of test job.
In addition, when tested software interface system changes, be that a whole set of tested order format is when having change, only need regenerate the input and output rule of software interface testing tool and software interface interactive information according to amended description document, just can easily software interface testing tool of the present invention be transplanted to other software interface system, new software interface is tested, realized seamless transplanting, promoted the hardware and software platform of software interface testing tool, strengthen the reusability of software interface testing tool, reduce the use complicacy of software interface testing tool.
For same set of tested software interface system, in case software interface change, only need just can dynamically revise the interactive information of pattern manipulation interface and updating interface by revising the description text, thus shortcomings such as the dirigibility that has improved the static graphics interface is not enough, portability is poor, operation inconvenience.
Whether the test process of software interface is the proof procedure of information interaction in fact, correct as the information interaction of verifying software interface testing instrument and tested software interface, and accompanying drawing 2 is the information interaction synoptic diagram in the software interface test process of the present invention.
Among Fig. 2, setting need be carried out the software interface test based on a software interface testing tool of software interface test approach of the present invention, and software interface test process then of the present invention comprises: the information interaction between the information interaction between user side and the testing tool, testing tool and the tested software interface.
Information interaction between user side and the testing tool comprises: the importation 1., 4. and 5., output is 6..Information interaction between testing tool and the tested software interface comprises: input 8..
1. for user side is provided with the process of description document according to testing requirement, promptly user side becomes simple software interface description document according to its understanding to tested software interface such as AT instruction interface etc. with the tested software interface conversion.2. be the process that generates graphical interfaces according to the descriptor in the description document of the present invention.5. activate, trigger the process that graphical interfaces carries out the software interface test for user side.3. be the process that generates the corresponding script file according to the graphical interfaces that user side activates, triggers.4. can edit or the direct process of Input Software interface instruction in script file the instruction of the software interface in the script file that generates for user side.6. being in the software interface execution process instruction, instructing to tested software interface Input Software interface instruction such as AT, and resolve the process of carrying out, also is the resolving to the AT command information of exporting from software interface.8. being the process that the software interface instruction after resolving is imported to the tested software interface by physical port such as serial ports, also is software interface is exported its detecting information by physical port such as serial ports process.
Describe below in conjunction with 3 pairs of software interface test processs of the present invention of accompanying drawing.
Among Fig. 3,, begin software interface test process of the present invention in step 300.
To step 310, the testing tool initialization is provided with the description document of software interface according to the tested software interface, and loads description document in testing tool equipment.
To step 320, dynamically generate graphical interfaces and input and output rule according to description document, the graphical interfaces here can be menu activation type graphical interfaces or static window type graphical interfaces.After the testing tool initialization is finished, the user can trigger or activation manipulation graphical interfaces, trigger or activation manipulation in case have, to step 330, testing tool judges whether the graphical interfaces that the user triggers is the graphical interfaces that withdraws from, if the graphical interfaces that withdraws from, to step 331, withdraw from testing tool, this software interface test process finishes.
In step 330, if not the graphical interfaces that withdraws from, to step 340, testing tool continues to judge whether the graphical interfaces that the user triggers is the graphical interfaces that carries out the software interface test, if the graphical interfaces that is triggered is not the graphical interfaces of software interface test, to step 341, testing tool is carried out corresponding other operations according to the graphical interfaces that triggers, and after executing other operations,, wait for triggering or the activation manipulation of user to graphical interfaces to step 320.
In step 340, if it is the graphical interfaces of software interface test that testing tool is judged the graphical interfaces of user's triggering, to step 350, testing tool encapsulates automatically to the software interface instruction of the graphical interfaces correspondence that triggers or activate, and generate can edit, executable script file.In this step, can edit the software interface instruction in the automatic script file that generates of testing tool.
To step 360, testing tool is carried out this script file.
To step 370, testing tool judges one by one according to sequencing whether the software interface instruction that is committed to the virtual interface layer is arranged in the executed script file, that is to say, testing tool judges whether the software interface instruction that need transfer to the tested software interface is arranged in the executed script file, if the software interface instruction that need be committed to the virtual interface layer is arranged, to step 380,381, the instruction of software interface in the script file is sent to tested software interface, and it is mutual that promptly virtual interface layer and tested interface carry out original order input and output.To step 390, testing tool finds correspondence to meet the information of the input and output rule of this order, and resolves and export according to the description document of having loaded in the step 310.Be that testing tool is resolved the software interface instruction of the input of virtual interface layer, output according to the input in the description document, output Rule Information.
In step 370,,, continue script file is handled to step 371 if there is not to be committed to the software interface instruction of virtual interface layer.
To step 372, whether the software interface instruction in the judgement script file disposes, if do not dispose, to step 370, testing tool continues to judge one by one whether the software interface instruction that is committed to the virtual interface layer is arranged in the script file.
In step 372,,, wait for triggering or the activation manipulation of user to graphical interfaces to step 320 if the instruction of the software interface in the script file disposes.
In the above-mentioned flow process, step 370,371,372 and step 380 be exactly the implementation of script file, have only when script file has been carried out software interface order place, just the processing of virtual interface layer submitted in the software interface order in the script file.
Software interface proving installation of the present invention is the software interface testing tool as shown in Figure 4.The software interface proving installation mainly comprises among Fig. 4: describing module, generate following interface module, software interface test module, outside load module and generate the input and output rule module.
Describing module is mainly used in the descriptor of each software interface that the needs of storing predetermined syntax format test, the descriptor of a software interface can corresponding description document, description document also can corresponding a plurality of software interfaces descriptor, the specifying information that comprises in the description document is like the description in the said method.
Generation graphical interfaces module is mainly used in according to the descriptor of storing in the describing module and dynamically generates graphical interfaces, and output shows.The graphical interfaces here such as menu activation type graphical interfaces or static window type graphical interfaces etc.Concrete as the description in the above-mentioned method.
The software interface test module is mainly used in to trigger and generates the graphical interfaces that the graphical interfaces module dynamically generates, and carries out the software interface test according to the descriptor of the graphical interfaces correspondence that is triggered of storing in the describing module.The software interface test module is made up of generation script submodule, software interface test submodule.
The descriptor generation that the generation script submodule is mainly used in according to the graphical interfaces correspondence that is triggered of storing in the graphical interfaces that has triggered or activated, the describing module comprises software interface instruction software interface testing script, the software interface instruction to the graphical interfaces correspondence that triggers or activate just encapsulates automatically, and generate can edit, executable script file.The generation script submodule transfers to software interface test submodule with test script.This script file for can edit, executable script file.
Generate the input and output rule module and be mainly used in the input and output rule that dynamically generates the software interface instruction according to the descriptor of each software interface of storing in the describing module, and with the input and output rale store that generates in describing module.
Software interface test submodule is mainly used in the script file of carrying out its reception, software interface in script instruction is sent to the tested software interface, and the information input and output of described tested software interface, that meet the input and output rule is resolved and show according to the input and output rule of storing in the describing module.
The form that outside load module is mainly used in script file receives the software interface instruction that the user side transmission comes, promptly receive the software interface instruction of input software interface testing tool of the present invention, and this script file transferred to software interface test submodule, carry out this script file by software interface test submodule.
Software interface proving installation of the present invention can be the software test device based on the AT command set of serial ports, at this moment, when software interface proving installation of the present invention need be transplanted to the software interface of non-serial communication or non-AT command set, only need to upgrade the descriptor of storing in the describing module, and make and generate the input and output rule module and regenerate the input and output rule and get final product.
Though described the present invention by embodiment, those of ordinary skills know, the present invention has many distortion and variation and do not break away from spirit of the present invention, and the claim of application documents of the present invention comprises these distortion and variation.
Claims (11)
1, a kind of software interface test approach is characterized in that, comprising:
A, each software interface of needs being tested according to predetermined syntax format are described;
B, dynamically generate the graphical interfaces of software interface test according to each software interface of described description;
C, carry out the software interface test according to the descriptor of the graphical interfaces correspondence that triggers.
2, a kind of software interface test approach as claimed in claim 1 is characterized in that, described step a is specially:
According to predetermined syntax format the description document of each software interface that needs test is set, and described description document is one or more, describes one or more software interfaces in the description document.
3, a kind of software interface test approach as claimed in claim 2 is characterized in that, the description document of the software interface of described predetermined syntax format comprises: the parameter-definition item of the title of software interface, software interface, the functional description of software interface.
4, a kind of software interface test approach as claimed in claim 3 is characterized in that, the description document of the software interface of described predetermined syntax format also comprises: one or more in coding before the span tabulation, default value, transmission, the decoding after receiving.
5, a kind of software interface test approach as claimed in claim 1 is characterized in that, described step c specifically comprises:
C1, generate corresponding software interface test script according to the graphical interfaces that triggers;
C2, by carrying out test script, corresponding software interface instruction is sent to the tested software interface, and shows the input/output information of tested software interface.
6, a kind of software interface test approach as claimed in claim 1 is characterized in that, described method also comprises:
D1, the software interface of importing with the form reception outside of script file instruct;
D2, the software interface in script file instruction is sent to the tested software interface, and shows the input/output information of tested software interface.
7, as claim 5 or 6 described a kind of software interface test approach, it is characterized in that described step b also comprises:
Dynamically generate the input and output rule of software interface instruction according to each software interface of described description;
And the step that shows the input/output information of tested software interface among described step c2 or the d2 is specially:
The information input and output of described tested software interface, that meet described input and output rule is resolved and show according to the descriptor of software interface.
8, a kind of software interface proving installation is characterized in that, comprising:
Describing module: be used to store the descriptor that each software interface of needs being tested according to predetermined syntax format is described;
Generate the graphical interfaces module: the descriptor that is used for storing according to describing module dynamically generates graphical interfaces, and output shows;
Software interface test module: be used to trigger generating the graphical interfaces that the graphical interfaces module dynamically generates, and carry out the software interface test according to the descriptor of the graphical interfaces correspondence that is triggered of storing in the describing module.
9, a kind of software interface proving installation as claimed in claim 8 is characterized in that, described software interface test module comprises:
The generation script submodule: the descriptor that is used for the graphical interfaces correspondence that is triggered of storing according to the graphical interfaces, the describing module that trigger generates and comprises software interface instruction software interface testing script, and test script is transferred to software interface test submodule;
Software interface test submodule: be used to carry out the script file of its reception, the instruction of the software interface in the script is sent to the tested software interface, and show the input/output information of tested software interface.
10, a kind of software interface proving installation as claimed in claim 9 is characterized in that described device also comprises:
Outside load module: be used for receiving the software interface instruction of outside input, and the instruction of the software interface in the described script file is transferred to software interface test submodule with the form of script file.
11, as claim 9 or 10 described a kind of software interface proving installations, it is characterized in that described device also comprises: generate the input and output rule module;
Generate the input and output rule module: dynamically generate the input and output rule of software interface instruction according to the descriptor of each software interface of storing in the describing module, and with the input and output rale store that generates in describing module;
Software interface test submodule is resolved the information input and output of described tested software interface, that meet described input and output rule according to the input and output rule of storing in the describing module and is shown.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNB2006100578110A CN100383755C (en) | 2006-02-27 | 2006-02-27 | Software interface testing method and apparatus |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNB2006100578110A CN100383755C (en) | 2006-02-27 | 2006-02-27 | Software interface testing method and apparatus |
Publications (2)
Publication Number | Publication Date |
---|---|
CN1866221A true CN1866221A (en) | 2006-11-22 |
CN100383755C CN100383755C (en) | 2008-04-23 |
Family
ID=37425246
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CNB2006100578110A Expired - Fee Related CN100383755C (en) | 2006-02-27 | 2006-02-27 | Software interface testing method and apparatus |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN100383755C (en) |
Cited By (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101645808B (en) * | 2009-05-15 | 2012-01-04 | 天津七一二通信广播有限公司 | Method for testing communication terminal by adopting analogue feedback frame |
CN104077216A (en) * | 2013-03-28 | 2014-10-01 | 腾讯科技(深圳)有限公司 | Software test method and test device |
WO2015000314A1 (en) * | 2013-07-05 | 2015-01-08 | 中兴通讯股份有限公司 | Interface call system and method |
CN104615534A (en) * | 2015-01-28 | 2015-05-13 | 广州酷狗计算机科技有限公司 | Interface test method and device |
CN104809056A (en) * | 2014-01-27 | 2015-07-29 | 阿里巴巴集团控股有限公司 | Interface testing code generating method and device |
CN105204991A (en) * | 2015-08-28 | 2015-12-30 | 青岛海尔智能家电科技有限公司 | Internet of things test method and device |
CN105373469A (en) * | 2014-08-25 | 2016-03-02 | 广东金赋信息科技有限公司 | Interface based software automation test method |
CN105490881A (en) * | 2015-12-09 | 2016-04-13 | 北京交控科技股份有限公司 | Configurable data interface test method and system |
CN105528294A (en) * | 2015-12-29 | 2016-04-27 | 广东金赋信息科技有限公司 | Method and system for automatically generating interface testing case |
CN106330593A (en) * | 2015-07-01 | 2017-01-11 | 中兴通讯股份有限公司 | Protocol detection method and device |
CN106874188A (en) * | 2016-12-30 | 2017-06-20 | 北京五八信息技术有限公司 | Software interface test approach and device |
CN108614906A (en) * | 2016-12-09 | 2018-10-02 | 厦门紫光展锐科技有限公司 | A kind of generation method and system of I/O interface feature database |
CN109960492A (en) * | 2018-10-15 | 2019-07-02 | 扬州万方电子技术有限责任公司 | A kind of detection system and its application method based on QT platform |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102571761B (en) * | 2011-12-21 | 2014-08-20 | 四川长虹电器股份有限公司 | Information transmission method of network interface |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5991537A (en) * | 1997-09-16 | 1999-11-23 | The United States Of America As Represented By The Secretary Of The Navy | VXI test executive |
US6378088B1 (en) * | 1998-07-14 | 2002-04-23 | Discreet Logic Inc. | Automated test generator |
CN100417075C (en) * | 2001-09-10 | 2008-09-03 | 中兴通讯股份有限公司 | Interface test method |
CN1519725A (en) * | 2003-01-20 | 2004-08-11 | 英业达股份有限公司 | Visual method ofr testing object |
CN1314225C (en) * | 2003-10-24 | 2007-05-02 | 中兴通讯股份有限公司 | System for realizing open telecommunication business based on XML file and thereof |
-
2006
- 2006-02-27 CN CNB2006100578110A patent/CN100383755C/en not_active Expired - Fee Related
Cited By (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101645808B (en) * | 2009-05-15 | 2012-01-04 | 天津七一二通信广播有限公司 | Method for testing communication terminal by adopting analogue feedback frame |
CN104077216A (en) * | 2013-03-28 | 2014-10-01 | 腾讯科技(深圳)有限公司 | Software test method and test device |
CN104077216B (en) * | 2013-03-28 | 2018-04-27 | 腾讯科技(深圳)有限公司 | Method for testing software and test device |
WO2015000314A1 (en) * | 2013-07-05 | 2015-01-08 | 中兴通讯股份有限公司 | Interface call system and method |
US9898352B2 (en) | 2013-07-05 | 2018-02-20 | Zte Corporation | Interface call system and method |
CN104809056A (en) * | 2014-01-27 | 2015-07-29 | 阿里巴巴集团控股有限公司 | Interface testing code generating method and device |
CN104809056B (en) * | 2014-01-27 | 2018-10-02 | 阿里巴巴集团控股有限公司 | A kind of generation method and device of interface testing code |
CN105373469B (en) * | 2014-08-25 | 2018-09-04 | 广东金赋科技股份有限公司 | A kind of software automated testing system and method based on interface |
CN105373469A (en) * | 2014-08-25 | 2016-03-02 | 广东金赋信息科技有限公司 | Interface based software automation test method |
CN104615534A (en) * | 2015-01-28 | 2015-05-13 | 广州酷狗计算机科技有限公司 | Interface test method and device |
CN104615534B (en) * | 2015-01-28 | 2017-08-01 | 广州酷狗计算机科技有限公司 | interface test method and device |
CN106330593A (en) * | 2015-07-01 | 2017-01-11 | 中兴通讯股份有限公司 | Protocol detection method and device |
CN106330593B (en) * | 2015-07-01 | 2021-03-26 | 中兴通讯股份有限公司 | Protocol detection method and device |
CN105204991A (en) * | 2015-08-28 | 2015-12-30 | 青岛海尔智能家电科技有限公司 | Internet of things test method and device |
CN105490881A (en) * | 2015-12-09 | 2016-04-13 | 北京交控科技股份有限公司 | Configurable data interface test method and system |
CN105528294B (en) * | 2015-12-29 | 2018-05-25 | 广东金赋科技股份有限公司 | The method and system that a kind of interface testing use-case automatically generates |
CN105528294A (en) * | 2015-12-29 | 2016-04-27 | 广东金赋信息科技有限公司 | Method and system for automatically generating interface testing case |
CN108614906A (en) * | 2016-12-09 | 2018-10-02 | 厦门紫光展锐科技有限公司 | A kind of generation method and system of I/O interface feature database |
CN108614906B (en) * | 2016-12-09 | 2021-11-26 | 厦门紫光展锐科技有限公司 | Method and system for generating IO interface feature library |
CN106874188A (en) * | 2016-12-30 | 2017-06-20 | 北京五八信息技术有限公司 | Software interface test approach and device |
CN106874188B (en) * | 2016-12-30 | 2020-05-12 | 北京五八信息技术有限公司 | Software interface testing method and device |
CN109960492A (en) * | 2018-10-15 | 2019-07-02 | 扬州万方电子技术有限责任公司 | A kind of detection system and its application method based on QT platform |
Also Published As
Publication number | Publication date |
---|---|
CN100383755C (en) | 2008-04-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN1866221A (en) | Software interface testing method and apparatus | |
CN1828591A (en) | Command-line data-type discovery and conversion | |
CN1258137C (en) | Control apparatus | |
CN1308823C (en) | Terminal device | |
CN1300389A (en) | Apparatus and method for conversion of messages | |
CN1725177A (en) | Built-in equipment integrated development system and using method thereof | |
CN1491382A (en) | System and method for providing dialog management and arbitration in multi-modal environment | |
CN1908894A (en) | Brew-based dynamic user interface system structure and method for realization | |
CN1767453A (en) | Automatic test method and system | |
CN1643573A (en) | Audio video conversion apparatus and method, and audio video conversion program | |
CN1882146A (en) | Device and method for sending and receiving voice call contents | |
CN1737779A (en) | Method and system for expanding peripherals | |
CN1859177A (en) | Method for processing customized task in equipment management | |
CN1848889A (en) | Multimodal service session establishing and providing method, multimodal service session establishing and providing system | |
CN1167011C (en) | Method of testing several kinds of application protocol | |
CN1790957A (en) | Apparatus testing method | |
CN1499359A (en) | Communicating device, program and recording medium | |
CN1069583A (en) | Generate many editions panels by the single panel defined file | |
CN102625266A (en) | Intelligent terminal and information processing method thereof | |
CN101068119A (en) | Trunk state detecting method, device and testing information terminal equipment thereof | |
CN101047555A (en) | Detection method for quality of equipment | |
CN1200516A (en) | Method and apparatus for information processing using electronic mail, storage medium for storing program for controlling information processing apparatus | |
CN1862488A (en) | Method of dynamic binding displaying of control element and multi-language text in computer system | |
CN1770108A (en) | Online software updating method | |
CN1645326A (en) | Method and system for updating software function |
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 | ||
C41 | Transfer of patent application or patent right or utility model | ||
TR01 | Transfer of patent right |
Effective date of registration: 20160425 Address after: American California Patentee after: Snaptrack, Inc. Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Patentee before: Huawei Technologies Co., Ltd. |
|
CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20080423 Termination date: 20200227 |
|
CF01 | Termination of patent right due to non-payment of annual fee |