CN103164312B - Method and system for preparing interface testing data - Google Patents
Method and system for preparing interface testing data Download PDFInfo
- Publication number
- CN103164312B CN103164312B CN201110410150.6A CN201110410150A CN103164312B CN 103164312 B CN103164312 B CN 103164312B CN 201110410150 A CN201110410150 A CN 201110410150A CN 103164312 B CN103164312 B CN 103164312B
- Authority
- CN
- China
- Prior art keywords
- data
- statement
- sql statement
- record
- database
- 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.)
- Active
Links
Abstract
The invention provides a method and a system for preparing interface testing data. The method comprises the steps that when a test case is executed for the first time, a structured query language (SQL) statement in the test case is monitored and intercepted; the operation type of the SQL statement is analyzed, and the SQL statement is analyzed according to the operation type; when the SQL statement is analyzed to be a querying statement, relative data are searched through execution of the query statement and relative configuration information between data and data is automatically stored into an excel table; then the test case is executed again, and the data in the excel table is restored into a data base automatically; if the SQL statement is analyzed to be a deleting statement, the deleting statement is stored into a corresponding property profile; then the test case is executed again, and the property profile is called automatically to execute deleting operation. Automatic interception of the SQL statement can be realized, the relevant data are automatically stored and configured, time consumption is little, efficiency is high, and error rate is low.
Description
Technical field
The application relates to technical field of measurement and test, particularly relates to a kind of method and system preparing interface testing data.
Background technology
Interface testing is the one test of test system components interface, mainly for detection of the interaction point between external system and system and between inner subsystems.
In interface testing, during implementation of test cases, SQL statement can be applied the operation such as inquiry, renewal is performed to the data in database, now need the data called from database needed for test, then perform corresponding operating.Because system is through upgrading and the maintenance of being everlasting, therefore need constantly to perform same test case to carry out test macro and whether have problems, after implementation of test cases performs, because the operations such as renewal can cause the change of data, but all need to call raw data from database during each implementation of test cases.Therefore in order to ensure the uniqueness of data, can will in advance the raw data in database be saved in excel table, again before implementation of test cases, can use and the raw data in excel table is reverted in database.
During concrete operations, first need to obtain in test case the data needing to call in advance, then manually input the above-mentioned data that will call of SQL statement inquiry in a database, and manually statistical conversion is restored in excel table.In this process, because the data in database are that manual read statement obtains, therefore data are all independently, and this just needs the relevance between manual maintenance master-salve table.Because the corresponding excel table of each database when storing data, data needed for interface testing may be distributed in several database, therefore interface testing may need to use the data in multiple excel table, now needs to guarantee that in each excel table, data are associated with each other.At data convert to database, implementation of test cases just can not make mistakes.
Secondly, due to the data needing to call will be obtained in test case in advance, therefore require that operating personnel are very familiar to test case, in just the data needing in database to call can accurately being shown stored in excel, just can guarantee that showing from excel the data reverted to database is accurately.Otherwise once interface testing data are inaccurate, test case will report an error, then perform debugging, write test script and will strengthen workload, and the longer time can be expended.And, if when in interface testing, SQL statement will perform some operation, originally may exist in the data and perform afoul data with operation, therefore need manually to add deletion action statement in test script, unnecessary data are deleted to guarantee that test script runs successfully.
From the above, the method preparing interface testing data is very loaded down with trivial details, and a large amount of manual configuration, expend time in very long, what had a strong impact on interface testing script writes efficiency, and error rate is higher.
Summary of the invention
The application provides a kind of method and system preparing interface testing data, with solve interface testing data store in method loaded down with trivial details, length consuming time and the high problem of error rate.
In order to solve the problem, this application discloses a kind of method preparing interface testing data, comprising:
First during implementation of test cases, monitor and tackle the SQL statement in test case;
Analyze the action type of described SQL statement, and resolve described SQL statement according to described action type;
If described SQL statement is resolved to query statement, then search related data by performing described query statement, and the relevant configuration information of described data and data is saved in excel form;
Implementation of test cases again, by the data convert in excel form in database;
If described SQL statement is resolved to cancel statement, then preserve described cancel statement in respective attributes file;
Implementation of test cases again, calls property file and performs deletion action.
Accordingly, disclosed herein as well is a kind of system preparing interface testing data, comprising:
Monitor and blocking module, during for implementation of test cases first, monitor and tackle the SQL statement in test case;
Analyzing and parsing module, for analyzing the action type of described SQL statement, and resolving described SQL statement according to described action type;
First preserves module, if for described SQL statement is resolved to query statement, then searches related data by performing described query statement, and is saved in excel form by the relevant configuration information of described data and data;
First recovery module, for implementation of test cases again, by the data convert in excel form in database;
Second preserves module, if for described SQL statement is resolved to cancel statement, then preserves described cancel statement in respective attributes file;
Second recovery module, for implementation of test cases again, calls property file and performs deletion action.
Compared with prior art, the application comprises following advantage:
Method described in the application, when implementation of test cases first, can be monitored and tackle the SQL statement in test case, and resolving according to the action type of SQL statement, can resolve to query statement.Inquire about and preserve related data, and the relevant configuration information simultaneously can preserving data is in excel form, automatically maintaining the relevance of each excel form, searching related data, without the need to the relevance of manual maintenance excel form without the need to manually inputting SQL statement.In execution use-case, tackle SQL statement and preserve data, the accuracy of data can be guaranteed.Further, relevant cancel statement is prestored in property file, implementation of test cases again, without the need to manual configuration cancel statement, but Automatically invoked is stored in advance in the cancel statement in property file, afoul data dump may be performed with operation, guarantee that test script runs successfully.Can realize the automatic interception of SQL statement, related data autostore and configuration, consuming time short, efficiency is high and error rate is low.
Accompanying drawing explanation
Fig. 1 is a kind of method flow diagram preparing interface testing data described in the embodiment of the present application;
Fig. 2 is a kind of method flow diagram preparing interface testing data described in the application's preferred embodiment;
Fig. 3 is a kind of system construction drawing preparing interface testing data described in the embodiment of the present application.
Embodiment
For enabling above-mentioned purpose, the feature and advantage of the application more become apparent, below in conjunction with the drawings and specific embodiments, the application is described in further detail.
Itest is a kind of interface testing framework, and it take junit as the basic framework of whole test, and adopt dbunit to be the instrument of automatic management database, the content that the test data encapsulating dbunit is correlated with is to complete generation and the verification of data.Itest is that data carrier loads data by POI with excel, finally by the annotation mechanism of unitils the input/output procedure transparence of whole data and excel.The logical operations such as its supports to use the data in excel file to insert database, contrast, deletion.
Wherein, POI is Java Open-Source Tools bag, is exclusively used in and resolves and generate the file type relevant to microsoft OLE2, as word, excel etc.
In prior art, manual preparation interface testing data, need to obtain in test case the data needing to call in advance, then the above-mentioned data that will call of SQL statement inquiry are manually inputted in a database, and manually statistical conversion is restored in excel table, data preparation method is very loaded down with trivial details, a large amount of manual configuration, expends time in very long.
This application provides a kind of method preparing interface testing data, can realize the automatic interception of SQL statement, related data autostore and configuration, consuming time short, efficiency is high and error rate is low.
With reference to Fig. 1, which show a kind of method flow diagram preparing interface testing data described in the embodiment of the present application.
Step 11, first during implementation of test cases, monitors and tackles the SQL statement in test case;
In order to preserve the raw data in database, therefore when implementation of test cases first, can SQL statement in snoopy test use-case, carry out interception operation when performing SQL statement.
Step 12, analyzes the action type of described SQL statement, and resolves described SQL statement according to described action type;
After interception SQL statement, can analyze the action type of SQL statement, the action type of SQL statement comprises: inquiry (selsct), deletion (delete), renewal (update) and insertion (insert).
The action type of SQL statement refers to the type of the operation that SQL will perform can comprise query manipulation, deletion action, renewal rewards theory and update.
When described action type is for inquiring about, delete and upgrading, described SQL statement is resolved to query statement, then perform step 13;
Such as, X is deleted in the operation that SQL statement will perform, then described SQL statement is resolved to query statement, inquiry X.
In concrete enforcement, for the interface of query type, such as, SQL statement form is select field1, field2 from table where condition, can resolve to corresponding query statement by SQL statement, and its form is as select*from table where condition.
Same, for the interface deleting type, SQL statement form is as delete from table wherecondition; Is SQL statement form as update table set field=with the interface of updating type? Wherecondition.SQL statement can be resolved to corresponding query statement, its form is as select*fromtable where condition.
When described action type is for inserting, described SQL statement being resolved to cancel statement, then performing step 14.
Such as, the operation of SQL statement inserts B between A and C, therefore SQL statement can be resolved to cancel statement, as deleted the B between A and C.
For the interface inserting type, SQL statement form is as: insert into talbe values (,) wherecondition, SQL statement directly can be resolved to cancel statement, its form is as delete from tablewhere condition.
Wherein, the interface of described query type refers to that this Interface realization carries out query manipulation to the data in database; The interface of described deletion type refers to that this Interface realization carries out deletion action to the data in database; The interface of described updating type refers to that this Interface realization carries out renewal rewards theory to the data in database; The interface of described insertion type refers to that this Interface realization carries out update to the data in database.
If described SQL statement is resolved to query statement, then:
Step 13, then searching related data by performing described query statement, being automatically saved in excel form by the relevant configuration information of described data and data;
If described SQL statement is resolved to query statement in aforesaid operations, then can perform the query manipulation of described query statement, find relevant data, automatically the relevant configuration information of described data and data is saved in excel form.After step 13, again during implementation of test cases, perform step 15.
X is deleted in the operation that in upper example, SQL statement will perform, then described SQL statement is resolved to query statement, inquiry X.Then perform the operation of inquiry X, search X and the relevant configuration information of X and X is saved in corresponding excel form automatically.
Specifically can comprise:
Step 131, performs described query statement, the record of query-relevant data;
In above-mentioned steps, by SQL statement resolve be shaped as: the query statement of select*from table where condition, then can perform the query manipulation of described query statement, whether have the record of related data and data in Query Database.
When there being record to return, perform step 132; When no record returns, described SQL statement is resolved to cancel statement, then perform step 14.
Such as, perform the operation of inquiry X, whether have X in Query Database, if there is X, have the record of X, then have record to return; If without X, without the record of X, also return with regard to no record.For the situation that no record returns, step 14 can be performed.
Such as, can be the situation of 0 by Record to return, be considered as no record and return.Be a kind of mode in concrete enforcement herein, should not be understood as the restriction to the application.
Step 132, in the database that described record is corresponding, carries out duplicate removal process according to major key to record;
If there is related data, then having data record, have record and return when performing query manipulation, now in the database that described record is corresponding, carry out duplicate removal process according to major key to record, is the state that data keep the most original.
This is because, may relate to calling repeatedly to the inquiry of some tables in interface, in the middle of process, some field is by the process of the interface interchange of outside, and field value can change, and the data needed for interface testing must guarantee the most original state, otherwise script assert will be failed.Wherein, assert it is for catching the hypothesis made in code.
Step 133, in automatic preservation database, the related data of this record and the configuration information of data are in cxcel form.
By the data of return recording in database and the configuration information of data, be saved in cxcel form.Specifically in the operation of preserving data, the data of a database are saved in a cxcel form, and the data of a test case are kept in a cxcel file.Because test case may call the data in multiple database, therefore multiple cxcel form may be contained in the cxcel file of test case.
The application, when automatically data being saved in excel, can configure the relevance that each excel shows automatically.In concrete enforcement, the function that dbunit carries can be utilized, realizing data is saved in excel form, because interception is the SQL statement of inquiring about database, database itself just can guarantee the integrality of data to the access of data, therefore do not need artificial carrying out to intervene, just can move the relevance that each excel of configuration shows.This is a kind of mode in concrete enforcement, should not be understood as the restriction to the application herein.
If described SQL statement is resolved to cancel statement, then:
Step 14, preserves described cancel statement in respective attributes file;
In above-mentioned steps, SQL statement is directly resolved be shaped as: the cancel statement of delete from table wherecondition, is saved in described cancel statement in corresponding property file, such as XML file.After step 14, again during implementation of test cases, perform step 16.
In upper example, the operation of SQL statement inserts B between A and C, therefore SQL statement can be resolved to cancel statement, as deleted the B between A and C, is kept in corresponding property file by described cancel statement.
Step 15, automatically by the data convert in excel form in database.
In above-mentioned steps, when implementation of test cases first, can automatically the configuration information of data and data be kept in excel form.Therefore implementation of test cases again, then can data convert in excel form in database, to guarantee in database for the data of interface testing it is raw data.
Such as, first during implementation of test cases, the operation of SQL statement is that A is updated to A ', therefore can inquire A and stored in excel form, and then perform renewal rewards theory and make Data Update be A ', then the data of preserving in database change to A '.Again during implementation of test cases, the A in excel form can be reverted in database, replace to A by A ', can to guarantee in database for the data of interface testing it is raw data by above-mentioned steps.
Step 16, Automatically invoked property file performs deletion action.
In above-mentioned steps, when implementation of test cases first, can automatically cancel statement be saved in corresponding property file.Therefore implementation of test cases again, the relevant deletion action of cancel statement can be performed by Automatically invoked property file, this is in order to ensure can be preferentially that incoherent data scrubbing is clean during test case initialization, and the impact of incoherent data on last test use-case operation result is reduced to 0.Can to guarantee in database for the data of interface testing it is raw data by above-mentioned steps
Such as, first during implementation of test cases, the operation of SQL statement inserts B between A and C, therefore SQL statement can be resolved to cancel statement, as deleted the B between A and C.Then perform update, make the data in database change to A, B, C by A, C.Again during implementation of test cases, the cancel statement preserved in property file can be called and perform deletion action, delete the B between A and C, can to guarantee in database for the data of interface testing it is raw data by above-mentioned steps.
In sum, the method described in the application, when implementation of test cases first, can be monitored and tackle the SQL statement in test case, and resolving according to the action type of SQL statement, can resolve to query statement.Inquire about and preserve related data, and the relevant configuration information simultaneously can preserving data is in excel form, automatically maintaining the relevance of each excel form, searching related data, without the need to the relevance of manual maintenance excel form without the need to manually inputting SQL statement.In execution use-case, tackle SQL statement and preserve data, the accuracy of data can be guaranteed.Further, relevant cancel statement is prestored in property file, implementation of test cases again, without the need to manual configuration cancel statement, but Automatically invoked is stored in advance in the cancel statement in property file, afoul data dump may be performed with operation, guarantee that test script runs successfully.Can realize the automatic interception of SQL statement, related data autostore and configuration, consuming time short, efficiency is high and error rate is low.
In the process of concrete enforcement, a kind of preferred embodiment is after carrying out duplicate removal process according to major key to record, temporarily saves the data in internal memory, after test case is finished, then data is preserved in excel.
Preferably, monitor and before tackling the SQL statement in test case, also comprise:
Interface, by data-driven connection data storehouse, obtains the connection of interface and database by monitoring described data-driven.
In interface testing, interface by data-driven and DataBase combining, in this application, can achieve the specification in connection data storehouse, thus has tackled all data-drivens.Namely to tackle the SQL statement in test case, need all connections in monitored data storehouse, just can tackle before database being performed to the operation such as inquiry, renewal.Therefore by monitoring described data-driven, obtaining the connection of interface and database, just can intercept corresponding SQL statement.
Further, according to the action type being blocked SQL statement, execution is inquired about accordingly, deletes, is upgraded or update.
In aforesaid operations, save data and data relevant configuration information, but the SQL statement be blocked also does not perform, therefore can perform corresponding SQL statement.
After the SQL statement be blocked performs and terminates, if still there is the SQL statement needing interception, then continue to perform SQL statement interception operation, perform the process of above-mentioned steps 11 to step 14.Otherwise end operation, test case is finished.
Usually a lot of SQL statement can be comprised in a test case, these SQL statement may perform inquiry, renewal, deletion or update, therefore the order performed according to statement is needed to tackle corresponding SQL statement, circulation performs the process of step 11 to step 14, until do not have the SQL statement needing to be blocked.
In prior art, by manual for data derive from database after, when being saved in excel form, must the uniqueness of maintenance record major key again.
Prepare data by excel in this application, use@ITestDataSet label to carry out the insertion of data.In order to prevent data operationally with the conflicting of functional test data, the rule of the data major key of setup unit test, such as: data major key adopts 11 bit numbers, * 2 bullets+4 bit test classes numberings+3 use-cases numbering+2 bit data numberings.Data number, increases progressively when needs prepare many data.
With reference to Fig. 2, give a kind of method flow diagram preparing interface testing data described in the application's preferred embodiment.
First monitor interface to the connection of database, then tackle SQL statement, and analyze the SQL statement be blocked, if SQL statement is inquiry, deletes or renewal rewards theory, then described SQL statement is resolved to query statement; If SQL statement is update, then described SQL statement is resolved to cancel statement.Then perform query manipulation, in database, inquire about corresponding data, if there is record to return in database, be then switched to database, according to major key, duplicate removal process is carried out to record result, and save the data in internal memory; If no record returns in database, namely Record to return is 0, then SQL statement is resolved to cancel statement, and is kept in internal memory by cancel statement.Perform and be blocked the inquiry of SQL statement, deletion, renewal or update, judge whether to tackle complete (SQL statement that namely whether will not be blocked), if not, then return the operation of interception SQL statement, continue to perform interception; If so, then implementation of test cases is complete, by the data of preserving in internal memory stored in excel, is kept in property file by cancel statement, and the details of detailed recorded data storehouse, table and field etc.
With reference to Fig. 3, which show a kind of system construction drawing preparing interface testing data described in the embodiment of the present application.
Present invention also provides a kind of system preparing interface testing data accordingly, comprise: monitoring link block 10, monitoring be blocking module 11, analysis also parsing module 12, first preservation module 13, second preservation module 14, executable operations module 15, judge module 16, first recovery module 17 and the second recovery module 18 also, wherein
Monitoring link block 10, for interface by data-driven connection data storehouse, obtaining the connection of interface and database by monitoring described data-driven;
Monitor and blocking module 11, during for implementation of test cases first, monitor and tackle the SQL statement in test case;
Analyzing and parsing module 12, for analyzing the action type of described SQL statement, and resolving described SQL statement according to described action type;
First preserves module 13, if for described SQL statement is resolved to query statement, then searches related data by performing described query statement, and is automatically saved in excel form by the relevant configuration information of described data and data;
Second preserves module 14, if for described SQL statement is resolved to cancel statement, then preserves described cancel statement in respective attributes file;
Executable operations module 15, is blocked the action type of SQL statement for basis, execution is inquired about accordingly, deletes, upgraded or update;
Judge module 16, if still there is for judging the SQL statement needing interception, then continues to perform SQL statement interception operation, otherwise end operation;
First recovery module 17, for implementation of test cases again, automatically by the data convert in excel form in database;
Second recovery module 18, for implementation of test cases again, Automatically invoked property file performs deletion action.
Concrete, described analysis parsing module 12, comprising:
First analyzing sub-module 121, for when described action type is for inquiring about, delete and upgrading, resolves to query statement by described SQL statement;
Second analyzing sub-module 122, for when described action type is for inserting, resolves to cancel statement by described SQL statement.
Concrete, described first preserves module 13, comprising:
Inquiry submodule 131, for performing described query statement, the record of query-relevant data;
Duplicate removal process submodule 132, for when there being record to return, then, in the database that described record is corresponding, carries out duplicate removal process according to major key to record;
Analyzing sub-module, for when no record returns, resolves to cancel statement by described SQL statement and is saved in corresponding property file.
Preserve submodule 134, for automatically preserving in database the related data of this record and the configuration information of data in cxcel form.
For system embodiment, due to itself and embodiment of the method basic simlarity, so description is fairly simple, relevant part illustrates see the part of embodiment of the method.
Each embodiment in this instructions all adopts the mode of going forward one by one to describe, and what each embodiment stressed is the difference with other embodiments, between each embodiment identical similar part mutually see.
The application can be used in numerous general or special purpose computing system environment or configuration.Such as: personal computer, server computer, handheld device or portable set, laptop device, multicomputer system, system, Set Top Box, programmable consumer-elcetronics devices, network PC, small-size computer, mainframe computer, the distributed computing environment comprising above any system or equipment etc. based on microprocessor.
The application can describe in the general context of computer executable instructions, such as program module.Usually, program module comprises the routine, program, object, assembly, data structure etc. that perform particular task or realize particular abstract data type.Also can put into practice the application in a distributed computing environment, in these distributed computing environment, be executed the task by the remote processing devices be connected by communication network.In a distributed computing environment, program module can be arranged in the local and remote computer-readable storage medium comprising memory device.
Finally, also it should be noted that, in this article, the such as relational terms of first and second grades and so on is only used for an entity or operation to separate with another entity or operational zone, and not necessarily requires or imply the relation that there is any this reality between these entities or operation or sequentially.And, term " comprises ", " comprising " or its any other variant are intended to contain comprising of nonexcludability, thus make to comprise the process of a series of key element, method, commodity or equipment and not only comprise those key elements, but also comprise other key elements clearly do not listed, or also comprise by the intrinsic key element of this process, method, commodity or equipment.When not more restrictions, the key element limited by statement " comprising ... ", and be not precluded within process, method, commodity or the equipment comprising described key element and also there is other identical element.
Above to the method and system of the preparation interface testing data that the application provides, be described in detail, apply specific case herein to set forth the principle of the application and embodiment, the explanation of above embodiment is just for helping method and the core concept thereof of understanding the application; Meanwhile, for one of ordinary skill in the art, according to the thought of the application, all will change in specific embodiments and applications, in sum, this description should not be construed as the restriction to the application.
Claims (8)
1. prepare a method for interface testing data, it is characterized in that, comprising:
First during implementation of test cases, monitor and tackle the SQL statement in test case;
Analyze the action type of described SQL statement, and according to described action type, resolve described SQL statement;
If described SQL statement is resolved to query statement, then search related data by performing described query statement, and the relevant configuration information of described data and data is saved in excel form;
Again during implementation of test cases, by the data convert in excel form in database;
If described SQL statement is resolved to cancel statement, then preserve described cancel statement in respective attributes file;
Again during implementation of test cases, call property file and perform deletion action;
Wherein, describedly resolve described SQL statement according to described action type, comprising:
When described action type is for inquiring about, delete and upgrading, described SQL statement is resolved to query statement;
When described action type is for inserting, described SQL statement is resolved to cancel statement.
2. method according to claim 1, is characterized in that, if described SQL statement is resolved to query statement, then searches related data by performing described query statement, and the relevant configuration information of described data and data is saved in excel form, comprising:
Perform described query statement, the record of query-relevant data;
When there being record to return, then, in the database that described record is corresponding, according to major key, duplicate removal process is carried out to record;
In preservation database, the related data of this record and the configuration information of data are in cxcel form.
3. method according to claim 2, is characterized in that, also comprises:
When no record returns, described SQL statement is resolved to cancel statement and is saved in corresponding property file.
4. method according to claim 1, is characterized in that, also comprises:
According to the action type being blocked SQL statement, execution is inquired about accordingly, deletes, is upgraded or update.
5. method according to claim 3, is characterized in that, also comprises:
If still there is the SQL statement needing interception, then continue to perform SQL statement interception operation.
6. method according to any one of claim 1 to 5, is characterized in that, monitors and before tackling the SQL statement in test case, also comprises:
Interface, by data-driven connection data storehouse, obtains the connection of interface and database by monitoring described data-driven.
7. prepare a system for interface testing data, it is characterized in that, comprising:
Monitor and blocking module, during for implementation of test cases first, monitor and tackle the SQL statement in test case;
Analyzing and parsing module, for analyzing the action type of described SQL statement, and resolving described SQL statement according to described action type;
First preserves module, if for described SQL statement is resolved to query statement, then searches related data by performing described query statement, and is saved in excel form by the relevant configuration information of described data and data;
First recovery module, for implementation of test cases again, by the data convert in excel form in database;
Second preserves module, if for described SQL statement is resolved to cancel statement, then preserves described cancel statement in respective attributes file;
Second recovery module, for implementation of test cases again, calls property file and performs deletion action;
Wherein, described analysis parsing module, comprising:
First analyzing sub-module, for when described action type is for inquiring about, delete and upgrading, resolves to query statement by described SQL statement;
Second analyzing sub-module, for when described action type is for inserting, resolves to cancel statement by described SQL statement;
8. system according to claim 7, is characterized in that, described first preserves module, comprising:
Inquiry submodule, for performing described query statement, the record of query-relevant data;
Duplicate removal process submodule, for when there being record to return, then, in the database that described record is corresponding, carries out duplicate removal process according to major key to record;
Preserve submodule, for preserving in database the related data of this record and the configuration information of data in cxcel form.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110410150.6A CN103164312B (en) | 2011-12-09 | 2011-12-09 | Method and system for preparing interface testing data |
| HK13109885.4A HK1182782A1 (en) | 2011-12-09 | 2013-08-23 | Method and system for preparing interface test data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110410150.6A CN103164312B (en) | 2011-12-09 | 2011-12-09 | Method and system for preparing interface testing data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103164312A CN103164312A (en) | 2013-06-19 |
| CN103164312B true CN103164312B (en) | 2015-07-01 |
Family
ID=48587420
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110410150.6A Active CN103164312B (en) | 2011-12-09 | 2011-12-09 | Method and system for preparing interface testing data |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN103164312B (en) |
| HK (1) | HK1182782A1 (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104731697A (en) * | 2013-12-19 | 2015-06-24 | 青岛海尔空调器有限总公司 | Running control method, control system and sound monitor of test case |
| CN104133772B (en) * | 2014-08-13 | 2017-04-12 | 广东电网公司信息中心 | Automatic test data generation method |
| CN105138461B (en) * | 2015-09-23 | 2018-01-26 | 网易（杭州）网络有限公司 | The interface test method and device of a kind of application program |
| CN105117345B (en) * | 2015-09-23 | 2017-12-19 | 网易（杭州）网络有限公司 | The interface test method and device of a kind of application program |
| CN107678963A (en) * | 2017-09-27 | 2018-02-09 | 国云科技股份有限公司 | A kind of automatic interface testing method based on JAVA |
| CN111124870A (en) * | 2018-10-31 | 2020-05-08 | 北京国双科技有限公司 | Interface testing method and device |
| CN110209584A (en) * | 2019-06-03 | 2019-09-06 | 广东电网有限责任公司 | A kind of automatic generation of test data and relevant apparatus |
| CN110825745B (en) * | 2019-10-31 | 2023-03-07 | 口碑(上海)信息技术有限公司 | Page generation method and device |
| CN114237699B (en) * | 2022-02-24 | 2022-05-03 | 四川信用通数字科技股份有限公司 | Configuration script exporting method and device and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101515250A (en) * | 2009-04-09 | 2009-08-26 | 腾讯科技（深圳）有限公司 | Method for testing software system and device thereof |
| CN101174240B (en) * | 2006-11-03 | 2011-04-06 | 凌阳科技股份有限公司 | Software testing management method and system thereof |
-
2011
- 2011-12-09 CN CN201110410150.6A patent/CN103164312B/en active Active
-
2013
- 2013-08-23 HK HK13109885.4A patent/HK1182782A1/en unknown
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101174240B (en) * | 2006-11-03 | 2011-04-06 | 凌阳科技股份有限公司 | Software testing management method and system thereof |
| CN101515250A (en) * | 2009-04-09 | 2009-08-26 | 腾讯科技（深圳）有限公司 | Method for testing software system and device thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| HK1182782A1 (en) | 2013-12-06 |
| CN103164312A (en) | 2013-06-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103164312B (en) | Method and system for preparing interface testing data | |
| US20200019494A1 (en) | Method and apparatus for performing test by using test case | |
| US8782609B2 (en) | Test failure bucketing | |
| US8903762B2 (en) | Modeling data exchange in a data flow of an extract, transform, and load (ETL) process | |
| Behnamghader et al. | A large-scale study of architectural evolution in open-source software systems | |
| US10387236B2 (en) | Processing data errors for a data processing system | |
| US7853930B2 (en) | Annotating graphs to allow quick loading and analysis of very large graphs | |
| US9311345B2 (en) | Template based database analyzer | |
| CN111309760A (en) | Data retrieval method, system, device and storage medium | |
| US11487742B2 (en) | Consistency checks between database systems | |
| CN105095059A (en) | Method and device for automated testing | |
| CN110019116B (en) | Data tracing method, device, data processing equipment and computer storage medium | |
| CN105556474A (en) | Managing memory and storage space for a data operation | |
| US9195730B2 (en) | Verifying correctness of a database system via extended access paths | |
| CN110737594A (en) | Database standard conformance testing method and device for automatically generating test cases | |
| CN115309831B (en) | Local database state synchronization method, electronic equipment and storage medium | |
| CN103064780B (en) | A kind of method of software test and device | |
| US11347796B2 (en) | Eliminating many-to-many joins between database tables | |
| CN116148636A (en) | Method and device for testing embedded board card, electronic equipment and readable storage medium | |
| CN115599588A (en) | Method and device for acquiring memory use information, storage medium and electronic device | |
| Psallidas et al. | OneProvenance: Efficient Extraction of Dynamic Coarse-Grained Provenance from Database Logs [Technical Report] | |
| Hammad et al. | An approach to automatically enforce object-oriented constraints | |
| CN117389908B (en) | Dependency analysis method, system and medium for interface automation test case | |
| US9465723B2 (en) | Systems and/or methods for monitoring live software | |
| CN110795451B (en) | SQL fingerprint restoring method, SQL fingerprint restoring device, SQL fingerprint restoring computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 1182782 Country of ref document: HK |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |