Automatic testing method and device, equipment and storage medium

Abstract

The invention discloses an automatic testing method and device, equipment and a storage medium, and relates to the technical field of software testing. Determining a to-be-tested software type according to the current test requirement; calling a target test tool according to the type of the to-be-tested software; and performing automatic testing on to-be-tested software through the target testing tool. The specific to-be-tested software type can be determined according to the current test requirement, so that the corresponding target test tool is called, automatic testing is performed through the target test tool, manual test type identification or manual test process interference is not needed, automation of the whole test process is realized, and the test efficiency and accuracy are improved.

Description

Technical Field

[0001] The present application relates to the field of software testing technology, and in particular to automated testing methods, devices, equipment and storage media. Background Art

[0002] Software testing in existing vehicles is done by manually formulating a test plan, including test scope, resource allocation, schedule, test environment settings, etc., so that software testing is performed according to the test plan. Frequent human intervention leads to low test efficiency and unstable tests. Summary of the invention

[0003] The main purpose of this application is to provide an automated testing method, device, equipment and storage medium, aiming to solve the technical problems of low testing efficiency and accuracy in the prior art.

[0004] To achieve the above objectives, the present application proposes an automated testing method, which includes:

[0005] Responding to current testing needs;

[0006] Determine the type of software to be tested according to the current test requirements;

[0007] Calling a target testing tool according to the type of software to be tested;

[0008] The target testing tool is used to perform automated testing on the software to be tested.

[0009] In one embodiment, the step of calling a target testing tool according to the type of software to be tested includes:

[0010] Determine a preset test process according to the type of software to be tested;

[0011] Determine script data through the preset test process;

[0012] A target testing tool is determined according to the script data.

[0013] In one embodiment, the step of calling a target testing tool according to the type of software to be tested includes:

[0014] When the type of the software to be tested is unit testing, determining a unit testing classification;

[0015] When the unit test is classified as a dynamic test, obtaining a unit dynamic test process;

[0016] Determine a plurality of unit test script data according to the unit dynamic test process;

[0017] A plurality of target testing tools are selected according to the plurality of unit test script data.

[0018] In one embodiment, the step of calling a target testing tool according to the type of software to be tested includes:

[0019] When the type of the software to be tested is an integration test, obtaining an integration test process;

[0020] Determine the integration test script data through the integration test process;

[0021] A target testing tool is selected according to the integrated testing script data.

[0022] In one embodiment, before the step of calling the target testing tool according to the type of software to be tested, the method further includes:

[0023] Respond to user-triggered custom needs;

[0024] Determine and adjust script parameters according to the custom requirements;

[0025] A target test tool is generated according to the adjustment script parameters.

[0026] In one embodiment, the method further comprises:

[0027] Obtain automated test results for the software to be tested;

[0028] Generate a test log according to the automated test results;

[0029] Generate a target display format according to the test log;

[0030] The automated test results are displayed in the target display format.

[0031] In one embodiment, after the step of responding to the current test requirement, the method further includes:

[0032] Analyzing the current test requirements;

[0033] When the current test requirement has an associated test task, obtaining an associated task type of the associated test task;

[0034] A target testing tool is called based on the associated task type to perform synchronous testing.

[0035] In addition, to achieve the above objectives, the present application also proposes an automated testing device, the automated testing device comprising:

[0036] A response module, used to respond to current test requirements;

[0037] A determination module, used to determine the type of software to be tested according to the current test requirements;

[0038] A calling module, used to call a target testing tool according to the type of software to be tested;

[0039] The testing module is used to perform automated testing on the software to be tested through the target testing tool.

[0040] In addition, to achieve the above objectives, the present application also proposes an automated testing device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the automated testing method described above.

[0041] In addition, to achieve the above objectives, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the automated testing method described above are implemented.

[0042] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the automated testing method described above are implemented.

[0043] One or more technical solutions proposed in this application respond to current test requirements; determine the type of software to be tested according to the current test requirements; call the target test tool according to the type of software to be tested; and perform automated testing on the software to be tested through the target test tool. The specific type of software to be tested can be determined by the current test requirements, so as to call the corresponding target test tool, and perform automated testing through the target test tool, without the need for manual identification of test types or manual intervention in the test process, so as to achieve automation of the entire test process and improve test efficiency and accuracy. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0045] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0046] Figure 1 A schematic diagram of a process flow provided for the first embodiment of the automated testing method of the present application;

