Application test method and terminal

Abstract

The invention discloses an application test method and a terminal, and the method comprises the steps: receiving a selected to-be-tested application, testing the to-be-tested application, and monitoring a test process of the to-be-tested application through a monitoring device; when it is monitored that errors exist in the testing process, testing pop-up window early warning is displayed, a request interface corresponding to the testing process with the errors and interface information of the request interface are obtained, and an intelligent agent is used for generating a testing case according to the request interface and the interface information of the request interface; and executing the test case, and recording the execution result of the test case, so that the test efficiency and quality can be improved, and stable delivery of the application is ensured.

Description

Technical Field

[0001] The present invention relates to the field of testing technology, and in particular to an application testing method and a terminal. Background Art

[0002] In today's booming internet era, websites, as core application carriers, have become the preferred development platform for all types of application developers. Software testing, as a key step in ensuring application quality and stable launch, has become increasingly prominent in the software development process. However, in the actual software development process, due to factors such as market competition pressure and urgent client demands, the testing phase is often unreasonably compressed, resulting in significant challenges for testing. Furthermore, with the frequent iterations of applications and the continuous expansion of their functionality, short regression testing processes are prone to missed tests, making it difficult to strike a balance between time and quality during application delivery. Developers and testers are forced to make a difficult trade-off between the two.

[0003] Currently, the common software quality assurance method in the industry mainly relies on manual testing and manually written scripts to achieve automated testing. Some large companies also use interface documentation such as Swagger and Wikipedia to generate corresponding test cases for targeted testing on the service interface side, but this method has limitations:

[0004] 1. When manual testing is performed on website regression tests, testers are easily distracted and may overlook anomalies in non-visually focused areas. For example, display anomalies in areas that require scrolling down to be visible, or inconspicuous data values ​​not being displayed correctly due to abnormal interface requests, which can easily lead to missed tests and potential defects.

[0005] 2. Conventional script testing requires a significant amount of time to fully cover test paths, compiling test cases one by one. This trades time for quality. Under tight deadlines, the investment in automated testing is relatively high, potentially sacrificing development and self-testing. According to GPT's automated return on investment, the return on investment for interfaces is 50 rounds, which simply doesn't allow for the investment in scripts.

[0006] 3. With the increasing number of application development iterations or the emergence of poor development and testing standards, many interfaces lack introductions and descriptions. Some wiki pages even deviate from the actual interface implementation. This forces testers to re-capture the actual interface when writing interface test cases and simulate the test environment through actual interface requests. This not only requires a lot of work and time, but also, when converting the captured interface data into script templates for expansion writing, it is often difficult to run scripts smoothly within the unified interface framework due to differences in account permissions between different personnel, limited by security compliance and data isolation requirements, further hindering the improvement of testing efficiency.

[0007] 4. For troubleshooting during testing, the typical practice is for testers to provide developers with interface data captured using F12, manually taking screenshots, or copying console data. However, this information lacks context, leading to frequent retesting and time-consuming problem locating, which seriously impacts the efficiency of development and testing collaboration.

[0008] 5. During the development of iterative versions, some developers failed to promptly inform testers of interface adjustments. Changes in the interface response structure can easily lead to compatibility issues. Developers who have just taken over the business code are also prone to negligence in assessing the impact of the changes themselves, making it difficult for testers to focus on key business testing, exacerbating software quality risks. Summary of the Invention

[0009] The technical problem to be solved by the present invention is: an application testing method and terminal provided by the present invention can improve testing efficiency and quality and ensure stable delivery of applications.

[0010] In order to solve the above technical problems, the technical solution adopted by the present invention is:

[0011] An application testing method comprises the steps of:

[0012] S1. Receive a selected application to be tested and test the application to be tested, and use a monitoring device to monitor the testing process of the application to be tested;

[0013] S2. When an error is detected during the test process, a test pop-up window warning is displayed, and the request interface and interface information corresponding to the test process with the error are obtained. A test case is generated using the agent based on the request interface and interface information.

