Multi-component collaborative automated testing system, method, equipment and medium
Through a multi-component collaborative automated testing system, the problems of complex environment configuration and poor scheduling flexibility of existing UI automated testing tools are solved, efficient and flexible end-to-end testing is achieved, and testing efficiency and accuracy are improved.
Patent Information
- Application Number
- CN202510943872.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-07-09
- Publication Date
- 2025-09-12
AI Technical Summary
Existing UI automation testing tools have problems such as cumbersome environment configuration, high code complexity, poor scheduling flexibility, and delayed result feedback, making it difficult to efficiently meet modern high-frequency iterative testing needs.
An automated testing system with multi-component collaboration is adopted, including network request control components, test task scheduling components, automated testing components and persistent storage components. Through the collaborative work between components, the automated testing component uses Playwright as the core component, combined with OkHttp, XXL-Job, MyBatis, Spring Boot, Druid and Shiro technology stacks to achieve end-to-end business logic coverage and efficient testing.
It improves testing efficiency, reduces human involvement, enhances the accuracy and flexibility of data testing, supports stable operation in multiple browser environments, shortens the testing cycle, and pushes test results in real time through DingTalk, meeting the needs of team collaboration.
Smart Images
Figure CN120631784A_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present disclosure relate to the field of automated testing technology, and in particular, to an automated testing system, method, device, and medium applicable to multi-component collaboration. Background Art
[0002] In the field of computer technology, software technology is developing rapidly in terms of UI (User Interface) automation testing tools. In particular, Web applications and mobile applications are becoming increasingly complex. With the continuous iteration of application technology, existing UI automation testing tools face many challenges.
[0003] In related technologies, Selenium is usually used as the core framework, and manual configuration of various browser drivers is required. Dynamic elements are processed by explicit or implicit waiting codes. Network requests are implemented through the native Requests library or third-party tools. Task scheduling relies on manual configuration of pipelines through external tools such as Jenkins. Message notifications are mostly sent by email. The various components are loosely integrated, and manual coordination of driver versions, data transmission and other issues is required. There are limitations such as cumbersome environment configuration, high code complexity, poor scheduling flexibility, and delayed result feedback, making it difficult to efficiently respond to modern high-frequency iterative testing needs.
[0004] However, the existing testing method is inefficient. Summary of the Invention
[0005] The embodiments described herein provide a multi-component collaborative automated testing system, method, device, and medium that overcome the aforementioned problems.
[0006] In a first aspect, according to the present disclosure, a multi-component collaborative automated testing system is provided, comprising: a network request control component, a test task scheduling component, an automated testing component, and a persistent storage component;
[0007] The network request control component is connected to the test task scheduling component, and is used to obtain target business data from the system under test through communication interaction with the API of the system under test, and send the target business data to the test task scheduling component;
[0008] The test task scheduling component is connected to the automated test component and is used to generate a target test task with an automated test tag based on the target business data, determine a corresponding task scheduling strategy according to the automated test tag attached to the target test task, and send the target test task to the automated test component based on the task scheduling strategy;
[0009] The automated testing component is connected to the persistent storage component and is used to execute the target test task to perform automated testing on the target business data to obtain data test results, and send the data test results corresponding to the target business data to the persistent storage component;
[0010] The persistent storage component is used to persistently store the data test results corresponding to the target business data.
[0011] Optionally, the automated testing component includes: an automated detection node and a first testing node;
[0012] The automated detection node is connected to the first test node and is used to perform a test content class detection on the target test task, and if the test content class associated with the target test task corresponds to a preset content class, send the target test task to the first test node;
[0013] The first test node is used to execute the target test task according to preset test rules to obtain the data test result corresponding to the target business data.
[0014] Optionally, the automated testing component further includes: a second testing node, the second testing node being connected to the automated testing node;
[0015] The automated detection node is further configured to send the target test task to the second test node if the test content class associated with the target test task corresponds to a non-preset content class;
[0016] The second test node is used to call the image processing model to perform test processing on the target test task to obtain the data test result corresponding to the target business data.
[0017] Optionally, it also includes: a database allocation component;
[0018] The database allocation component is connected to the persistent storage component and is used to determine the mapping database corresponding to the target business data from the database management pool according to the data type corresponding to the target business data;
[0019] The persistent storage component is specifically used to:
[0020] A connection relationship with the mapping database is established through a database connection pool, and the data test results corresponding to the target business data are stored in the mapping database corresponding to the target business data through the connection relationship with the mapping database.
[0021] Optionally, it also includes: testing the permission control component;
[0022] The test authority control component is connected to the network request control component and is used to verify the data acquisition authority of the network request control component;
[0023] The test authority control component is connected to the test task scheduling component and is also used to verify the task scheduling authority of the test task scheduling component;
[0024] The automated test component is connected to the automated test component and is also used to verify the test authority of the automated test component;
[0025] The test authority control component is connected to the persistent storage component and is also used to verify the information storage authority of the persistent storage component.
[0026] Optionally, it also includes: a test result push component;
[0027] The test result pushing component is connected to the persistent storage component and is used to push the data test result corresponding to the target business data to the target device.
[0028] Optionally, it also includes: a test result access component and a test result display component;
[0029] The test result access component is connected to the persistent storage component and the test result display component respectively, and is used to obtain the data test result corresponding to the target business data from the persistent storage component in response to a data access request, and send the data test result corresponding to the target business data to the test result display component;
[0030] The test result display component is used to display the data test results corresponding to the target business data.
[0031] In a second aspect, according to the present disclosure, a multi-component collaborative automated testing method is provided, comprising:
[0032] Acquire target business data from the system under test through communication interaction with the API of the system under test;
[0033] Generate a target test task with an automated test mark based on the target business data;
[0034] Executing the target test task to perform automated testing on the target business data to obtain data test results;
[0035] The data test results corresponding to the target business data are persistently stored.
[0036] In a third aspect, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the steps of the multi-component collaborative automated testing method in any of the above embodiments are implemented.
[0037] In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the automated testing method for multi-component collaboration in any of the above embodiments are implemented.
[0038] The multi-component collaborative automated testing system provided by the embodiment of the present application includes: a network request control component, a test task scheduling component, an automated testing component and a persistent storage component; the network request control component is connected to the test task scheduling component, and is used to obtain target business data from the system under test through communication interaction with the API of the system under test, and send the target business data to the test task scheduling component; the test task scheduling component is connected to the automated testing component, and is used to generate a target test task with an automated test tag based on the target business data, determine the corresponding task scheduling strategy according to the automated test tag attached to the target test task, and send the target test task to the automated testing component based on the task scheduling strategy; the automated testing component is connected to the persistent storage component, and is used to execute the target test task to perform automated testing on the target business data to obtain data test results, and send the data test results corresponding to the target business data to the persistent storage component; the persistent storage component is used to persistently store the data test results corresponding to the target business data. In this way, through the collaborative approach of multiple components, human participation in the testing process is reduced, and automated testing is effectively achieved and data testing efficiency is improved.
[0039] The above description is only an overview of the technical solutions of the embodiments of the present application. In order to more clearly understand the technical means of the embodiments of the present application, they can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the embodiments of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS
[0040] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings of the embodiments will be briefly described below. It should be noted that the drawings described below only relate to some embodiments of the present disclosure and are not intended to limit the present disclosure.
[0041] Figure 1 This is a structural diagram of a multi-component collaborative automated testing system provided by the present disclosure.
[0042] Figure 2 This is a flowchart of a multi-component collaborative automated testing method provided by the present disclosure.
[0043] Figure 3 It is a structural diagram of a computer device provided by the present disclosure.
[0044] It should be noted that the elements in the drawings are schematic and not drawn to scale. DETAILED DESCRIPTION
[0045] In order to make the purpose, technical solutions and advantages of the embodiments of the present disclosure more clear, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the described embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without creative work also fall within the scope of protection of the present disclosure.
[0046] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present disclosure belongs. It will be further understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the specification and the relevant art, and will not be interpreted in an idealized or overly formal manner unless otherwise explicitly defined herein. As used herein, a statement that two or more parts are "connected" or "coupled" together shall mean that the parts are joined together either directly or through one or more intermediate components.
[0047] References to "embodiments" herein mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase "embodiment" in various places in the specification does not necessarily refer to the same embodiment, nor does it necessarily refer to independent or alternative embodiments that are mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.
[0048] The term "and / or" in this document simply describes an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists, A and B exist simultaneously, and B exists. Additionally, the character " / " in this document generally indicates that the related objects are in an "or" relationship. Terms such as "first" and "second" are used solely to distinguish one component (or portion of a component) from another component (or portion of a component).
[0049] In the description of this application, unless otherwise specified, "plurality" means more than two (including two), and similarly, "multiple groups" means more than two (including two).
[0050] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings.
[0051] Figure 1 This is a schematic diagram of the structure of a multi-component collaborative automated testing system provided by an embodiment of the present disclosure. Figure 1 As shown, the multi-component collaborative automated testing system specifically includes: a network request control component 110 , a test task scheduling component 120 , an automated testing component 130 and a persistent storage component 140 .
[0052] The network request control component 110 is connected to the test task scheduling component 120 and is used to obtain target business data from the system under test through communication interaction with the API (Application Program Interface) of the system under test and send the target business data to the test task scheduling component 120.
[0053] Among them, the network request control component 110 can be OkHttp, which is an efficient HTTP (Hypertext Transfer Protocol) client that can be used to process network requests. It supports HTTP / 2 and SPDY protocols and can improve the efficiency and stability of network requests. This embodiment uses OkHttp to obtain backend key data and interact with UI operations, breaking through the limitation of traditional UI testing that only verifies the surface interface and achieving end-to-end business logic coverage.
[0054] The test task scheduling component 120 is connected to the automated test component 130, and is used to generate a target test task with an automated test tag based on the target business data, determine the corresponding task scheduling strategy according to the automated test tag attached to the target test task, and send the target test task to the automated test component 130 based on the task scheduling strategy.
[0055] The automated test tag attached to the target test task can be used to describe the test type corresponding to the target test task. For example, the automated test tag "1" indicates the test type is type 1, and the automated test tag "2" indicates the test type is type 2. If the automated test tag attached to the target test task indicates type 1, the determined task scheduling strategy is timed scheduling. If the automated test tag attached to the target test task indicates type 2, the determined task scheduling strategy is code submission-triggered scheduling.
[0056] The test task scheduling component 120 may be XXL-Job, which is a distributed task scheduling platform that provides a visual task scheduling management interface, supports scheduled task scheduling, distributed execution, and monitoring, and simplifies the scheduling and management of test tasks. This embodiment implements visual task scheduling through XXL-Job.
[0057] The automated testing component 130 is connected to the persistent storage component 140 and is used to execute target testing tasks to perform automated testing on target business data to obtain data testing results, and send the data testing results corresponding to the target business data to the persistent storage component 140 .
[0058] Among them, the automated testing component 130 can use Playwright as the core component, and deeply collaborate with technology stacks such as Spring Boot and MyBatis to build an efficient and stable testing system. Playwright is an open source automated testing framework that can control the browser through code for automated testing. It natively supports multiple mainstream browsers and has powerful cross-browser testing capabilities; the built-in intelligent waiting mechanism automatically handles dynamic elements, avoiding manual writing of complex waiting code, greatly improving the stability and writing efficiency of test scripts; native support for multiple browsers and no manual configuration of drivers is required, completely solving the driver compatibility problem of traditional tools.
[0059] In some embodiments, the automated testing component 130 includes: an automated detection node and a first test node; the automated detection node is connected to the first test node and is used to perform test content class detection on the target test task. If the test content class associated with the target test task corresponds to a preset content class, the target test task is sent to the first test node; the first test node is used to execute the target test task through preset test rules to obtain data test results corresponding to the target business data.
[0060] In some embodiments, the automated testing component 130 also includes: a second test node, which is connected to the automated detection node; the automated detection node is also used to send the target test task to the second test node if the test content class associated with the target test task corresponds to a non-preset content class; the second test node is used to call the image processing model to perform test processing on the target test task to obtain data test results corresponding to the target business data.
[0061] The test content class detection can be used to determine the complexity of the UI element corresponding to the target test task. If the test content class associated with the target test task corresponds to the preset content class, the complexity of the UI element corresponding to the target test task is low. If the test content class associated with the target test task corresponds to the non-preset content class, the complexity of the UI element corresponding to the target test task is high.
[0062] The second test node can be an OpenCV component, which provides various image processing and computer vision algorithms for image recognition and analysis. When the target test task corresponds to a complex UI element, image comparison using the OpenCV component provides a precise basis for UI visual verification, comprehensively optimizing the execution efficiency and problem location capabilities of automated testing.
[0063] The persistent storage component 140 is used to persistently store the data test results corresponding to the target business data.
[0064] Among them, the persistent storage component 140 can be MyBatis, which supports customized SQL, stored procedures and advanced mapping, making database operations more flexible and efficient, and facilitating the management of persistent storage and reading of data.
[0065] In this embodiment, the automated testing system with multiple components working together includes: a network request control component, a test task scheduling component, an automated testing component and a persistent storage component; the network request control component is connected to the test task scheduling component, and is used to obtain target business data from the system under test through communication interaction with the API of the system under test, and send the target business data to the test task scheduling component; the test task scheduling component is connected to the automated testing component, and is used to generate a target test task with an automated test tag based on the target business data, determine the corresponding task scheduling strategy according to the automated test tag attached to the target test task, and send the target test task to the automated testing component based on the task scheduling strategy; the automated testing component is connected to the persistent storage component, and is used to execute the target test task to perform automated testing on the target business data to obtain data test results, and send the data test results corresponding to the target business data to the persistent storage component; the persistent storage component is used to persistently store the data test results corresponding to the target business data. In this way, through the collaboration of multiple components, human participation in the testing process is reduced, and automated testing is effectively achieved and data testing efficiency is improved.
[0066] Some embodiments further include: a database allocation component; the database allocation component is connected to the persistent storage component and is used to determine the mapping database corresponding to the target business data from the database management pool based on the data type corresponding to the target business data.
[0067] The persistent storage component 140 is specifically used to:
[0068] A connection relationship with a mapping database is established through a database connection pool, and data test results corresponding to target business data are stored in the mapping database corresponding to the target business data through the connection relationship with the mapping database.
[0069] Among them, the database connection pool can be Druid, which has powerful performance monitoring and management functions, can improve the reuse rate of database connections and enhance system performance.
[0070] Some embodiments further include a test permission control component, which may be Shiro, and can provide authentication, authorization, encryption, and session management functions to ensure secure access control of the system and the operating permissions of each test process component.
[0071] The test permission control component is connected to the network request control component 110 and is used to verify the data acquisition permission of the network request control component 110; and after the network request control component 110 is verified, a verification success indication is sent to the network request control component 110, so that the network request control component 110 obtains the target business data from the system under test through communication interaction with the API of the system under test.
[0072] The test authority control component is connected to the test task scheduling component 120 and is also used to verify the task scheduling authority of the test task scheduling component 120; and after the test task scheduling component 120 is verified, a verification success indication is sent to the test task scheduling component 120, so that the test task scheduling component 120 generates a target test task with an automated test tag based on the target business data, and determines the corresponding task scheduling strategy according to the automated test tag attached to the target test task.
[0073] The automated test component is connected to the automated test component 130 and is also used to verify the test authority of the automated test component 130; and after the automated test component 130 is verified, a verification success indication is sent to the automated test component 130 so that the automated test component 130 executes the target test task and obtains the data test results.
[0074] The test permission control component is connected to the persistent storage component 140 and is also used to verify the information storage permission of the persistent storage component 140; and after the persistent storage component 140 is verified, a verification success indication is sent to the persistent storage component 140, so that the persistent storage component 140 persistently stores the data test results corresponding to the target business data.
[0075] In some embodiments, the system further includes: a test result push component; the test result push component is connected to the persistent storage component 140 and is used to push data test results corresponding to target business data to the target device.
[0076] The test result push component can be DingTalk, which can provide message notifications of test results and support multiple message push methods, allowing team members to obtain information in a timely manner. This embodiment uses DingTalk to push data test results in real time, replacing the manual configuration and email notification mode of traditional tools, significantly shortening the testing cycle and improving team collaboration efficiency.
[0077] Some embodiments further include: a test result access component and a test result display component.
[0078] The test result access component is connected to the persistent storage component 140 and the test result display component respectively, and is used to respond to the data access request, obtain the data test results corresponding to the target business data from the persistent storage component 140, and send the data test results corresponding to the target business data to the test result display component; the test result display component is used to display the data test results corresponding to the target business data.
[0079] Among them, this embodiment responds to the data access request sent by the user device through the test result access component, obtains the data test results corresponding to the target business data from the persistent storage component 140, and displays the data test results corresponding to the target business data through the test result display component, so that the user can view the access data in time.
[0080] When performing automated testing in this embodiment, the backend relies on technology stacks such as Spring Boot to complete core functions such as data processing, operation execution, logging, report generation, and message notification. In back-end interaction, Playwright, as a core component, deeply collaborates with technology stacks such as Spring Boot and MyBatis to build an efficient and stable testing system: based on the automated configuration capabilities of SpringBoot, the system quickly integrates MyBatis to achieve persistent management of test data; combined with the Druid connection pool to optimize database access performance, Shiro ensures security and permission control of the test process; among them, Playwright, as a browser automation engine, is compatible with mainstream browsers without manual configuration of the driver, and its intelligent waiting mechanism automatically processes dynamic elements, significantly improving script stability.
[0081] During testing, the OkHttp component seamlessly interacts with the API of the system under test, providing Playwright with critical business data and enabling end-to-end verification of the UI and backend logic. Execution results are stored in the database via MyBatis and pushed to the team collaboration platform in real time by the DingTalk component, ensuring rapid response to issues. XXL-Job is responsible for scheduling and monitoring test tasks, supporting flexible modes such as scheduled execution or code submission triggering. The OpenCV component provides Playwright with image comparison capabilities, enabling visual verification of complex UI elements. Through the collaborative efforts of these components, the system forms a complete closed loop from test initiation and execution to result notification, comprehensively improving the efficiency and quality of automated testing.
[0082] In summary, this embodiment uses Playwright as the core UI automation test component in the back-end during testing. Compared with Selenium, it natively supports multiple mainstream browsers, does not require additional driver configuration, and can automatically manage versions. This avoids the cumbersome configuration and potential test failure risks caused by browser driver compatibility issues, allowing the test to run stably in different browser environments, effectively improving the comprehensiveness and accuracy of the test, and timely discovering product compatibility issues under different browsers. Playwright has a built-in intelligent waiting mechanism that can automatically wait for elements to enter an interactive state, reducing the workload of manually writing waiting code and reducing code complexity. At the same time, combined with other back-end components, such as okhttp responsible for network requests and xxl-job management task scheduling, each component works together to complete a series of test processes such as data processing, operation execution, and logging, greatly improving test execution efficiency and shortening the test cycle. Message notification is achieved through dingtalk, supporting multiple instant messaging methods, and can promptly inform team members of test results, meeting diverse team collaboration needs and ensuring that problems are handled in a timely manner. xxl-job provides a visual task scheduling interface, allowing users to easily set up test task execution plans, such as scheduled execution or execution triggered by specific events, making testing more flexible and controllable. System stability and scalability are ensured by mature foundational components such as Spring Boot, MyBatis, and Druid. These components are widely used in software development and have extensive technical documentation and community support, facilitating subsequent system maintenance and functionality expansion.
[0083] Figure 2 This is a flow chart of a multi-component collaborative automated testing method provided in this embodiment. The specific steps of the multi-component collaborative automated testing method include:
[0084] S210 : Acquire target business data from the system under test through communication interaction with the API of the system under test.
[0085] S220: Generate a target test task with an automated test tag based on the target business data.
[0086] The automated test tag attached to the target test task can be used to describe the test type corresponding to the target test task. For example, the automated test tag "1" indicates the test type is type 1, and the automated test tag "2" indicates the test type is type 2. If the automated test tag attached to the target test task indicates type 1, the determined task scheduling strategy is timed scheduling. If the automated test tag attached to the target test task indicates type 2, the determined task scheduling strategy is code submission-triggered scheduling.
[0087] S230: Execute the target test task to perform automated testing on the target business data to obtain data test results.
[0088] In some embodiments, executing a target test task includes:
[0089] The target test task is tested for its test content class. If the test content class associated with the target test task corresponds to a preset content class, the target test task is executed using the preset test rules to obtain the data test results corresponding to the target business data. If the test content class associated with the target test task corresponds to a non-preset content class, the image processing model is invoked to test and process the target test task to obtain the data test results corresponding to the target business data.
[0090] Test content class detection can be used to determine the complexity of the UI element corresponding to the target test task. If the test content class associated with the target test task corresponds to a preset content class, the UI element corresponding to the target test task is relatively low in complexity. If the test content class associated with the target test task corresponds to a non-preset content class, the UI element corresponding to the target test task is relatively high in complexity. This allows for separate testing of different test content classes, further improving data testing efficiency.
[0091] S240. Persistently store the data test results corresponding to the target business data.
[0092] Therefore, through the collaboration of multiple components, human participation in the testing process is reduced, automated testing is effectively achieved, and data testing efficiency is improved.
[0093] In some embodiments, the present invention further comprises:
[0094] Based on the data type of the target business data, the corresponding mapping database is determined from the database management pool. A connection relationship is established between the database connection pool and the mapping database. Through the connection relationship with the mapping database, the data test results corresponding to the target business data are stored in the mapping database corresponding to the target business data. In this way, the appropriate database can be selected for the target business data to store the test results.
[0095] Some embodiments also include: pushing data test results corresponding to target business data to the target device. This allows components to push data test results in real time, replacing the manual configuration and email notification model of traditional tools, significantly shortening testing cycles and improving team collaboration efficiency.
[0096] In some embodiments, the method further includes: obtaining data test results corresponding to the target business data in response to the data access request, and displaying the data test results corresponding to the target business data. Thus, the data test results corresponding to the target business data are displayed, making it easier for users to view access data in a timely manner.
[0097] The present application also provides a computer device. Figure 3 , Figure 3 This is a basic structural block diagram of the computer device in this embodiment.
[0098] The computer device includes a memory 310 and a processor 320 that are interconnected and communicate with each other via a system bus. It should be noted that the figure only shows a computer device with a memory 310 and a processor 320, but it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to a microprocessor, an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a digital signal processor (DSP), an embedded device, etc.
[0099] Computer devices can be desktop computers, laptops, PDAs, cloud servers, etc. Computer devices can interact with users through keyboards, mice, remote controls, touchpads, or voice control devices.
[0100] The memory 310 includes at least one type of readable storage medium, including non-volatile memory or volatile memory, such as flash memory, hard disk, multimedia card, card-type memory (such as SD or DX memory), random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic storage, magnetic disk, optical disk, etc. The RAM may include static RAM or dynamic RAM. In some embodiments, the memory 310 may be an internal storage unit of a computer device, such as a hard disk or memory of the computer device. In other embodiments, the memory 310 may also be an external storage device of the computer device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) card, or a Flash Card equipped on the computer device. Of course, the memory 310 may also include both the internal storage unit of the computer device and its external storage device. In this embodiment, the memory 310 is generally used to store the operating system and various application software installed on the computer device, such as the program code of the above-mentioned method. In addition, the memory 310 may also be used to temporarily store various types of data that have been output or are about to be output.
[0101] The processor 320 is generally used to perform the overall operation of the computer device. In this embodiment, the memory 310 is used to store program code or instructions, which include computer operating instructions. The processor 320 is used to execute the program code or instructions stored in the memory 310 or process data, such as the program code for running the above method.
[0102] In this document, a bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. This bus system can be divided into address buses, data buses, and control buses. For ease of illustration, the figure uses only one thick line, but this does not mean that there is only one bus or only one type of bus.
[0103] Another embodiment of the present application further provides a computer-readable medium, which may be a computer-readable signal medium or a computer-readable medium. A processor in a computer reads the computer-readable program code stored in the computer-readable medium, enabling the processor to execute the functional actions specified in each step or combination of steps in the above method, and to generate a device that implements the functional actions specified in each block or combination of blocks in the block diagram.
[0104] Computer-readable media include but are not limited to electronic, magnetic, optical, electromagnetic, infrared memory or semiconductor systems, devices or apparatuses, or any appropriate combination of the foregoing, the memory is used to store program codes or instructions, the program codes include computer operating instructions, and the processor is used to execute the program codes or instructions of the above-mentioned methods stored in the memory.
[0105] For the definitions of memory and processor, please refer to the description of the aforementioned computer device embodiment and will not be repeated here.
[0106] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0107] Each functional unit or module in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The above-mentioned integrated units may be implemented in the form of hardware or software functional units.
[0108] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program code.
[0109] In the claims, any reference signs placed between brackets shall not be construed as limiting the claims. The word "comprising" described in the present application does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The present application can be implemented with the aid of hardware comprising several different elements and with the aid of a suitably programmed computer. In a unit claim that lists several means, several units of these means may be embodied by the same hardware item. The use of first, second, and third etc. does not indicate any order and these words may be interpreted as names. The steps in the above embodiments should not be understood as limiting the order of execution unless otherwise specified.
[0110] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.
Claims
1. A multi-component collaborative automated testing system, characterized in that: include: Network request control component, test task scheduling component, automated testing component, and persistent storage component; The network request control component is connected to the test task scheduling component, and is used to obtain target business data from the system under test through communication interaction with the API of the system under test, and send the target business data to the test task scheduling component; The test task scheduling component is connected to the automated test component and is used to generate a target test task with an automated test tag based on the target business data, determine a corresponding task scheduling strategy according to the automated test tag attached to the target test task, and send the target test task to the automated test component based on the task scheduling strategy; The automated testing component is connected to the persistent storage component and is used to execute the target test task to perform automated testing on the target business data to obtain data test results, and send the data test results corresponding to the target business data to the persistent storage component; The persistent storage component is used to persistently store the data test results corresponding to the target business data.
2. The system according to claim 1, wherein: The automated testing component includes: an automated detection node and a first testing node; The automated detection node is connected to the first test node and is used to perform a test content class detection on the target test task, and if the test content class associated with the target test task corresponds to a preset content class, send the target test task to the first test node; The first test node is used to execute the target test task according to preset test rules to obtain the data test result corresponding to the target business data.
3. The system according to claim 2, characterized in that The automated testing component further includes: a second testing node, the second testing node being connected to the automated testing node; The automated detection node is further configured to send the target test task to the second test node if the test content class associated with the target test task corresponds to a non-preset content class; The second test node is used to call the image processing model to perform test processing on the target test task to obtain the data test result corresponding to the target business data.
4. The system according to claim 1, wherein: Also includes: Database allocation component; The database allocation component is connected to the persistent storage component and is used to determine the mapping database corresponding to the target business data from the database management pool according to the data type corresponding to the target business data; The persistent storage component is specifically used to: A connection relationship with the mapping database is established through a database connection pool, and the data test results corresponding to the target business data are stored in the mapping database corresponding to the target business data through the connection relationship with the mapping database.
5. The system according to claim 1, wherein: Also includes: Test the permission control component; The test authority control component is connected to the network request control component and is used to verify the data acquisition authority of the network request control component; The test authority control component is connected to the test task scheduling component and is also used to verify the task scheduling authority of the test task scheduling component; The automated test component is connected to the automated test component and is also used to verify the test authority of the automated test component; The test authority control component is connected to the persistent storage component and is also used to verify the information storage authority of the persistent storage component.
6. The system according to claim 1, wherein: Also includes: Test result push component; The test result pushing component is connected to the persistent storage component and is used to push the data test result corresponding to the target business data to the target device.
7. The system according to claim 1, wherein: Also includes: Test result access component and test result display component; The test result access component is connected to the persistent storage component and the test result display component respectively, and is used to obtain the data test result corresponding to the target business data from the persistent storage component in response to a data access request, and send the data test result corresponding to the target business data to the test result display component; The test result display component is used to display the data test results corresponding to the target business data.
8. A multi-component collaborative automated testing method, characterized in that: include: Acquire target business data from the system under test through communication interaction with the API of the system under test; Generate a target test task with an automated test mark based on the target business data; Executing the target test task to perform automated testing on the target business data to obtain data test results; The data test results corresponding to the target business data are persistently stored.
9. A computer device, characterized in that: The system comprises a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the multi-component collaborative automated testing method as claimed in claim 8 is implemented.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the multi-component collaborative automated testing method according to claim 8 is implemented.