[0047] Figure 2This is a schematic diagram of application lifecycle management of an embedded software development management platform in an embodiment of an automated testing method of this application;

[0048] Figure 3 A schematic diagram of the process flow provided for the second embodiment of the automated testing method of the present application;

[0049] Figure 4 A schematic diagram of the process flow provided for the third embodiment of the automated testing method of the present application;

[0050] Figure 5 A flowchart of the fourth embodiment of the automated testing method of the present application is provided;

[0051] Figure 6 A flowchart of the fifth embodiment of the automated testing method of the present application is provided;

[0052] Figure 7 This is a schematic diagram of the module structure of the automated testing device according to an embodiment of the present application;

[0053] Figure 8 This is a schematic diagram of the device structure of the hardware operating environment involved in the automated testing method in the embodiment of the present application.

[0054] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0055] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0056] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0057] The main solution of the embodiment of the present application is: responding to current test requirements; determining the type of software to be tested according to the current test requirements; calling a target test tool according to the type of software to be tested; and performing automated testing on the software to be tested through the target test tool.

[0058] Since the prior art mainly uses manual testing or testing software-assisted testing when conducting software testing in vehicles, human participation in testing leads to low testing efficiency and low testing accuracy.

[0059] The present application provides a solution by stratifying the vehicle's ECU (Electronic Control Unit) in advance and analyzing the stratification results to determine that the application layer software can be directly reused across ECUs. Therefore, an automated testing platform is developed based on the application layer software, and an embedded software testing tool is integrated and developed on the automated testing platform, so that the entire software testing process can be automated during testing to improve testing efficiency and accuracy.

[0060] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, an automated testing platform, etc. The following takes the automated testing platform as an example to illustrate this embodiment and the following embodiments.

[0061] Based on this, the present application embodiment provides an automated testing method, referring to Figure 1 , Figure 1 This is a flowchart of the first embodiment of the automated testing method of the present application.

[0062] In this embodiment, the automated testing method is applied to an automated testing platform, and the automated testing method includes steps S10 to S40:

[0063] Step S10: responding to current test requirements.

[0064] It should be noted that the current test requirements may be requirements initiated by users by using an automated testing platform, and the main usage scenario of the current test requirements is the testing requirements of various software in the vehicle.

[0065] like Figure 2 As shown, Figure 2 This is a schematic diagram of the application lifecycle management of the embedded software development management platform, including early demand analysis, and then outline design, system design and detailed design based on the analysis. The demand analysis, outline design and system design can be implemented based on system engineering management of requirements and models. The system design and detailed design are mainly detailed designs of electronic and electrical architectures. After the design is completed, software development is carried out. DevOps automated pipelines, code version management and code storage management can be set up. Unit testing, system testing, integration testing, etc. are carried out after software development, so that the software can be released after the test passes, and the cloud test software can be reliably called to perform virtual testing.

[0066] The current test requirements may be functional test requirements, performance test requirements, safety test requirements, etc. of the software in the vehicle. The current test requirements may be manually triggered by the user or timed triggering, for example, the user sets in advance to execute the automated test process every 1 hour.

[0067] In a feasible implementation manner, step S10 may include steps S11 to S13:

[0068] Step S11: Analyze the current test requirements.

[0069] It should be noted that in order to improve the efficiency of automatic testing, the current test requirements can also be analyzed to determine whether there are related test tasks corresponding to the current test requirements. The association between test tasks can be analyzed in advance by analyzing the properties of each test task, and binding them according to the properties to obtain related test tasks.

[0070] In a specific implementation, if there is no associated test task for the current test requirement, a step of determining the type of software to be tested according to the current test requirement is performed.

[0071] Step S12: when the current test requirement has an associated test task, obtaining an associated task type of the associated test task.

[0072] It should be understood that when the current test requirement has an associated test task, the associated task type of the associated test task can be obtained at the same time, and the step of determining the type of software to be tested according to the current test requirement can be synchronously executed to determine the target test tool of the current test requirement.

[0073] Step S13: calling a target testing tool to perform synchronous testing based on the associated task type.

[0074] In a specific implementation, the corresponding target test tool may be called according to the associated task type, so that the target test tool may be used to synchronously test the test task corresponding to the current test requirement and the associated test task, thereby improving the test efficiency.

[0075] Step S20: Determine the type of software to be tested according to the current test requirement.

[0076] It should be noted that different test requirements correspond to different types of software to be tested. The types of software to be tested may be unit testing, system testing, integration testing, qualification testing, etc. The test requirements can be analyzed to determine the keywords in the current test requirements, and the type of software to be tested can be determined based on the keywords.

[0077] In a feasible implementation manner, in order to improve the interactivity with the automated test platform and support user-defined script parameters, steps A01 to A03 may be included before step S20:

[0078] Step A01: Responding to a customization requirement triggered by a user.

[0079] It should be noted that when the user has the need to set script parameters, the setting button can be triggered through the automated testing platform to generate custom requirements.

[0080] Step A02: Determine and adjust script parameters according to the custom requirements.

[0081] In the specific implementation, the script parameters that the user needs to adjust or the new script parameters uploaded by the user can be determined according to the customized requirements. The automated testing platform supports the user to jump from the automated testing platform to the specific tool software to modify the software configuration parameters, so as to obtain the final adjusted script parameters. The script parameters can be set or modified through the user interaction interface. Specifically, the configuration can be adjusted in the tool software through the configuration parameter modification module.

[0082] Step A03: Generate a target test tool according to the adjustment script parameters.

[0083] In a specific implementation, a target test tool is generated according to the adjustment script parameters, and the automated test platform will generate a corresponding target test tool according to the user-defined script parameters to meet specific test requirements.

[0084] Step S30: calling a target testing tool according to the type of software to be tested.

[0085] It should be noted that the target test tool can be a tool in a pre-configured test tool library or a customized test tool generated according to specific requirements. The selection of the target test tool depends on the type of software to be tested and the specific content of the test requirements.

[0086] Step S40: performing automated testing on the software to be tested by using the target testing tool.

[0087] It should be noted that when automated testing is performed through the target testing tool, comprehensive coverage of the software can be achieved, including but not limited to functional testing, performance testing, security testing, etc. The automated testing platform will automatically execute test cases, collect test results, and generate corresponding test reports based on the type of software to be tested and the test requirements.

[0088] This embodiment provides an automated testing method, which responds to current testing requirements; determines the type of software to be tested according to the current testing requirements; calls a target testing tool according to the type of software to be tested; and performs automated testing on the software to be tested through the target testing tool. The specific type of software to be tested can be determined according to the current testing requirements, so that the corresponding target testing tool can be called, and automated testing can be performed through the target testing tool, without the need for manual identification of the test type or manual intervention in the test process, thereby automating the entire test process and improving test efficiency and accuracy.

[0089] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction, and will not be repeated in the following. Figure 3 , step S30 includes steps S301 to S303:

[0090] Step S301: Determine a preset test process according to the type of software to be tested.

[0091] It should be noted that the preset test process can be a predefined test process template for different types of software to be tested, which can contain a series of standardized test steps and rules to ensure the consistency and repeatability of the test process. The preset test process can be determined based on historical test data, industry standards or best practices.

[0092] Different test software types correspond to different test processes. Multiple test processes can be defined according to the test software type, and the preset test process can be updated in real time according to the test results or user feedback.

[0093] Step S302: Determine script data through the preset test process.

[0094] It should be noted that script data is key information used to control the test tool to perform test tasks during automated testing. By presetting the test process to determine the script data, it can ensure that the test tool operates according to the predetermined test steps and rules, thereby improving the accuracy and consistency of the test.

[0095] Step S303: Determine the target testing tool according to the script data.

[0096] In a specific implementation, according to the determined script data, a target test tool suitable for the current test requirements can be further selected. The selection of the target test tool can be based on the test type, test environment, test parameters and other information in the script data to ensure that the test tool can meet the specific test requirements.

[0097] This embodiment determines a preset test process according to the type of software to be tested; determines script data through the preset test process; and determines a target test tool according to the script data. The corresponding script data is quickly determined according to the preset test process, thereby determining the target test tool that can be tested, thereby improving the efficiency and effect of the test.

[0098] Based on the first embodiment of the present application, in the third embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction, and will not be repeated in the following. Figure 4 , step S30 includes steps S301' to S304':

[0099] Step S301': when the type of the software to be tested is unit test, determine the unit test classification.