[0014] S3. Execute the test case and record the execution result of the test case.

[0015] In order to solve the above technical problems, another technical solution adopted by the present invention is:

[0016] An application testing terminal includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, each step of the above-mentioned application testing method is implemented.

[0017] The beneficial effects of the present invention are: an application testing method and terminal provided by the present invention, by receiving a selected application to be tested and testing the application to be tested, using a monitoring device to monitor the test process of the application to be tested in real time, can quickly discover and locate errors in the test process, and reduce problem troubleshooting time; when an error is monitored in the test process, a test pop-up warning is displayed, and the request interface and its interface information corresponding to the test process with the error are obtained, and an intelligent agent is used to generate test cases based on the request interface and its interface information, which helps to verify the problem interface and improve test efficiency and accuracy; the test cases are executed and the test results are recorded, ensuring the traceability and consistency of the test results and ensuring the stable delivery of the application. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 A flowchart of an application testing method according to an embodiment of the present invention;

[0019] Figure 2 Schematic diagram of detection of a monitoring device in an embodiment of the present invention;

[0020] Figure 3 This is a flow chart of interface detection in an embodiment of the present invention;

[0021] Figure 4 This is a flowchart of console detection in an embodiment of the present invention;

[0022] Figure 5 This is a flowchart of file download detection in an embodiment of the present invention;

[0023] Figure 6 A flowchart of the test case execution in an embodiment of the present invention;

[0024] Figure 7 A schematic diagram of an application test terminal according to an embodiment of the present invention;

[0025] Description of labels:

[0026] 1. An application test terminal; 2. Memory; 3. Processor. DETAILED DESCRIPTION

[0027] To illustrate the technical content, achieved objectives and effects of the present invention in detail, the following description is given in conjunction with the embodiments and accompanying drawings.

[0028] Please refer to Figure 1 , an embodiment of the present invention provides an application testing method, comprising the steps of:

[0029] S1. Receive a selected application to be tested and test the application to be tested, and use a monitoring device to monitor the testing process of the application to be tested;

[0030] S2. When an error is detected during the test process, a test pop-up warning is displayed, and the request interface and interface information corresponding to the test process with the error are obtained, and the intelligent agent is used to generate a test case based on the request interface and interface information.

[0031] S3. Execute the test case and record the execution result of the test case.

[0032] From the above description, it can be seen that the beneficial effects of the present invention are: by receiving the selected application to be tested and testing the application to be tested, and using a monitoring device to monitor the test process of the application to be tested in real time, it is possible to quickly discover and locate errors in the test process, thereby reducing the time for troubleshooting; when an error is detected in the test process, a test pop-up warning is displayed, and the request interface and its interface information corresponding to the test process with the error are obtained, and an intelligent agent is used to generate test cases based on the request interface and its interface information, which helps to verify the problem interface and improve test efficiency and accuracy; the test cases are executed and the test results are recorded to ensure the traceability and consistency of the test results and ensure the stable delivery of the application.

[0033] Furthermore, the step S1 includes:

[0034] Use the application management module to create at least one application, configure basic information, application domain name list, authentication encryption proxy interface and parsing rules for the created application, and configure the corresponding encryption method for each domain name in the application domain name list.

[0035] From the above description, it can be seen that by using the application management module to support the independent creation and parameter configuration of multiple applications, a corresponding encryption method is configured for each domain name in the application domain name list, so as to achieve refined and customized application management, improve the security and flexibility of the application, and ensure encryption protection during data transmission, effectively preventing the risk of information leakage.

[0036] Furthermore, generating a test case using an agent according to the request interface and its interface information includes:

[0037] Generate a unique identifier for the request interface based on the request method and interface resource path in the interface information, determine whether the request interface is obtained for the first time based on the unique identifier, and if so, generate a test case using an agent based on the request interface and its interface information;

