CN1632747A - Software interface testing method - Google Patents
Software interface testing method Download PDFInfo
- Publication number
- CN1632747A CN1632747A CN 200310121900 CN200310121900A CN1632747A CN 1632747 A CN1632747 A CN 1632747A CN 200310121900 CN200310121900 CN 200310121900 CN 200310121900 A CN200310121900 A CN 200310121900A CN 1632747 A CN1632747 A CN 1632747A
- Authority
- CN
- China
- Prior art keywords
- test
- interface
- function
- test interface
- case file
- 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
This invention discloses a software interface test method, which comprises the following steps: first to use the test sample file for XML analysis; to get a function name of the test interface in order of the sample file forms; to get the test interface function pointer according to the relation between the interface and the pointer; to further analyze the test sample file interface; finally to input the sample file test interface parameters into the test interface function for test; to output the current test results and return to the next software interface test.
Description
Technical field
The present invention relates to the computer software testing technology, be meant a kind of software interface test approach especially.
Background technology
Along with extend markup language (XML) technology is constantly ripe, its application also more and more widely.The data layout ability to express of XML is very strong, and nearly all data structure can be come out with the formal representation of XML, can adopt the XML language to carry out program development on any platform.In addition, it is exactly data and display separation that XML also has a very important characteristic, and what promptly be shown to the user is document form, and inside then can be data mode.
Software test is a very important link in the soft project, and the test of software interface is a crucial part in the software test, it all has application in unit testing and integration testing, the stability of guaranteed interface only could guarantee the stability of whole software program.But carrying out software interface when test now, often all is that the tester writes test procedure voluntarily and tests.Because the complicacy that test case file and test code etc. are write, so the tester often feels difficulty very when carrying out the software interface test, not only the time flower is very long, but also not necessarily reaches good effect.
Thereby, according to some common ground in the software interface test, attempt having proposed some general software interface testing schemes in the prior art.Common feature at a certain class software interface test, necessary operation steps in the test process is integrated, when carrying out the software interface test like this, the software test personnel only need to write test case file at the software interface of needs test just can finish test with a small amount of interface testing function.But because the kind of software interface test is more, particularly software development institute based on the platform difference, so the versatility and the dirigibility of existing software interface testing scheme are good inadequately, can't cross-platformly use; In addition, owing to carry out test case file in the prior art when writing, the design documentation of test case file adopts document form usually, the test code of test case file then must adopt data layout to write, form disunity between the two, when occurring not matching between test case file indoor design document and the test code etc. when wrong, be difficult to be found, particularly test code itself also mistake can occur, and because test code adopts data layout, the tester is difficult to check and therefrom finds mistake, thereby influences the reliability that software interface is tested.
Summary of the invention
In view of this, fundamental purpose of the present invention is to provide a kind of software interface test approach, improves versatility, the reliability of software interface test, and is user-friendly.
A kind of software interface test approach may further comprise the steps:
A) the used test case file of software interface test write of call XML form carries out XML to this test case file and resolves;
B) obtain the function name of a test interface in proper order according to the test case file form after resolving, this test interface is as current test interface;
C) function name of the test interface that obtains according to step b) and the corresponding relation of function pointer obtain the function pointer of this test interface;
D) the test interface function pointer that obtains according to step c) calls the test interface function, by this test interface function current test interface corresponding parameters in the test case file is further carried out XML and resolves;
E) step d) is resolved current test interface corresponding parameters input step d in the test case file of back) the test interface function that obtains tests;
F) with the test result output of current test interface, judge whether current test case file also has the not test interface function of test, if, then return step b), otherwise, process ends.
This method is set up the corresponding tables of test interface function name and test interface function pointer in advance, then step c) specifically comprises: the function name of the current test interface that obtains according to step b), by inquiry test interface function name and test interface function corresponding tables, obtain the function pointer of current test interface.
This method step a) described XML resolves to and utilizes the XML resolver to carry out XML to resolve.
This method step f) described output comprises: actual output parameter value, and the comparative result of desired output parameter value and actual output parameter value.
This method step f) described output further comprises: to zero-time, input parameter value and the detection concluding time of each software interface detection.
If the current test case file test interface function of test not in the described step f) of this method then further comprises: judge whether the test case file that need call in addition, if, then return step a), otherwise, process ends.
From above as can be seen, the test case file of software interface adopts the XML form to write in the software interface test approach provided by the invention, and finish test case file and interface testing function calls automatically, can carry out the software interface test under the various platforms, improve the versatility of software interface test; And by ingenious data and the show sepn that utilizes XML, design documentation and test code in the test case file have been unified, solved matching problem between the two, and the tester that is more convenient for checks to test case file, improved the reliability of software interface test; By finishing test case file and interface testing function call automatically, simplified tester's workload greatly simultaneously, made the software interface test convenient.
Description of drawings
Fig. 1 is a software interface testing total body structure block diagram of the present invention;
Fig. 2 is a software interface test flow chart of the present invention.
Embodiment
The present invention is further described in more detail below in conjunction with drawings and the specific embodiments.
The invention provides the general frame of test procedure, the tester only needs the Software Interface Design interface testing function at the needs test, and adopts the XML language format to write test case file.The software interface test used test use-case file that can utilize the automatic call XML form of the present invention program to write then carries out XML to this test case file and resolves; Obtain the function name of a test interface in proper order according to the test case file form after resolving; According to the function name of test interface and the corresponding relation of function pointer, obtain the function pointer of this test interface; Call the test interface function according to the test interface function pointer, by this test interface function current test interface corresponding parameters in the test case file is further carried out XML and resolve; At last, will resolve the back test case file in current test interface corresponding parameters input test interface function test; With current test interface test result output, and return the test of carrying out next software interface according to the requirement of test case file.
The process of carrying out software interface test according to the present invention program, can be referring to shown in Figure 1:
At first, prepare used test case file and the software interface trial function collection of software interface test.
Step 101, utilization provides is used to the application programming interface (API that reads in parameter, comparative parameter and write daily record, Application Programming Interface), at each software interface to be tested, write the interface testing function that is used for each software interface test, and the total interface trial function is formed collection of functions.
The tester can not need to consider test case in the compiling procedure, needs only the clearly object of test, and each interface that need test is created a function.This function mainly is responsible for finishing from test case file and is read in input parameter value and desired output parameter value, and the test case file that the XML form is write is carried out further XML resolve, go back cocoa in addition and further actual output parameter value and desired output parameter value are compared, comparative result is write journal file.
Step 102, software interface collection of functions are set up the trial function title of software interface and the corresponding tables of the corresponding interface trial function after setting up and finishing.The corresponding relation of regulation interface testing function name and interface testing function pointer in the corresponding tables.
Step 103 is utilized XML language compilation test case file.
Test case file is used to the whole test procedure of software interface that concrete test parameter is provided, and wherein should include the interface name of test and concrete content measurement etc.Test case file can be that an interface is tested, and also can test a plurality of interfaces.Utilize the characteristic of XML language data and display separation, the user is as long as finish a test case file with XML, just can obtain the test case code of corresponding data mode, and utilize extensible style language conversion (XLST) technology simultaneously, directly on browser, view the test case document of document form.
Wherein, this step 103 also can with step 101 parallel processing, or carry out step 103 earlier and write test case file, carry out step 101 again and write software interface trial function collection and also can.
It is as follows that the present invention writes the XML form that test case file uses:
＜TestCases loop=" 1 "〉be the root node of this XML file.Wherein it has the number of times that an attribute loop specifies whole use-case to carry out, and default value is " 1 ".Its lower node comprises:
＜Comment〉be the note of whole test case file, the purposes of this test case file is described.
＜Initialize〉be before carrying out each concrete use-case, may need to do some initial work, these work are to finish under this node.
＜Exit〉be after executing all use-cases, to need to do some tailing in works, these work are to finish under this node.
＜TestCase name=" DM001 " sleep=" 0 " loop=" 2 " tempreset=" true "〉be the realization node of concrete each use-case.Attribute name is the title or the numbering of this use-case; Attribute sleep is used to specify to execute to need time of waiting for after this use-case, and its unit be a millisecond, represents to wait for that the user confirms to continue the use-case of execution back if value is " 1 "; Attribute loop is used to specify to carry out this use-case cycle index, and default value is " 1 "; Attribute tempreset was used to specify before carrying out this use-case whether remove all temporary variables.
＜Function name=" Test_B_RentService " sleep=" 0 " loop=" 1 " fault=" continue "〉be exactly to finish the node that test interface calls.It can be＜Initialize 〉,＜Exit 〉,＜TestCase〉and child node.Attribute name is the title of trial function; Attribute sleep need after executing this trial function to be used to time of waiting for, and its unit is a millisecond, must wait for that the user confirms to continue the trial function of execution back if value is " 1 " expression; Attribute loop is used to specify the cycle index of carrying out this trial function, and default value is " 1 "; Down carry out if attribute fault is incorrect whether also continuation of result that is used to specify the test corresponding interface of trial function, " exit " expression is directly withdrawed from, and mistake is ignored in " continue " expression, continues to carry out.
＜IN〉node comprises is the input parameter value of tested interface needs.
＜OUT〉node comprises is the desired output parameter value of tested interface needs.
＜Parameter name=" RC " type=" string " encoding=" text " valuetype=" fixed " compare=" e " load=" 2 " save=" 3 "〉be to be used for node to the assignment of parameter.Attribute name is the title of the parameter of test interface needs; Attribute type is the type of the parameter of test interface needs, and wherein, " string " is character string type; " int " is the shaping numeric type; " struct " represents structure type; " null " expression null pointer type; Attribute encoding is a kind of coded system of this node content as the value of parameter, and wherein, " text " expression is that content is printable text string; " hex " expression is represented a binary data with the ASCII character of 16 systems; " file " expression data are to take out in the file of node content appointment; Attribute valuetype is the type of the value of parameter, and wherein, " fixed " represents that this value is unique; " floating " represents that this value changes; " optional " represents that this value is not unique, but limited several values; Attribute compare is the manner of comparison of specifying the result of actual result and expectation, and wherein, " e " expression is done and equated relatively; " le " expression is done smaller or equal to comparing; Attribute load and save are used for transmitting two parameter values between the test interface in the present invention, the meaning representation temporary variable unit number of the value of load and save.When transmitting parameter, at first value save is arrived in certain unit number, when using this value, as long as the same unit number of load just can take out value.
＜Value〉be as＜Parameter the attribute valuetype of node is used to give the node of a plurality of probable values of parameter during for " optional ".
Step 104, be used for the test case file of software interface test and interface function collection write finish after, can carry out the software interface test.
This testing process is referring to shown in Figure 2:
Here, because test case file is normally tested a plurality of interfaces, generally be the function name of obtaining test interface according to the form of test case file in proper order therefore, wherein, the corresponding function name of test interface.
In this step for some complicated test case, between a plurality of interfaces, transmit the value of parameter if desired, can the interface function output parameter of certain interface temporarily be preserved by the requirement of test case, when calling next interface function and test, with the parameter of preserving a input value as interface function, input in this next one interface function and test, so can be implemented in the value of transmitting parameter between a plurality of interfaces, so that satisfy the requirement of complicated test case.
Step 105 after test procedure executes, can generate corresponding journal file.The test log content comprises: the concluding time of the zero-time of each software interface test, input parameter value, desired output result, each software interface test, actual output result and actual output result and desired output result's comparative result.These information all are taking statistics and analyze the data that provide the foundation afterwards, and also similar with test case file, journal file also can directly be checked with browser.After this, the tester both can carry out manual analysis to test result, also can utilize SDK further to write the statistical analysis program of test result, so that a large amount of test results is assessed.
The tester writes at the software test interface in the present invention program a test case file and test interface function a module as whole procedure, call relation between the module all can be realized automatically, finishes automatically and read in input parameter and the desired output parameter that needs from test case file.Simplify the workload of the test procedure of tester's exploitation like this, and reduced the chance that the problem of test procedure own occurs.
The above only is preferred embodiment of the present invention, and is in order to restriction the present invention, within the spirit and principles in the present invention not all, any modification of being done, is equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (6)
1, a kind of software interface test approach is characterized in that, may further comprise the steps:
A) the used test case file of software interface test write of call XML form carries out XML to this test case file and resolves;
B) obtain the function name of a test interface in proper order according to the test case file form after resolving, this test interface is as current test interface;
C) function name of the test interface that obtains according to step b) and the corresponding relation of function pointer obtain the function pointer of this test interface;
D) the test interface function pointer that obtains according to step c) calls the test interface function, by this test interface function current test interface corresponding parameters in the test case file is further carried out XML and resolves;
E) step d) is resolved current test interface corresponding parameters input step d in the test case file of back) the test interface function that obtains tests;
F) with the test result output of current test interface, judge whether current test case file also has the not test interface function of test, if, then return step b), otherwise, process ends.
2, according to the described method of claim 1, it is characterized in that, set up the corresponding tables of test interface function name and test interface function pointer in advance, then step c) specifically comprises: the function name of the current test interface that obtains according to step b), by inquiry test interface function name and test interface function corresponding tables, obtain the function pointer of current test interface.
According to the described method of claim 1, it is characterized in that 3, the described XML of step a) resolves to and utilizes the XML resolver to carry out the XML parsing.
According to the described method of claim 1, it is characterized in that 4, the described output of step f) comprises: actual output parameter value, and the comparative result of desired output parameter value and actual output parameter value.
According to the described method of claim 4, it is characterized in that 5, the described output of step f) further comprises: to zero-time, input parameter value and the detection concluding time of each software interface detection.
6, according to the described method of claim 1, it is characterized in that, if the test interface function that current test case file is not tested in the described step f), then further comprise: judge whether the test case file that need call in addition, if then return step a), otherwise, process ends.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200310121900 CN1277186C (en) | 2003-12-22 | 2003-12-22 | Software interface testing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200310121900 CN1277186C (en) | 2003-12-22 | 2003-12-22 | Software interface testing method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1632747A true CN1632747A (en) | 2005-06-29 |
| CN1277186C CN1277186C (en) | 2006-09-27 |
Family
ID=34844330
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 200310121900 Expired - Fee Related CN1277186C (en) | 2003-12-22 | 2003-12-22 | Software interface testing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1277186C (en) |
Cited By (32)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100361082C (en) * | 2005-08-26 | 2008-01-09 | 北京中星微电子有限公司 | Method for calling function containing pointer parameter between different operation platforms |
| CN100363906C (en) * | 2006-02-28 | 2008-01-23 | 华为技术有限公司 | Method for testing software unit |
| CN100444127C (en) * | 2006-12-12 | 2008-12-17 | 北京中星微电子有限公司 | System and method for testing software |
| CN100458703C (en) * | 2005-08-26 | 2009-02-04 | 北京中星微电子有限公司 | A cross-platform function call system |
| CN100458702C (en) * | 2005-08-26 | 2009-02-04 | 北京中星微电子有限公司 | A method of function call between different running platforms |
| CN101488085A (en) * | 2008-01-17 | 2009-07-22 | 中兴通讯股份有限公司 | Software interface test method and apparatus |
| CN101650655A (en) * | 2009-09-07 | 2010-02-17 | 苏州瀚瑞微电子有限公司 | Method for analyzing test data of chip |
| CN1952818B (en) * | 2005-10-22 | 2010-12-15 | 康佳集团股份有限公司 | Testing method of program unit with capability of checking test result automatically |
| CN101944062A (en) * | 2010-09-21 | 2011-01-12 | 中国人民解放军63961部队 | Method for configuring universal virtual instrument interface |
| CN101944026A (en) * | 2010-09-21 | 2011-01-12 | 中国人民解放军63961部队 | Implementation method of universal virtual instrument interface |
| CN101980173A (en) * | 2010-11-03 | 2011-02-23 | 北京世纪高通科技有限公司 | Method and device for system integrated test |
| CN101699409B (en) * | 2009-09-30 | 2011-09-14 | 深圳市普联技术有限公司 | Method for controlling testing equipment to test and system thereof |
| CN102999329A (en) * | 2012-11-05 | 2013-03-27 | 浙江吉利汽车研究院有限公司杭州分公司 | Active directory interface developing method based on extensive markup language mapping configuration |
| CN103049378A (en) * | 2012-12-18 | 2013-04-17 | 惠州市亿能电子有限公司 | Program debugging method without emulator |
| CN103778052A (en) * | 2012-10-17 | 2014-05-07 | 百度在线网络技术（北京）有限公司 | Method and device for front end javascript code testing |
| CN104035859A (en) * | 2013-03-07 | 2014-09-10 | 腾讯科技（深圳）有限公司 | Visualized automatic testing method and system thereof |
| CN104360920A (en) * | 2014-12-02 | 2015-02-18 | 微梦创科网络科技（中国）有限公司 | Automatic testing method and device for interface |
| CN104615534A (en) * | 2015-01-28 | 2015-05-13 | 广州酷狗计算机科技有限公司 | Interface test method and device |
| CN105139892A (en) * | 2015-09-23 | 2015-12-09 | 浪潮(北京)电子信息产业有限公司 | Data driving test method and system applied to storage product |
| CN105138461A (en) * | 2015-09-23 | 2015-12-09 | 网易（杭州）网络有限公司 | Interface testing method and device for application program |
| CN105528294A (en) * | 2015-12-29 | 2016-04-27 | 广东金赋信息科技有限公司 | Method and system for automatically generating interface testing case |
| CN106021111A (en) * | 2016-05-30 | 2016-10-12 | 上海携程商务有限公司 | Interface testing method and system |
| CN106502916A (en) * | 2016-12-05 | 2017-03-15 | 广州唯品会信息科技有限公司 | Method for testing software and system |
| CN106547684A (en) * | 2015-09-22 | 2017-03-29 | 腾讯科技（深圳）有限公司 | A kind of method of testing of application program, test device and mobile terminal |
| CN106598851A (en) * | 2016-12-05 | 2017-04-26 | 广州唯品会信息科技有限公司 | Software interface test method and system |
| CN107247665A (en) * | 2017-05-18 | 2017-10-13 | 北京信安世纪科技有限公司 | A kind of method of testing and system of C interface function |
| CN107329861A (en) * | 2017-06-12 | 2017-11-07 | 北京奇安信科技有限公司 | A kind of multiplex roles method of testing and device |
| CN107562614A (en) * | 2016-07-01 | 2018-01-09 | 北京京东尚科信息技术有限公司 | Interface setting method, service management, service executing apparatus and its equipment |
| CN107608873A (en) * | 2016-07-11 | 2018-01-19 | 珠海优特电力科技股份有限公司 | Method for testing software and system and test platform |
| CN107992421A (en) * | 2017-12-07 | 2018-05-04 | 畅捷通信息技术股份有限公司 | Interface test method and its device and computer installation and its readable storage medium storing program for executing |
| CN108804882A (en) * | 2018-06-11 | 2018-11-13 | 北京北信源信息安全技术有限公司 | A kind of copyrighted software detection process method and system |
| CN109271313A (en) * | 2018-08-13 | 2019-01-25 | 中国平安财产保险股份有限公司 | Code test method, device and computer readable storage medium |
-
2003
- 2003-12-22 CN CN 200310121900 patent/CN1277186C/en not_active Expired - Fee Related
Cited By (43)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100458703C (en) * | 2005-08-26 | 2009-02-04 | 北京中星微电子有限公司 | A cross-platform function call system |
| CN100458702C (en) * | 2005-08-26 | 2009-02-04 | 北京中星微电子有限公司 | A method of function call between different running platforms |
| CN100361082C (en) * | 2005-08-26 | 2008-01-09 | 北京中星微电子有限公司 | Method for calling function containing pointer parameter between different operation platforms |
| CN1952818B (en) * | 2005-10-22 | 2010-12-15 | 康佳集团股份有限公司 | Testing method of program unit with capability of checking test result automatically |
| CN100363906C (en) * | 2006-02-28 | 2008-01-23 | 华为技术有限公司 | Method for testing software unit |
| CN100444127C (en) * | 2006-12-12 | 2008-12-17 | 北京中星微电子有限公司 | System and method for testing software |
| CN101488085A (en) * | 2008-01-17 | 2009-07-22 | 中兴通讯股份有限公司 | Software interface test method and apparatus |
| CN101650655A (en) * | 2009-09-07 | 2010-02-17 | 苏州瀚瑞微电子有限公司 | Method for analyzing test data of chip |
| CN101699409B (en) * | 2009-09-30 | 2011-09-14 | 深圳市普联技术有限公司 | Method for controlling testing equipment to test and system thereof |
| CN101944026B (en) * | 2010-09-21 | 2013-01-02 | 中国人民解放军63961部队 | Implementation method of universal virtual instrument interface |
| CN101944026A (en) * | 2010-09-21 | 2011-01-12 | 中国人民解放军63961部队 | Implementation method of universal virtual instrument interface |
| CN101944062B (en) * | 2010-09-21 | 2013-01-23 | 中国人民解放军63961部队 | Method for configuring universal virtual instrument interface |
| CN101944062A (en) * | 2010-09-21 | 2011-01-12 | 中国人民解放军63961部队 | Method for configuring universal virtual instrument interface |
| CN101980173A (en) * | 2010-11-03 | 2011-02-23 | 北京世纪高通科技有限公司 | Method and device for system integrated test |
| CN103778052A (en) * | 2012-10-17 | 2014-05-07 | 百度在线网络技术（北京）有限公司 | Method and device for front end javascript code testing |
| CN103778052B (en) * | 2012-10-17 | 2017-12-19 | 百度在线网络技术（北京）有限公司 | A kind of method of testing and device of front end javascript codes |
| CN102999329B (en) * | 2012-11-05 | 2016-01-20 | 浙江吉利汽车研究院有限公司杭州分公司 | The Active Directory interface exploitation method of configuration is mapped based on extend markup language |
| CN102999329A (en) * | 2012-11-05 | 2013-03-27 | 浙江吉利汽车研究院有限公司杭州分公司 | Active directory interface developing method based on extensive markup language mapping configuration |
| CN103049378A (en) * | 2012-12-18 | 2013-04-17 | 惠州市亿能电子有限公司 | Program debugging method without emulator |
| CN104035859A (en) * | 2013-03-07 | 2014-09-10 | 腾讯科技（深圳）有限公司 | Visualized automatic testing method and system thereof |
| CN104035859B (en) * | 2013-03-07 | 2018-03-27 | 腾讯科技（深圳）有限公司 | A kind of Visual Automatic Test method and its system |
| CN104360920A (en) * | 2014-12-02 | 2015-02-18 | 微梦创科网络科技（中国）有限公司 | Automatic testing method and device for interface |
| CN104360920B (en) * | 2014-12-02 | 2018-06-26 | 微梦创科网络科技（中国）有限公司 | A kind of automatic interface testing method and device |
| 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 |
| CN106547684A (en) * | 2015-09-22 | 2017-03-29 | 腾讯科技（深圳）有限公司 | A kind of method of testing of application program, test device and mobile terminal |
| CN105139892A (en) * | 2015-09-23 | 2015-12-09 | 浪潮(北京)电子信息产业有限公司 | Data driving test method and system applied to storage product |
| CN105138461A (en) * | 2015-09-23 | 2015-12-09 | 网易（杭州）网络有限公司 | Interface testing method and device for application program |
| CN105139892B (en) * | 2015-09-23 | 2018-01-26 | 浪潮(北京)电子信息产业有限公司 | A kind of data-driven method of testing and system for being applied to storage product |
| CN105138461B (en) * | 2015-09-23 | 2018-01-26 | 网易（杭州）网络有限公司 | The interface test method and device of a kind of application program |
| CN105528294A (en) * | 2015-12-29 | 2016-04-27 | 广东金赋信息科技有限公司 | Method and system for automatically generating interface testing case |
| CN105528294B (en) * | 2015-12-29 | 2018-05-25 | 广东金赋科技股份有限公司 | The method and system that a kind of interface testing use-case automatically generates |
| CN106021111A (en) * | 2016-05-30 | 2016-10-12 | 上海携程商务有限公司 | Interface testing method and system |
| CN107562614A (en) * | 2016-07-01 | 2018-01-09 | 北京京东尚科信息技术有限公司 | Interface setting method, service management, service executing apparatus and its equipment |
| CN107608873A (en) * | 2016-07-11 | 2018-01-19 | 珠海优特电力科技股份有限公司 | Method for testing software and system and test platform |
| CN106502916A (en) * | 2016-12-05 | 2017-03-15 | 广州唯品会信息科技有限公司 | Method for testing software and system |
| CN106598851A (en) * | 2016-12-05 | 2017-04-26 | 广州唯品会信息科技有限公司 | Software interface test method and system |
| CN107247665A (en) * | 2017-05-18 | 2017-10-13 | 北京信安世纪科技有限公司 | A kind of method of testing and system of C interface function |
| CN107247665B (en) * | 2017-05-18 | 2020-06-26 | 北京信安世纪科技股份有限公司 | Method and system for testing C interface function |
| CN107329861A (en) * | 2017-06-12 | 2017-11-07 | 北京奇安信科技有限公司 | A kind of multiplex roles method of testing and device |
| CN107992421A (en) * | 2017-12-07 | 2018-05-04 | 畅捷通信息技术股份有限公司 | Interface test method and its device and computer installation and its readable storage medium storing program for executing |
| CN108804882A (en) * | 2018-06-11 | 2018-11-13 | 北京北信源信息安全技术有限公司 | A kind of copyrighted software detection process method and system |
| CN109271313A (en) * | 2018-08-13 | 2019-01-25 | 中国平安财产保险股份有限公司 | Code test method, device and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1277186C (en) | 2006-09-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1277186C (en) | Software interface testing method | |
| CN110781086B (en) | Cross-project defect influence analysis method | |
| CN110399133B (en) | JavaScript code optimization method based on front-end byte code technology | |
| CN108121542B (en) | MyBatis-based SQL statement configuration method and system | |
| AU2054900A (en) | Method and apparatus for executing pl/sql stored code objects in a database | |
| US20080320054A1 (en) | Database and Software Conversion System and Method | |
| CN106528399A (en) | Test case determination method and apparatus | |
| CN101841515A (en) | Target variable protocol data unit codec code automatic generation implementation method | |
| CN1834907A (en) | System, method and program product to optimize code during run time | |
| CN1248115C (en) | Method for readlizing universal test report | |
| CN116450616A (en) | General heterogeneous relational database SQL migration method based on parse tree | |
| US20050039166A1 (en) | XML validation processing | |
| US7409619B2 (en) | System and methods for authoring domain specific rule-driven data generators | |
| CN101826049A (en) | Implementation method for debugging information output in embedded system | |
| CN105893052A (en) | War packet analyzer | |
| CN1635497A (en) | Hardware-level based test script automatic generating system and method | |
| CN1992715A (en) | Implementation method for automatic generation of PDU coding/decoding code based on ASN.1 definition | |
| US7634764B2 (en) | Method and system for flexible/extendable at command interpreter | |
| US20050234924A1 (en) | Automated patching of code for schema derived classes | |
| US8650536B2 (en) | Modular server architecture | |
| CN111221519B (en) | Python-based CLI automatic export method | |
| CN1282917A (en) | Software simulation test method | |
| CN100347702C (en) | Extendible marked language key constraint verification method based on structural analysis | |
| CN1767524A (en) | Message processing system and its processing method | |
| CN1896954A (en) | Method for realizing structural dynamic compiler of complicated multi-service |
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 | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20060927 Termination date: 20100122 |