[0100] In specific implementation, unit testing is the testing of the smallest testable part of the software (usually a function or method). Unit testing classification can include static testing and dynamic testing. Static testing can mainly be done through user-assisted testing, focusing on the grammatical correctness and coding style of the code, while dynamic testing focuses on the behavior and functionality of the code at runtime. By determining the unit testing classification, you can more accurately select the appropriate testing tools and testing methods.

[0101] Step S302': when the unit test is classified as a dynamic test, obtain a unit dynamic test process.

[0102] In a specific implementation, the unit dynamic test process may include a series of test steps for verifying the behavior of the code at runtime. These steps may include simulating input data, monitoring output results, checking exception handling, etc. Obtaining the unit dynamic test process helps ensure the comprehensiveness and accuracy of the test process.

[0103] Step S303': determining a plurality of unit test script data according to the unit dynamic test process.

[0104] In a specific implementation, unit test script data is key information for automating the unit dynamic test process. This data may include test cases, expected results, test environment configuration, etc. Multiple unit test script data can be obtained according to different processes in the unit dynamic test process. By determining the unit test script data, it can be ensured that the test tool operates according to the predetermined test steps and rules, thereby improving the accuracy and consistency of the test.

[0105] Step S304': selecting multiple target testing tools through the multiple unit test script data.

[0106] In a specific implementation, selecting multiple target test tools based on multiple unit test script data can ensure that the test tools can cover the key test points in all unit dynamic test processes. When selecting a target test tool, factors such as the function, performance, and compatibility of the test tool can be considered to ensure that the test tool can meet specific test requirements.

[0107] The specific target testing tools used for unit testing may include: Simulink check, PolySpace, QAC, Simulink test, Tessy, and gtest.

[0108] In this embodiment, when the type of the software to be tested is unit testing, the unit test classification is determined; when the unit test classification is dynamic testing, the unit dynamic test process is obtained; multiple unit test script data are determined according to the unit dynamic test process; and multiple target test tools are selected through the multiple unit test script data. It can ensure that the unit test covers each independent unit of the software, find and fix problems in time, and improve code quality and development efficiency. At the same time, by selecting a suitable target test tool, the automation and efficiency of the test can be improved.

[0109] Based on the first embodiment of the present application, in the fourth embodiment of the present application, the same or similar contents as those in the first embodiment can be referred to the above description, and will not be described in detail later. Figure 5 , step S30 includes steps S301" to S303":

[0110] Step S301": when the type of the software to be tested is an integration test, obtain the integration test process.

[0111] In specific implementation, the integration test process refers to the process of combining various modules for testing after unit testing. The acquisition of the integration test process can be based on software architecture design documents, historical test data or industry standards. Determining the integration test process helps ensure that the interfaces and interactions between various modules can work correctly.

[0112] Step S302": Determine the integrated test script data through the integrated test process.

[0113] In specific implementations, the integrated test script data is key information used to automate the integrated test process. This data may include test cases, expected results, test environment configuration, etc. By determining the integrated test script data, it is possible to ensure that the test tool operates according to the predetermined test steps and rules, thereby improving the accuracy and consistency of the test.

[0114] Step S303": selecting a target testing tool according to the integrated testing script data.

[0115] In specific implementation, selecting the target test tool based on the integrated test script data can ensure that the test tool can cover all key test points in the integrated test process. When selecting the target test tool, factors such as the function, performance, and compatibility of the test tool can be considered to ensure that the test tool can meet specific test requirements.

[0116] The target testing tools for integration testing include but are not limited to CANoe, GreenHills, Tasking, CS+, GCC, IAR, ARM Compiler, and Clang.

[0117] In some embodiments, the automated test type may also include a qualification test, which is mainly a hardware test of the vehicle. The specific test tools used include LABView, NI, etc.

[0118] In this embodiment, when the type of software to be tested is an integration test, an integration test process is obtained; integration test script data is determined through the integration test process; and a target test tool is selected according to the integration test script data. By determining the integration test script data and selecting the target test tool, the comprehensiveness and effectiveness of the integration test can be ensured, problems in the integration can be discovered and fixed in time, and the overall quality and stability of the software can be improved.

[0119] Based on the first embodiment of the present application, in the fifth embodiment of the present application, the same or similar contents as those in the first embodiment can be referred to the above description, and will not be described in detail later. Figure 6 , after step S40, further comprising steps S41 to S44:

[0120] Step S41: Obtain the automated test results of the software to be tested.

[0121] It should be noted that the automated testing platform will collect various data during the testing process, including test case execution results, test coverage, performance indicators, etc., and summarize these data into test results. Different types of software to be tested have different acquisition methods. For example, unit testing and integration testing can use Matlab command lines to obtain data, such as running detailed records, and qualification testing can call the MATLAB engine in LabVIEW to execute MATLAB code directly in the LabVIEW environment.

[0122] Step S42: Generate a test log according to the automated test result.

[0123] In specific implementations, the test log will record in detail various events during the test process, including the execution status of test cases, error messages, warning messages, etc., to facilitate subsequent analysis and problem location.

[0124] Step S43: Generate a target display format according to the test log.

[0125] It should be noted that the target display form generated based on the test log can be a graphical report, chart, dashboard, etc., which is convenient for users to intuitively understand the test results and software quality status. The tool software returns the test results (excel, html files) to the automated testing platform, and the automated testing platform can generate the target display form, which can be a report or a dashboard.

[0126] Step S44: displaying the automated test results in the target display format.

[0127] In a specific implementation, the target display form can be displayed on the display of the automated test platform through a graphical user interface (GUI), or the test results can be sent to a remote user through a network interface, or the test report can be exported to a PDF, Excel or other format for users to download and analyze. In addition, the target display form can also include a real-time monitoring function, allowing users to view the test progress and results in real time during the test process, so as to adjust the test strategy or perform troubleshooting in a timely manner.

[0128] For example, the test results of unit testing can use Matlab's command line to obtain data, such as running detailed records; using the report function provided by the tool, a detailed test report can be generated, including charts, lists and detailed information. The test results of integration testing can be exported (CSV, XML or other formats) and displayed on the Web through system integration. The qualification test can export data (JSON or XML or other formats) and display on the Web through system integration.

[0129] This embodiment obtains the automated test results of the software to be tested; generates a test log according to the automated test results; generates a target display form according to the test log; and displays the automated test results in the target display form. This can ensure the transparency and traceability of the automated test results, help users quickly identify test problems and take action, and improve the efficiency of the entire software testing and development process.

[0130] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the automated testing method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0131] This application also provides an automated testing device, please refer to Figure 7 , the automated testing device comprises:

[0132] The response module 10 is used to respond to the current test requirement.

[0133] The determination module 20 is used to determine the type of software to be tested according to the current test requirement.

[0134] The calling module 30 is used to call the target testing tool according to the type of the software to be tested.

[0135] The testing module 40 is used to perform automated testing on the software to be tested through the target testing tool.

[0136] The automated testing device provided by the present application adopts the automated testing method in the above embodiment, which can solve the technical problems of low testing efficiency and accuracy in the prior art. Compared with the prior art, the beneficial effects of the automated testing device provided by the present application are the same as the beneficial effects of the automated testing method provided by the above embodiment, and other technical features in the automated testing device are the same as the features disclosed in the above embodiment method, which will not be described in detail here.

[0137] In one embodiment, the determination module 20 is further used to determine a preset test process according to the type of software to be tested; determine script data through the preset test process; and determine a target test tool according to the script data.

[0138] In one embodiment, the determination module 20 is also used to determine the unit test classification when the type of the software to be tested is unit test; when the unit test classification is dynamic test, obtain the unit dynamic test process; determine multiple unit test script data according to the unit dynamic test process; and select multiple target testing tools through multiple unit test script data.

[0139] In one embodiment, the determination module 20 is further used to obtain an integration test process when the type of the software to be tested is an integration test; determine the integration test script data through the integration test process; and select a target test tool according to the integration test script data.

[0140] In one embodiment, the determination module 20 is further configured to respond to a custom requirement triggered by a user; determine an adjustment script parameter according to the custom requirement; and generate a target test tool according to the adjustment script parameter.

[0141] In one embodiment, the automated testing device further includes a display module, which is used to obtain automated testing results of the software to be tested; generate a test log based on the automated testing results; generate a target display format based on the test log; and display the automated testing results using the target display format.

[0142] In one embodiment, the response module 10 is further used to analyze the current test requirement; when the current test requirement has an associated test task, obtain the associated task type of the associated test task; and call the target test tool for synchronous testing based on the associated task type.