[0038] Otherwise, verify whether the interface information has changed. When the verification result determines that there has been a change, display an interface information pop-up warning, and use the intelligent agent to generate a test case based on the request interface and its interface information.

[0039] As can be seen from the above description, a unique identifier for the requested interface is constructed based on the request method and resource path. This is used to determine whether the requested interface is being obtained for the first time, ensuring timely test case generation, avoiding duplication of work, and improving testing efficiency. If the interface is not being obtained for the first time, the interface is verified to have changed. If so, a pop-up window with interface information is displayed and the test case is regenerated. This effectively ensures the accuracy and timeliness of the test case, reduces the testing risks caused by interface changes, and improves the automation and quality of application testing.

[0040] Furthermore, executing the test case includes:

[0041] Use parsing rules to parse local storage and obtain authentication conditions;

[0042] Call the authentication encryption proxy interface and generate an authentication header based on the authentication condition and the request method and interface resource path in the interface information;

[0043] A request is sent to the request interface according to the input information of the authentication header and the test case, a response result of the request interface is received, and the response result is input into the intelligent agent, which makes a rationality judgment on the response result. If the response result meets the expected conditions of the request, the test case is marked as executed successfully, otherwise the test case is marked as executed failed.

[0044] From the above description, it can be seen that the parsing rules are used to parse local storage and extract authentication conditions to lay the foundation for the subsequent authentication process. The authentication encryption proxy interface is called, and the authentication header is generated by combining the authentication conditions with the request method and resource path in the interface information to ensure the legitimacy and security of the request; a request is sent to the request interface, and the response result of the request interface is received. The intelligent agent makes a rationality judgment on the response result, objectively and accurately evaluates whether the response meets the expected conditions, thereby accurately marking the execution status of the test case and improving the accuracy and reliability of the test results.

[0045] Furthermore, the step S3 then includes:

[0046] A test suite is created, a test scope of the test suite is set, a build strategy is configured for the test suite, and the test suite is executed according to the build strategy to perform regression testing on the test case.

[0047] As can be seen from the above description, by creating a test suite and setting its test scope to ensure the comprehensiveness and pertinence of the test, configuring a build strategy for the test suite, and executing the test suite according to the build strategy to perform regression testing on the test cases, testing efficiency is improved, and test accuracy and consistency are ensured. Risks caused by omissions or duplications in tests are avoided, providing a solid guarantee for the stable iteration and high-quality delivery of applications.

[0048] Please refer to Figure 7 Another embodiment of the present invention provides an application testing terminal, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, each step of the above-mentioned application testing method is implemented.

[0049] The application testing method and terminal described above are applicable to testing scenarios, can improve testing efficiency and quality, and ensure robust application delivery. Specific implementation methods are described below:

[0050] Please refer to Figures 1 to 6 , embodiment 1 of the present invention is:

[0051] An application test comprises the steps of:

[0052] S0. Use the application management module to create at least one application, configure basic information, application domain name list, authentication encryption proxy interface and parsing rules for the created application, and configure a corresponding encryption method for each domain name in the application domain name list.

[0053] In this embodiment, the application management module supports the creation and configuration of applications, including: basic configurations such as the application name and the default website address, specific domain names or application domain name list configurations that are fuzzy configured through key fields (for example, if the configuration is: test.cn, then all domain names containing test.cn are the scope of the application that needs to be tested), authentication encryption proxy interface address configuration, and definition of local storage parsing rules, specifying authentication dependent information fields such as token and mac_key that need to be parsed, to achieve universal authentication processing. A corresponding encryption method is configured for each domain name in the application domain name list, so that in the subsequent use case test phase, an authentication header can be dynamically generated through the encrypted information in the local storage to ensure that the test request passes normally. In addition, when the corresponding application to be tested is selected in the application options, whether to report the interface is determined based on the domain name information. If reported, the reporting interface is accompanied by an application identifier to track and analyze the test data.

[0054] S1. Receive a selected application to be tested and test the application to be tested, and use a monitoring device to monitor the testing process of the application to be tested.

[0055] In this embodiment, when a user uses the monitoring device client for the first time, he or she sets the user_id according to his or her needs so that the test data can be pushed to the corresponding IM message, and configures the interface anomaly detection and console anomaly detection. The interface anomaly detection configuration includes the error.http.code list (the default configuration is common http error codes such as 500, 501, 502, 503, and 504) and the error.http.keyword dictionary (the default is {"code":"INTERNAL_SERVER_ERROR","message":access blocked}). The user can add search keywords by himself or herself. When the above error keywords appear, the corresponding test pop-up warning is displayed; the console anomaly detection configuration includes error. console.type, error.console.type is a json file. The default configuration is {"error":{"white_list":[],"black_list":[]}}, indicating that only error-level console logs are detected. Only one of white_list and black_list can be set. white_list is a whitelist. When a whitelist is configured, only errors in the whitelist are ignored, and all others are considered errors. black_list is a blacklist. When a blacklist is configured, only errors in the blacklist are considered errors, and all other errors are ignored. If no configuration is made, all error-level logs are considered errors. The specific configuration can be customized according to user needs.

[0056] For further information, please refer to Figure 2 After selecting the corresponding application to be tested in the application product selection, the monitoring device will automatically request the domain name information of the application to be tested. Turn on the [Interface Test] switch, select the Chrome browser, and click [Open Webpage] to launch the computer system's default Chrome browser. The monitoring device automatically retrieves the Chrome browser's installation path chrome_executable_path and executes the "browser=playwright.chromium.launch(executable_path=chrome_executable_path,headless=False)" command through Playwright to launch it. If the monitoring device fails to retrieve the chrome_executable_path, it will prompt the user to configure the chrome_executable_path address to ensure the correct startup of the Chrome browser.

[0057] S2. When an error is detected during the test process, a test pop-up warning is displayed, and the request interface and interface information corresponding to the test process with the error are obtained, and the intelligent agent is used to generate a test case based on the request interface and interface information.

[0058] In this embodiment, Playwright is used to monitor various registration events, including Context route "** / *" And handle (network layer listener, monitoring the interface requests of the entire browser), Context on console And handle (console listener, monitoring the console log printing of all page tags of the entire browser), Context onpage And handle (page listener, used to detect file downloads) and Trace open or close (trace status monitoring). Specifically:

[0059] 1. Interface detection: please refer to Figure 3, use Playwright's context.route("** / *", handle_request) to globally intercept all requests, ensuring that requests from existing pages or user-defined new tab pages will be intercepted and processed, ensuring that all requests in the entire browser context are captured, and obtaining the web page information of the request source through request.frame.url and request.frame.page.title(), and obtaining and parsing the localStorage of the corresponding domain through context. Combined with the interface information, key interface information is output, and the response status code is judged according to the error.http.code list configured by the monitoring device to determine whether it is abnormal (that is, whether the response status code is included in the error.http.code list). If so, copy the interface information to the clipboard and display a test pop-up warning. Otherwise, loop to check whether the response.data in the key interface information contains the keywords in error.content.keyword. If it does, and the corresponding value has an error keyword, the information is also copied and a pop-up prompt is displayed. When the interface is normal and belongs to the product domain list, determine whether the interface has been reported to the backend (determine whether the key fields of the interface exist in report_api_list, key fields: interface request method + parameter formatted API URL + parameter formatted page URL, for example: get_http: / / www.test.com / v1 / user / {id}_http: / / www.test.com / user). If not, report the interface information to the backend to avoid repeated reporting.

[0060] 2. Console detection: Please refer to Figure 4, use Playwright's context.on("console",handle_request) to intercept console logs. By default, all errors at the error level are intercepted, and corresponding detection can be performed according to the user-configured rules. For example, if the configuration condition is {"error":{"white_list":[],"black_list":[]}}, when an error-level error occurs, the error message is copied and a pop-up warning window is displayed; if the configuration condition is {"error":{"white_list":[],"black_list":["is not defined"]}}, an alarm is triggered only when the error-level log contains the "is not defined" keyword; if the configuration condition is {"error":{"white_list":["this is warning"],"black_list":[]}}, all other error-level logs except those containing the "this is warning" keyword are triggered.

[0061] 3. File download detection: please refer to Figure 5 , supports monitoring file downloads through Playwright's context.on("page", lambdapages:pages.on("download", self.handle_download)) , ensuring the availability of file downloads and improving its usability while keeping the Chrome browser under the monitoring device's proxy. You can specify the download directory and save the original name of the downloaded file.

[0062] 4. Trace status monitoring: When a user discovers a problem and needs to provide development assistance to troubleshoot and reproduce the issue, they can directly click [Start trace] on the monitoring device to start recording by calling context.tracing.start(screenshots=True, snapshots=True). When [Stop trace] is clicked, context.tracing.stop(path=path) is called to generate a trace file. At the same time, the trace file will be uploaded to a CS cloud content center, and the webpage address for online trace preview will be copied to the clipboard. A pop-up window will prompt the user to copy the corresponding information.

[0063] In addition, the monitoring device also provides the function of saving local_storage when closing a web page. Local_storage can be saved through context.storage_state (path = self.storage_state_path), or the user can manually save the storage_state button to quickly restore the context next time and reduce unnecessary pre-operations.

[0064] Furthermore, generating a test case using an agent according to the request interface and its interface information includes:

[0065] Generate a unique identifier for the request interface based on the request method and interface resource path in the interface information, determine whether the request interface is obtained for the first time based on the unique identifier, and if so, generate a test case using an agent based on the request interface and its interface information;

[0066] Otherwise, verify whether the interface information has changed. When the verification result determines that there has been a change, display an interface information pop-up warning, and use the intelligent agent to generate a test case based on the request interface and its interface information.

[0067] In this embodiment, the interface information reported by the monitoring device is stored in the interface management module, and is provided as a query method based on parameters such as user ID, application identifier, request method (method) and interface resource path (interface URL) in the interface information, so that the user can find out the list of Pages currently applying the interface by selecting method and interface URL. The request method and interface resource path in the interface information are used as the unique identifier of the request interface to determine whether the request interface is reported for the first time. If so, the use case management module is used to design a test case. Otherwise, the requested data interface and the returned data structure are verified to see if there are any changes. If so, a pop-up window warning of the interface information is displayed and the test case design is performed again.

[0068] Please refer to Figure 6 , receive the interface information (including request method, interface resource path, request body and expected response result) sent by the interface management module through the use case management module, send the interface information to the intelligent agent, and the intelligent agent designs test cases according to the interface information (based on the model, through prompt word engineering and knowledge base to constrain the output results, realize an AI application, and provide a way to integrate the interface into the system). For example, on Deepseek, it is required to design test cases according to the interface characteristics from the perspective of a senior software test engineer who is good at interface testing, using dimensions including but not limited to boundary values, abnormal scenarios, parameter verification, sorting / filtering logic, etc. Each use case includes test objectives, request body call parameters, expected response results and use case levels, and parse and save the test cases returned by the intelligent agent.

[0069] S3. Execute the test case and record the execution result of the test case, specifically including:

[0070] Use parsing rules to parse local storage and obtain authentication conditions;

[0071] Call the authentication encryption proxy interface and generate an authentication header based on the authentication condition and the request method and interface resource path in the interface information;

[0072] A request is sent to the request interface according to the input information of the authentication header and the test case, a response result of the request interface is received, and the response result is input into the intelligent agent, which makes a rationality judgment on the response result. If the response result meets the expected conditions of the request, the test case is marked as executed successfully, otherwise the test case is marked as executed failed.

