Automated testing method, apparatus, device, and computer-readable storage medium
By recording user actions to generate test tasks, the problem of low efficiency in existing automated testing technologies is solved, and a highly efficient automated testing process that does not require manual coding is realized, meeting the needs of rapid project iteration.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- BEIJING KINGSOFT CLOUD NETWORK TECH CO LTD
- Filing Date
- 2024-12-27
- Publication Date
- 2026-06-30
AI Technical Summary
Existing product testing methods lack automation and are inefficient, requiring professionals to manually write test cases, which is time-consuming and labor-intensive.
By recording user actions, the system generates action recording results, automatically generates test tasks, including API call information and page display information, and executes the test tasks on the page to be tested.
No need for manual test case writing, which improves the efficiency of automated testing, allows for rapid follow-up on project iteration requirements, and shortens the development iteration cycle.
Smart Images
Figure CN122309335A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of computer technology, and in particular to an automated testing method, apparatus, device, and computer-readable storage medium. Background Technology
[0002] Product testing is an essential process in product development. Through product testing, we can try out various interactive functions in the product, discover errors and deficiencies in the current version, and provide data support for product development and iteration.
[0003] Typically, product testing requires specific use cases to be written by professional developers or testers.
[0004] However, this approach requires developers or testers to have knowledge of the business details, and writing repetitive test cases when performing the same tests on different products will also consume a lot of time. Therefore, existing testing methods are not sufficiently automated and are inefficient. Summary of the Invention
[0005] To address the aforementioned technical problems, this disclosure provides an automated testing method, apparatus, device, and computer-readable storage medium to improve testing efficiency.
[0006] In a first aspect, embodiments of this disclosure provide an automated testing method, including:
[0007] Record the user's actions on the page to be tested to obtain the operation recording results. The operation recording results include the interface call information and page display information corresponding to each operation step.
[0008] The multiple operation steps corresponding to the recorded operation results are arranged to obtain the test task corresponding to the page to be tested. The test task includes the interface call information and page display information corresponding to each test step.
[0009] The test task is executed on the page to be tested to test the page.
[0010] In some embodiments, before recording user actions on the page to be tested and obtaining the action recording results, the method further includes:
[0011] Display the address retrieval interface;
[0012] Based on the user's input on the address acquisition interface, obtain the access address of the page to be tested;
[0013] The page to be tested is pre-accessed based on the access address;
[0014] If the pre-access to the page to be tested fails, a first prompt message is generated, which is used to inform the user that the access address of the page to be tested has expired.
[0015] In some embodiments, arranging multiple operation steps corresponding to the operation recording result to obtain the test task corresponding to the page to be tested includes:
[0016] Based on the user's initial testing requirements, multiple first testing steps are determined from the multiple operation steps;
[0017] Determine the first execution order of the plurality of first test steps;
[0018] Based on the first execution order and the operation recording results, a test task corresponding to the page to be tested is generated.
[0019] In some embodiments, arranging multiple operation steps corresponding to the operation recording result to obtain the test task corresponding to the page to be tested includes:
[0020] If, based on the first test requirement, it is determined that at least one first test step corresponding to the first test requirement is missing among the multiple operation steps, a second prompt message is generated. The second prompt message is used to guide the user to record the missing first test step among the multiple operation steps.
[0021] After recording the first test step that was missing from the multiple operation steps, a supplementary recording result was obtained;
[0022] The operation recording results and the supplementary recording results are arranged to obtain the test task corresponding to the page to be tested.
[0023] In some embodiments, after arranging the multiple operation steps corresponding to the operation recording result to obtain the test task corresponding to the page to be tested, the method further includes:
[0024] In response to user modifications to the test task, the plurality of first test steps are adjusted to obtain a plurality of second test steps; and / or
[0025] In response to the user's modification operation on the test task, the first execution order is updated to obtain a second execution order;
[0026] Based on the second test step, the second execution order, and the operation recording results, a test task corresponding to the page to be tested is generated.
[0027] In some embodiments, before executing the test task on the page to be tested, the method further includes:
[0028] Based on the user's configuration information, obtain the target prompt method and target prompt address;
[0029] After executing the test task on the page to be tested, the method further includes:
[0030] Obtain the execution result of the test task;
[0031] The execution result is sent to the target prompt address using the target prompt method.
[0032] In some embodiments, the method is applied to a device with an automated testing plugin installed. Before recording user actions on the page to be tested and obtaining the action recording results, the method further includes:
[0033] Verify the automated testing plugin;
[0034] If the automated testing plugin fails to be verified, installation guidance information is generated to guide the user in installing the automated testing plugin.
[0035] Secondly, embodiments of this disclosure provide an automated testing apparatus, comprising:
[0036] The recording module is used to record the user's operations on the page to be tested and obtain the operation recording results. The operation recording results include the interface call information and page display information corresponding to each operation step.
[0037] The orchestration module is used to orchestrate multiple operation steps corresponding to the operation recording results to obtain the test task corresponding to the page to be tested. The test task includes the interface call information and page display information corresponding to each test step.
[0038] An execution module is used to execute the test task on the page to be tested in order to test the page to be tested.
[0039] Thirdly, embodiments of this disclosure provide an electronic device, including:
[0040] Memory;
[0041] Processor; and
[0042] Computer programs;
[0043] The computer program is stored in the memory and configured to be executed by the processor to implement the method as described in the first aspect.
[0044] Fourthly, embodiments of this disclosure provide a computer-readable storage medium having a computer program stored thereon, the computer program being executed by a processor to implement the method described in the first aspect.
[0045] Fifthly, embodiments of this disclosure also provide a computer program product, which includes a computer program or instructions that, when executed by a processor, implement the automated testing method described above.
[0046] The automated testing method, apparatus, device, and computer-readable storage medium provided in this disclosure automatically generate and execute test tasks corresponding to the page to be tested based on the recorded operation recording results. This eliminates the need for manually writing test tasks for the page to be tested, improves the efficiency of automated testing, quickly keeps up with project iteration requirements, and shortens the iteration cycle of automated development. Attached Figure Description
[0047] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.
[0048] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0049] Figure 1 A flowchart of an automated testing method provided in this embodiment of the disclosure;
[0050] Figure 2 This is a schematic diagram of the structure of the automated testing device provided in the embodiments of this disclosure;
[0051] Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Detailed Implementation
[0052] To better understand the above-mentioned objectives, features, and advantages of this disclosure, the solutions disclosed herein will be further described below. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.
[0053] Numerous specific details are set forth in the following description in order to provide a full understanding of this disclosure, but this disclosure may also be implemented in other ways different from those described herein; obviously, the embodiments in the specification are only some, and not all, of the embodiments of this disclosure.
[0054] This disclosure provides an automated testing method, which will be described below with reference to specific embodiments.
[0055] Figure 1 This is a flowchart illustrating an automated testing method provided in an embodiment of this disclosure. The method can be applied to devices equipped with automated testing plugins, which include automated testing models, such as browser extensions or standalone software. The devices can be smartphones, PDAs, tablets, wearable devices with displays, desktop computers, laptops, all-in-one computers, smart home devices, etc. It is understood that the automated testing method provided in this disclosure can also be applied to other scenarios.
[0056] The following is about Figure 1 The automated testing method shown below will be introduced. The specific steps of this method are as follows:
[0057] S101. Record the user's operations on the page to be tested and obtain the operation recording results. The operation recording results include the interface call information and page display information corresponding to each operation step.
[0058] The page to be tested is the page that the user needs to test, including any webpage, software program page, etc. The page to be tested can be a single page or multiple pages, and this disclosure does not limit this.
[0059] Specifically, an automated testing plugin is used to record user actions on the page to be tested, and the recorded action results are obtained.
[0060] The user's actions on the test page are equivalent to the user's normal use of the various functions on the test page, such as clicking on various controls on the test page, inputting text or voice on the test page, scrolling on the test page, etc.
[0061] User interactions with the test page often involve multiple steps. Each step requires calling the corresponding function interface and changing the page display to provide feedback to the user.
[0062] In this context, the page display, or User Interface (UI), refers to the interface through which users interact with software or a website. It includes all user-visible elements that allow users to communicate with the system, including inputting data, issuing commands, and receiving feedback.
[0063] Correspondingly, the information displayed on the page includes information about changes in various elements on the page, such as the arrangement of elements; interface elements that allow users to input data, such as text boxes, drop-down menus, checkboxes, etc.; and the system's response after user operation, such as pop-ups, prompts, loading animations, etc.
[0064] S102. Arrange the multiple operation steps corresponding to the operation recording result to obtain the test task corresponding to the page to be tested. The test task includes the interface call information and page display information corresponding to each test step.
[0065] Optionally, an automated testing plugin can be used to perform a detailed analysis of the recorded operation steps to understand the specific behavior and purpose of each step. Through analysis, common operation types can be identified, such as login, search, and form submission, and API call information and page display information can be categorized and stored according to operation type.
[0066] Furthermore, the test steps are arranged in a logical order to form a complete test process. According to the test process, the interface call information and page display information corresponding to each test step are organized into test tasks corresponding to the page to be tested.
[0067] Optionally, each operation step corresponds to a movable control, and users can arrange multiple operation steps by dragging and dropping the controls.
[0068] S103. Execute the test task on the page to be tested to test the page to be tested.
[0069] The test task is an executable code-level file. Executing the test task on the page to be tested allows each test step to be implemented in a specified order based on the interface call information and page display information corresponding to each test step.
[0070] Optionally, the test task also includes the expected results and verification points for each test step. The expected results can be the page display information recorded after the operation steps corresponding to the test steps are completed.
[0071] During the execution of the test task, when the verification point is reached, the content displayed on the current page to be tested is compared with the expected result to determine whether the two are consistent or whether the similarity is greater than a preset threshold. This will determine whether the current test task has been executed normally.
[0072] Optionally, if the current test task fails, step S102 is executed to regenerate the test task; if the number of test task failures exceeds a preset threshold, an alarm message is generated and displayed to prompt the user to handle the issue.
[0073] This embodiment of the disclosure records user operations on a page to be tested, obtaining operation recording results. These recording results include interface call information and page display information corresponding to each operation step. Multiple operation steps corresponding to the recording results are arranged to obtain test tasks for the page to be tested. Each test task includes interface call information and page display information corresponding to each test step. The test tasks are then executed on the page to be tested. By automatically generating and executing test tasks corresponding to the page to be tested based on the recorded operation results, the need for manually writing test tasks for the page to be tested is eliminated, improving the efficiency of automated testing, quickly keeping up with project iteration requirements, and shortening the iteration cycle of automated development.
[0074] Based on the above embodiments, the step of arranging multiple operation steps corresponding to the operation recording result to obtain the test task corresponding to the page to be tested includes: determining multiple first test steps from the multiple operation steps according to the user's first test requirements; determining a first execution order of the multiple first test steps; and generating the test task corresponding to the page to be tested according to the first execution order and the operation recording result.
[0075] The first test requirement includes the objective of the test task. Based on the first test requirement, steps related to the test requirement are selected from all recorded operation steps as the first test steps. The first execution order of multiple first test steps is determined to ensure that the execution of each first test step in accordance with logic and dependencies can achieve the objective of the test task corresponding to the first test requirement.
[0076] After determining multiple first test steps and their corresponding first execution order, the interface call information and page display information corresponding to each test step are extracted from the operation recording results to generate the test task corresponding to the page to be tested.
[0077] Optionally, the test task may include the expected behavior, input data, and expected results for each test step.
[0078] One possible implementation is to utilize an automated testing plugin to generate and execute test tasks. Specifically, the automated testing plugin includes an automated testing model. The user's initial test requirements are input into the automated testing model, which then parses these requirements, determines multiple initial test steps and an initial execution order, and generates and outputs the test task corresponding to the page to be tested based on the initial execution order and the recorded operation results.
[0079] In some embodiments, arranging multiple operation steps corresponding to the operation recording results to obtain the test task corresponding to the page to be tested includes: if, according to the first test requirement, it is determined that at least one first test step corresponding to the first test requirement is missing among the multiple operation steps, then generating a second prompt message, the second prompt message being used to guide the user to record the missing first test step among the multiple operation steps; after recording the missing first test step among the multiple operation steps, obtaining a supplementary recording result; arranging the multiple operation steps in the operation recording result and the supplementary recording result to obtain the test task corresponding to the page to be tested.
[0080] After obtaining the first test requirement, the system first checks whether the multiple operation steps corresponding to the operation recording result can meet the first test requirement. If it is determined that at least one necessary first test step is missing among the multiple operation steps corresponding to the operation recording result to fulfill the user's first test requirement, a second prompt message is generated and displayed. The purpose of this second prompt message is to clearly inform the user which first test steps are missing and to provide necessary guidance to guide the user to record the missing first test steps.
[0081] The second prompt guides the user to complete the recording of the missing first test step, resulting in a supplementary recording. The original recording is then combined with the supplementary recording to uniformly organize and integrate all operation steps. This includes determining the execution order of the test steps, integrating API call information and page display information, ensuring the test task executes smoothly according to the user's needs. After organization, the system generates a complete test task for the page under test, containing all necessary first test steps for automated testing of the page.
[0082] One possible implementation is to utilize an automated testing plugin to generate and execute test tasks. Specifically, the automated testing plugin includes an automated testing model. The user's initial test requirements are input into the automated testing model, which then parses these requirements to determine if the multiple operation steps corresponding to the recorded operation results can satisfy them. If it is determined that at least one necessary first test step is missing from the multiple operation steps corresponding to the recorded operation results to fulfill the user's initial test requirements, a second prompt is generated and displayed, guiding the user to complete the recording of the missing first test step. The multiple operation steps in the recorded operation results and the supplementary recording results are then arranged to generate and output the test task corresponding to the page to be tested.
[0083] In some embodiments, after arranging the multiple operation steps corresponding to the operation recording results to obtain the test task corresponding to the page to be tested, the method further includes: adjusting the multiple first test steps in response to the user's modification operation on the test task to obtain multiple second test steps; and / or updating the first execution order in response to the user's modification operation on the test task to obtain a second execution order; and generating the test task corresponding to the page to be tested based on the second execution order and the operation recording results.
[0084] When users review or adjust test tasks, they may modify the test steps, such as adding new test steps, deleting unnecessary test steps, or modifying certain details of existing steps. In response to user modifications, the previously defined multiple first test steps are adjusted accordingly, resulting in updated multiple second test steps, including replacing test steps, adding test steps, or deleting test steps.
[0085] Users may also request modifications to the initial execution order of test steps to better reflect the logic or priority of the test process. In response to user modifications, the original initial execution order is updated to form a new second execution order, including the reordering of multiple second test steps, to ensure that the tests are executed according to the correct process and sequence.
[0086] After the user modifies the test steps and their execution order, the interface call information and page display information corresponding to each second test step are extracted from the operation recording results, and the test task corresponding to the page to be tested is regenerated.
[0087] One possible implementation is to use an automated testing plugin to generate and execute test tasks. Specifically, the automated testing plugin includes an automated testing model. The user's modification requirements are input into the automated testing model, which then parses the modification requirements and adjusts them based on the original first test step and first execution order to obtain multiple second test steps and a second execution order, thereby generating a new test task.
[0088] This disclosure embodiment automatically generates test tasks that meet the user's first test requirements based on the operation recording results, or prompts the user to supplement the recording when the current operation recording results cannot meet the first test requirements, or adjusts the existing test tasks according to the user's modified operations, so as to meet the user's automated testing needs in various scenarios and ensure that the test tasks can fit the user's testing needs, thereby improving the flexibility of the automated testing method.
[0089] In some embodiments, before executing the test task on the page to be tested, the method further includes: obtaining a target prompting method and a target prompting address based on the user's prompting configuration information; after executing the test task on the page to be tested, the method further includes: obtaining the execution result of the test task; and sending the execution result to the target prompting address through the target prompting method.
[0090] Before executing test tasks on the page to be tested, the system determines how and where to send test-related prompts or notifications based on the prompt configuration information provided by the user. The target prompt method indicates how the user expects to receive prompts, which may include email, SMS, in-app notifications, desktop notifications, etc. The target prompt address indicates the address where the user needs to receive prompts, such as an email address, phone number, or user ID within the app.
[0091] When the test task is completed on the page to be tested, the execution results of the test task are collected and obtained, including whether the test passed, the defects found, performance indicators and other key information; and the execution results of the automated test are sent to the target prompt address specified by the user through the target prompt method specified by the user.
[0092] For example, if the user selects email as the notification method and provides an email address, the system will send the test results to that email address. Optionally, before sending the automated test execution results to the user-specified target notification address, the sending email address needs to be configured according to the user's configuration information.
[0093] This disclosure enhances the interactivity and real-time nature of the testing process by providing real-time feedback on the execution results to the user before and after the test based on the user's configuration, thus helping the user to more effectively monitor and manage the testing process.
[0094] In some embodiments, before recording user actions on the page to be tested and obtaining the action recording result, the method further includes: verifying the automated testing plugin; if the automated testing plugin verification fails, generating installation guidance information, which is used to guide the user to install the automated testing plugin.
[0095] Specifically, the automated testing plugin is validated, including checking whether the necessary software dependencies, such as browsers and browser drivers, are installed; checking whether the plugin is compatible with the user's operating system and browser version; testing the plugin's key functions, such as recording, playback, and analysis, to ensure the plugin functions correctly; checking whether the plugin can successfully connect to external servers, such as API services and databases; and checking whether the plugin has the necessary permissions to execute automated tests and whether the permissions are configured correctly, etc.
[0096] If the automated plugin verification fails, detailed installation guidance information will be generated and displayed, including but not limited to: installation guide, providing the plugin download link and installation steps; dependency installation information, listing all necessary software dependencies and providing installation instructions; configuration instructions: providing the plugin's required configuration and corresponding configuration information.
[0097] This disclosure embodiment verifies the automated testing plugin before executing automated tests to ensure that the automated testing plugin can provide normal functional support during the automated testing process, and provides installation guidance information when the verification fails, so as to ensure that users can successfully install and use the automated testing plugin, thereby improving the efficiency of testing work and user experience.
[0098] In some embodiments, before recording the user's operations on the page to be tested and obtaining the operation recording result, the method further includes: displaying an address acquisition interface; obtaining the access address of the page to be tested based on the user's input in the address acquisition interface; performing a pre-access on the page to be tested according to the access address; if the pre-access on the page to be tested fails, generating a first prompt message, the first prompt message being used to prompt the user that the access address of the page to be tested is invalid.
[0099] The address acquisition interface is used for users to enter the access address of the page to be tested. For example, when the page to be tested is a webpage, the access address is the Uniform Resource Locator (URL) of the webpage; when the page to be tested is an application, the access address is the launch address of the application.
[0100] After obtaining the access address of the page to be tested, attempt to pre-access the page to verify the validity of the address, and determine whether the pre-access was successful by checking the HTTP response status code.
[0101] Optionally, pre-accessing the page to be tested may include determining whether the page can be opened successfully, whether the various functions on the page can be used successfully, and so on.
[0102] If the pre-access fails, such as returning a 404 Page Not Found, 500 Server Error, or Network Timeout, a first message will be generated and displayed to the user in a user-friendly manner, indicating that the access address of the page to be tested may be invalid.
[0103] Optionally, possible solutions can be provided in the initial prompt message, such as rechecking the URL, trying different addresses, or contacting the website administrator.
[0104] This embodiment of the disclosure pre-accesses the access address of the page to be tested before executing automated testing, thereby ensuring that the page to be tested can be accessed normally during the automated testing process, ensuring that users can perform automated testing on the page to be tested normally, and improving the efficiency of testing work and user experience.
[0105] Figure 2 This is a schematic diagram of the structure of the automated testing apparatus provided in the embodiments of this disclosure. The automated testing apparatus may be a device equipped with an automated testing plugin as described in the above embodiments, or the automated testing apparatus may be a component or assembly within that device. The automated testing apparatus provided in the embodiments of this disclosure can execute the processing flow provided in the embodiments of the automated testing method, such as... Figure 2 As shown, the automated testing device 20 includes: a recording module 21, an orchestration module 22, and an execution module 23. The recording module 21 records user operations on the page to be tested, obtaining operation recording results. The operation recording results include interface call information and page display information corresponding to each operation step. The orchestration module 22 orchestrates multiple operation steps corresponding to the operation recording results to obtain test tasks corresponding to the page to be tested. The test tasks include interface call information and page display information corresponding to each test step. The execution module 23 executes the test tasks on the page to be tested to test the page.
[0106] Optionally, the automated testing device 20 further includes an address verification module 24, used to display an address acquisition interface before recording the user's operation on the page to be tested and obtaining the operation recording result; obtain the access address of the page to be tested based on the user's input in the address acquisition interface; perform pre-access on the page to be tested according to the access address; if the pre-access of the page to be tested fails, generate a first prompt message, the first prompt message being used to prompt the user that the access address of the page to be tested is invalid.
[0107] Optionally, the orchestration module 22 includes a first determining unit 221, a second determining unit 222, and a generating unit 223; the first determining unit 221 is used to determine a plurality of first test steps from the plurality of operation steps according to the user's first test requirements; the second determining unit 222 is used to determine a first execution order of the plurality of first test steps; and the generating unit 223 is used to generate a test task corresponding to the page to be tested according to the first execution order and the operation recording result.
[0108] Optionally, the first determining unit 221 is further configured to generate a second prompt message if, based on the first test requirement, it is determined that at least one first test step corresponding to the first test requirement is missing among the multiple operation steps. The second prompt message is used to guide the user to record the missing first test step among the multiple operation steps. The recording module 21 is further configured to obtain a supplementary recording result after recording the missing first test step among the multiple operation steps. The arrangement module 22 is further configured to arrange the multiple operation steps in the operation recording result and the supplementary recording result to obtain the test task corresponding to the page to be tested.
[0109] Optionally, the orchestration module 22 further includes a modification unit 224, which is used to adjust the plurality of first test steps in response to the user's modification operation on the test task to obtain a plurality of second test steps; and / or update the first execution order in response to the user's modification operation on the test task to obtain a second execution order; the generation unit 223 is further used to generate a test task corresponding to the page to be tested based on the second test steps, the second execution order and the operation recording result.
[0110] Optionally, the automated testing device 20 further includes a notification module 25, which is used to obtain the target prompting method and the target prompting address according to the user's prompting configuration information before executing the test task on the page to be tested; to obtain the execution result of the test task after executing the test task on the page to be tested; and to send the execution result to the target prompting address through the target prompting method.
[0111] Optionally, the automated testing device 20 further includes a plug-in verification module 26, which is used to verify the automated testing plug-in; if the automated testing plug-in fails to verify, installation guidance information is generated, which is used to guide the user to install the automated testing plug-in.
[0112] Figure 2 The automated testing apparatus shown in the embodiment can be used to execute the technical solutions of the above method embodiments. Its implementation principle and technical effect are similar, and will not be repeated here.
[0113] Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. The electronic device may be a device equipped with an automated testing plugin as described in the above embodiments. The electronic device provided in this disclosure can execute the processing flow provided in the automated testing method embodiments, such as… Figure 3 As shown, the electronic device 30 includes: a memory 31, a processor 32, a computer program, and a communication interface 33; wherein the computer program is stored in the memory 31 and configured to be executed by the processor 32 using the automated testing method described above.
[0114] In addition, this disclosure also provides a computer-readable storage medium having a computer program stored thereon, the computer program being executed by a processor to implement the automated testing method described in the above embodiments.
[0115] Furthermore, this disclosure also provides a computer program product, which includes a computer program or instructions that, when executed by a processor, implement the automated testing method described above.
[0116] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0117] The above description is merely a specific embodiment of this disclosure, enabling those skilled in the art to understand or implement it. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not to be limited to the embodiments described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. An automated testing method, characterized in that, The method is applied to the method including: Record the user's actions on the page to be tested to obtain the operation recording results. The operation recording results include the interface call information and page display information corresponding to each operation step. The multiple operation steps corresponding to the recorded operation results are arranged to obtain the test task corresponding to the page to be tested. The test task includes the interface call information and page display information corresponding to each test step. The test task is executed on the page to be tested to test the page.
2. The method according to claim 1, characterized in that, Before obtaining the operation recording results by recording the user's actions on the page to be tested, the method further includes: Display the address retrieval interface; Based on the user's input on the address acquisition interface, obtain the access address of the page to be tested; The page to be tested is pre-accessed based on the access address; If the pre-access to the page to be tested fails, a first prompt message is generated, which is used to inform the user that the access address of the page to be tested has expired.
3. The method according to claim 1, characterized in that, The step of arranging multiple operation steps corresponding to the operation recording results to obtain the test task corresponding to the page to be tested includes: Based on the user's initial testing requirements, multiple first testing steps are determined from the multiple operation steps; Determine the first execution order of the plurality of first test steps; Based on the first execution order and the operation recording results, a test task corresponding to the page to be tested is generated.
4. The method according to claim 1, characterized in that, The step of arranging multiple operation steps corresponding to the operation recording results to obtain the test task corresponding to the page to be tested includes: If, based on the first test requirement, it is determined that at least one first test step corresponding to the first test requirement is missing among the multiple operation steps, a second prompt message is generated. The second prompt message is used to guide the user to record the missing first test step among the multiple operation steps. After recording the first test step that was missing from the multiple operation steps, a supplementary recording result was obtained; The operation recording results and the supplementary recording results are arranged to obtain the test task corresponding to the page to be tested.
5. The method according to claim 3, characterized in that, After arranging multiple operation steps corresponding to the operation recording results to obtain the test task corresponding to the page to be tested, the method further includes: In response to user modifications to the test task, the plurality of first test steps are adjusted to obtain a plurality of second test steps; and / or In response to the user's modification operation on the test task, the first execution order is updated to obtain a second execution order; Based on the second test step, the second execution order, and the operation recording results, a test task corresponding to the page to be tested is generated.
6. The method according to claim 1, characterized in that, Before executing the test task on the page to be tested, the method further includes: Based on the user's configuration information, obtain the target prompt method and target prompt address; After executing the test task on the page to be tested, the method further includes: Obtain the execution result of the test task; The execution result is sent to the target prompt address using the target prompt method.
7. The method according to claim 1, characterized in that, The method is applied to devices equipped with automated testing plugins. Before recording user actions on the page to be tested and obtaining the recording results, the method further includes: Verify the automated testing plugin; If the automated testing plugin fails to be verified, installation guidance information is generated to guide the user in installing the automated testing plugin.
8. An automated testing device, characterized in that, include: The recording module is used to record the user's operations on the page to be tested and obtain the operation recording results. The operation recording results include the interface call information and page display information corresponding to each operation step. The orchestration module is used to orchestrate multiple operation steps corresponding to the operation recording results to obtain the test task corresponding to the page to be tested. The test task includes the interface call information and page display information corresponding to each test step. An execution module is used to execute the test task on the page to be tested in order to test the page to be tested.
9. An electronic device, characterized in that, include: Memory; processor; as well as Computer programs; The computer program is stored in the memory and configured to be executed by the processor to implement the method as described in any one of claims 1-7.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-7.