Automatic testing method and equipment
By listening to the application and injecting the test server, the problem of low test coverage of existing test tools in a multi-tech container environment is solved, and comprehensive testing of any technical container interface in the application is achieved, improving the test coverage.
Patent Information
- Application Number
- CN202310822659.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-07-05
- Publication Date
- 2025-01-10
AI Technical Summary
Existing test tools have low test coverage for applications, especially when applications involve multiple technical containers, and cannot effectively jump to a non-native interface for testing.
By listening to the application to determine the target interface, and when the target interface does not belong to the native interface, the target test server injected into the application determines the target test server corresponding to the technical container where the target interface is located, so as to conduct the test.
It realizes testing of any technical container interface in the application, improves test coverage, and allows flexibly switching the test server to adapt to interface changes.
Smart Images
Figure CN119292909A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the technical field of software testing, and in particular to an automated testing method and device. Background Art
[0002] In the field of software testing technology, a test framework is a tool for automated testing of applications, which can also be called a test tool. The test tool can start the application and open the application interface to perform operations in the interface to test the application. During this test process, the application interface will switch continuously as the test instructions are executed.
[0003] In the prior art, commonly used testing tools may include: cypress testing tool, selenium testing tool and puppeteer testing tool. Among them, cypress testing tool can operate other page elements based on the same iframe (frame) element under the same origin policy to test the application. Selenium testing tool tests the application based on the driver provided by the browser. Puppeteer testing tool tests the application based on the connection driver between the application and the application.
[0004] However, the above commonly used testing tools have low test coverage of applications. Summary of the invention
[0005] The embodiments of the present disclosure provide an automated testing method and device, which can improve the testing coverage of an application program.
[0006] In a first aspect, an embodiment of the present disclosure provides an automated testing method, the method comprising:
[0007] Monitor the application to determine the target interface to which the application jumps;
[0008] When the target interface is not a native interface, determining a target test server corresponding to the technical container where the target interface is located from the test server injected into the application;
[0009] The target interface is tested through the target test server.
[0010] In a second aspect, an embodiment of the present disclosure provides an automated testing device, the device comprising:
[0011] A monitoring module, used for monitoring an application to determine a target interface to which the application jumps;
[0012] A test server determination module, used for determining, when the target interface does not belong to a native interface, a target test server corresponding to the technical container where the target interface is located from the test server injected into the application;
[0013] The test module is used to test the target interface through the target test server.
[0014] In a third aspect, an embodiment of the present disclosure provides an electronic device, including: at least one processor and a memory;
[0015] The memory stores computer-executable instructions;
[0016] The at least one processor executes the computer-executable instructions stored in the memory, so that the electronic device implements the method as described in the first aspect.
[0017] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer execution instructions, and when the computer execution instructions are executed by an electronic device, they are used to implement the method described in the first aspect.
[0018] In a fifth aspect, an embodiment of the present disclosure provides a computer program, wherein the computer program is used to implement the method described in the first aspect.
[0019] The disclosed embodiment provides an automated testing method and device, the method comprising: monitoring an application to determine the target interface to which the application jumps; when the target interface does not belong to the native interface, determining the target test server corresponding to the technical container where the target interface is located from the test server injected into the application; and testing the target interface through the target test server. The disclosed embodiment can monitor the application so that when the application jumps to the target interface, the test is performed through the test server built into the application by the technical container of the target interface. During the test process, as the interface switches, it is possible to switch to the test server of the corresponding technical container to implement the interface test after the switch. Thus, it is possible to test the interface of any technical container in the application, thereby improving the test coverage. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.
[0021] Figure 1 is a schematic diagram of a test scenario provided by an embodiment of the present disclosure;
[0022] Figure 2 is a flowchart of the steps of an automated testing method provided by an embodiment of the present disclosure;
[0023] Figure 3 is a schematic diagram of an automated testing process provided by an embodiment of the present disclosure;
[0024] Figure 4 is a structural block diagram of an automated testing device provided by an embodiment of the present disclosure;
[0025] Figure 5 It is a structural block diagram of an electronic device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION
[0026] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.
[0027] The embodiments of the present disclosure are applied in testing scenarios. Figure 1 Schematic diagram of a test scenario provided by an embodiment of the present disclosure. Figure 1 As shown, the test scenario of the embodiment of the present disclosure involves a test tool and an application to be tested, and the test tool is used to test the application. Figure 1 As shown, the test tool can send a test instruction to the application, and the application can perform corresponding operations based on the test instruction and feed back the test results to the test tool. The test instruction here can be an instruction to test any function of the application, including but not limited to: an instruction to start the application, an instruction to close the application, an instruction to open a certain interface in the application, an instruction to slide a certain interface in the application, an instruction to operate an operation control in the application, etc.
[0028] The above-mentioned test tools can be cypress test tools, selenium test tools and puppeteer test tools in the prior art. However, these test tools all perform interface jumps in the web technology container. When the application is implemented by multiple technology containers, the test tools cannot support the interface display of the remaining technology containers, and therefore cannot jump to the interface of the remaining technology containers for testing, resulting in low test coverage.
[0029] In order to solve the above technical problems, the embodiment of the present disclosure can monitor the application so that when the application jumps to the target interface, the test server built into the application by the technical container of the target interface is tested. During the test process, as the interface switches, the test server of the corresponding technical container can be switched to implement the interface test after the switch. Thus, the interface of any technical container in the application can be tested, which improves the test coverage.
[0030] The following specific embodiments are used to describe in detail the technical solutions of the embodiments of the present disclosure and how the technical solutions of the present disclosure solve the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present disclosure will be described below in conjunction with the accompanying drawings.
[0031] Based on the above Figure 1 The test scenario shown, Figure 2 is a flowchart of the steps of an automated testing method provided by an embodiment of the present disclosure. The automated testing method of the embodiment of the present disclosure is composed of Figure 1 The test harness shown is executed. Figure 2 As shown, the automated testing method includes:
[0032] S201: Monitor the application to determine the target interface to which the application jumps.
[0033] When the test tool is testing an application, the interface of the application will be constantly switched. For example, after testing a control in interface A, it will jump to interface B, and then after testing a control in interface B, it will jump to interface C. In this way, continuous jumping can test all interfaces and controls of the application, achieving complete testing of the application. Therefore, the target interface can be understood as the next interface to which the application jumps.
[0034] The disclosed embodiment can monitor the application program during the test process to determine whether an interface jump occurs in the application program, and when an interface jump occurs, determine the target interface for the jump.
[0035] In some implementations, an interface monitoring service may be started to monitor the above-mentioned application. The interface monitoring service may be used to monitor whether an interface jump occurs in the application, and when an interface jump occurs, determine the target interface to jump to. After starting the application, the interface monitoring service may be started to detect changes in the application as much as possible, ensure that the target interface is tested normally, and improve the test coverage. In addition, the interface monitoring service may be flexibly started and stopped, thereby improving the flexibility of monitoring.
[0036] After starting the application, you can also create a second connection between the test tool and the application, and start the interface monitoring service to monitor the application through the second connection. It is understandable that the second connection can be reused, and the second connection needs to be created each time the application is started. Then, during this test, the second connection can be reused multiple times. After the test is completed, you can close the application, and at this time, the second connection will also be disconnected.
[0037] S202: When the target interface is not a native interface, determine a target test server corresponding to the technical container where the target interface is located from the test server injected into the application.
[0038] The technical container is a container used to implement the interface in the application. The technical container provides an environment for the application components in it, so that these application components only need to interact with the environment variables inside the container, without paying attention to system variables. In other words, the technical container can be understood as a standardized software unit that packages the code and dependencies in it so that the application can run quickly and reliably from one computing environment to another.
[0039] In the disclosed embodiment, the target interface can be of two types, the first type is a native interface, and the second type is a non-native interface. The native interface is an interface developed by the software framework of the application, and all functions of the software framework can be called. The non-native interface is an interface implemented by the software framework calling other technical containers, and all functions of the software framework cannot be used. The performance of the native interface is better than that of the non-native interface.
[0040] Therefore, when the target interface is a native interface, the target interface can be tested through the second connection between the test tool and the application. That is, the test tool controls the application to display the native interface through the second connection, and then the test tool can send operation instructions for the native interface to the application to operate the native interface, including but not limited to: sliding, clicking operation controls, etc. In this way, the display test and operation test of the native interface can be implemented to ensure that the display and operation of the target interface are normal, and a comprehensive test of the native interface is achieved.
[0041] It should be noted that after performing an operation test on the above-mentioned native interface, it is possible to jump to another native interface or a non-native interface. The non-native interface can be called a cross-end interface and can run on multiple types of clients. When jumping to another native interface, the above-mentioned second connection can be reused to continue testing another native interface. When jumping to a non-native interface, the test can be performed through steps S202 and S203.
[0042] In the disclosed embodiment, in order to implement the testing of non-native interfaces, multiple test servers are pre-injected into the application, each of which corresponds to a technical container and is used to test the interface of the technical container. Therefore, when the target interface does not belong to the native interface, that is, when the target interface is a cross-end interface, the target test server corresponding to the technical container where the target interface is located can be determined from multiple test servers, and the target test server is used to test the target interface that does not belong to the native interface.
[0043] S203: Testing the target interface through the target test server.
[0044] Specifically, the test instruction may be sent to the target test server through a preset protocol stack, so that the target test server executes the test indicated by the test instruction in the target interface.
[0045] When an application includes interfaces of multiple technology containers, different technology containers correspond to the same protocol stack, that is, all technology containers in the embodiments of the present disclosure share a protocol stack. In this scenario, the interaction protocol between the test tool and the application is the same. In this way, the code complexity and maintenance complexity can be reduced.
[0046] Optionally, sending the test instruction to the target test server via a preset protocol stack may include: first, establishing or reusing a first connection with the target test server; then, writing the test instruction into the protocol stack, and sending the protocol stack to the target test server via the first connection.
[0047] When entering any interface corresponding to a technical container for the first time, establish a first connection between the test tool and the target test server corresponding to the technical container. When entering any interface of the technical container again in the future, the first connection can be reused. When a test of the application is completed, close the application and disconnect the first connection. In this way, the first connection can be reused to reduce the number of times the first connection is established as much as possible, which can save the time consumed in establishing the first connection during the test and save test time.
[0048] In some implementations, the method further includes: before testing the application, starting a third connection so that the test tool connects to the terminal device where the application is located and starts the application to be tested in the terminal device.
[0049] Among them, the type of the third connection is related to the system of the terminal device. When the system of the terminal device is different, different third connections need to be used. For example, when the system of the terminal device is Android, the third connection can be an ADB (Android Debug Bridge) connection. Of course, the third connection can also be a BDC (Bidirectional Communication) connection, which can be applicable to any system of the terminal device.
[0050] In one example, the test tool in the embodiment of the present disclosure is implemented based on the browser debugging protocol (CDP, chromedevtool protocol). The target interface includes but is not limited to: Lynx interface (plain text browser interface), H5 interface, Flutter interface, React-Native interface. These target interfaces belong to different technology containers. The Lynx interface is an interface implemented by the Lynx technology container, the H5 interface is an interface implemented by the H5 technology container, the Flutter interface is an interface implemented by the Flutter technology container, and the React-Native interface is an interface implemented by the React-Native technology container.
[0051] When switching between these interfaces, the test tool can identify the technical container corresponding to the interface, so as to test the interface of the technical container through the target test server corresponding to the technical container. For example, when the test tool needs to enter the home interface of the application when starting the application, the test tool determines that the home interface is the native interface. At this time, the test tool can open the home interface through the second connection between the application and the test tool to implement the test of the home interface P0.
[0052] When operating the operation control B1 in the first interface P0 to enter an interface P1, the test tool determines that the interface P1 to be entered is a Lynx interface, and then the interface P1 can be displayed through the first connection between the test tool and the target test server of the Lynx technology container to implement the test of the interface P1.
[0053] Similarly, when an operation control B2 in the first interface or other interfaces is operated to enter an interface P2, when the testing tool determines that the interface P2 to be entered is an H5 interface, the interface P2 can be displayed through the first connection between the testing tool and the target testing server of the H5 technology container to implement the test of interface P2.
[0054] In summary, the disclosed embodiments are used to test applications that have interfaces that are mixed with multiple technology containers. During the test process, the test tool will monitor the application to determine the target interface to which the application jumps. In addition, the test tool will also identify the elements in the target interface to send test instructions to the target test server corresponding to the technology container to which the target interface in the application belongs through the protocol stack, so that the application can be tested.
[0055] Figure 3 Schematic diagram of an automated testing process provided by an embodiment of the present disclosure. Figure 3 As shown, the above automated testing process includes:
[0056] S301: Start a third connection to connect to the terminal device where the application is located.
[0057] S302: Start the application to be tested in the terminal device, into which the test servers corresponding to the multiple technical containers have been injected.
[0058] S303: Create a second connection with the application.
[0059] S304: Start the interface monitoring service.
[0060] S305: Call the interface monitoring service to monitor the application through the second connection to determine the target interface to which the application jumps.
[0061] S306: When the target interface is a native interface, the native interface is tested through the second connection.
[0062] S307: When the target interface is a non-native interface, a first connection is established between the target test server corresponding to the technical container to which the target interface belongs.
[0063] S308: Writing the test instruction into the protocol stack, and sending the protocol stack to the target test server through the first connection, so that the target test server executes the test indicated by the test instruction in the target interface.
[0064] After executing S306 or S308 to enter the next interface, the process goes to step S305 again, and the process continues in a loop until the last interface of the application is tested.
[0065] It should be noted that the above S301 to S308 in the embodiment of the present disclosure can be flexibly adjusted in sequence on a mutually independent basis, and the embodiment of the present disclosure does not limit their sequence.
[0066] Corresponding to the automated testing method of the above embodiment, Figure 41 is a structural block diagram of an automated testing device provided by an embodiment of the present disclosure. For ease of explanation, only the parts related to the embodiment of the present disclosure are shown. Figure 4 , the above-mentioned automated testing device 400 comprises:
[0067] The monitoring module 401 is used to monitor the application program to determine the target interface to which the application program jumps.
[0068] The test server determination module 402 is used to determine a target test server corresponding to the technical container where the target interface is located from the test servers injected into the application when the target interface does not belong to the native interface.
[0069] The testing module 403 is used to test the target interface through the target testing server.
[0070] Optionally, the testing module 403 is further used to:
[0071] The test instruction is sent to the target test server through a preset protocol stack, so that the target test server executes the test indicated by the test instruction in the target interface. When the application includes interfaces of multiple technical containers, different technical containers correspond to the same protocol stack.
[0072] Optionally, the testing module 403 is further used to:
[0073] Establish or reuse a first connection with the target test server.
[0074] The test instruction is written into the protocol stack, and the protocol stack is sent to the target test server through the first connection.
[0075] Optionally, the monitoring module 401 is further used for:
[0076] Start the interface monitoring service to monitor the application.
[0077] Optionally, the monitoring module 401 is further used for:
[0078] A second connection is created with the application.
[0079] The interface monitoring service is started to monitor the application through the second connection.
[0080] Optionally, the device further comprises:
[0081] A native interface testing module is used to test the target interface through the second connection when the target interface belongs to the native interface.
[0082] Optionally, the device further comprises:
[0083] The application program starting module is used to start a third connection to connect to the terminal device where the application program is located and start the application program.
[0084] Optionally, the test tool is implemented based on a browser debugging protocol CDP, and the target interface includes one of the following: a Lynx interface, an H5 interface, a Flutter interface, and a React-Native interface.
[0085] The automated testing device provided in this embodiment can be used to perform the above Figure 2 The technical solution of the method embodiment shown has similar implementation principles and technical effects, and will not be repeated here in this embodiment.
[0086] Figure 5 6 is a block diagram of an electronic device provided by an embodiment of the present disclosure. The electronic device 600 includes a memory 602 and at least one processor 601 .
[0087] The memory 602 stores computer-executable instructions.
[0088] At least one processor 601 executes the computer execution instructions stored in the memory 602, so that the electronic device 601 implements the aforementioned Figure 2 The method in .
[0089] In addition, the electronic device may further include a receiver 603 and a transmitter 604, wherein the receiver 603 is used to receive information from other devices or equipment and forward it to the processor 601, and the transmitter 604 is used to send the information to other devices or equipment.
[0090] In a first example of the first aspect, an embodiment of the present disclosure provides an automated testing method, which is applied to a testing tool. The method includes:
[0091] Monitor the application to determine the target interface to which the application jumps.
[0092] When the target interface is not a native interface, a target test server corresponding to the technical container where the target interface is located is determined from the test server injected into the application.
[0093] The target interface is tested through the target test server.
[0094] Based on the first example of the first aspect, in the second example of the first aspect, testing the target interface by the target test server includes:
[0095] The test instruction is sent to the target test server through a preset protocol stack, so that the target test server executes the test indicated by the test instruction in the target interface. When the application includes interfaces of multiple technical containers, different technical containers correspond to the same protocol stack.
[0096] Based on the second example of the first aspect, in a third example of the first aspect, sending the test instruction to the target test server through a preset protocol stack includes:
[0097] Establish or reuse a first connection with the target test server.
[0098] The test instruction is written into the protocol stack, and the protocol stack is sent to the target test server through the first connection.
[0099] Based on the first to third examples of the first aspect, in a fourth example of the first aspect, the monitoring application includes:
[0100] Start the interface monitoring service to monitor the application.
[0101] Based on the fourth example of the first aspect, in a fifth example of the first aspect, the starting interface monitoring service to monitor the application includes:
[0102] A second connection is created with the application.
[0103] The interface monitoring service is started to monitor the application through the second connection.
[0104] Based on the fifth example of the first aspect, in a sixth example of the first aspect, the method further includes:
[0105] When the target interface belongs to the native interface, the target interface is tested through the second connection.
[0106] Based on the first to third examples of the first aspect, in a seventh example of the first aspect, the method further includes:
[0107] A third connection is started to connect to the terminal device where the application is located, and the application is started.
[0108] Based on the first example of the first aspect, in an eighth example of the first aspect, the testing tool is implemented based on the browser debugging protocol CDP, and the target interface includes one of the following: Lynx interface, H5 interface, Flutter interface, React-Native interface.
[0109] In a first example of the second aspect, an automated testing device is provided, the device comprising:
[0110] The monitoring module is used to monitor the application program to determine the target interface to which the application program jumps.
[0111] The test server determination module is used to determine the target test server corresponding to the technical container where the target interface is located from the test server injected into the application when the target interface does not belong to the native interface.
[0112] The test module is used to test the target interface through the target test server.
[0113] Based on the first example of the second aspect, in the second example of the second aspect, the test module is further used for:
[0114] The test instruction is sent to the target test server through a preset protocol stack, so that the target test server executes the test indicated by the test instruction in the target interface. When the application includes interfaces of multiple technical containers, different technical containers correspond to the same protocol stack.
[0115] Based on the second example of the second aspect, in a third example of the second aspect, the test module is further used to:
[0116] Establish or reuse a first connection with the target test server.
[0117] The test instruction is written into the protocol stack, and the protocol stack is sent to the target test server through the first connection.
[0118] Based on the first to third examples of the second aspect, in a fourth example of the second aspect, the monitoring module is further used to:
[0119] Start the interface monitoring service to monitor the application.
[0120] Based on the fourth example of the second aspect, in a fifth example of the second aspect, the monitoring module is further used to:
[0121] A second connection is created with the application.
[0122] The interface monitoring service is started to monitor the application through the second connection.
[0123] Based on the fifth example of the second aspect, in a sixth example of the second aspect, the device further includes:
[0124] A native interface testing module is used to test the target interface through the second connection when the target interface belongs to the native interface.
[0125] Based on the first to third examples of the second aspect, in a seventh example of the second aspect, the device further includes:
[0126] The application program starting module is used to start a third connection to connect to the terminal device where the application program is located and start the application program.
[0127] Based on the first example of the second aspect, in the eighth example of the second aspect, the testing tool is implemented based on the browser debugging protocol CDP, and the target interface includes one of the following: Lynx interface, H5 interface, Flutter interface, React-Native interface.
[0128] In a third aspect, according to one or more embodiments of the present disclosure, there is provided an electronic device, comprising: at least one processor and a memory.
[0129] The memory stores computer executable instructions.
[0130] The at least one processor executes the computer-executable instructions stored in the memory, so that the electronic device implements the method described in any one of the first aspects.
[0131] In a fourth aspect, according to one or more embodiments of the present disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer execution instructions, and when the computer execution instructions are executed by an electronic device, they are used to implement the method described in the first aspect.
[0132] In a fifth aspect, according to one or more embodiments of the present disclosure, a computer program is provided, wherein the computer program is used to implement the method described in any one of the first aspects.
[0133] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present disclosure (but not limited to) by each other to form a technical solution.
[0134] In addition, although each operation is described in a specific order, this should not be understood as requiring these operations to be performed in the specific order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination mode.
[0135] Although the subject matter has been described in language specific to structural features and / or methodological logical actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. On the contrary, the specific features and actions described above are merely example forms of implementing the claims.
Claims
1. An automated testing method, characterized in that: The method comprises: Monitor the application to determine the target interface to which the application jumps; When the target interface is not a native interface, determining a target test server corresponding to the technical container where the target interface is located from the test server injected into the application; The target interface is tested through the target test server.
2. The method according to claim 1, characterized in that The testing of the target interface by the target test server includes: The test instruction is sent to the target test server through a preset protocol stack, so that the target test server executes the test indicated by the test instruction in the target interface. When the application includes interfaces of multiple technical containers, different technical containers correspond to the same protocol stack.
3. The method according to claim 2, characterized in that The step of sending the test instruction to the target test server through a preset protocol stack includes: Establishing or reusing a first connection with the target test server; The test instruction is written into the protocol stack, and the protocol stack is sent to the target test server through the first connection.
4. The method according to any one of claims 1 to 3, characterized in that: The monitoring application comprises: Start the interface monitoring service to monitor the application.
5. The method according to claim 4, characterized in that The startup interface monitoring service is used to monitor the application, including: creating a second connection with the application; The interface monitoring service is started to monitor the application through the second connection.
6. The method according to claim 5, characterized in that The method further comprises: When the target interface belongs to the native interface, the target interface is tested through the second connection.
7. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: A third connection is started to connect to the terminal device where the application is located, and the application is started.
8. The method according to claim 1, characterized in that The target interface includes one of the following: Lynx interface, H5 interface, Flutter interface, React-Native interface.
9. An automated testing device, characterized in that: include: A monitoring module, used for monitoring an application to determine a target interface to which the application jumps; A test server determination module, used for determining, when the target interface does not belong to a native interface, a target test server corresponding to the technical container where the target interface is located from the test server injected into the application; The test module is used to test the target interface through the target test server.
10. An electronic device, characterized in that: include: at least one processor and memory; The memory stores computer-executable instructions; The at least one processor executes the computer-executable instructions stored in the memory, so that the electronic device implements the method according to any one of claims 1 to 8.
11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 8 when executed by an electronic device.
12. A computer program, characterized in that The computer program is used to implement the method according to any one of claims 1 to 8.