[0143] The present application provides an automated testing device, which includes: at least one processor; and a memory that is communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the automated testing method in the above-mentioned embodiment one.

[0144] Reference below Figure 8 , which shows a schematic diagram of the structure of the automated test equipment suitable for implementing the embodiment of the present application. The automated test equipment in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 8 The automated testing equipment shown is merely an example and should not impose any limitation on the functions and scope of use of the embodiments of the present application.

[0145] like Figure 8 As shown, the automated test equipment may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the automated test equipment are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the automated test equipment to communicate with other equipment wirelessly or by wire to exchange data. Although the figure shows an automated test equipment with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.

[0146] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0147] The automated testing equipment provided by the present application adopts the automated testing method in the above embodiment, which can solve the technical problems of low testing efficiency and accuracy in the prior art. Compared with the prior art, the beneficial effects of the automated testing equipment provided by the present application are the same as the beneficial effects of the automated testing method provided by the above embodiment, and the other technical features in the automated testing equipment are the same as the features disclosed in the method of the previous embodiment, which will not be described in detail here.

[0148] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0149] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0150] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the automated testing method in the above-mentioned embodiment.

[0151] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0152] The computer-readable storage medium may be included in the automated testing equipment; or may exist independently without being assembled into the automated testing equipment.

[0153] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the automated testing equipment, the automated testing equipment: responds to current testing requirements; determines the type of software to be tested according to the current testing requirements; calls a target testing tool according to the type of software to be tested; and performs automated testing on the software to be tested through the target testing tool.

[0154] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0155] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0156] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0157] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned automated testing method, and can solve the technical problems of low test efficiency and accuracy when testing in the prior art. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the automated testing method provided by the above-mentioned embodiment, and will not be described in detail here.

[0158] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned automated testing method when executed by a processor.

[0159] The computer program product provided by the present application can solve the technical problems of low test efficiency and accuracy when testing in the prior art. Compared with the prior art, the beneficial effects of the computer program product provided by the present application are the same as the beneficial effects of the automated testing method provided in the above embodiment, which will not be described in detail here.

[0160] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. An automated testing method, characterized in that: The automated testing method is applied to an automated testing platform, and the method comprises: Responding to current testing needs; Determine the type of software to be tested according to the current test requirements; Calling a target testing tool according to the type of software to be tested; The target testing tool is used to perform automated testing on the software to be tested.

2. The method according to claim 1, characterized in that The step of calling the target testing tool according to the type of software to be tested comprises: Determine a preset test process according to the type of software to be tested; Determine script data through the preset test process; A target testing tool is determined according to the script data.

3. The method according to claim 1, characterized in that The step of calling the target testing tool according to the type of software to be tested comprises: When the type of the software to be tested is unit testing, determining a unit testing classification; When the unit test is classified as a dynamic test, obtaining a unit dynamic test process; Determine a plurality of unit test script data according to the unit dynamic test process; A plurality of target testing tools are selected according to the plurality of unit test script data.

4. The method according to claim 1, characterized in that The step of calling the target testing tool according to the type of software to be tested comprises: When the type of the software to be tested is an integration test, obtaining an integration test process; Determine the integration test script data through the integration test process; A target testing tool is selected according to the integrated testing script data.

5. The method according to claim 1, characterized in that Before the step of calling the target testing tool according to the type of software to be tested, the method further includes: Respond to user-triggered custom needs; Determine and adjust script parameters according to the custom requirements; A target test tool is generated according to the adjustment script parameters.

6. The method according to claim 1, characterized in that The method further comprises: Obtain automated test results for the software to be tested; Generate a test log according to the automated test results; Generate a target display format according to the test log; The automated test results are displayed in the target display format.

7. The method according to any one of claims 1 to 6, characterized in that After the step of responding to the current test requirement, the method further includes: Analyzing the current test requirements; When the current test requirement has an associated test task, obtaining an associated task type of the associated test task; A target testing tool is called based on the associated task type to perform synchronous testing.

8. An automated testing device, characterized in that: The device comprises: A response module, used to respond to current test requirements; A determination module, used to determine the type of software to be tested according to the current test requirements; A calling module, used to call a target testing tool according to the type of software to be tested; The testing module is used to perform automated testing on the software to be tested through the target testing tool.

9. An automated testing device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the automated testing method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the automated testing method according to any one of claims 1 to 7 are implemented.

Images