[0073] In this embodiment, each test case is tested accordingly. By calling the authentication and encryption proxy interface, the corresponding header authentication information is obtained by combining the key authentication conditions parsed in local_storage and the interface method and URL to ensure the legitimacy of the request. The request is initiated with the test case input information, and the response result is submitted to the intelligent agent for rationality judgment. If the response result meets the expectations, the test is marked as passed; otherwise, the test is marked as failed. If a test case fails, a corresponding prompt warning can be set, and the background supports filtering and viewing the failed test case table.

[0074] Furthermore, in this embodiment, step S3 then includes: creating a test suite, setting the test scope of the test suite to ensure comprehensiveness and pertinence of the test, configuring a build strategy for the test suite, and executing the test suite according to the build strategy to perform regression testing on the test cases. This improves test efficiency, ensures test accuracy and consistency, avoids risks caused by missed or duplicated tests, and provides a solid guarantee for stable iteration and high-quality delivery of the application. Furthermore, a test recording module is used to record and store test case execution results, regression test execution results, and debug test results, allowing users to review test records.

[0075] In this embodiment, the following specific application scenarios are provided:

[0076] Scenario 1:

[0077] Tester Xiao A is responsible for testing an online education website. The website uses iframes to embed many sub-pages. It has a wide range of resources and path combinations. As an agile and iterative project, the release frequency is very high, and as the business continues to expand. When Xiao A releases a feature, the core focus is generally on testing the scope associated with the feature, and the content that passes through the feature scope is often quickly glanced at. During the process of modifying a feature, the development affected the functions of other modules. However, this function was not a global failure, which caused local data display anomalies in other businesses along the feature path. The core reason was that the server interface had a 502 error, so the corresponding iframe could not parse the corresponding data, resulting in an abnormal display. This page is the core page of the website, but due to the lack of process and global observation, the pull-down swipe to check the inventory resulted in missed tests, which were discovered by users.

[0078] By using the monitoring device in the technical solution of the present invention to open a browser for testing, user A can detect a 50* error during the process. A pop-up window will appear on the desktop to remind user A that a 50* error exists on the corresponding page, allowing user A to avoid this missed test. Similarly, as long as the data can be intercepted at the network or console layer, when an anomaly occurs, this solution can detect it, eliminating missed tests due to testing blind spots.

[0079] Scenario 2:

[0080] In the same scenario, tester Xiao A's project experienced a rapid release cycle. Furthermore, due to frequent interruptions from the client, developers rushed to meet deadlines, even failing to write timely interface documentation for some emergency releases. Consequently, QA often only performed quick, functional tests of the main process, sometimes even releasing the project with issues. In this context, the project underwent almost no interface testing, relying heavily on front-end functional testing. Furthermore, online monitoring tasks were not completed promptly. During subsequent version iterations, the lack of interface regression testing made it easy for new releases to impact other legacy modules. Furthermore, when online failures occurred, the lack of monitoring prevented timely detection, often leading to user feedback leading to the corresponding issues.

[0081] Through the technical solution of the present invention, Xiao A only needs to create a corresponding application in the background, set the domain list currently used by the website on the application, and have the development / QA provide an authentication-generated proxy interface for configuration. Then, after selecting the corresponding application using the monitoring device provided by the solution and opening the browser for testing, all interface requests involved in the process can be transcribed to the background management, and used as a P0 use case, a P0 interface is set up for regular construction for routine online dialing tests. At the same time, the background will design corresponding test cases for the characteristics of each interface and perform corresponding tests. The process marks the list of use cases with errors. When the user function test is completed, the system will complete the corresponding interface test and provide the error test results for QA / development to confirm again. Finally, the use cases that pass the test can also be used for regression testing in the subsequent service release process.

[0082] Scenario 3:

