CN107203373B - Interface control acquiring method, interface control testing method, interface control acquiring device and interface control testing device - Google Patents

Interface control acquiring method, interface control testing method, interface control acquiring device and interface control testing device Download PDF

Info

Publication number
CN107203373B
CN107203373B CN201610158666.9A CN201610158666A CN107203373B CN 107203373 B CN107203373 B CN 107203373B CN 201610158666 A CN201610158666 A CN 201610158666A CN 107203373 B CN107203373 B CN 107203373B
Authority
CN
China
Prior art keywords
control
target control
target
interface
characteristic value
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
Application number
CN201610158666.9A
Other languages
Chinese (zh)
Other versions
CN107203373A (en
Inventor
潘子晶
周丹丹
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Banma Zhixing Network Hongkong Co Ltd
Original Assignee
Alibaba Group Holding Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to CN201610158666.9A priority Critical patent/CN107203373B/en
Publication of CN107203373A publication Critical patent/CN107203373A/en
Application granted granted Critical
Publication of CN107203373B publication Critical patent/CN107203373B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • G06F8/38Creation or generation of source code for implementing user interfaces
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/362Software debugging
    • G06F11/3648Software debugging using additional hardware
    • G06F11/3656Software debugging using additional hardware using a specific debug interface
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3688Test management for test execution, e.g. scheduling of test suites

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Software Systems (AREA)
  • Human Computer Interaction (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The application discloses an acquisition method, a test method, an acquisition device and a test device of an interface control, wherein the acquisition method of the interface control can acquire control parameters of at least one target control through a specified control interface; the control parameters comprise a control type and a characteristic value, and the characteristic value is used for uniquely identifying the target control; and packaging the control type through a reflection mechanism and obtaining the target control corresponding to the characteristic value. When the control is acquired, different control types can be acquired through the appointed control interface through the reflection mechanism, and the static implementation mode that the types are determined in advance to call different interfaces is avoided.

Description

Interface control acquiring method, interface control testing method, interface control acquiring device and interface control testing device
Technical Field
The present application relates to an interface control acquiring technology, and in particular, to an interface control acquiring method, an interface control testing method, an interface control acquiring apparatus, and an interface control testing apparatus.
Background
In the prior art, a method for acquiring a control of a User Interface (UI) generally needs to call different control methods according to a control type to acquire the control, for example, a userclassname (strinclassname) method acquires the control by transmitting a class name String, and a userclasstext (strinclasstext) method acquires the control by transmitting a display text String. When the control has multiple types, multiple interfaces are required to be called to obtain the control, and the called control methods (such as className (), text ()) need to be fixedly written in the code, and if the type or the attribute of the control changes, the code needs to be modified, or the control needs to be obtained by using other interfaces instead.
Disclosure of Invention
In view of this, the present application provides an interface control obtaining method, an interface control testing method, an interface control obtaining apparatus, and an interface control testing apparatus, so as to solve the problems in the prior art.
According to a first aspect of an embodiment of the present application, a method for acquiring an interface control is provided, where the method includes:
acquiring control parameters of at least one target control through a specified control interface; the control parameters comprise a control type and a characteristic value, and the characteristic value is used for uniquely identifying the target control;
and packaging the control type through a reflection mechanism and obtaining the target control corresponding to the characteristic value.
According to a second aspect of the embodiments of the present application, there is provided a method for testing an interface control, the method including the steps of:
acquiring control parameters of at least one target control through a specified control interface; the control parameters comprise a control type and a characteristic value, and the characteristic value is used for uniquely identifying the target control;
packaging the control type through a reflection mechanism and obtaining a target control corresponding to the characteristic value;
and testing the target control.
According to a third aspect of the embodiments of the present application, an apparatus for obtaining an interface control is provided, including:
the parameter acquisition module is used for acquiring control parameters of at least one target control through a specified control interface; the control parameters comprise a control type and a characteristic value, and the characteristic value is used for uniquely identifying the target control;
and the control acquisition module is used for packaging the control type through a reflection mechanism and acquiring the target control corresponding to the characteristic value.
According to a fourth aspect of the embodiments of the present application, there is provided an apparatus for testing an interface control, including:
the control acquisition interface is used for acquiring control parameters of at least one target control through the specified control interface; the control parameters comprise a control type and a characteristic value, and the characteristic value is used for uniquely identifying the target control; packaging the control type through a reflection mechanism and obtaining a target control corresponding to the characteristic value;
and the control verification interface is used for testing the target control.
When the control is acquired, different control types can be acquired through the appointed control interface through the reflection mechanism, and the static implementation mode that the types are determined in advance to call different interfaces is avoided. In addition, the designated control interface can acquire different control types, so that the control types can be dynamically determined through codes, and the codes of the control interface can be modified without modifying and acquiring partial codes of each control when the subsequent control types change.
Drawings
FIG. 1 is a flowchart of a method for obtaining an interface control according to an embodiment of the present application;
FIG. 2 is a flow chart of a testing method in an embodiment of the present application;
FIG. 3 is a flow chart of an application scenario of the present application;
FIG. 4 is a diagram of a hardware architecture of an acquisition device/test device for interface controls according to the present application;
FIG. 5 is a logic block diagram of a test method and an acquisition device;
FIG. 6 is a logic block diagram of a test apparatus.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
In the present application, a control may be an interface element of a user interface, and the information arrangement displayed by the control may be changed by a user, for example, a window, a text box, a slider, a pull-down menu, and the like. The user interface may be a user interface of an application client, or a user interface of a browser, operating system application, or the like. The user interface may be presented to the user through a display device of the device, and the device may be any device capable of presenting the user interface, such as a personal computer, a tablet computer, a mobile terminal, a smart home device, a vehicle-mounted device, and the like.
The process for acquiring the interface control provided by the present application may refer to fig. 1.
S101, acquiring control parameters of at least one target control through a specified control interface; the control parameters comprise a control type and a characteristic value, and the characteristic value is used for uniquely identifying the target control;
and S102, packaging the control type through a reflection mechanism, and obtaining a target control corresponding to the characteristic value.
The method and the device establish a uniform control interface, and obtain more than one control parameter through the control interface.
By way of example, the control parameters may be uniformly pre-stored in a collection. Besides the control parameters required by the acquired control, other parameters such as related parameters (e.g., information such as control name, text description, attribute value, etc.) for testing whether the setting parameters of the control are correct can be included in the set. The collection may store the individual control parameters in the form of a two-dimensional array. The control interface may traverse all arrays in the set to obtain control parameters.
The control parameters are uniformly stored in the set, so that decentralized processing can be avoided, but the control interface is not excluded from obtaining the control parameters in other decentralized processing modes, for example, the control parameters of each control can be read from a plurality of files respectively.
In some scenarios, a collection for saving control parameters may be stored in a configuration file, and a control interface obtains the control parameters by reading the configuration file; in other scenarios, the collection for storing the control parameters may be stored in a server, and the control interface may interact with the server through the device where the control interface is located to obtain the control parameters.
In the S102 stage, the present application obtains the control by using a reflection mechanism (Method), and the reflection mechanism may be implemented by JAVA. The reflection mechanism may enable designer-created code to be assembled at runtime without the need for source-representative links between components. The method and the device can achieve batch acquisition of the plurality of target controls through a reflection mechanism.
Due to the diversity of control types, a reflection mechanism may be used to encapsulate the control types to obtain different types of controls, and as an example, the specific steps may be:
firstly, packaging a control type, obtaining a method name character string corresponding to the control type, and obtaining a target control corresponding to the control type by using a reflection mechanism; and then calling the obtained method of the target control, and transmitting a characteristic value corresponding to the control type to obtain the target control corresponding to the characteristic value. In some cases, a single string may be used as a feature value, and in other cases, a combination of more than one string may be required to construct a feature value. To facilitate distinguishing individual controls when there are multiple identical controls on the interface, the order of the controls to be looked up in the results can also be identified.
Therefore, the control acquisition can be realized by using the unified control interface provided by the application, and different control types can be acquired through the control interface, so that a static realization mode that the type is determined in advance to call different interfaces is avoided. In addition, different control types can be acquired through the designated control interface, so that the control type can be dynamically determined through the code, and the code of the control interface can be modified without modifying and acquiring partial codes of each control when the subsequent control type changes.
After the control is obtained in the above manner, the method may be applied to various occasions, and fig. 2 is an example of performing a UI test on the obtained control.
Referring to fig. 2, S101, acquiring control parameters of at least one target control through a designated control interface; the control parameters comprise a control type and a characteristic value, and the characteristic value is used for uniquely identifying the target control;
s102, packaging the control type through a reflection mechanism, and obtaining a target control corresponding to the characteristic value;
s201, testing the target control.
The process of obtaining the control in S101 and S102 is not repeated.
The verification method of each target control can be called to test the acquired target controls respectively according to the prior art, and in addition, a plurality of target controls can be tested in a unified manner through a unified verification interface according to the following mode.
The conditions that different controls need to be tested can be different, for example, for some controls, only the control needs to be verified whether the control exists on the interface; for other controls, it is necessary to verify that the control is present and available on the interface; there are also controls that need to verify that certain properties of the control and the value settings of the properties are correct (e.g., for Button controls, the control available property (Enable), Focus property (Focus), and property values (True, False) need to be tested). Thus, as an example, the process of stage S201 may be to test the target control for one or more of:
judging whether a target control exists or not;
when the target control exists, judging whether the target control is available;
and when the target control is available, judging whether the attribute to be detected and the attribute value setting of the target control are correct or not.
In one example, the test result may be output, for example, whether the target control exists may be determined according to the output result of S102, and if not, an error log may be output; if the target control exists, further acquiring an 'Enable' attribute of the target control, and if the attribute is unavailable, outputting an error log; and if the attribute is available, further acquiring the attribute and the attribute value of the target control, then comparing the attribute and the attribute value with a preset value, and if the attribute and the attribute value of the target control do not correspond to the preset value, outputting an error log. As an example, the manner of comparing the obtained attributes and attribute values of the target control may be that the two perform an and operation.
In one example, the preset values of the parameters of the control that need to be verified (i.e., the various properties and property values in the correct state of the control) can all be stored in the above-mentioned collection. The attributes and attribute values of the controls may be assigned to values raised to the power of two when stored, an example illustration of a set follows. The preset values of the control parameters to be verified are stored in the set: the control parameters "CHECKABLE", "UNCHECKABLE", "CHECKED", "UNCHECKED". Each control parameter is assigned a different value, for example, CHECKABLE has a value of 0x0001, UNCHECKED has a value of 0x0002, CHECKED has a value of 0x0004, UNCHECKED has a value of 0x 0008.
A two-dimensional array may be defined and traversed to check the properties of each target control to be verified. After the attributes and the attribute values of the target control are obtained, the attributes and the attribute values are converted into corresponding binary systems according to assignment rules in the set, then the binary systems are compared with the values in the corresponding array items in the two-dimensional array, if the attributes and the attribute values are consistent, the attribute setting is considered to be correct, and if not, an error log is output.
The following is an example of a process for testing a control. During testing, firstly, sequentially taking out the control type and the characteristic value from the control parameter of each array from the two-dimensional array as input parameters of a unified control interface, if the result of obtaining the control is not null, checking the 'Enable' attribute of the obtained control, if the 'Enable' attribute is available, judging whether the attribute of the control and the preset value of the attribute value exist in the two-dimensional array, if so, performing 'AND' operation on the attribute of the control, the attribute value and the preset value, and outputting a correct or wrong return value according to the 'AND' result.
FIG. 3 is an example of an application client interface control test.
S301, in a configuration stage before control testing, a configuration file is created, a two-dimensional array is stored in the configuration file, and preset values of control parameters of all controls to be tested on a UI interface are stored in the two-dimensional array to represent setting parameters of the controls during normal working. The control parameters at least comprise a control type and a characteristic value of the control; for the control needing to test the attribute, the control parameter may further include the attribute of the control and a preset value of the attribute value.
S302 is an interface creating stage, wherein a control acquiring interface and a control verifying interface are created.
And S303 is a control acquiring stage. And traversing each array in the configuration file by the control acquisition interface, acquiring the control type parameter in each array, packaging and acquiring the controls corresponding to the characteristic values in the array through a reflection mechanism.
S304 is a control testing stage. And the control verification interface tests the output result of the control acquisition interface. For a certain control, if the control is not obtained, outputting an error log; if the control is acquired, acquiring an 'Eable' attribute of the control, if the 'Eable' attribute is set to be unavailable, outputting an error log, if the 'Eable' attribute is available, checking whether the array in the configuration file has the attribute of the control and the preset value of the attribute value, if the array in the configuration file has the attribute of the control and the preset value of the attribute value, taking out the preset value and the attribute value of the control to carry out 'AND' operation, if the result is 1, returning a correct value of the test result, and if the result is not 1, outputting the error log.
Corresponding to the embodiments of the obtaining method and the testing method of the interface control, the application also provides embodiments of an obtaining device and a testing device of the interface control.
The embodiment of the acquisition device and the test device of the interface control can be applied to a computer. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for running through the processor of the computer where the software implementation is located as a logical device. From a hardware aspect, as shown in fig. 4, the hardware structure diagram of the computer of the present application is shown, except for the processor, the memory, the network interface, and the nonvolatile memory shown in fig. 4, a computer where the apparatus is located in the embodiment may also include other hardware according to an actual function of the computer, which is not described again.
Referring to fig. 5, the interface control acquiring apparatus 500 includes:
a parameter obtaining module 501, configured to obtain a control parameter of at least one target control through a specified control interface; the control parameters comprise a control type and a characteristic value, and the characteristic value is used for uniquely identifying the target control;
a control obtaining module 502, configured to encapsulate the control type through a reflection mechanism and obtain a target control corresponding to the feature value.
The control parameters may be pre-stored in the same collection. The collection may be stored in a configuration file.
The step of the control obtaining module 502 encapsulating the control type through a reflection mechanism and obtaining the target control corresponding to the feature value may include:
packaging the control type and obtaining a method name character string corresponding to the control type;
a method for acquiring a target control corresponding to the control type by using a reflection mechanism;
and calling the obtained method of the target control, and transmitting the characteristic value corresponding to the control type to obtain the target control corresponding to the characteristic value.
Referring to fig. 6, the interface control testing apparatus 600 includes:
the control acquiring interface 601 is used for acquiring control parameters of at least one target control through a specified control interface; the control parameters comprise a control type and a characteristic value, and the characteristic value is used for uniquely identifying the target control; packaging the control type through a reflection mechanism and obtaining a target control corresponding to the characteristic value;
a control verification interface 602, configured to test the target control.
The control parameters may be pre-stored in the same collection. The collection may be stored in a configuration file.
The step of encapsulating the control type and obtaining the target control corresponding to the feature value by the control obtaining interface 601 through a reflection mechanism includes:
packaging the control type and obtaining a method name character string corresponding to the control type;
a method for acquiring a target control corresponding to the control type by using a reflection mechanism;
and calling the obtained method of the target control, and transmitting the characteristic value corresponding to the control type to obtain the target control corresponding to the characteristic value.
Testing the target control by the control validation interface 602 may include one or more of:
judging whether the target control exists or not;
when the target control exists, judging whether the target control is available;
and when the target control is available, judging whether the attribute and the attribute value setting of the target control are correct or not.
The control parameters can also comprise attributes of the target control and preset values of attribute values;
the control verification interface 602 determines whether the setting of the attribute and the attribute value of the target control is correct according to whether the attribute and the attribute value of the target control correspond to the preset value.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.

Claims (16)

1. A method for acquiring an interface control is characterized by comprising the following steps:
acquiring control parameters of at least one target control through a specified control interface; the control parameters comprise a control type and a characteristic value, and the characteristic value is used for uniquely identifying the target control;
packaging the control type through a reflection mechanism and obtaining a target control corresponding to the characteristic value, wherein the steps of:
packaging the control type and obtaining a method name character string corresponding to the control type;
a method for acquiring a target control corresponding to the control type by using a reflection mechanism;
and calling the obtained method of the target control, and transmitting the characteristic value corresponding to the control type to obtain the target control corresponding to the characteristic value.
2. The method of claim 1, wherein the control parameters are pre-stored in the same set.
3. The method of claim 2, wherein the collection is stored in a configuration file.
4. A method for testing an interface control is characterized by comprising the following steps:
acquiring control parameters of at least one target control through a specified control interface; the control parameters comprise a control type and a characteristic value, and the characteristic value is used for uniquely identifying the target control;
packaging the control type through a reflection mechanism and obtaining a target control corresponding to the characteristic value, wherein the steps of:
packaging the control type and obtaining a method name character string corresponding to the control type;
a method for acquiring a target control corresponding to the control type by using a reflection mechanism;
calling the obtained method of the target control, and transmitting a characteristic value corresponding to the control type to obtain the target control corresponding to the characteristic value;
and testing the target control.
5. The method of claim 4, wherein the control parameters are pre-stored in the same set.
6. The method of claim 5, wherein the collection is stored in a configuration file.
7. The method of claim 4, wherein testing the target control comprises one or more of:
judging whether the target control exists or not;
when the target control exists, judging whether the target control is available;
and when the target control is available, judging whether the attribute and the attribute value setting of the target control are correct or not.
8. The method of claim 7, wherein the control parameters further comprise preset values for properties and property values of the target control;
and judging whether the attribute and the attribute value of the target control are correctly set or not according to whether the attribute and the attribute value of the target control correspond to the preset value or not.
9. An apparatus for acquiring an interface control, comprising:
the parameter acquisition module is used for acquiring control parameters of at least one target control through a specified control interface; the control parameters comprise a control type and a characteristic value, and the characteristic value is used for uniquely identifying the target control;
a control obtaining module, configured to encapsulate the control type through a reflection mechanism and obtain a target control corresponding to the feature value, where the control obtaining module includes:
packaging the control type and obtaining a method name character string corresponding to the control type;
a method for acquiring a target control corresponding to the control type by using a reflection mechanism;
and calling the obtained method of the target control, and transmitting the characteristic value corresponding to the control type to obtain the target control corresponding to the characteristic value.
10. The apparatus of claim 9, wherein the control parameters are pre-stored in the same set.
11. The apparatus of claim 10, wherein the collection is stored in a configuration file.
12. An apparatus for testing interface controls, comprising:
the control acquisition interface is used for acquiring control parameters of at least one target control through the specified control interface; the control parameters comprise a control type and a characteristic value, and the characteristic value is used for uniquely identifying the target control; packaging the control type through a reflection mechanism and obtaining a target control corresponding to the characteristic value, wherein the steps of:
packaging the control type and obtaining a method name character string corresponding to the control type;
a method for acquiring a target control corresponding to the control type by using a reflection mechanism;
calling the obtained method of the target control, and transmitting a characteristic value corresponding to the control type to obtain the target control corresponding to the characteristic value;
and the control verification interface is used for testing the target control.
13. The apparatus of claim 12, wherein the control parameters are pre-stored in the same set.
14. The apparatus of claim 13, wherein the collection is stored in a configuration file.
15. The apparatus of claim 12, wherein the control validation interface testing the target control comprises one or more of:
judging whether the target control exists or not;
when the target control exists, judging whether the target control is available;
and when the target control is available, judging whether the attribute and the attribute value setting of the target control are correct or not.
16. The apparatus of claim 15, wherein the control parameters further comprise preset values for properties and property values of the target control;
and the control verification interface judges whether the attribute and attribute value setting of the target control is correct or not according to whether the attribute and attribute value of the target control correspond to the preset value or not.
CN201610158666.9A 2016-03-18 2016-03-18 Interface control acquiring method, interface control testing method, interface control acquiring device and interface control testing device Active CN107203373B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610158666.9A CN107203373B (en) 2016-03-18 2016-03-18 Interface control acquiring method, interface control testing method, interface control acquiring device and interface control testing device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610158666.9A CN107203373B (en) 2016-03-18 2016-03-18 Interface control acquiring method, interface control testing method, interface control acquiring device and interface control testing device

Publications (2)

Publication Number Publication Date
CN107203373A CN107203373A (en) 2017-09-26
CN107203373B true CN107203373B (en) 2020-10-20

Family

ID=59904471

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610158666.9A Active CN107203373B (en) 2016-03-18 2016-03-18 Interface control acquiring method, interface control testing method, interface control acquiring device and interface control testing device

Country Status (1)

Country Link
CN (1) CN107203373B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110704327B (en) * 2019-10-11 2023-03-31 江苏赛诺格兰医疗科技有限公司 Auxiliary method for PET-CT system control software automatic test
CN114416084B (en) * 2021-12-31 2023-04-07 北京五八信息技术有限公司 Data processing method and device, electronic equipment and storage medium
CN115080026B (en) * 2022-08-23 2022-11-25 湖南云畅网络科技有限公司 Plug-in control integration method and system based on low codes

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101739251A (en) * 2008-11-17 2010-06-16 康佳集团股份有限公司 Method and system for generating interface control
CN103176802A (en) * 2013-03-29 2013-06-26 厦门亿联网络技术股份有限公司 Method of achieving separation of user interface UI of system and control library through control pool
CN103995694A (en) * 2014-03-31 2014-08-20 中邮科通信技术股份有限公司 Mobile client browser control with telecommunication capacity and calling method thereof

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101739251A (en) * 2008-11-17 2010-06-16 康佳集团股份有限公司 Method and system for generating interface control
CN103176802A (en) * 2013-03-29 2013-06-26 厦门亿联网络技术股份有限公司 Method of achieving separation of user interface UI of system and control library through control pool
CN103995694A (en) * 2014-03-31 2014-08-20 中邮科通信技术股份有限公司 Mobile client browser control with telecommunication capacity and calling method thereof

Also Published As

Publication number Publication date
CN107203373A (en) 2017-09-26

Similar Documents

Publication Publication Date Title
EP4224309A2 (en) Model integration tool
CN105589805B (en) Method and device for generating code coverage rate report
CN107729227B (en) Application program test range determining method, system, server and storage medium
CN109408375B (en) Method and device for generating interface document
CN105302710A (en) Method and apparatus for determining test case in need of regression testing
CN111290742A (en) Parameter verification method and device, electronic equipment and readable storage medium
CN107526676B (en) Cross-system test method and device
CN107203373B (en) Interface control acquiring method, interface control testing method, interface control acquiring device and interface control testing device
CN108132876B (en) Embedded software object code unit testing method based on injection mode
CN106126424A (en) A kind of visual automated testing method of script, device and mobile terminal
CN109558313B (en) Method and device for constructing abnormal test scene
CN111124871A (en) Interface test method and device
CN112464317A (en) Drawing modification method, product management system and computer storage medium
CN107357721B (en) Method and device for testing system
CN106326102A (en) Test method and apparatus
CN113032202B (en) Chip verification method, system, device, computer equipment and storage medium
CN106502887A (en) A kind of stability test method, test controller and system
CN113778878A (en) Interface testing method and device, electronic equipment and storage medium
CN113220568A (en) Method, device and medium for testing USIM card file system
CN110399304B (en) Script testing method and system
CN111767218A (en) Automatic testing method, equipment and storage medium for continuous integration
CN111538659A (en) Interface testing method and system for service scene, electronic device and storage medium
CN113127099B (en) Server configuration method, device, equipment and storage medium
CN105162799A (en) Method for checking whether client is legal mobile terminal or not and server
CN106294104B (en) Test case execution method and mobile terminal

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right

Effective date of registration: 20201217

Address after: Room 603, 6 / F, Roche Plaza, 788 Cheung Sha Wan Road, Kowloon, China

Patentee after: Zebra smart travel network (Hong Kong) Limited

Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands

Patentee before: Alibaba Group Holding Ltd.

TR01 Transfer of patent right