Delivery test method, device, equipment, medium and product

Abstract

The invention discloses a version issuing test method and device, equipment, a medium and a product, and the method comprises the steps: obtaining a current version file of a to-be-tested component in response to a version issuing action and no test case task exists at present; and based on the test case script of the to-be-tested component, testing the current version file, and determining a test result. The version issuing action is automatically monitored, when the version issuing action is monitored, obtaining of the current version file of the to-be-tested part and the corresponding test case script is automatically triggered, the new version is tested through the test case script, the test result is obtained, and the test report is generated. According to the invention, automation of the whole version issuing test process is realized, the manpower investment is reduced, the test efficiency is improved, and the test cost is saved.

Description

Technical Field

[0001] The present invention relates to the field of vehicle testing technology, and in particular to a release testing method, device, equipment, medium and product. Background Art

[0002] With the development of the automotive industry, parts to be tested account for an increasing proportion in the cockpit field. Release testing of parts to be tested not only helps to ensure product quality and reliability, but also reduces costs, reduces risks, and improves efficiency and market competitiveness.

[0003] The current testing methods in the testing field can be divided into the following steps: manually monitor the release information of different components and manually flash the version; manually send canoe signals to test the basic functions of the version; summarize the test data and count the problems of the new version.

[0004] However, this method of manually monitoring component releases will lead to delays in testing. At the same time, when a component involves multiple controllers, multiple testers need to be arranged to manually test the component, which increases the difficulty of the work and reduces the work efficiency of the tester. Summary of the invention

[0005] The present invention provides a version release test method, device, equipment, medium and product to realize automatic monitoring of version release actions and automatic testing of version release files.

[0006] According to a first aspect of the present invention, there is provided a release testing method, comprising:

[0007] In response to the release action, if there is no test case task currently, obtain the current version file of the component to be tested;

[0008] Based on the test case script of the component to be tested, the current version file is tested and the test result is determined.

[0009] According to a second aspect of the present invention, there is provided a release testing device, comprising:

[0010] A file acquisition module, used to respond to the release action and obtain the current version file of the component to be tested if there is no test case task at present;

[0011] The result determination module is used to test the current version file based on the test case script based on the component to be tested, and determine the test result.

[0012] According to a third aspect of the present invention, there is provided an electronic device, the electronic device comprising:

[0013] at least one processor; and

[0014] a memory communicatively connected to the at least one processor; wherein,

[0015] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the release testing method described in any embodiment of the present invention.

[0016] According to a fourth aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the release testing method described in any embodiment of the present invention when executed.

[0017] According to another aspect of the present invention, an embodiment of the present invention further provides a computer program product, the computer program product includes a computer program, and when the computer program is executed by a processor, the release testing method of any embodiment of the present invention is implemented.

[0018] The technical solution of the embodiment of the present invention obtains the current version file of the component to be tested by responding to the release action and when there is no test case task at present; the current version file is tested based on the test case script of the component to be tested, and the test result is determined. The release action of the associated end is automatically monitored, and the acquisition of the current version file and the corresponding test case script of the component to be tested is automatically triggered when the release action is monitored, and the new version is tested through the test case script to obtain the test result and generate a test report. Different test case scripts and report templates are provided for each component to be tested, which improves the pertinence and test quality of the test, improves the pertinence of the test report, realizes the automation of the entire release test process, reduces manpower input, improves test efficiency, and saves test costs.

[0019] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0021] Figure 1 is a flow chart of a version release testing method provided according to Embodiment 1 of the present invention;

[0022] Figure 2is a flow chart of a version release testing method provided according to Embodiment 2 of the present invention;

[0023] Figure 3 This is an example flow chart of a version release testing method provided according to Embodiment 2 of the present invention;

[0024] Figure 4 is a structural schematic diagram of a version release testing device provided according to Embodiment 3 of the present invention;

[0025] Figure 5 It is a schematic diagram of the structure of an electronic device implementing an embodiment of the present invention. DETAILED DESCRIPTION

[0026] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0027] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0028] Embodiment 1

[0029] Figure 1 A flow chart of a release test method is provided for the first embodiment of the present invention. This embodiment can be applied to the automatic release test of the vehicle components to be tested. The method can be executed by a release test device. The release test device can be implemented in the form of hardware and / or software. The release test device can be configured in an electronic device. Figure 1 As shown, the method includes:

[0030] S110 , in response to the version release action, and if there is no test case task currently, obtain the current version file of the component to be tested.

[0031] In this embodiment, the associated end can be understood as the end that releases the new version, such as the server end of the self-developed software or the server end of the supplier. The release action can be understood as the operation of sending the developed new software version to the test end. The test case task can be understood as the test task being tested. The component to be tested can be understood as the component to be tested corresponding to this update, and the component to be tested can be understood as the component that provides intelligence through the electronic control unit, etc. The current version file can be understood as the file used for this version update.

[0032] Specifically, the processor can establish a connection with the associated end through a front-end interface or the like, and monitor the interface, event or list related to the release action of the associated end. When the associated end is monitored to have a release action, the processor can determine whether there is a test case task in progress, for example, it can be determined through system variables related to the test process. If there is no test case task in progress, the processor can obtain the current version file of the component to be tested based on the release action. For example, the release action includes a download link, wherein the release action may include a current download link for downloading the current version file, the download link is a link for downloading a new version file, or the download link is preset in advance so that the associated end stores the version file in the link, etc. to obtain the current download link, and the version file can be stored in the link in the form of a compressed package, etc.

[0033] S120. Based on the test case script of the component to be tested, test the current version file and determine the test result.

[0034] In this embodiment, the test case script can be understood as an automated test script written in a programming language for the test process of the component to be tested, which is used to automatically execute and verify the functions and performance of the component to be tested. The test result can be understood as a result indicating whether the functions and performance corresponding to the current version file meet expectations.

[0035] Specifically, the processor can first determine a pre-set test case address corresponding to the component to be tested, flash the current version file to the test case address, and provide the functions supporting the vehicle bus by calling a pre-configured bus test tool (such as the Tongxing tool, i.e. TSMaster). The test case script is started through the bus test tool to automatically test the updated component to be tested according to the behavioral steps indicated by the test case script, and automatically obtain the test results after the test is completed.

[0036] The technical solution of the embodiment of the present invention obtains the current version file of the component to be tested by responding to the release action and when there is no test case task at present; the current version file is tested based on the test case script of the component to be tested, and the test result is determined. The release action of the associated end is automatically monitored, and the acquisition of the current version file and the corresponding test case script of the component to be tested is automatically triggered when the release action is monitored, and the new version is tested through the test case script to obtain the test result and generate a test report. Different test case scripts and report templates are provided for each component to be tested, which improves the pertinence and test quality of the test, improves the pertinence of the test report, realizes the automation of the entire release test process, reduces manpower input, improves test efficiency, and saves test costs.

[0037] It is understandable that when multiple release actions are obtained within a certain interval, it may not be possible to perform tests on each test task at the same time, and the tasks that have not been tested can be stored in the form of setting a test queue.

[0038] As a first optional embodiment of the first embodiment, based on the above embodiment, it also includes:

[0039] If there are currently unfinished test case tasks, the current version file corresponding to the release action or the download link of the current version file is stored in the test queue.

[0040] In this embodiment, the test queue can be understood as a queue for storing untested version files, for example, a queue that can directly store version files or download links, wherein the download link can be understood as a link for downloading the current version file.

[0041] Specifically, if there are currently unexecuted test case tasks, the processor can use the download link provided by the release action or directly store the version file in the test queue, where the test queue can be sorted according to the order in which the release actions are listened to, or it can be sorted according to the pre-set priority of the components to be tested, which can be set according to actual needs.

[0042] The first optional embodiment of the first embodiment of the present invention avoids the test conflict caused by executing multiple test tasks simultaneously during the test process through such an arrangement, thereby ensuring the stability of the test.

[0043] As a second optional embodiment of the first embodiment, based on the above embodiment, it also includes:

[0044] When the test case task is executed, the current version file is retrieved from the test queue and the test steps for the current version file are returned.

[0045] Specifically, the processor continuously monitors the test process. When the processor monitors that the test case task is executed, the processor can re-obtain the first or more version files to be tested from the test queue as the current version file, and return the test steps for the current version file based on the test case script of the component to be tested.

[0046] The second optional embodiment of the first embodiment monitors the test process through such a setting, and automatically obtains the version files to be tested in the test queue in sequence for testing, thereby improving the test efficiency and the reliability of the test.

[0047] As a third optional embodiment of the first embodiment, after testing the current version file based on the test case script of the component to be tested and determining the test result, the method further includes:

[0048] Generate a test report based on the test results and the report template of the component to be tested.

[0049] In this embodiment, the report template can be understood as a report template pre-set with the report results to be displayed by the component to be tested, for example, the hardware equipment, software environment and test results used for each component to be tested can be set according to the needs. The test report can be understood as a report reflecting the basis and results of this test.

[0050] Specifically, the processor can search for the report template corresponding to the component to be tested in the associated storage medium (such as memory and cloud storage medium, etc.), and the processor can fill in the current version information, associated end information and test results of this release action into the corresponding position in the report template to generate a test report corresponding to this test.

[0051] The third optional embodiment of the first embodiment of the present invention, through such a setting, generates a test report through the report template corresponding to the component to be tested, thereby improving the pertinence of the test report, recording the test process and results of the component to be tested in more detail, and facilitating the viewing and analysis of the test.

[0052] As a fourth optional embodiment of the first embodiment, after generating a test report according to the test results and the report template of the component to be tested, the method further includes:

[0053] The report name of the test report is modified according to the identity information of the associated end that sends the release task and the version information of the current version file.

[0054] In this embodiment, the identity information can be understood as information used to characterize the identity of the associated end, for example, it can include the name and ID of the associated end, etc. The version information can be understood as the version number of this update, etc. The report name can be understood as the name of the test report, which is used to concisely and clearly reflect the main content and purpose of the test report.

[0055] Specifically, the processor can extract keywords for naming the report from the identity information of the associated end and the version information of the current version file, and can also combine the test results in the test report as the report name. For example, the report name can be: Supplier A-Component Bn version-Test successful.

[0056] Furthermore, the processor can store the named test report in a designated file address, awaiting subsequent data recovery and result analysis, wherein the designated file address can set different addresses for different components to be tested to distinguish the components to be tested, making it easier to find previous update records.

[0057] The fourth optional embodiment of the first embodiment, through such a setting, names the test report in a set manner, which provides support for subsequent data recovery and result analysis.

[0058] Embodiment 2

[0059] Figure 2 This is a flow chart of a version release testing method provided in the second embodiment of the present invention. This embodiment is a further refinement of the above embodiment. Figure 2 As shown, the method includes:

[0060] S201 . In response to a version release action and if no test case task currently exists, obtain the current version file of the component to be tested.

[0061] Further, based on the above embodiment, the method for determining the version release action includes:

[0062] Whether the associated end that sends the release action sends a release event, whether the front-end interface of the associated end has a release action, or whether the list length of the version list of the associated end changes.

[0063] In this embodiment, the release event can be understood as an action event triggered by the release. The front-end interface can be understood as an interface communication method for exchanging data with the associated end. The version list can be understood as a list of compressed packages, files or names under all versions of the component to be tested, and the list can be divided according to each component to be tested. The list length can be understood as the length of characters or quantities recorded in the list.

[0064] Specifically, when there is a version update on the associated end, a release event will be automatically sent out. The processor can monitor whether the associated end sends a release event to determine whether the associated end has a release action. For example, Supplier A can send a release event to notify the outside that there is a version update. The associated end can also directly send a compressed package of this version update to the processor through the front-end interface, or directly send information related to this release to the processor. For example, if the component to be tested is independently developed, the R&D server can directly send release-related information to the processor through the front-end port. The processor can also set a time threshold, access the release website at fixed intervals to obtain a version list, and detect whether the length of the list has changed to determine whether a new version has been added.

[0065] The technical solution of the embodiment of the present invention meets the requirements of monitoring the release actions of different components to be tested by setting multiple ways of monitoring the release actions.

[0066] S202: Flash the current version file to the test case address of the component to be tested.

[0067] In this embodiment, the test case address can be understood as the address of the relevant program used to store the simulation component to be tested on the test end. The last version file can be understood as the version file of the component to be tested that was last updated.

[0068] Specifically, in order to update the version of the component to be tested, a test case project that simulates the component to be tested can be pre-set, and there will be a corresponding test case address. The processor can flash the current version file to the test case address to overwrite the previous version file, thereby realizing the update of the component to be tested based on the current version file.

[0069] S203: Run the test case script based on the test case address to execute the test case task corresponding to the test case script to test the current version file.

[0070] Specifically, the processor can run the test case script based on the test case address through the test tool, so as to execute the test case task by executing the test steps corresponding to the test case script through the test tool, so as to implement the test of the current version file. For example, the test tool simulates the vehicle environment, and according to the control signals and simulation steps recorded in the test case script, simulates the operation of the electronic control unit corresponding to the component to be tested on other vehicle components, so as to implement the test of the update corresponding to the current version file.

[0071] As a first optional embodiment of the second embodiment, after running the test case script based on the test case address to execute the test case task corresponding to the test case script to test the current version file, it also includes:

[0072] Monitor test-related variables and determine whether the test case task is completed based on the test-related variables.

[0073] In this embodiment, the test-related variable can be understood as a variable used to indicate whether the test case task is completed.

[0074] Specifically, after executing the test case script, the test-related variables can be monitored in real time, and the values ​​of the test-related variables can be used to determine whether the test case task is completed.

[0075] The first optional embodiment of the second embodiment monitors the completion progress of the test case task in real time through such a setting, so as to automatically trigger the start of the next test case task when it is completed, thereby improving the test efficiency.

[0076] The technical solution of the embodiment of the present invention, when monitoring the existence of a release action and the current absence of a test case task, automatically obtains the corresponding current version file through the current download link of the release action of the component to be tested, decompresses the current version file, obtains the current version file, and automatically writes it to the test case address corresponding to the component to be tested, overwrites the previous version file, and provides support for subsequent testing of the current version file. By automatically running the test case script, the test case task corresponding to the test case script is automatically executed, and the manually executed canoe signal sending test method is converted into an executable test case script written in code, which reduces the manpower input of the test, saves the test cost, realizes the automatic testing of the current version file, and improves the test efficiency. Different test case scripts are provided for each component to be tested, which improves the test quality and provides support for the subsequent rapid discovery of problems in software iteration updates.

[0077] For the sake of illustrative purposes, a specific example is used to illustrate the present invention. Figure 3 This is an example flow chart of a release testing method provided in Embodiment 2 of the present invention, such as Figure 3 As shown, the steps may include:

[0078] S301, start the test tool (for example, it can be Tongxing tool), and monitor the release action of the associated end (for example, it can be monitored through the jfog front-end interface);

[0079] S302, monitoring that there is a publishing action;

[0080] S303, determine whether there is a test case task currently in progress; if yes, jump to step S304, if no, jump to step S305;

[0081] S304, storing the download link in the test queue, and waiting for the completion of the current test case task;

[0082] S305, obtaining the current version file through the download link, and decompressing the current version file to obtain the current version file;

[0083] S306, writing the current version file to the test case address of the component to be tested to overwrite the previous version file;

[0084] S307, running the test case script based on the test case address to execute the test case task corresponding to the test case script to test the current version file;

[0085] S308, monitor whether the current test case task is completed; if yes, jump to step S309, if no, jump to step S308;

[0086] S309, generating a test report according to the test results and the report template of the component to be tested;

[0087] S310, determine whether the download queue is empty; if so, jump to step S302, if not, jump to step S305.

[0088] Embodiment 3

[0089] Figure 4 This is a schematic diagram of the structure of a version testing device provided in Embodiment 3 of the present invention. Figure 4 As shown, the device comprises:

[0090] The file acquisition module 41 is used to obtain the current version file of the component to be tested in response to the release action and if there is no test case task at present;

[0091] The result determination module 42 is used to test the current version file based on the test case script of the component to be tested and obtain the test result.

[0092] The technical solution of the embodiment of the present invention obtains the current version file of the component to be tested by responding to the release action and when there is no test case task at present; the current version file is tested based on the test case script of the component to be tested, and the test result is determined. The release action of the associated end is automatically monitored, and the acquisition of the current version file and the corresponding test case script of the component to be tested is automatically triggered when the release action is monitored, and the new version is tested through the test case script to obtain the test result and generate a test report. Different test case scripts and report templates are provided for each component to be tested, which improves the pertinence and test quality of the test, improves the pertinence of the test report, realizes the automation of the entire release test process, reduces manpower input, improves test efficiency, and saves test costs.

[0093] Furthermore, the method for determining the version release action includes:

[0094] Whether the associated end that sends the release action sends a release event, whether the front-end interface of the associated end has a release action, or whether the list length of the version list of the associated end changes.

[0095] Furthermore, the result determination module 42 is specifically used for:

[0096] Flash the current version file to the test case address of the component to be tested;

[0097] Based on the test case address, the test case script is run to execute the test case task corresponding to the test case script to test the current version file.

[0098] Optionally, the device further comprises:

[0099] A process determination module is used to monitor test-related variables after running the test case script based on the test case address to execute the test case task corresponding to the test case script to test the current version file, and determine whether the test case task is completed based on the test-related variables.

[0100] Optionally, the device further comprises:

[0101] The link storage module is used to store the current version file corresponding to the release action or the download link of the current version file in the test queue if there is currently an unexecuted test case task.

[0102] Optionally, the device further comprises:

[0103] The link acquisition module is used to reacquire the current version file from the test queue and return the test steps for the current version file when the test case task is executed.

[0104] Optionally, the device further comprises:

[0105] The report generation module is used to generate a test report according to the test result and the report template of the component to be tested after testing the current version file based on the test case script of the component to be tested and determining the test result.

[0106] Optionally, the device further comprises:

[0107] The report determination module is used to modify the report name of the test report according to the identity information of the associated end that sends the release task and the version information of the current version file after generating the test report according to the test results and the report template of the component to be tested.

[0108] The release test device provided in the embodiment of the present invention can execute the release test method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0109] Embodiment 4

[0110] Figure 5 A schematic diagram of the structure of an electronic device 40 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0111] like Figure 5 As shown, the electronic device 50 includes at least one processor 51, and a memory connected to the at least one processor 51 in communication, such as a read-only memory (ROM) 52, a random access memory (RAM) 53, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 51 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 52 or the computer program loaded from the storage unit 58 to the random access memory (RAM) 53. In the RAM 53, various programs and data required for the operation of the electronic device 50 can also be stored. The processor 51, the ROM 52, and the RAM 53 are connected to each other via a bus 54. An input / output (I / O) interface 55 is also connected to the bus 54.

[0112] A number of components in the electronic device 50 are connected to the I / O interface 55, including: an input unit 56, such as a keyboard, a mouse, etc.; an output unit 57, such as various types of displays, speakers, etc.; a storage unit 58, such as a disk, an optical disk, etc.; and a communication unit 59, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 59 allows the electronic device 50 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0113] The processor 51 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 51 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 51 executes the various methods and processes described above, such as a release test method.

[0114] In some embodiments, the release test method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 58. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 50 via the ROM 52 and / or the communication unit 59. When the computer program is loaded into the RAM 53 and executed by the processor 51, one or more steps of the release test method described above may be performed. Alternatively, in other embodiments, the processor 51 may be configured to perform the release test method in any other appropriate manner (e.g., by means of firmware).

[0115] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0116] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0117] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, 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 foregoing.

[0118] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0119] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0120] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0121] In one embodiment, the present invention further includes a computer program product, the computer program product includes a computer program, and when the computer program is executed by a processor, the release testing method of any embodiment of the present invention is implemented.

[0122] In the process of implementation, the computer program product can be written in one or more programming languages ​​or a combination thereof to perform the computer program code of the present invention, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" language or similar programming languages. The program code can 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 can 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 can be connected to an external computer (for example, using an Internet service provider to connect through the Internet).

[0123] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0124] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A version testing method, characterized in that: include: In response to the release action, if there is no test case task currently, obtain the current version file of the component to be tested; Based on the test case script of the component to be tested, the current version file is tested and the test result is determined.

2. The method according to claim 1, characterized in that The method for determining the release action includes: Whether the associated end that sends the release action sends a release event, whether the front-end interface of the associated end has a release action, or whether the list length of the version list of the associated end changes.

3. The method according to claim 1, characterized in that The testing of the current version file based on the test case script of the component to be tested includes: Flash the current version file to the test case address of the component to be tested; Based on the test case address, the test case script is run to execute the test case task corresponding to the test case script to test the current version file.

4. The method according to claim 3, characterized in that After running the test case script based on the test case address to execute the test case task corresponding to the test case script to test the current version file, the method further includes: Monitor the test-related variables and determine whether the test case task is completed based on the test-related variables.

5. The method according to claim 1, characterized in that Also includes: If there is currently an uncompleted test case task, the current version file corresponding to the release action or the download link of the current version file is stored in the test queue.

6. The method according to claim 5, characterized in that Also includes: When the test case task is executed, the current version file is retrieved from the test queue, and the test steps for the current version file are returned.

7. The method according to claim 1, characterized in that After the test case script based on the component to be tested tests the current version file and determines the test result, the method further includes: A test report is generated according to the test results and the report template of the component to be tested.

8. The method according to claim 7, characterized in that After generating a test report according to the test result and the report template of the component to be tested, the method further includes: The report name of the test report is modified according to the identity information of the associated end that sends the release task and the version information of the current version file.

9. A version testing device, characterized in that: include: A file acquisition module, used to respond to the release action and obtain the current version file of the component to be tested if there is no test case task at present; The result determination module is used to test the current version file based on the test case script based on the component to be tested, and determine the test result.

10. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can perform the release testing method according to any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the release testing method according to any one of claims 1 to 8 when executed.

12. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the computer program implements the release testing method according to any one of claims 1 to 8.

Images