[0083] When tester Xiao A finds some problems during the testing process, he usually provides network screenshots or data to the developer for troubleshooting, which easily leads to the developer rework and requesting more complete context information.

[0084] Through the technical solution of the present invention, as long as Xiao A finds a relevant error, he can directly click Start Trace to start recording the entire test process. Click End Trace to save the relevant information of the entire process and provide an online trace recording webpage that can be directly accessed for easy troubleshooting.

[0085] Scenario 4:

[0086] Tester Xiao A's project frequently requires server-side API adjustments and hotfixes due to various factors, including security improvements, version iterations, and bug fixes. Furthermore, with personnel changes, many developers lack a clear understanding of their new responsibilities. This can easily lead to compatibility issues with other application pages due to inadequate consideration of the scope of impact, such as focusing on only one application scenario. Similarly, QA teams can easily overlook testing due to inadequate development assessments, ultimately leading to undetected releases.

[0087] The technical solution of the present invention allows testing via a browser launched by a monitoring device, recording the application page corresponding to each interface, providing guidance and reference for developers / QA when modifying the server-side interface. Furthermore, when interface structure parameters are changed, the corresponding QA can be prompted to conduct targeted testing.

[0088] Please refer to Figure 7, embodiment 2 of the present invention is: an application testing terminal 1, comprising a memory 2, a processor 3, and a computer program stored in the memory 2 and executable on the processor 3, wherein the processor 3 implements each step of an application testing method of embodiment 1 when executing the computer program.

[0089] In summary, the present invention provides an application testing method and terminal, which creates and configures applications through an application management module, receives the selected application to be tested and tests the application to be tested, and uses a monitoring device to monitor the test process of the application to be tested in real time, which can quickly discover and locate errors in the test process and reduce the time for troubleshooting; when an error is detected in the test process, a test pop-up warning is displayed, and the request interface and its interface information corresponding to the test process with the error are obtained, and an intelligent agent is used to generate a test case based on the request interface and its interface information, which helps to verify the problem interface and improve the test efficiency and accuracy; the test case is executed and the test results are recorded, which ensures the traceability and consistency of the test results and guarantees the stable delivery of the application. In addition, a build management module is used to create a test suite and set its test scope, configure a build strategy for the test suite, and execute the test suite according to the build strategy to perform regression testing on the test case, thereby improving test efficiency, ensuring the accuracy and consistency of the test, avoiding risks caused by omissions or duplications in testing, and providing a solid guarantee for the stable iteration and high-quality delivery of the application.

[0090] Therefore, the embodiments of the present invention can achieve the following beneficial effects:

[0091] 1. During the walkthrough test process, the system automatically completes the design and generation of interface test cases, and performs test cases and result evaluation to improve test efficiency;

[0092] 2. During the version testing process, it can quantitatively analyze the changes in interfaces compared to previous versions, providing precise testing guidance to the QA team. This helps the team quickly identify potential risk points and focus on targeted testing, thereby ensuring the stability and reliability of the new version.

[0093] 3. Reduce testing costs by using automatically generated test cases for daily monitoring and regression testing;

[0094] 4. Use monitoring devices to capture all abnormal situations and effectively monitor all preset interface response anomalies and console errors that occur during the test process. Even if the business impact area is not within the visual range, this ensures that no test is missed, helps to discover and fix potential problems, and improves the overall quality of the software;

[0095] 5. By recording the program execution path or data flow during the test process, it provides rich and accurate data support for problem reproduction and saves historical interface request records, which helps developers quickly locate the root cause of the problem, shorten the problem troubleshooting cycle, and improve the efficiency of problem solving;

[0096] 6. By implementing the mapping relationship between the front-end page and the application interface, when an exception occurs in service monitoring, the applied Page range can be quickly located, improving the efficiency and accuracy of problem troubleshooting.

