CN106557411B - Method and system for testing Hybrid application in Android system - Google Patents
Method and system for testing Hybrid application in Android system Download PDFInfo
- Publication number
- CN106557411B CN106557411B CN201510616653.7A CN201510616653A CN106557411B CN 106557411 B CN106557411 B CN 106557411B CN 201510616653 A CN201510616653 A CN 201510616653A CN 106557411 B CN106557411 B CN 106557411B
- Authority
- CN
- China
- Prior art keywords
- test
- hybrid application
- instruction
- behavior data
- component
- 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
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a method and a system for testing Hybrid application in an Android system, wherein the method for testing the Hybrid application in the Android system comprises the following steps: adding a custom component in the Hybrid application; generating test behavior data by taking an onNewIntent method in the custom component as an entrance; and acquiring a test instruction and calling the test behavior data according to the test instruction so as to execute the test of the Hybrid application through the called test behavior data. The testing system of the Hybrid application in the Android system is matched with the method. The method and the system for testing the Hybrid application in the Android system can improve the testing efficiency of the Hybrid application.
Description
Technical Field
The invention relates to the technical field of computer application, in particular to a method and a system for testing Hybrid application in an Android system.
Background
Hybrid applications have emerged due to the updating of computer application technology and market needs. The Hybrid application is a mixed-mode mobile application between a Native App (Native App) and a Web App (Web App). For the user, the access of the Hybrid application feels that the local application is accessed, but actually, the network application is accessed through the browser kernel packaged in the Hybrid application.
In order to improve the experience of a user, some Hybrid applications usually encapsulate a third-party browser kernel, however, most of test frames used in the existing test method cannot support the third-party browser kernel, so that the Hybrid applications embedded with the third-party browser kernel cannot be tested, and if a test environment is additionally established, the test method is complex, and time and labor are wasted.
Therefore, the existing testing method has the problem of low testing efficiency in the testing of the Hybrid application embedded with the third-party browser kernel.
Disclosure of Invention
Therefore, a method for testing the Hybrid application in the Android system, which can improve the testing efficiency of the Hybrid application, is needed.
In addition, it is necessary to provide a Hybrid application testing system in the Android system, which can improve the Hybrid application testing efficiency.
In order to solve the technical problems, the technical scheme adopted by the invention is as follows:
a method for testing Hybrid application in an Android system comprises the following steps: adding a custom component in the Hybrid application; generating test behavior data by taking an onNewIntent method in the custom component as an entrance; and acquiring a test instruction and calling the test behavior data according to the test instruction so as to execute the test of the Hybrid application through the called test behavior data.
A test system for Hybrid application in an Android system comprises a terminal, wherein the terminal comprises: the component adding module is used for adding a custom component in the Hybrid application; the data generation module is used for generating test behavior data by taking an onNewIntent method in the custom component as an entrance; and the data calling module is used for acquiring a test instruction and calling the test behavior data according to the test instruction so as to execute the test of the Hybrid application through the called test behavior data.
Compared with the prior art, the invention has the following beneficial effects:
adding a custom component in the Hybrid application, generating test behavior data by taking an oneNewIntent method in the custom component as an entrance, calling the test behavior data according to the obtained test instruction, and executing the test of the Hybrid application through the called test behavior data. That is to say, since the Hybrid application to be tested is injected by Intent, the Hybrid application can directly execute the test according to the obtained test instruction, thereby avoiding that the test framework in the existing test method can not test the Hybrid application embedded with the third-party browser kernel, and avoiding additionally setting up a test environment, thereby improving the test efficiency of the Hybrid application.
Drawings
Fig. 1 is an application environment schematic diagram of a method for testing Hybrid applications in an Android system according to an embodiment;
fig. 2 is a flowchart of a method for testing Hybrid applications in an Android system according to an embodiment;
FIG. 3 is a flow chart of a method of test behavior data generation of FIG. 2;
fig. 4 is a flowchart of a method for testing Hybrid applications in an Android system according to another embodiment;
FIG. 5 is a flow chart of the test behavior data invocation method of FIG. 2;
fig. 6 is a flowchart of a method for testing Hybrid applications in an Android system according to another embodiment;
fig. 7 is one of schematic graphical interfaces illustrating a method for testing Hybrid applications in an Android system according to an embodiment;
fig. 8 is a second graphical interface diagram of a method for testing Hybrid applications in an Android system according to an embodiment;
fig. 9 is a third graphical interface diagram of a testing method for Hybrid applications in the Android system according to the embodiment;
fig. 10 is a fourth graphical interface diagram of a method for testing Hybrid applications in the Android system according to an embodiment;
fig. 11 is a block diagram illustrating a structure of a test system for Hybrid applications in an Android system according to an embodiment;
FIG. 12 is a block diagram of a data generation module of FIG. 11;
fig. 13 is a block diagram illustrating a structure of a test system for Hybrid applications in an Android system according to another embodiment;
FIG. 14 is a block diagram of the data call module of FIG. 11;
fig. 15 is a block diagram illustrating a structure of testing a Hybrid application in an Android system according to another embodiment.
Detailed Description
Exemplary embodiments that embody features and advantages of the invention are described in detail below in the specification. It is to be understood that the invention is capable of other embodiments and that various changes in form and details may be made therein without departing from the scope of the invention and the description and drawings are to be regarded as illustrative in nature and not as restrictive.
In an embodiment, a computer system operated by a method for testing Hybrid applications in an Android system is shown in fig. 1. The computer system 100 includes a terminal 110, a tester 130 that interacts with the terminal 110.
The terminal 110 may be a smart phone, a tablet computer, or the like. The terminal 110 supports an Android system, and a Hybrid application can run therein.
The testing machine 130 may be a desktop computer, a laptop computer, a server, etc. A test environment may be built on the test machine 130, for example, a test framework Selenium Web Driver is used as a test environment body. Native components on the Android system of the terminal 110, such as a local interface component and a web view (WebView) component, can be grasped and operated through the built test environment, so as to test the Hybrid application running on the terminal 110.
It should be noted that, when the method for testing the Hybrid application runs on the computer system, not only the Hybrid application embedded with the native browser kernel can be tested, but also the Hybrid application embedded with the third-party browser kernel can be tested.
Referring to fig. 2, in an embodiment, a method for testing Hybrid applications in an Android system includes the following steps:
The Hybrid application runs in a terminal supporting an Android system, and comprises three basic components, namely an Activity component, a Service component and a Broadcast Receiver component, so as to form various native components capable of realizing different access requests of a user. For example, a native component may implement an access request for a user to browse a web page.
In the test of the Hybrid application, in order to distinguish from the native component, the addition of the custom component is performed, so that the test of the Hybrid application is performed through the custom component.
That is, the native component and the custom component can realize different access requests of the user, and the difference is that the native component is used for daily access of the Hybrid application, and the custom component is only used for testing the Hybrid application.
And step 230, generating test behavior data by taking an onNewIntent method in the custom component as an entrance.
As mentioned previously, for the user, the access of the Hybrid application is actually the access of the web application through the browser kernel enclosed therein. Therefore, in the test of the Hybrid application, the test behavior data is used for simulating the access behavior of the user to access the Hybrid application so as to test whether the Hybrid application can be normally accessed.
By using the ONNewIntent method in the custom component as an entrance to generate test behavior data, the Hybrid application of the embedded browser kernel is injected by the Intent, so that the precondition that the Hybrid application of the embedded third-party browser kernel can directly execute the test is met. When the access behavior of the user simulated by the test behavior data triggers the Hybrid application, the test of the Hybrid application is executed.
Certainly, in other embodiments, a test case may be further generated by combining multiple groups of different test behavior data, so as to facilitate the automated test of the Hybrid application, thereby further improving the test efficiency of the Hybrid application.
And step 250, acquiring a test instruction and calling test behavior data according to the test instruction so as to execute the test of the Hybrid application through the called test behavior data.
The test instruction is sent to the Hybrid application running on the terminal through the test environment built on the tester, for example, the main body of the test environment may be an automatic test framework or an ADB debugging tool dedicated for the Android system.
The test instruction at least comprises an instruction for indicating how the Hybrid application calls the test behavior data, so that the Hybrid application calls the test behavior data according to the instruction of the test instruction.
After the test behavior data is called according to the test instruction, the Hybrid application executes triggering according to the access behavior of the user simulated by the test behavior data, so as to execute the test of the Hybrid application.
By the method, the Hybrid application injected by the Intent can call the test behavior data according to the obtained test instruction to directly execute the test, so that the method can support not only the native browser kernel, but also the third-party browser kernel, the problem that a test frame cannot test the Hybrid application embedded with the third-party browser kernel in the existing test method is avoided, and extra test environment building is also avoided, thereby improving the test efficiency of the Hybrid application.
Referring to fig. 3, in one embodiment, step 230 includes the following steps:
and 231, adding the JAVA object for the custom component in the Hybrid application.
In this embodiment, the JAVA object is a javascript object, and the javascript object supports an transliterated script language. By adding the javascript object to the custom component, a method for directly accessing the JAVA object in the custom component is provided for the script generated in the test machine.
Of course, in other embodiments, other types of objects may be added to the custom component to support other kinds of scripting languages, for example, Python objects support Python scripting languages, and Ruby objects support Ruby scripting languages.
Through the steps, the Hybrid application can be accurately and stably tested through any script language, so that the problem that the Hybrid application testing efficiency is low due to the fact that errors are prone to occur when different script languages are switched to test the Hybrid application is solved, and the testing cost is reduced.
Through the established binding relationship, the JAVA object in the custom component and the native object in the kernel of the Hybrid application can be mutually called.
Based on this, for the tester, it accesses the JAVA objects in the custom components it can support, while for the Hybrid application, it calls the native objects in the kernel.
That is to say, even if the third-party browser kernel is packaged by the Hybrid application, the third-party browser kernel is disguised as the native browser kernel which can be supported in the tester through the binding relationship, so that the tester can directly test the Hybrid application, and the problem that the Hybrid application embedded with the third-party browser kernel cannot be tested by a test frame in the existing test method is solved.
In addition, as described above, since the JAVA object in the custom component can be accessed by the script generated in the tester, the script generated in the tester can also access the native object in the kernel through the JAVA object in the custom component based on the binding relationship between the native object and the JAVA object.
Through the steps, the script generated in the testing machine can be used for executing the test of the Hybrid application, so that the limitation of the automatic test of the graphical interface in the existing testing method can be avoided, and the testing efficiency of the Hybrid application is further improved.
And step 235, adding the native object at the entrance according to the access behavior of the simulation user to form test behavior data.
The access behavior of the user comprises clicking a button, opening a webpage, browsing the webpage and the like, and correspondingly, the triggering operation of the user on the Hybrid application comprises clicking operation, opening operation, sliding operation and the like. For example, through the sliding operation of the user on the Hybrid application, the user will browse the web page through the web page interface displayed by the Hybrid application.
Based on the method, the native objects in the kernel are added to the entry according to the access behaviors of the simulation user, and the formed test behavior data can simulate the access behaviors of the simulation user to execute corresponding trigger operations so as to realize certain access requests of the user.
That is, by calling the test behavior data, the Hybrid application is triggered by the corresponding trigger operation, so that a certain access request of the user is realized, and the test of the Hybrid application is performed.
Referring to fig. 4, in an embodiment, before step 250, the method further includes the following steps:
In this embodiment, the test environment body built on the test machine is an ADB debugging tool dedicated to the Android system.
Through the click operation triggered by the tester in the command input interface of the ADB debugging tool, the ADB debugging tool can intercept to obtain a test instruction and send the test instruction to the Hybrid application running in the terminal through the tester.
As described above, the test instruction at least includes an instruction indicating how the Hybrid application calls the test behavior data, so that the Hybrid application calls the test behavior data according to the instruction of the test instruction, and the test behavior data is generated in the entry of the onenewintent method in the custom component, so that the test instruction at least includes a start instruction and an execution instruction. The starting instruction is used for starting the custom assembly, and the executing instruction is used for calling the test behavior data in the custom assembly.
After receiving the test instruction sent by the tester, the Hybrid application calls the test behavior data generated in the custom component according to the starting instruction and the execution instruction in the test instruction, so as to execute the test of the Hybrid application through the called test behavior data.
Referring to FIG. 5, in one embodiment, step 250 includes the following steps:
in step 251, a start instruction and an execution instruction are extracted from the acquired test instruction.
As mentioned above, the test instructions are fetched by the ADB debug tool, which includes at least the start instruction and the execution instruction, and based on this, the start instruction and the execution instruction can be extracted from the fetched test instructions.
And step 253, starting the self-defining component according to the starting instruction.
In step 255, when the execution condition indicated by the execution instruction is satisfied, the Hybrid application is triggered according to the test behavior indicated by the test behavior data, so as to execute the test of the Hybrid application.
Before triggering the Hybrid application, whether an execution condition indicated by an execution instruction is met needs to be judged, if the execution condition is judged to be not met, the execution condition is continuously waited until the execution condition is met, and if the execution condition is judged to be met, test behavior data is called to simulate an access behavior of a user to access the Hybrid application.
The test behavior data is used for simulating the access behavior of the user to access the Hybrid application, so that the test behavior indicated by the test behavior data is the corresponding trigger operation executed by simulating the access behavior of the user.
After the test behavior data is called, triggering the Hybrid application according to the test behavior indicated by the test behavior data, if the test behavior is effective, triggering the Hybrid application to indicate that the Hybrid application can be normally accessed, otherwise, indicating that the access of the Hybrid application is abnormal.
Referring to fig. 6, in an embodiment, before step 253, the method further includes the following steps:
and step 410, adding nodes in the global configuration file of the Hybrid application.
The global configuration file of the Hybrid application is used for describing all components added in the Hybrid application, so that the Android system can know which components in the Hybrid application and which access requests of the user can be realized by the components respectively.
Based on this, after the custom component is added to the Hybrid application, a corresponding node needs to be added to the global configuration file, so that it is ensured that the added custom component is not abnormal in starting.
The starting mode of the components in the Android system comprises four modes, and the starting operation mode corresponding to the components in each mode is different. Therefore, after the starting mode of the custom component is set in the node, the custom component can be started according to the set starting mode.
For example, the following are set in the node: launchmode = 'singleTask', namely, the starting mode of the custom component is a single task mode, and the custom component is started and called through an onNewIntent method.
In an application scenario, please refer to fig. 7 to 10, and fig. 7 to 10 show a complete test process of the method for testing the Hybrid application in the Android system in a specific implementation process. Taking the terminal as a smart phone, running the Hybrid application therein, and taking the test environment body set up in the tester as a dedicated ADB debugging tool in the Android system, performing button click test on the Hybrid application as an example, the specific implementation process is described as follows.
After the smart phone is powered on, a custom component browse activity is added to the Hybrid application com.test.app, and the onenewintent method in the custom component is used as an entrance to generate test behavior data as shown in fig. 7.
Then, a test instruction as shown in fig. 8 is input in a command input interface Terminal of the ADB debugging tool, and is sent to the Hybrid application running on the smartphone through the tester. Wherein, the adb shell am start is a start instruction in the test instruction, and the ClickElementByID is an execution instruction in the test instruction.
Further, when the execution condition is judged to be met by executing the instruction, the test behavior indicated by the click () in the test behavior data is effective, the L ogin button is clicked, and the test behavior data enters a welcor page, as shown in fig. 10, which indicates that the button click test of the Hybrid application passes, and the user can normally access the function of the Hybrid application.
Referring to fig. 11, in an embodiment, a system for testing Hybrid applications in an Android system includes a terminal 500, where the terminal 500 includes: a component adding module 510, a data generating module 530, and a data calling module 550.
The component adding module 510 is used for adding a custom component in the Hybrid application.
The data generation module 530 is configured to generate test behavior data by using an onenewintent method in the custom component as an entry.
The data calling module 550 is configured to obtain a test instruction and call the test behavior data according to the test instruction, so as to execute a test on the Hybrid application through the called test behavior data.
Referring to fig. 12, in an embodiment, the data generating module 530 includes: a JAVA object adding unit 531, a JAVA object injecting unit 533, and a native object adding unit 535.
The JAVA object adding unit 531 is configured to add a JAVA object to the custom component in the Hybrid application.
The JAVA object injecting unit 533 is configured to inject a JAVA object for the kernel of the Hybrid application in the onCreate method in the custom component, so as to establish a binding relationship between the primitive object in the kernel and the JAVA object.
The native object adding unit 535 is for adding the native object at the portal in accordance with the access behavior of the simulation user to form test behavior data.
Referring to fig. 13, in an embodiment, the apparatus further includes a testing machine 600 interacting with the terminal 500, where the testing machine 600 includes: an instruction interception module 610 and an instruction sending module 630.
The instruction interception module 610 is configured to intercept a test instruction that is triggered to be input in the debug tool.
The instruction sending module 630 is configured to send a test instruction to the Hybrid application.
Referring to fig. 14, in an embodiment, the data calling module 550 includes: an instruction fetch unit 551, a component activation unit 553, and a test trigger unit 555.
The instruction extracting unit 551 is configured to extract a start instruction and an execution instruction from the acquired test instruction.
The component start unit 553 is configured to start the custom component according to the start instruction.
The test triggering unit 555 is configured to trigger the Hybrid application according to the test behavior indicated by the test behavior data to execute the test of the Hybrid application when the execution condition indicated by the execution instruction is satisfied.
Referring to fig. 15, in an embodiment, the terminal 500 further includes: a node adding module 570 and a starting mode setting module 590.
The node adding module 570 is configured to add a node in the global configuration file of the Hybrid application.
The starting mode setting module 590 is used for setting the starting mode of the custom component in the node.
The above-mentioned embodiments are merely preferred examples of the present invention, and not intended to limit the present invention, and those skilled in the art can easily make various changes and modifications according to the main concept and spirit of the present invention, so that the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (8)
1. A method for testing Hybrid application in an Android system is characterized by comprising the following steps:
adding a custom component in the Hybrid application;
adding a scripting language object to the custom component in the Hybrid application;
injecting the script language object into the kernel of the Hybrid application by an onCreate method in the custom component so as to establish the binding relationship between the original object in the kernel and the script language object;
adding the native object in the entrance according to the trigger operation performed by the simulation user by taking an onNewIntent method in the custom assembly as the entrance to form test behavior data;
and acquiring a test instruction and calling the test behavior data according to the test instruction so as to execute the test of the Hybrid application through the called test behavior data.
2. The method of claim 1, wherein prior to the step of obtaining a test instruction and invoking the test behavior data in accordance with the test instruction to perform testing of the Hybrid application with the invoked test behavior data, the method further comprises:
monitoring to obtain the test instruction triggered and input in the debugging tool; and
and sending the test instruction to the Hybrid application.
3. The method of claim 1, wherein the step of obtaining a test instruction and calling the test behavior data according to the test instruction to perform the test of the Hybrid application through the called test behavior data comprises:
extracting a starting instruction and an executing instruction from the acquired test instruction;
starting the self-defining component according to the starting instruction; and
and when the execution condition indicated by the execution instruction is met, triggering the Hybrid application according to the test behavior indicated by the test behavior data so as to execute the test of the Hybrid application.
4. The method of claim 3, wherein prior to the step of launching the custom component according to the launch instruction, the method further comprises:
adding nodes in the global configuration file of the Hybrid application; and
and setting the starting mode of the self-defined component in the node.
5. The testing system for the Hybrid application in the Android system is characterized by comprising a terminal, wherein the terminal comprises:
the component adding module is used for adding a custom component in the Hybrid application;
the object adding unit is used for adding a script language object to the custom component in the Hybrid application;
the object injection unit is used for injecting the script language object into the kernel of the Hybrid application by an onCreate method in the custom component so as to establish the binding relationship between the original object in the kernel and the script language object;
the native object adding unit is used for taking an onNewIntent method in the custom component as an entrance, and adding the native object in the entrance according to the triggering operation performed by a simulation user to form test behavior data;
and the data calling module is used for acquiring a test instruction and calling the test behavior data according to the test instruction so as to execute the test of the Hybrid application through the called test behavior data.
6. The system of claim 5, further comprising a tester interacting with the terminal, the tester comprising:
the instruction interception module is used for intercepting and obtaining the test instruction triggered and input in the debugging tool; and
and the instruction sending module is used for sending the test instruction to the Hybrid application.
7. The system of claim 5, wherein the data call module comprises:
the instruction extracting unit is used for extracting a starting instruction and an execution instruction from the acquired test instruction;
the component starting unit is used for starting the self-defined component according to the starting instruction; and
and the test triggering unit is used for triggering the Hybrid application according to the test behavior indicated by the test behavior data when the execution condition indicated by the execution instruction is met so as to execute the test of the Hybrid application.
8. The system of claim 7, wherein the terminal further comprises:
the node adding module is used for adding nodes in the global configuration file of the Hybrid application; and
and the starting mode setting module is used for setting the starting mode of the self-defined component in the node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510616653.7A CN106557411B (en) | 2015-09-24 | 2015-09-24 | Method and system for testing Hybrid application in Android system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510616653.7A CN106557411B (en) | 2015-09-24 | 2015-09-24 | Method and system for testing Hybrid application in Android system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106557411A CN106557411A (en) | 2017-04-05 |
| CN106557411B true CN106557411B (en) | 2020-08-07 |
Family
ID=58414011
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510616653.7A Active CN106557411B (en) | 2015-09-24 | 2015-09-24 | Method and system for testing Hybrid application in Android system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106557411B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107239389B (en) * | 2017-06-07 | 2020-10-09 | 网易（杭州）网络有限公司 | Method and device for determining user operation record in hybrid APP |
| CN107861875B (en) * | 2017-11-15 | 2021-02-05 | 北京中电普华信息技术有限公司 | Simulation method and system for hybrid mobile application |
| EP4104426A4 (en) * | 2020-02-10 | 2024-03-06 | Visa International Service Association | Network based testing of mobile device kernels system and method |
| CN113918447B (en) * | 2021-09-03 | 2022-11-11 | 北京荣耀终端有限公司 | Application testing method and electronic equipment |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102033803B (en) * | 2009-09-29 | 2014-07-09 | 国际商业机器公司 | Method and device for testing web application across browsers |
| KR20130017337A (en) * | 2011-08-10 | 2013-02-20 | 케이티하이텔 주식회사 | Hybrid app development platform architecture and test method of the same, and computer-readable recording medium with program for the same |
| KR101416089B1 (en) * | 2012-08-06 | 2014-07-09 | 인크로스 주식회사 | An integrated platform for authoring web applications and the authoring method thereof |
| US9047404B1 (en) * | 2013-03-13 | 2015-06-02 | Amazon Technologies, Inc. | Bridge to connect an extended development capability device to a target device |
| CN104281518B (en) * | 2013-07-02 | 2018-05-15 | 腾讯科技（深圳）有限公司 | Terminal applies test method, device, system, platform and mobile terminal |
| CN104699604B (en) * | 2015-02-28 | 2017-11-07 | 百度在线网络技术（北京）有限公司 | Method and device for testing the Android application that kernel is browsed based on customization |
-
2015
- 2015-09-24 CN CN201510616653.7A patent/CN106557411B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN106557411A (en) | 2017-04-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108595329B (en) | Application testing method and device and computer storage medium | |
| CN108345535A (en) | Mock test methods, device and equipment | |
| CN107688529B (en) | Component debugging method and device | |
| CN109873735B (en) | Performance test method and device for H5 page and computer equipment | |
| CN111176629A (en) | Application development method and device | |
| CN106557411B (en) | Method and system for testing Hybrid application in Android system | |
| JP7106001B2 (en) | SUB-APPLICATION DEVELOPMENT METHOD, APPARATUS, COMPUTER DEVICE, AND COMPUTER PROGRAM | |
| CN108614767A (en) | A kind of remote debugging method and device | |
| CN110597709B (en) | Interactive debugging method and device for mixed-mode mobile application and computer equipment | |
| CN111666199B (en) | Debugging method executed on intelligent terminal and software debugger | |
| CN105224457B (en) | A kind of test frame implementation method and device | |
| US10705858B2 (en) | Automatic import of third party analytics | |
| US20170161171A1 (en) | Tenant Code Debugging in Multi-Tenant Systems | |
| CN107844486B (en) | Method and system for analyzing webpage problems for client | |
| CN112650689A (en) | Test method, test device, electronic equipment and storage medium | |
| CN105893235A (en) | Simulation testing method and apparatus, and server | |
| CN107102937B (en) | User interface testing method and device | |
| CN113138915A (en) | Page testing method, device and medium | |
| CN108509228B (en) | Page loading method, terminal equipment and computer readable storage medium | |
| CN113971257A (en) | Function menu access method and device for hybrid application | |
| CN113127329B (en) | Script debugging method, device and computer storage medium | |
| CN106776285B (en) | Webpage front end debugging method and device | |
| CN112667490A (en) | Performance test method and device based on hook function | |
| CN113609417A (en) | Method, device, equipment and medium for processing mobile terminal page | |
| CN116627850B (en) | Function debugging method and device, storage medium and electronic equipment |
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 |