CN101488085A - Software interface test method and apparatus - Google Patents
Software interface test method and apparatus Download PDFInfo
- Publication number
- CN101488085A CN101488085A CNA2008100563699A CN200810056369A CN101488085A CN 101488085 A CN101488085 A CN 101488085A CN A2008100563699 A CNA2008100563699 A CN A2008100563699A CN 200810056369 A CN200810056369 A CN 200810056369A CN 101488085 A CN101488085 A CN 101488085A
- Authority
- CN
- China
- Prior art keywords
- type
- self
- test
- defined object
- test result
- 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.)
- Pending
Links
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a software interface test method and comprises the steps as follows: configuration file information is obtained; Extensible Markup Language (XML) analysis is carried out on the obtained configuration file information to obtain the information of a software interface to be tested; a test operation is carried out according to interface instruction and input parameter in the obtained information of the software interface to be tested; and a test result is recorded according to the output parameter type in the information of the software interface to be tested. The invention also provides a software interface tester which is applied to a software interface test based on Hibernate in Java development. XML is used for compiling a configuration file instead of the complex process of compiling a test code, and a test end executes the software interface test by analyzing the configuration file. The method and the device do not require compiling the test code, thereby reducing the workload of the software interface test, simplifying the test operation and improving the test efficiency.
Description
Technical field
The present invention relates to software testing technology, relate in particular to a kind of software interface test approach and device.
Background technology
Hibernate is a kind of Object Relation Mapping framework of open source code, and is very extensive in Java uses at present.Hibernate connects the object encapsulation that (JDBC, Java Data Base Connectivity) carries out lightweight to the Java database, makes java applet person can be convenient to use object programming thinking and comes the manipulation data storehouse.Hibernate can be applied in the occasion of any use JDBC, just is based on as the backstage code of: current operation management support platform that Hibernate develops.Along with service management support platform function becomes increasingly complex, need provide increasing functional interface to call to realize all kinds of demands for the foreground, and the custom data object that application Hibernate encapsulates is also more and more, need in actual applications the various software interfaces of service management support platform are tested, the test process of software interface is exactly the proof procedure of tester and tested software interactive interfacing information.
Prior art is to the test based on software interface in the Java exploitation of Hibernate, be that test code by the manual compiling software interface carries out, this method requires the tester to have stronger test code development ability, the test code development workload is very big, be unfavorable for extensively carrying out of software interface test job, and the cost of software interface test is higher.In addition,, cause the test code needs of software interface often to be revised, thereby make that the maintenance workload of software interface test code is big because software program often changes in actual applications, maintainable relatively poor.
Summary of the invention
In view of this, fundamental purpose of the present invention is to provide a kind of software interface test approach and device, and the software interface test job amount based on Hibernate in the prior art is big to solve, the problem of complicated operation.
For achieving the above object, technical scheme of the present invention is achieved in that
The invention provides a kind of software interface test approach, comprising:
Obtain profile information;
The profile information that obtains is carried out the XML of extensibility identifiable language parsing obtain the software under testing interface message;
Value according to interface specification in the gained software under testing interface message and input parameter is carried out test operation, and according to the output parameter class record test result in the gained software under testing interface message.
The described profile information that obtains specifically comprises:
Be provided with and store the profile information that is used for the software interface test by XML;
Read the profile information of being stored.
Described software under testing interface message comprises class node set and self-defined object node set; Comprise software under testing interface place class name and software under testing interface message in the described class node set; Comprise software under testing interface name, input and output parameter in the described software under testing interface message; Comprise the attribute information of self-defined object node title and self-defined object in the described self-defined object node set, comprise initial value as each attribute of input parameter.
Described value according to interface specification and input parameter in the gained software under testing interface message is carried out test operation, specifically comprises:
Determine described input parameter type according to the property value of described input parameter type;
If determine that described input parameter type is a fundamental type, then from described input parameter, obtain initial value;
If determine that described input parameter type is self-defined object type, then, obtain initial object in the corresponding self-defined object node from self-defined object node set according to the self-defined object node title in the described input parameter;
The initial value or the initial object that obtain are sent to the software under testing interface, and wait for that described software under testing interface returns test result.
Described according to the output parameter class record test result in the gained software under testing interface message, specifically comprise:
Determine described output parameter type according to the property value of described output parameter type;
If determine that described output parameter type is a fundamental type, then described test result do not changed; If determine that described output parameter type is self-defined object type, then generate a self-defined object according to test result, the field value of this self-defined object is set, and described field value is converted to character string type; If determine that described output parameter type is an aggregate type, each element during then traversal is gathered, element for fundamental type, then described test result is not changed, element for self-defined object type, then generate a self-defined object, the field value of this self-defined object is set, and described field value is converted to character string type according to test result;
Test result is deposited in the destination file.
The present invention also provides a kind of software interface proving installation, comprising: profile information acquiring unit, profile information resolution unit, test operation performance element and outcome record unit; Wherein,
Described profile information acquiring unit is used to obtain profile information and offers described profile information resolution unit;
Described profile information resolution unit is used for that the profile information that obtains is carried out XML and resolves and to obtain the software under testing interface message and offer described test operation performance element and outcome record unit;
Described test operation performance element is used for carrying out test operation according to the initial value of gained software under testing interface message interface specification and input parameter;
Described outcome record unit is used for the output parameter class record test result according to gained software under testing interface message.
Described profile information acquiring unit comprises: subelement is set interconnective profile information and profile information reads subelement; Wherein,
Described profile information is provided with subelement, is used for being provided with and storing the profile information that is used for the software interface test by XML;
Described profile information reads subelement, is used to read the profile information of being stored.
Described test operation performance element comprises: the input parameter type determines that subelement, initial value obtain subelement and initial value sends subelement; Wherein,
Described input parameter type is determined subelement, is used for determining that according to the property value of described input parameter type described input parameter type offers described initial value and obtains subelement;
Described initial value obtains subelement, when being used for determining that described input parameter type is fundamental type, obtains initial value from described input parameter; When determining that described input parameter type is self-defined object type,, obtain initial object in the corresponding self-defined object node from self-defined object node set according to the self-defined object node title in the described input parameter;
Described initial value sends subelement, and the initial value or the initial object that are used for obtaining send to the software under testing interface.
Described outcome record unit comprises: the output parameter type is determined subelement, test result processing subelement and test result storing sub-units; Wherein,
Described output parameter type is determined subelement, is used for determining that according to the property value of described output parameter type described output parameter type offers described test result and handles subelement;
Described test result is handled subelement, when being used for determining that the output parameter type is fundamental type, described test result is not changed; When determining that the output parameter type is self-defined object type, generate a self-defined object, the field value of this self-defined object is set, and described field value is converted to character string type according to test result; When determining that the output parameter type is aggregate type, each element in the traversal set, element for fundamental type, then test result is not changed, element for self-defined object type, then generate a self-defined object, the field value of this self-defined object is set, and described field value is converted to character string type according to test result;
Described test result storing sub-units is used for depositing the test result that test result is handled after subelement is handled in destination file.
Software interface test approach provided by the invention and device, be applied in the Java exploitation software interface test based on Hibernate, by adopting the extensibility (XML of identifiable language, Extensible MarkupLanguage) writes configuration file and replace the complex process of writing test code, test lead carries out the software interface test by resolving configuration file, and the complex work of avoiding writing test code has reduced the workload that software interface is tested, simplify test operation, improved testing efficiency; The present invention shields the realization details of software interface, and the defined declaration that the tester only need understand software interface can carry out the software interface test, has reduced the requirement to the tester; Test data of the present invention can be a fundamental type, can be self-defined object type also, has stronger extensibility; The configuration file of writing among the present invention is not subjected to the influence of software program change, as long as software interface definition does not change, does not then need configuration file is made amendment, thereby makes configuration file have higher maintainability.
Description of drawings
Fig. 1 is the process flow diagram of a kind of software interface test approach of the present invention;
Fig. 2 is the structural representation of configuration file in the embodiment of the invention;
Fig. 3 is the process flow diagram of the software interface test approach of the embodiment of the invention;
Fig. 4 is the composition structural representation of a kind of software interface proving installation of the present invention.
Embodiment
The technical solution of the present invention is further elaborated below in conjunction with the drawings and specific embodiments.
Because XML has very strong data layout ability to express, overwhelming majority data structure can be come out with the formal representation of XML, therefore the present invention is applied in the Java exploitation software interface test based on Hibernate with XML, adopt XML to write configuration file and replace the complex process of writing test code, test lead carries out the test of software interface by resolving configuration file, the operation of writing configuration file compares that the operation of writing test code is simple more, workload is little, and configuration file is compared the easier maintenance of test code.
As shown in Figure 1, Fig. 1 is the process flow diagram of a kind of software interface test approach of the present invention, and this method mainly may further comprise the steps:
The user writes the configuration file that is used for software interface test in advance and is stored in test lead by XML, and when carrying out the software interface test operation, test lead reads the configuration file stored to obtain profile information.
The structural representation of configuration file as shown in Figure 2, comprise class node set and self-defined object node set in the configuration file root node that adopts XML to write, comprise one or more class nodes in the class node set, all kinds of nodes identify with class name, certainly can comprise zero class node in the class node set, zero class ode table is shown in does not need the class of testing in the software interface test yet; Comprise one or more interface node again in each class node, certainly also can comprise the zero interface node in the class node, comprise in the class node that the zero interface node is illustrated in class node in the software interface test and does not need the interface tested; Comprise one or more self-defined object nodes in the self-defined object node set, can comprise the self-defined object node of zero certainly yet, the self-defined object node of zero then is illustrated in the software interface test does not have self-defined object.Self-defined object node set is used for the specifying information when being self-defined object of the input parameter of software under testing interface message in the storage class node, the attribute information that comprises self-defined object node title and self-defined object, attribute information comprise each attribute field, field type and the initial value etc. of this self-defined object as input parameter.
In each class node, specify the class name at software under testing interface place by attribute className, and by＜methods〉the interface node set that comprises in the child node specified class, in interface node, defined information such as software under testing interface name, input and output parameter.
Wherein, the definition of interface name is as＜method name=＂ findSubscribeApp ＂ isNeedExecute=＂ true ＂ 〉, name represents the software under testing interface name, isNeedExecute is for indicating whether software interface needs the attribute of testing, and the value of isNeedExecute is that true represents that software interface needs test; The value of isNeedExecute is that false represents that then software interface does not need test.
Wherein, the definition of input parameter as＜inputPara name=＂ srcID ＂ type=＂ java.lang.String ＂ value=＂ 123 ＂/, name represents the input parameter name, type represents the input parameter type, value represents the input parameter initial value.It is pointed out that if type is a fundamental type, then the value of value is concrete input parameter initial value; If type is self-defined object type, then the value of value is certain the self-defined object node title in the self-defined object node set.So-called fundamental type comprises integer and character string type etc.; So-called self-defined object type is meant that the user requires to define voluntarily the input and output parameter information of interface to be measured according to actual needs according to Hibernate.When input parameter when being a plurality of, a plurality of input parameters can be formed the input parameters tabulation.
Wherein, define the type of test result in the output parameter, comprised fundamental type, self-defined object type and aggregate type.So-called aggregate type is meant that the test result type of output parameter definition comprises a plurality of elements, and each element can be a fundamental type entirely, also can be self-defined object type entirely.It is to be noted, if the output parameter type is an aggregate type, then pass through the type of each element in the attribute referTo definition set, as＜outputResult type=＂ j ava.util.List ＂ referTo=＂ java.lang.Integer ＂/in, by type=＂ java.util.List ＂ as can be known the output parameter type be aggregate type, and among the referTo in the definition set type of each element all be integer.
Specifying information when the input parameter that has defined the software under testing interface message in the self-defined object node is self-defined object comprises field, field type and initial value etc.As＜inputParaObjectname=＂ adviceData ＂ 〉, name represents the title of self-defined object, the value of value was corresponding when type was self-defined object type in name value herein and the aforementioned input parameter.When type in the input parameter is self-defined object type, specifies the title of self-defined object node by the value of value, thereby set up the direct correlation of software under testing interface and self-defined object node.In addition, comprise one or more＜field in the self-defined object node〉node composition list structure,＜field〉defined field, field type and the initial value etc. of self-defined object in the node, as＜field name=＂ timeLimit ＂ type=＂ java.lang.String ＂ value=＂ 20071211 ＂/, name represents field name, type represents field type, and value represents initial value.
Test lead carries out XML to the profile information that obtains and resolves the information such as software under testing interface name, input and output parameter that obtain.
Test lead is determined the input parameter type according to the type attribute of input parameter definition, if be fundamental type, then directly obtains initial value from the value attribute of output parameter definition; If be self-defined object type, then according to the self-defined object node title of appointment in the value attribute, find self-defined object node corresponding in the self-defined object node set with the value attribute, be obtained from definition object node＜field the node tabulation, according to＜field〉name, the type and the value property value that define in the node, and require that field is set and the field respective value obtains an initial object in self-defining data file according to Hibernate.Then, test lead calls the software under testing interface according to the software under testing interface definition, and input parameter initial value or the initial object of obtaining sent to the software under testing interface, and waits for that the software under testing interface returns test result.
The software under testing interface is carried out corresponding test operation according to the input parameter that receives, and test result is returned to test lead.After test lead receives test result, read output parameter and obtain test result type,, then directly test result is write destination file if the test result type in the output parameter is a fundamental type; If be self-defined object type, then generate a self-defined object according to the test result that Hibernate requires and basis obtains, the field value of this self-defined object is set, then the field value that obtains is converted to character string type and writes in the destination file; If be aggregate type, each element during then traversal is gathered, according to the type that defines in the referTo attribute each element is handled, element for fundamental type, then directly test result is write destination file,, then generate a self-defined object according to the test result that Hibernate requires and basis obtains for the element of self-defined object type, the field value of this self-defined object is set, then the field value that obtains is converted to character string type and writes in the destination file.
Below in conjunction with embodiment shown in Figure 3 above-mentioned software interface test approach shown in Figure 1 is further elaborated, Fig. 3 is the process flow diagram of the software interface test approach of the embodiment of the invention, mainly may further comprise the steps:
Step 301, test lead starts test procedure, reads in profile information.
The mode of test lead startup test procedure comprises two kinds in the embodiment of the invention: a kind of is directly the configuration file that edits to be put into class file place catalogue, in developing instrument, carry out running example, thereby the startup test procedure, this mode can be used by the research staff; Another kind is that jar bag and the configuration file that will edit are placed on same catalogue as the ant script file, directly carry out the ant script file that provides by ant, thereby the startup test procedure, this mode can be used by non-research staff, and the research staff also can use this kind mode certainly.
Step 302, test lead are carried out the XML parsing to profile information and are obtained the class node set, comprise the list information of all class nodes in the class node set.
Step 303, test lead judge whether the tabulation of class node is empty.
Whether test lead searches whether there is the class node information in the tabulation, be sky to judge class node tabulation, is sky if judge the tabulation of class node, and showing does not need the class of testing, and then finishes testing process; Otherwise, forward step 304 to.
Step 304, test lead is chosen one of them class node from the tabulation of class node, and resolves the list information that obtains the software under testing interface corresponding with such node according to the class name of class node from configuration file.
Step 305, test lead judge whether the software under testing interface list is empty.
Whether test lead searches whether there is the software under testing interface message in the tabulation, be sky to judge the software under testing interface list, is empty if judge the software under testing interface list, then forwards step 303 to, chooses other class nodes from the tabulation of class node; Otherwise, forward step 306 to.
Step 306, test lead are chosen a software interface from the software under testing interface list.
Step 307, test lead judge whether the software interface of choosing needs test.
Test lead is resolved from configuration file according to the software interface chosen and is obtained indicating the whether property value isNeedExecute of needs execution test operation of this software interface, if the value of isNeedExecute is false, show that then software interface need not carry out test operation, forward step 305 to, from the software under testing interface list, choose other interfaces; If the value of isNeedExecute is true, show that then software interface need carry out test operation, forward step 308 to.
Step 308, test lead judge whether there is selected software under testing interface in the class node.
According to selected software under testing interface message, search whether there is corresponding software interface information in the class node, if exist, show that then selected software under testing interface is the normal software interface, forward step 309 to; If there is no, show that then selected software under testing interface is improper software interface, identify selected software under testing interface and forward step 305 to, from the software under testing interface list, choose other software under testing interfaces.Judge whether selected software interface exists in the class node, the software interface that can avoid will not belonging to owing to writing configuration file the class node is edited into the situation that causes the configuration file mistake in the class node and takes place.
Step 309, test lead is resolved the input parameter that obtains the software under testing interface according to selected software under testing interface from configuration file.
Step 310, test lead is carried out the test operation of software under testing interface, receives the test result of returning.
Test lead is determined the input parameter type according to the type attribute of input parameter definition, if be fundamental type, then directly obtains initial value from the value attribute of output parameter definition; If be self-defined object type, then according to the self-defined object node title of appointment in the value attribute, find self-defined object node corresponding in the self-defined object node set with the value attribute, be obtained from definition object node＜field the node tabulation, according to＜field〉name, the type and the value property value that define in the node, and require that field is set and the field respective value obtains an initial object in self-defining data file according to Hibernate.Then, test lead calls the software under testing interface according to the software under testing interface definition, and input parameter initial value or the initial object of obtaining sent to the software under testing interface, and waits for that the software under testing interface returns test result.The software under testing interface is carried out corresponding test operation according to the input parameter that receives, and test result is returned to test lead.Test lead reads output parameter and obtains test result type information from configuration file.
Step 311, test lead is handled test result according to the test result type in the output parameter.
Test lead reads output parameter and obtains test result type information from configuration file, if the test result type in the output parameter is a fundamental type, then test result is not changed; If be self-defined object type, then generate a self-defined object according to the test result that Hibernate requires and basis obtains, the field value of this self-defined object is set, then the field value that obtains is converted to character string type; If be aggregate type, each element during then traversal is gathered, according to the type that defines in the referTo attribute each element is handled, element for fundamental type, then test result is not changed,, then generated a self-defined object according to the test result that Hibernate requires and basis obtains for the element of self-defined object type, the field value of this self-defined object is set, then the field value that obtains is converted to character string type.
Step 312, the test result after will handling deposits in the destination file.
It is pointed out that after step 312 executes, forward to step 305 choose other software under testing interfaces proceed the test, all execute test operation up to all software under testing interfaces.
The present invention also provides a kind of software interface proving installation, and as shown in Figure 4, this device comprises: profile information acquiring unit 10, profile information resolution unit 20, test operation performance element 30 and outcome record unit 40.Profile information acquiring unit 10 is used to obtain profile information and offers profile information resolution unit 20.Profile information resolution unit 20 is used for that the profile information that obtains is carried out XML and resolves and to obtain the software under testing interface message and offer test operation performance element 30 and outcome record unit 40.Test operation performance element 30 is used for carrying out test operation according to the interface specification of gained software under testing interface message and the initial value of input parameter.Outcome record unit 40 is used for the output parameter class record test result according to gained software under testing interface message.
Profile information acquiring unit 10 comprises: subelement 11 is set interconnective profile information and profile information reads subelement 12.Profile information is provided with subelement 11, is used for being provided with and storing the profile information that is used for the software interface test by XML.Profile information reads subelement 12, is used to read the profile information of being stored.
Test operation performance element 30 comprises: the input parameter type determines that subelement 31, initial value obtain subelement 32 and initial value sends subelement 33.The input parameter type is determined subelement 31, is used for determining that according to the property value of input parameter type the input parameter type offers initial value and obtains subelement 32.Initial value obtains subelement 32, when being used for the input parameter type and being fundamental type, obtains initial value from input parameter; When the input parameter type is self-defined object type,, obtain initial object in the corresponding self-defined object node from self-defined object node set according to the self-defined object node title in the input parameter.Initial value sends subelement 33, and the initial value or the initial object that are used for obtaining send to the software under testing interface.
In sum, software interface test approach provided by the invention and device, be applied in the Java exploitation software interface test based on Hibernate, replace the complex process of writing test code by adopting XML to write configuration file, test lead carries out the software interface test by resolving configuration file, and the complex work of avoiding writing test code has reduced the workload that software interface is tested, simplify test operation, improved testing efficiency; The present invention shields the realization details of software interface, and the defined declaration that the tester only need understand software interface can carry out the software interface test, has reduced the requirement to the tester; Test data of the present invention can be a fundamental type, can be self-defined object type also, has stronger extensibility; The configuration file of writing among the present invention is not subjected to the influence of software program change, as long as software interface definition does not change, does not then need configuration file is made amendment, thereby makes configuration file have higher maintainability.
The above is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention.
Claims (9)
1, a kind of software interface test approach is characterized in that, comprising:
Obtain profile information;
The profile information that obtains is carried out the XML of extensibility identifiable language parsing obtain the software under testing interface message;
Value according to interface specification in the gained software under testing interface message and input parameter is carried out test operation, and according to the output parameter class record test result in the gained software under testing interface message.
According to the described software interface test approach of claim 1, it is characterized in that 2, the described profile information that obtains specifically comprises:
Be provided with and store the profile information that is used for the software interface test by XML;
Read the profile information of being stored.
According to the described software interface test approach of claim 1, it is characterized in that 3, described software under testing interface message comprises class node set and self-defined object node set; Comprise software under testing interface place class name and software under testing interface message in the described class node set; Comprise software under testing interface name, input and output parameter in the described software under testing interface message; Comprise the attribute information of self-defined object node title and self-defined object in the described self-defined object node set, comprise initial value as each attribute of input parameter.
According to claim 1 or 2 or 3 described software interface test approach, it is characterized in that 4, described value according to interface specification and input parameter in the gained software under testing interface message is carried out test operation, specifically comprises:
Determine described input parameter type according to the property value of described input parameter type;
If determine that described input parameter type is a fundamental type, then from described input parameter, obtain initial value;
If determine that described input parameter type is self-defined object type, then, obtain initial object in the corresponding self-defined object node from self-defined object node set according to the self-defined object node title in the described input parameter;
The initial value or the initial object that obtain are sent to the software under testing interface, and wait for that described software under testing interface returns test result.
5, according to claim 1 or 2 or 3 described software interface test approach, it is characterized in that, described according to the output parameter class record test result in the gained software under testing interface message, specifically comprise:
Determine described output parameter type according to the property value of described output parameter type;
If determine that described output parameter type is a fundamental type, then described test result do not changed; If determine that described output parameter type is self-defined object type, then generate a self-defined object according to test result, the field value of this self-defined object is set, and described field value is converted to character string type; If determine that described output parameter type is an aggregate type, each element during then traversal is gathered, element for fundamental type, then described test result is not changed, element for self-defined object type, then generate a self-defined object, the field value of this self-defined object is set, and described field value is converted to character string type according to test result;
Test result is deposited in the destination file.
6, a kind of software interface proving installation is characterized in that, comprising: profile information acquiring unit, profile information resolution unit, test operation performance element and outcome record unit; Wherein,
Described profile information acquiring unit is used to obtain profile information and offers described profile information resolution unit;
Described profile information resolution unit is used for that the profile information that obtains is carried out XML and resolves and to obtain the software under testing interface message and offer described test operation performance element and outcome record unit;
Described test operation performance element is used for carrying out test operation according to the initial value of gained software under testing interface message interface specification and input parameter;
Described outcome record unit is used for the output parameter class record test result according to gained software under testing interface message.
According to the described software interface proving installation of claim 6, it is characterized in that 7, described profile information acquiring unit comprises: subelement is set interconnective profile information and profile information reads subelement; Wherein,
Described profile information is provided with subelement, is used for being provided with and storing the profile information that is used for the software interface test by XML;
Described profile information reads subelement, is used to read the profile information of being stored.
According to the described software interface proving installation of claim 6, it is characterized in that 8, described test operation performance element comprises: the input parameter type determines that subelement, initial value obtain subelement and initial value sends subelement; Wherein,
Described input parameter type is determined subelement, is used for determining that according to the property value of described input parameter type described input parameter type offers described initial value and obtains subelement;
Described initial value obtains subelement, when being used for determining that described input parameter type is fundamental type, obtains initial value from described input parameter; When determining that described input parameter type is self-defined object type,, obtain initial object in the corresponding self-defined object node from self-defined object node set according to the self-defined object node title in the described input parameter;
Described initial value sends subelement, and the initial value or the initial object that are used for obtaining send to the software under testing interface.
According to the described software interface proving installation of claim 6, it is characterized in that 9, described outcome record unit comprises: the output parameter type is determined subelement, test result processing subelement and test result storing sub-units; Wherein,
Described output parameter type is determined subelement, is used for determining that according to the property value of described output parameter type described output parameter type offers described test result and handles subelement;
Described test result is handled subelement, when being used for determining that the output parameter type is fundamental type, described test result is not changed; When determining that the output parameter type is self-defined object type, generate a self-defined object, the field value of this self-defined object is set, and described field value is converted to character string type according to test result; When determining that the output parameter type is aggregate type, each element in the traversal set, element for fundamental type, then test result is not changed, element for self-defined object type, then generate a self-defined object, the field value of this self-defined object is set, and described field value is converted to character string type according to test result;
Described test result storing sub-units is used for depositing the test result that test result is handled after subelement is handled in destination file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2008100563699A CN101488085A (en) | 2008-01-17 | 2008-01-17 | Software interface test method and apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2008100563699A CN101488085A (en) | 2008-01-17 | 2008-01-17 | Software interface test method and apparatus |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101488085A true CN101488085A (en) | 2009-07-22 |
Family
ID=40890992
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2008100563699A Pending CN101488085A (en) | 2008-01-17 | 2008-01-17 | Software interface test method and apparatus |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101488085A (en) |
Cited By (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101963933A (en) * | 2010-09-29 | 2011-02-02 | 清华大学 | Static instrument matching method adapting to multi-communication protocols in instrument test |
| CN101996148A (en) * | 2010-09-29 | 2011-03-30 | 清华大学 | Instrument test board configuration method for a plurality of communication protocols |
| CN102096631A (en) * | 2009-12-11 | 2011-06-15 | 华为技术有限公司 | Interface testing method and device |
| CN101699409B (en) * | 2009-09-30 | 2011-09-14 | 深圳市普联技术有限公司 | Method for controlling testing equipment to test and system thereof |
| CN102520963A (en) * | 2011-12-26 | 2012-06-27 | 重庆新媒农信科技有限公司 | Method and system for realizing service logic processing based on strongly-typed relation mapping |
| CN103049378A (en) * | 2012-12-18 | 2013-04-17 | 惠州市亿能电子有限公司 | Program debugging method without emulator |
| CN103679276A (en) * | 2013-12-16 | 2014-03-26 | 金蝶软件（中国）有限公司 | Method and system for controlling budget period range |
| CN103914377A (en) * | 2014-03-13 | 2014-07-09 | 中国联合网络通信集团有限公司 | Interface testing method and device |
| CN104035859A (en) * | 2013-03-07 | 2014-09-10 | 腾讯科技（深圳）有限公司 | Visualized automatic testing method and system thereof |
| CN104375814A (en) * | 2013-08-14 | 2015-02-25 | 腾讯科技（深圳）有限公司 | Generation method and device of an interface document |
| CN106301995A (en) * | 2015-06-24 | 2017-01-04 | 北京京东尚科信息技术有限公司 | The method and apparatus that a kind of automatic detection interface service is abnormal |
| CN106598851A (en) * | 2016-12-05 | 2017-04-26 | 广州唯品会信息科技有限公司 | Software interface test method and system |
| CN107395453A (en) * | 2017-07-03 | 2017-11-24 | 竹间智能科技（上海）有限公司 | Background service method for testing pressure and device |
| CN107562614A (en) * | 2016-07-01 | 2018-01-09 | 北京京东尚科信息技术有限公司 | Interface setting method, service management, service executing apparatus and its equipment |
| CN107908485A (en) * | 2017-10-26 | 2018-04-13 | 中国平安人寿保险股份有限公司 | Interface parameters transmission method, device, equipment and computer-readable recording medium |
| CN108920384A (en) * | 2018-08-21 | 2018-11-30 | 北京奇虎科技有限公司 | The test method and device of application |
| CN109308259A (en) * | 2018-08-21 | 2019-02-05 | 北京奇虎科技有限公司 | The test method and device of application |
| CN109558290A (en) * | 2018-11-12 | 2019-04-02 | 平安科技（深圳）有限公司 | Server, automatic interface testing method and storage medium |
| CN112181520A (en) * | 2020-09-27 | 2021-01-05 | 新奥数能科技有限公司 | Interface design method and configuration tool for energy equipment |
| CN112699020A (en) * | 2020-12-11 | 2021-04-23 | 浙江中控技术股份有限公司 | Industrial real-time database API (application program interface) interface testing method |
| CN113742224A (en) * | 2021-08-27 | 2021-12-03 | 武汉联影智融医疗科技有限公司 | Test system, method, device, computer equipment and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1632747A (en) * | 2003-12-22 | 2005-06-29 | 联想(北京)有限公司 | Software interface testing method |
| CN1858717A (en) * | 2005-05-08 | 2006-11-08 | 中兴通讯股份有限公司 | Data coding and decoding method and its coding and decoding device |
-
2008
- 2008-01-17 CN CNA2008100563699A patent/CN101488085A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1632747A (en) * | 2003-12-22 | 2005-06-29 | 联想(北京)有限公司 | Software interface testing method |
| CN1858717A (en) * | 2005-05-08 | 2006-11-08 | 中兴通讯股份有限公司 | Data coding and decoding method and its coding and decoding device |
Cited By (30)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101699409B (en) * | 2009-09-30 | 2011-09-14 | 深圳市普联技术有限公司 | Method for controlling testing equipment to test and system thereof |
| CN102096631A (en) * | 2009-12-11 | 2011-06-15 | 华为技术有限公司 | Interface testing method and device |
| CN102096631B (en) * | 2009-12-11 | 2013-09-25 | 华为技术有限公司 | Interface testing method and device |
| CN101996148A (en) * | 2010-09-29 | 2011-03-30 | 清华大学 | Instrument test board configuration method for a plurality of communication protocols |
| CN101963933B (en) * | 2010-09-29 | 2012-11-14 | 清华大学 | Static instrument matching method adapting to multi-communication protocols in instrument test |
| CN101963933A (en) * | 2010-09-29 | 2011-02-02 | 清华大学 | Static instrument matching method adapting to multi-communication protocols in instrument test |
| CN102520963B (en) * | 2011-12-26 | 2014-10-01 | 重庆新媒农信科技有限公司 | Method and system for realizing service logic processing based on strongly-typed relation mapping |
| CN102520963A (en) * | 2011-12-26 | 2012-06-27 | 重庆新媒农信科技有限公司 | Method and system for realizing service logic processing based on strongly-typed relation mapping |
| CN103049378A (en) * | 2012-12-18 | 2013-04-17 | 惠州市亿能电子有限公司 | Program debugging method without emulator |
| CN104035859B (en) * | 2013-03-07 | 2018-03-27 | 腾讯科技（深圳）有限公司 | A kind of Visual Automatic Test method and its system |
| CN104035859A (en) * | 2013-03-07 | 2014-09-10 | 腾讯科技（深圳）有限公司 | Visualized automatic testing method and system thereof |
| CN104375814A (en) * | 2013-08-14 | 2015-02-25 | 腾讯科技（深圳）有限公司 | Generation method and device of an interface document |
| CN103679276B (en) * | 2013-12-16 | 2017-11-21 | 金蝶软件（中国）有限公司 | The control method and system of budget period range |
| CN103679276A (en) * | 2013-12-16 | 2014-03-26 | 金蝶软件（中国）有限公司 | Method and system for controlling budget period range |
| CN103914377B (en) * | 2014-03-13 | 2016-08-24 | 中国联合网络通信集团有限公司 | Interface test method and device |
| CN103914377A (en) * | 2014-03-13 | 2014-07-09 | 中国联合网络通信集团有限公司 | Interface testing method and device |
| CN106301995A (en) * | 2015-06-24 | 2017-01-04 | 北京京东尚科信息技术有限公司 | The method and apparatus that a kind of automatic detection interface service is abnormal |
| CN107562614A (en) * | 2016-07-01 | 2018-01-09 | 北京京东尚科信息技术有限公司 | Interface setting method, service management, service executing apparatus and its equipment |
| CN106598851A (en) * | 2016-12-05 | 2017-04-26 | 广州唯品会信息科技有限公司 | Software interface test method and system |
| CN107395453A (en) * | 2017-07-03 | 2017-11-24 | 竹间智能科技（上海）有限公司 | Background service method for testing pressure and device |
| CN107908485B (en) * | 2017-10-26 | 2020-08-04 | 中国平安人寿保险股份有限公司 | Interface parameter transmission method, device, equipment and computer readable storage medium |
| CN107908485A (en) * | 2017-10-26 | 2018-04-13 | 中国平安人寿保险股份有限公司 | Interface parameters transmission method, device, equipment and computer-readable recording medium |
| CN108920384A (en) * | 2018-08-21 | 2018-11-30 | 北京奇虎科技有限公司 | The test method and device of application |
| CN109308259A (en) * | 2018-08-21 | 2019-02-05 | 北京奇虎科技有限公司 | The test method and device of application |
| CN109558290A (en) * | 2018-11-12 | 2019-04-02 | 平安科技（深圳）有限公司 | Server, automatic interface testing method and storage medium |
| CN109558290B (en) * | 2018-11-12 | 2023-06-02 | 平安科技（深圳）有限公司 | Server, interface automatic test method and storage medium |
| CN112181520A (en) * | 2020-09-27 | 2021-01-05 | 新奥数能科技有限公司 | Interface design method and configuration tool for energy equipment |
| CN112181520B (en) * | 2020-09-27 | 2024-05-14 | 新奥数能科技有限公司 | Interface design method and configuration tool for energy equipment |
| CN112699020A (en) * | 2020-12-11 | 2021-04-23 | 浙江中控技术股份有限公司 | Industrial real-time database API (application program interface) interface testing method |
| CN113742224A (en) * | 2021-08-27 | 2021-12-03 | 武汉联影智融医疗科技有限公司 | Test system, method, device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101488085A (en) | Software interface test method and apparatus | |
| US7908580B2 (en) | Connecting an integrated development environment with an application instance | |
| US9804837B2 (en) | System and method for creating, managing, and reusing schema type definitions in services oriented architecture services, grouped in the form of libraries | |
| US20210365347A1 (en) | Load test framework | |
| CN102597964B (en) | A computing device for enabling concurrent testing | |
| CN100520718C (en) | Script order registration method, method and device for calling source program code | |
| CN111459889B (en) | Equipment data model generation method and device for Internet of things platform | |
| US20090254881A1 (en) | Code generation techniques for administrative tasks | |
| CN109117164B (en) | Micro-service updating method and system based on difference analysis of key elements | |
| CN111158741B (en) | Method and device for monitoring dependency relationship change of service module on third party class library | |
| US20080127053A1 (en) | Controlling application features | |
| CN102566984B (en) | Method and device for configuring parameters | |
| CN111913713B (en) | Heterogeneous service integration method based on service call tracing | |
| CN103678135A (en) | System and method for achieving cross-process and cross-thread debugging in large-data environment | |
| CN112363953B (en) | Interface test case generation method and system based on crawler technology and rule engine | |
| CN103186463B (en) | Determine the method and system of the test specification of software | |
| CN110543427A (en) | Test case storage method and device, electronic equipment and storage medium | |
| US8707260B2 (en) | Resolving interdependencies between heterogeneous artifacts in a software system | |
| CN109284222B (en) | Software unit, project testing method, device and equipment in data processing system | |
| CN116302930A (en) | Application testing method and device | |
| JP2010140408A (en) | Source code converting device | |
| CN103678485B (en) | Virtual experiment process node driving and movable packaging system | |
| TW201324347A (en) | System and method for managing commands of function module | |
| CN111488144A (en) | Data processing method and equipment | |
| JP2010140407A (en) | Source code inspection device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20090722 |