[0097] The above descriptions are merely embodiments of the present invention and are not intended to limit the patent scope of the present invention. Any equivalent transformations made using the contents of the present invention's description and drawings, or directly or indirectly applied in related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. An application testing method, characterized in that: Including steps: S1. Receive a selected application to be tested and test the application to be tested, and use a monitoring device to monitor the testing process of the application to be tested; S2. When an error is detected during the test process, a test pop-up window warning is displayed, and the request interface and interface information corresponding to the test process with the error are obtained. A test case is generated using the agent based on the request interface and interface information. S3. Execute the test case and record the execution result of the test case.

2. An application testing method according to claim 1, characterized in that: The step S1 previously includes: Use the application management module to create at least one application, configure basic information, application domain name list, authentication encryption proxy interface and parsing rules for the created application, and configure the corresponding encryption method for each domain name in the application domain name list.

3. An application testing method according to claim 2, characterized in that: Generate test cases using an agent according to the request interface and its interface information, including: Generate a unique identifier for the request interface based on the request method and interface resource path in the interface information, determine whether the request interface is obtained for the first time based on the unique identifier, and if so, generate a test case using an agent based on the request interface and its interface information; Otherwise, verify whether the interface information has changed. When the verification result determines that there has been a change, display an interface information pop-up warning, and use the intelligent agent to generate a test case based on the request interface and its interface information.

4. An application testing method according to claim 3, characterized in that: Executing the test case includes: Use parsing rules to parse local storage and obtain authentication conditions; Call the authentication encryption proxy interface and generate an authentication header based on the authentication condition and the request method and interface resource path in the interface information; A request is sent to the request interface according to the input information of the authentication header and the test case, a response result of the request interface is received, and the response result is input into the intelligent agent, which makes a rationality judgment on the response result. If the response result meets the expected conditions of the request, the test case is marked as executed successfully, otherwise the test case is marked as executed failed.

5. An application testing method according to claim 1, characterized in that: The step S3 then includes: A test suite is created, a test scope of the test suite is set, a build strategy is configured for the test suite, and the test suite is executed according to the build strategy to perform regression testing on the test case.

6. An application test terminal comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the following steps are implemented: S1. Receive a selected application to be tested and test the application to be tested, and use a monitoring device to monitor the testing process of the application to be tested; S2. When an error is detected during the test process, a test pop-up window warning is displayed, and the request interface and interface information corresponding to the test process with the error are obtained. A test case is generated using the agent based on the request interface and interface information. S3. Execute the test case and record the execution result of the test case.

7. The application test terminal according to claim 6, characterized in that: The step S1 previously includes: Use the application management module to create at least one application, configure basic information, application domain name list, authentication encryption proxy interface and parsing rules for the created application, and configure the corresponding encryption method for each domain name in the application domain name list.

8. The application test terminal according to claim 7, characterized in that: Generate test cases using an agent according to the request interface and its interface information, including: Generate a unique identifier for the request interface based on the request method and interface resource path in the interface information, determine whether the request interface is obtained for the first time based on the unique identifier, and if so, generate a test case using an agent based on the request interface and its interface information; Otherwise, verify whether the interface information has changed. When the verification result determines that there has been a change, display an interface information pop-up warning, and use the intelligent agent to generate a test case based on the request interface and its interface information.

9. The application test terminal according to claim 8, characterized in that: Executing the test case includes: Use parsing rules to parse local storage and obtain authentication conditions; Call the authentication encryption proxy interface and generate an authentication header based on the authentication condition and the request method and interface resource path in the interface information; A request is sent to the request interface according to the input information of the authentication header and the test case, a response result of the request interface is received, and the response result is input into the intelligent agent, which makes a rationality judgment on the response result. If the response result meets the expected conditions of the request, the test case is marked as executed successfully, otherwise the test case is marked as executed failed.

10. The application test terminal according to claim 6, characterized in that: The step S3 then includes: A test suite is created, a test scope of the test suite is set, a build strategy is configured for the test suite, and the test suite is executed according to the build strategy to perform regression testing on the test case.

Images