Application verification method, task execution method, system, device, equipment, medium and product

Abstract

The invention discloses an application verification method, a task execution method, a system, a device, equipment, a medium and a product, and relates to the technical field of application system release. The method comprises the following steps: when an application publishing task is successfully published, receiving an application publishing parameter sent by a task execution server; constructing an application verification task based on the application release parameters and the application release task; sending the application verification task to a task execution server, so that the task execution server executes the application verification task; receiving a verification execution result of the application verification task fed back by the task execution server; and obtaining a verification logic criterion corresponding to the application verification task, and performing logic calculation on the verification execution result based on the verification logic criterion to obtain an application verification result of the application verification task. According to the technical scheme, the application publishing result can be quickly and efficiently verified, the publishing efficiency is improved, stable operation of an application system is guaranteed, and the method can be flexibly reused in various service systems or publishing scenes.

Description

Technical Field

[0001] Embodiments of the present invention relate to the technical field of application system publishing, and in particular to an application verification method, a task execution method, a system, a device, a equipment, a medium and a product. Background Art

[0002] As enterprise-level application deployment architecture becomes more complex and system scale expands, application production releases and daily version updates (collectively referred to as application releases) become more frequent, bringing with them a large amount of complex release result verification work.

[0003] In the prior art, the following two methods are usually used to verify the release results. The first method: After the application release is implemented. Operation and maintenance personnel, testers, or business personnel who use the system on a daily basis log in to the system or deployment environment, manually execute verification use cases, and manually judge whether the release results meet expectations based on the output results. The second method: Technical personnel analyze the impact scope of the application release in advance and write targeted verification scripts, and perform verification after the application release is implemented; this method is usually used as an auxiliary means of manual verification. However, this method of verifying the application release results through manual verification and script checking has the disadvantages of being time-consuming, labor-intensive, and inefficient. Therefore, it is urgent to design a reusable and flexibly configurable automated method to implement release result verification in order to improve release efficiency. Summary of the invention

[0004] The embodiments of the present invention provide a verification method, task execution method, system, device, equipment, medium and product, which can quickly and efficiently verify the results of application publishing, improve publishing efficiency, ensure the stable operation of the application system, and can be flexibly reused in various business systems or publishing scenarios.

[0005] In a first aspect, an embodiment of the present invention provides an application verification method, which is applied to a release verification platform, and the method includes:

[0006] When the application publishing task is successfully published, the application publishing parameters sent by the task execution server are received;

[0007] Building an application verification task based on the application publishing parameters and the application publishing task, wherein the application verification task includes a plurality of verification use cases;

[0008] Sending the application verification task to the task execution server so that the task execution server executes the application verification task;

[0009] Receiving a verification execution result of the application verification task fed back by the task execution server, wherein the verification execution result is obtained by the task execution server executing the sub-verification tasks corresponding to each of the multiple verification use cases;

[0010] A verification logic criterion corresponding to the application verification task for determining whether the application verification task is successfully executed is obtained, and a logic calculation is performed on the verification execution result based on the verification logic criterion to obtain an application verification result of the application verification task.

[0011] In a second aspect, an embodiment of the present invention provides a task execution method, which is applied to a task execution server, and the method includes:

[0012] Receive an application verification task sent by a publishing verification platform, wherein the application verification task includes multiple verification use cases;

[0013] Parsing the application verification task into a plurality of sub-verification tasks based on the plurality of verification cases and a first execution parameter corresponding to each verification case, each sub-verification task corresponding to a verification case;

[0014] Execute the multiple sub-verification tasks to obtain the verification execution result of the application verification task;

[0015] The verification execution result is fed back to the publishing verification platform, so that the publishing verification platform determines the application verification result of the application verification task based on the verification execution result and the verification logic criterion corresponding to the application verification task.

[0016] In a third aspect, an embodiment of the present invention provides an application publishing verification system, the system comprising a publishing verification platform and a task execution server;

[0017] Wherein, the release verification platform is used to execute the application verification method as described in any one of the embodiments of the present invention;

[0018] The task execution server is used to execute the task execution method as described in any one of the embodiments of the present invention.

[0019] In a fourth aspect, an embodiment of the present invention provides an application verification device, which is integrated into a release verification platform, and the device includes:

[0020] A first receiving module, used for receiving application publishing parameters sent by the task execution server when the application publishing task is successfully published;

[0021] A task generation module, used to construct an application verification task based on the application release parameters and the application release task, wherein the application verification task includes a plurality of verification use cases;

[0022] A task sending module, used for sending the application verification task to the task execution server, so that the task execution server executes the application verification task;

[0023] A second receiving module is used to receive the verification execution result of the application verification task fed back by the task execution server, where the verification execution result is obtained by the task execution server executing the sub-verification tasks corresponding to each of the multiple verification use cases;

[0024] The application verification module is used to obtain the verification logic criteria corresponding to the application verification task for determining whether the application verification task is successfully executed, and to perform logical calculations on the verification execution result based on the verification logic criteria to obtain the application verification result of the application verification task.

[0025] In a fifth aspect, an embodiment of the present invention provides a task execution device, which is integrated in a task execution server, and the device includes:

[0026] A task receiving module, used to receive an application verification task sent by a publishing verification platform, wherein the application verification task includes multiple verification use cases;

[0027] A task decomposition module, used for parsing the application verification task into a plurality of sub-verification tasks based on the plurality of verification cases and a first execution parameter corresponding to each verification case, each sub-verification task corresponding to a verification case;

[0028] A verification task execution module, used to execute the multiple sub-verification tasks and obtain the verification execution result of the application verification task;

[0029] The result feedback module is used to feed back the verification execution result to the publishing verification platform, so that the publishing verification platform determines the application verification result of the application verification task based on the verification execution result and the verification logic criterion corresponding to the application verification task.

[0030] In a sixth aspect, the present application also provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and run on the processor. When the processor executes the computer program, it implements an application verification method as described in any one of the embodiments of the present invention, or implements a task execution method as described in any one of the embodiments of the present invention.

[0031] In the seventh aspect, the present application also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer instructions are used to enable a processor to implement an application verification method as described in any one of the embodiments of the present invention, or to implement a task execution method as described in any one of the embodiments of the present invention when executed.

[0032] In an eighth aspect, the present application also provides a computer program product, including a computer program, which, when executed by a processor, implements an application verification method as described in any one of the embodiments of the present invention, or implements a task execution method as described in any one of the embodiments of the present invention.

[0033] In an embodiment of the present invention, when the application publishing task is successfully published, the application publishing parameters sent by the task execution server are received; the application verification task is constructed based on the application publishing parameters and the application publishing task; the application verification task is sent to the task execution server so that the task execution server executes the application verification task; the verification execution result of the application verification task fed back by the task execution server is received, and the verification execution result is logically calculated to obtain the application verification result of the application verification task. Executing this method can bring the following beneficial effects: after the application publishing action is completed, the application verification task can be flexibly configured based on the application publishing parameters and the application publishing task to call the pre-created verification orchestration template, the application verification task is automatically executed by the task execution server, and the obtained verification execution result is logically calculated to obtain the application verification result of the application verification task, so as to realize the automatic verification of the application system to determine whether the publishing result of the application system meets the expected effect. The present application can not only make up for the shortcomings of low execution efficiency, poor controllability and inability to ensure the execution as required of manual verification and script verification, but also can be flexibly reused in various business systems or publishing scenarios to quickly and efficiently verify the results of application publishing, thereby improving the publishing efficiency and ensuring the stable operation of the application system. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0035] Figure 1 A first flow chart of an application verification method provided in an embodiment of the present application;

[0036] Figure 2 A schematic diagram of a verification orchestration template for a certain business system provided in an embodiment of the present application;

[0037] Figure 3 A second flow chart of an application verification method provided in an embodiment of the present application;

[0038] Figure 4 A third flow chart of a task execution method provided in an embodiment of the present application;

[0039] Figure 5 A fourth flow chart of a task execution method provided in an embodiment of the present application;

[0040] Figure 6 A schematic diagram of the overall process of application release verification provided in an embodiment of the present application;

[0041] Figure 7 A schematic diagram of signaling interaction in the application release verification process provided in an embodiment of the present application;

[0042] Figure 8 A system diagram of an application publishing verification system provided in an embodiment of the present application;

[0043] Fig. 9 A first structural diagram of an application verification device provided in an embodiment of the present application;

[0044] Fig.10 A second structural diagram of a task execution device provided in an embodiment of the present application;

[0045] Fig.11 It is a block diagram of an electronic device used to implement an application verification method or a task execution method of an embodiment of the present application. DETAILED DESCRIPTION

[0046] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0047] It should be noted that similar numbers and letters represent similar items in the following figures. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. At the same time, in the description of the present invention, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance. The acquisition, storage, use, processing, etc. of data in the technical solution of this application comply with the relevant provisions of national laws and regulations. It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. The purpose is only to illustrate the feasibility of the implementation of the technical solution of this application, but it does not mean that the applicant has or must use the relevant content of the solution.

[0048] Figure 1The first flow diagram of an application verification method provided in an embodiment of the present application is applicable to automatically verifying an application system when the application system is successfully released or updated to determine whether the release result of the application system meets the expected effect. The application verification method provided in this embodiment can be executed by an application verification device provided in an embodiment of the present application, which can be implemented by software and / or hardware and integrated in an electronic device that executes the method. The method is applied to a release verification platform.

[0049] It should be noted that the release verification platform in this embodiment refers to an integrated platform formed by combining the application release system and the application verification system; the release verification platform uniformly executes the generation and delivery process of application release tasks and application verification tasks. Optionally, the release verification platform may not be used as the execution subject, but the application verification system may execute it separately. Figure 1 The generation and distribution process of the application verification task corresponding to the embodiment is performed separately by the application publishing system Figure 3 The generation and delivery process of application release tasks corresponding to the embodiment. This embodiment uses the release verification platform as the execution subject to explain in detail the generation and delivery process of application release tasks and application verification tasks.

[0050] See also Figure 1 The method of this embodiment includes but is not limited to the following steps:

[0051] S110. When the application publishing task is successfully published, receive application publishing parameters sent by the task execution server.

[0052] The application release task in this embodiment refers to the task of deploying the software package corresponding to the production release or version update of the application system (or application program, applet) to the specified computer. The task execution server refers to the server or device that executes the application release task, and can be an automated execution server. The application release parameters refer to the parameter information in the application system release process, which can at least include the result information, software package information and release path information of this release.

[0053] In this embodiment, the task execution server executes the application publishing task and feeds back the publishing execution result to the publishing verification platform, which receives and parses the publishing execution result. If the publishing verification platform parses the publishing execution result as a successful publishing, the publishing verification platform receives the application publishing parameters sent by the task execution server. Optionally, if the publishing execution result of the application publishing task executed by the task execution server is a successful execution, the publishing execution result including the successful execution and the application publishing parameters are sent to the publishing verification platform, which receives the publishing execution result and the application publishing parameters. The generation process of the application publishing task is the same as in Figure 3The corresponding embodiment explains in detail that the execution process of the application release task will be Figure 5 The details are explained in the corresponding embodiments.

[0054] S120: Construct an application verification task based on the application publishing parameters and the application publishing task.

[0055] The application verification task in this embodiment refers to the task of verifying the functions and performance (including technical indicators and business indicators) of the application system after the application system is successfully released or updated. The application verification task can include multiple verification cases, execution conditions between multiple verification cases, and complete instantiation information such as result judgment logic. The verification case includes the verification method, steps, input, output, etc.

[0056] Among them, the multiple verification use cases may include at least one technical verification use case and at least one business verification use case. Technical verification use cases are used to verify the technical indicators of the application system, such as performance indicators such as the response time, throughput, central processing unit (CPU) utilization rate and memory utilization rate of the software system. Technical verification use cases are generally general use cases and can be reused in different application systems. Business verification use cases are used to verify whether the application system can provide business services normally, whether the business process can flow normally, and whether the execution results meet expectations. Business verification use cases are unique and generally only applicable to specific application systems, and need to be designed and written separately.

[0057] In this embodiment, an application verification task is constructed based on application release parameters and application release tasks, including: determining an application scenario corresponding to the application release task based on the application release parameters; calling a verification case library interface to obtain a verification orchestration template that matches the application scenario; and configuring a first instantiation parameter for the verification case in the verification orchestration template based on the application release parameters to obtain an application verification task.

[0058] In this embodiment, the release verification platform pre-creates verification orchestration templates corresponding to multiple different release scenarios. After the application release task is successfully released, the application scenario corresponding to the application release task is first determined based on the application release parameters, and then the corresponding verification orchestration template is selected according to the application scenario. Finally, the first instantiation parameter is configured for the verification use case in the verification orchestration template according to the application release parameters, and an application verification task for verifying the function of the application system can be obtained. Among them, the verification orchestration template refers to a pre-defined template for executing the verification application release result to see if it meets the expected effect. The advantage of pre-creating the verification orchestration template in this embodiment is that there is no need to re-create the verification orchestration template every time the application is verified. It is only necessary to maintain the verification orchestration template (i.e., automated orchestration) in the system. When the application verification is actually executed, the verification orchestration template is called and the instantiation parameters are passed in for instantiation. By flexibly configuring the instantiation parameters of the verification orchestration template, the reusability of the verification orchestration template is achieved, and the efficiency of application verification can be improved.

[0059] For example, if there is a technical verification use case for verifying the network feedback relationship in the application verification task, the process of configuring the instantiation parameters of the technical verification use case can be: obtaining the release path information from the application release parameters, and then determining the address information of the device under test, and inputting the address information into the corresponding parameters in the technical verification use case for assignment.

[0060] S130: Send the application verification task to the task execution server, so that the task execution server executes the application verification task.

[0061] In the embodiment of the present application, after the publishing verification platform constructs the application verification task, it sends the application verification task to the task execution server, and the task execution server executes the application verification task. The specific process of the task execution server executing the application verification task will be described in Figure 4 The details are explained in the corresponding embodiments.

[0062] Optionally, the application verification task can be triggered manually or automatically by a timer and sent to the task execution server.

[0063] S140: Receive the verification execution result of the application verification task fed back by the task execution server.

[0064] The verification execution result in this embodiment is obtained by the task execution server executing the sub-verification tasks corresponding to each of the multiple verification cases. Each sub-verification task corresponds to a verification case.

[0065] In the embodiment of the present application, after the task execution server completes the application verification task, it automatically summarizes the execution results of each verification case to obtain the verification execution result of the application verification task. Then the verification execution result is fed back to the publishing verification platform. The publishing verification platform receives the verification execution result fed back by the task execution server.

[0066] S150, obtaining a verification logic criterion corresponding to the application verification task for determining whether the application verification task is successfully executed, and performing a logical calculation on the verification execution result based on the verification logic criterion to obtain an application verification result of the application verification task.

[0067] In the embodiment of the present application, while constructing the application verification task, the verification logic criteria corresponding to the application verification task can be set in advance in the verification case library and maintained in the verification case library. The verification logic criteria are logical rules used to determine whether the application verification task is successfully executed. After the publishing verification platform receives the verification execution result, it performs logical calculations on the verification execution result to obtain the application verification result of the application verification task.

[0068] Specifically, the application verification result of the application verification task is obtained by performing logical calculations on the verification execution result based on the verification logic criteria, including: determining from the verification logic criteria a first sub-verification task that has a parallel relationship among multiple sub-verification tasks included in the application verification task; determining the execution result of each sub-verification task in the multiple sub-verification tasks based on the verification execution result; when the execution result corresponding to the first sub-verification task satisfies the and relationship, performing logical calculations on the execution results corresponding to the remaining sub-verification tasks to obtain the application verification result of the application verification task, the remaining sub-verification tasks being the sub-verification tasks in the multiple sub-verification tasks except the first sub-verification task.

[0069] For example, if an application verification task contains 5 sub-verification tasks, namely: sub-verification tasks 1 to 5. Among them, sub-verification task 1 and sub-verification task 2 are in a parallel relationship, that is, only when the execution results of sub-verification task 1 and sub-verification task 2 are consistent with the corresponding standard results, can the subsequent sub-verification tasks 3 to 5, that is, the remaining sub-verification tasks, be executed.

[0070] Furthermore, logical calculations are performed on the execution results corresponding to the remaining sub-verification tasks to obtain the application verification result of the application verification task, including: determining whether the remaining sub-verification tasks have all been executed; if not all of them have been executed, determining that the application verification result is a verification failure; if all of them have been executed, comparing the execution results of each sub-verification task in the remaining sub-verification tasks with the corresponding standard results to obtain a comparison result; if there is at least one sub-verification task whose corresponding comparison result is incorrect, determining that the application verification result is a verification failure; if all of the comparison results corresponding to the sub-verification tasks are correct, determining that the application verification result is a verification success.

[0071] Exemplarily, taking the sub-verification task corresponding to the host access verification case as an example, if the execution result obtained by executing the host access verification case is that the host access is abnormal (i.e., the execution fails), then the application verification task is terminated, that is, the subsequent sub-verification tasks are no longer executed, that is, the remaining sub-verification tasks mentioned above are not fully executed, then the application verification result is determined to be a verification failure. When the execution result of the host access verification case is that the host access is normal, it indicates that the execution conditions of the next sub-verification task are met, and the execution continues in this way. If the last sub-verification task can be successfully executed, then the remaining sub-verification tasks mentioned above are all executed. Then, the execution results of each sub-verification task in the remaining sub-verification tasks are compared with the corresponding standard results to obtain the comparison results. You can take the sub-verification task corresponding to the memory usage verification case as an example, execute the memory usage verification case to get the current memory usage (i.e., the execution result), compare the current memory usage with the upper limit of the memory usage (i.e., the standard result), if the current memory usage exceeds the upper limit of the memory usage, then the comparison result is determined to be wrong, then the application verification result can be determined to be a verification failure; if the current memory usage does not exceed the upper limit of the memory usage, then the comparison result is determined to be correct. Continue to compare in this way until all the sub-verification tasks in the remaining sub-verification tasks are traversed. If the comparison results corresponding to all the sub-verification tasks are correct, then the application verification result is determined to be a verification success.

[0072] Furthermore, when it is determined that the application verification result is a verification failure, it is necessary to analyze and confirm the cause of the verification failure. The specific analysis process includes: determining the first verification case that caused the application verification task to fail from the verification cases included in the application verification task; determining the type of the first verification case, which includes a technical verification case or a business verification case; and determining the cause of the verification failure of the application verification task based on the type and the execution result corresponding to the first verification case.

[0073] Exemplarily, if the type of the first verification case is a technical verification case, and the execution result of the first verification case is execution failure, resulting in the failure to execute all the verification cases included in the application verification task, then it is determined that the cause of the verification failure is a failure in the publishing environment. If the type of the first verification case is a business verification case, and the comparison result of the execution result of the first verification case with the corresponding standard result is an error, then it is determined that the cause of the verification failure is a failure in the publishing medium or process.

[0074] Furthermore, if the problem is caused by the release environment and has nothing to do with the release media or process, then after resolving the release environment problem and successfully executing the application verification task again, the application system release and verification can be considered successful. If the problem is caused by the release media or process, the system release and verification will fail, and the media needs to be updated or the release process needs to be optimized before executing the application release again.

[0075] The technical solution provided in this embodiment is that when the application publishing task is successfully published, the application publishing parameters sent by the task execution server are received; the application verification task is constructed based on the application publishing parameters and the application publishing task; the application verification task is sent to the task execution server so that the task execution server executes the application verification task; the verification execution result of the application verification task fed back by the task execution server is received; the verification logic criteria corresponding to the application verification task are obtained, and the verification execution result is logically calculated based on the verification logic criteria to obtain the application verification result of the application verification task. After the application publishing action is completed, the application verification task can be flexibly configured based on the application publishing parameters and the application publishing task to call the pre-created verification orchestration template, and the application verification task is automatically executed by the task execution server, and the obtained verification execution result is logically calculated to obtain the application verification result of the application verification task, so as to realize the automatic verification of the application system to determine whether the publishing result of the application system meets the expected effect. The application can not only make up for the shortcomings of low efficiency, poor controllability and inability to ensure the execution as required of manual verification and script verification, but also can be flexibly reused in various business systems or publishing scenarios to quickly and efficiently verify the results of application publishing, thereby improving the publishing efficiency and ensuring the stable operation of the application system.

[0076] In an optional embodiment, before executing this embodiment, it is necessary to sort out and create verification cases and verification orchestration templates released by enterprise-level applications, and maintain them in the verification case library for management and subsequent use. Optionally, the verification case library can be provided with expansion capabilities, such as supporting the connection with professional interface automation testing tools such as (postman) to realize automated verification of system interfaces.

[0077] Specifically, the process of creating a verification orchestration template for a release scenario is as follows: determine multiple initial verification use cases corresponding to the release scenario, the multiple initial verification use cases include at least one technical verification use case and at least one business verification use case; for initial verification use cases that can be executed automatically, the initial verification use cases can be associated with an automated execution script (generally a script program); for initial verification use cases that are executed manually, the initial verification use cases can be associated with manual operation notification information (such as text messages, phone calls, etc.), so as to associate an automated execution script or manual operation notification information with each initial verification use case, thereby obtaining multiple target verification use cases; determine the orchestration order of the multiple target verification use cases; determine the execution conditions and result judgment logic of each target verification use case; and orchestrate the multiple target verification use cases based on the orchestration order, execution conditions, and result judgment logic to obtain a verification orchestration template corresponding to the release scenario.

[0078] The properties of the verification orchestration template include multiple verification use cases, execution conditions between multiple verification use cases, and result judgment logic. The verification orchestration template provides a reusable template that is adapted to different application systems or release scenarios. It is not instantiated and cannot actually run. The actual instantiation work is performed in the above step S120. The verification orchestration template includes multiple verification use cases, which can be reused; the execution conditions are used to set the conditions for triggering the next verification use case, which are set according to the actual verification situation and the experience of the executor. For example: verification use case a (such as: checking the CPU utilization of the application system deployment host) must be executed successfully and the CPU utilization must be less than 80% before verification use case b can be executed; the result judgment logic is used to set the verification result of the verification orchestration template, for example: all verification use cases must be executed successfully and the output must meet expectations before the verification result is considered successful.

[0079] like Figure 2 The figure shows a schematic diagram of a verification arrangement template for a business system, which illustrates host access verification, CPU usage verification, memory usage verification, system response time verification, system home page login verification, business process verification, and business amount calculation verification. Among them, host access verification, CPU usage verification, memory usage verification, and system response time verification belong to technical verification use cases, and the rest are business verification use cases. Generally, technical verification use cases are arranged before business verification use cases.

[0080] Each verification case will have an output result, and the output result is used to determine whether the execution condition of the next verification case is met. For example, the execution condition of "host access verification" is "host accessible", that is, the CPU usage verification can only be performed after the host where the application system is located can be accessed normally; if the access is abnormal, the current orchestration is terminated and the application verification result is calculated directly at the last step of the orchestration. The verification indicators of technical verification cases are relatively clear. If the execution result meets the execution condition, it generally means that the corresponding indicator is correct, otherwise the subsequent verification process of the orchestration cannot be continued; however, the situation of business verification cases is more complicated, and meeting the execution condition does not mean that there is no problem with the verification indicator of the business verification case. For example, the execution condition of "business amount calculation verification" is "the calculation process is completed normally", which does not mean that the calculation result is accurate. The purpose of setting the execution condition is only to allow the orchestration to smoothly enter the next verification case. The key to the result of the verification orchestration lies in the final judgment logic of "calculating the application verification result" (i.e. step S140). The judgment logic needs to be configured in advance, and logical calculations are performed based on the output results of all the executed verification cases. For example, if the output result of "Host Access Verification" is "Host Access Abnormal", the entire orchestration only executes one verification case, and the application verification result is "Failure". For another example, if all verification cases of the orchestration have been executed, the judgment logic of "Calculate Application Verification Result" needs to compare and logically calculate the output result of the verification case with a series of values ​​such as the preset CPU usage upper limit, memory usage upper limit, system response time upper limit, home page login return information, business process return information, business return result, business amount calculation value, etc. to obtain the final verification result.

[0081] The following further describes the application verification method provided by the embodiment of the present application. Figure 3 The second flow diagram of an application verification method provided by the embodiment of the present application is as follows: The embodiment of the present application is optimized on the basis of the above embodiments, and the specific optimization is as follows: the present embodiment explains in detail the generation process and the issuance process of the application release task of the application system.

[0082] See also Figure 3 The method of this embodiment includes but is not limited to the following steps:

[0083] S210: Determine a release orchestration template corresponding to a release scenario of the application system.

[0084] The release scenario in this embodiment refers to the scenario in which the application system is deployed, such as information release in public places, digital signage display, conferences and activities, and smart homes. A release orchestration template refers to a series of release operations of a software package application in the system that is predefined for executing production release or version update. The advantage of pre-creating a release orchestration template in this embodiment is that there is no need to re-create the release orchestration template every time an application is released. You only need to maintain the release orchestration template in the system (i.e., automated orchestration). When actually executing the application release, call the release orchestration template and pass in the instantiation parameters for instantiation. By flexibly configuring the instantiation parameters of the release orchestration template, the reusability of the release orchestration template can be achieved, which can improve the efficiency of application release.

[0085] Exemplarily, the release orchestration template for version update includes six release operations: 1. Retrieve the new version of the software package from the database; 2. Transfer the software package to the corresponding server; 3. Control the existing application system to pause; 4. Unzip the old version of the software package; 5. Execute the version update script to overwrite the existing version with the updated content; 6. Start the application system.

[0086] In the embodiment of the present application, the publishing verification platform pre-creates multiple publishing arrangement templates corresponding to different publishing scenarios. After determining the application scenario of the application system, the corresponding publishing arrangement template is selected according to the application scenario.

[0087] S220: Configure a second instantiation parameter for the release orchestration template to obtain an application release task corresponding to the release scenario.

[0088] The second instantiation parameter in this embodiment refers to a parameter for instantiating the release arrangement template, and may include the address of the version package, the decompression path of the version package, and parameters for executing the script.

[0089] In this embodiment, the release verification platform configures the release orchestration template with instantiation parameters such as the address of the version package, the decompression path of the version package, and the parameters of the execution script to obtain the application release task. It can be understood that by configuring different instantiation parameters for the same release orchestration template, multiple corresponding application release tasks can be obtained, that is, each release orchestration template can have multiple instances, and each instance is an application release task.

[0090] In an optional embodiment, after executing step S220, it also includes: the user selects the verification orchestration template corresponding to the application release task, and the release verification platform obtains the identification number of the verification orchestration template in response to the user's operation of selecting the verification orchestration template for the application release task; the identification number of the verification orchestration template is associated with the application release task to obtain associated information. This setting is for: if the application release task fails, then the application verification is not performed; if the application release task fails, the application verification is performed according to the verification orchestration template. Accordingly, in step S120, constructing the application verification task based on the application release parameters and the application release task can be: constructing the application verification task based on the associated information, the application release parameters and the application release task.

[0091] When creating a verification orchestration template, execution conditions and result judgment logic are optional. However, when associating a verification orchestration template when publishing an application task, you must set the execution conditions of each verification case and the final result judgment logic. If not set, it will be executed according to the default value. For example, if the result judgment logic is not set, the verification case is considered to meet the execution conditions as long as there is no execution error; as long as all verification cases are executed, the verification result is successful.

[0092] Specifically, an application verification task is constructed based on associated information, application release parameters and application release tasks, including: determining the identification number of the verification orchestration template corresponding to the application release task based on the associated information; the release verification platform calls the verification case library interface to obtain the verification orchestration template based on the identification number of the verification orchestration template; the release verification platform configures the first instantiation parameter for the verification case in the verification orchestration template based on the application release parameters to obtain the application verification task.

[0093] S230: Send the application publishing task to the task execution server, so that the task execution server executes the application publishing task.

[0094] The task execution server in this embodiment refers to the server or device that executes the application publishing task, and can be an automated task execution server. After the publishing verification platform constructs the application publishing task, it automatically sends the application publishing task to the task execution server, which executes the application publishing task. The detailed process of the task execution server executing the application publishing task will be described in Figure 5 The following explanation is given in the corresponding embodiments.

[0095] S240: Receive the publishing execution result fed back by the task execution server.

[0096] In the embodiment of the present application, after the task execution server completes the application publishing task, it obtains the publishing execution result of the application publishing task, and then feeds back the publishing execution result to the publishing verification platform. The publishing verification platform receives the publishing execution result fed back by the task execution server.

[0097] The technical solution provided in this embodiment determines the release orchestration template corresponding to the release scenario of the application system; configures the second instantiation parameter for the release orchestration template to obtain the application release task corresponding to the release scenario; sends the application release task to the task execution server, so that the task execution server executes the application release task; and receives the release execution result fed back by the task execution server. This application creates corresponding release orchestration templates for different release scenarios in advance. When actually executing the application release, the release orchestration template is called and the instantiation parameters are passed in for instantiation. By flexibly configuring the instantiation parameters of the release orchestration template, the reusability of the release orchestration template is achieved, which can improve the efficiency of application release.

[0098] Figure 4 The third flow chart of a task execution method provided in an embodiment of the present application, this embodiment can be applied to a task execution server to execute an application verification task and obtain a verification execution result of the application verification task. The task execution method provided in this embodiment can be executed by a task execution device provided in an embodiment of the present application, which can be implemented by software and / or hardware and integrated in an electronic device that executes this method, and this method is applied to a task execution server. The task execution server refers to a server or device that executes an application publishing task, and can optionally be an automated task execution server.

[0099] See also Figure 4 The method of this embodiment includes but is not limited to the following steps:

[0100] S310: Receive an application verification task sent by a publishing verification platform, where the application verification task includes multiple verification use cases.

[0101] In the embodiment of the present application, after the publishing and verification platform constructs the application verification task, it automatically sends the application verification task to the task execution server, and the task execution server receives the application verification task sent by the publishing and verification platform.

[0102] S320: Parse the application verification task into multiple sub-verification tasks based on multiple verification use cases and a first execution parameter corresponding to each verification use case, where each sub-verification task corresponds to one verification use case.

[0103] The first execution parameter in this embodiment is a parameter used to configure the execution task for the sub-verification task.

[0104] In this embodiment, the application verification task is decomposed into the same number of sub-verification tasks according to the number of verification cases included in the application verification task, and each sub-verification task corresponds to a verification case; and then the parameters for executing the corresponding sub-verification task are configured according to the first execution parameter, so as to complete the parsing of the application verification task into multiple sub-verification tasks. The execution order of the multiple sub-verification tasks is determined by the arrangement order of the verification cases in the application verification task.

[0105] S330, executing multiple sub-verification tasks to obtain the verification execution result of the application verification task.

[0106] In an optional embodiment, a plug-in that can automatically execute sub-verification tasks is pre-installed on the host where the application system is installed. The task execution server sends multiple sub-verification tasks that can be automatically executed to the host, and the host actually executes the multiple sub-verification tasks.

[0107] In another optional embodiment, for the current sub-verification task among multiple sub-verification tasks, the host installed with the application system is controlled to execute the current sub-verification task and obtain the execution result of the current sub-verification task; based on the execution result of the current sub-verification task and the corresponding result judgment logic, it is determined whether the execution condition of the next sub-verification task is met, and the verification case corresponding to each sub-verification task has an execution condition and a result judgment logic; if it is met, the host is controlled to execute the next sub-verification task; each sub-verification task among the multiple sub-verification tasks is traversed to obtain the execution result of each sub-verification task, and the verification execution result of the application verification task is determined according to the execution result of each sub-verification task. That is, after each sub-verification task is executed, it is determined whether to continue to execute the next sub-verification task according to the execution condition of its corresponding verification case until all executable sub-verification tasks are executed.

[0108] Furthermore, after determining whether the execution conditions of the next sub-verification task are met based on the execution result of the current sub-verification task and the corresponding result judgment logic, it also includes: if the execution conditions of the next sub-verification task are not met, stopping the execution of the application verification task; determining the verification execution result of the application verification task based on the execution result of the current sub-verification task and the execution result of the successfully executed sub-verification task; the arrangement order of the successfully executed sub-verification task is before the current sub-verification task.

[0109] Furthermore, the host computer on which the application system is installed is controlled to execute the current sub-verification task and obtain the execution result of the current sub-verification task, including: if the current sub-verification task is a sub-verification task associated with an automated execution script, the execution agent of the control host is controlled to execute the current sub-verification task and obtain the execution result of the current sub-verification task fed back by the execution agent; if the current sub-verification task is a sub-verification task associated with manual operation notification information, the control host sends operation notification information to the docking personnel corresponding to the current sub-verification task, and receives the docking personnel's input operation on the execution result to obtain the execution result of the current sub-verification task. In actual applications, complex business-type verification cases can often only be executed manually. Such verification cases can be associated with the notification system through the interface, and SMS, phone calls or emails can be sent to notify the docking personnel of the operation. After completion, the operation status and execution results are manually updated, and the host continues to execute subsequent sub-verification tasks.

[0110] S340: Feedback the verification execution result to the publishing verification platform, so that the publishing verification platform determines the application verification result of the application verification task based on the verification execution result and the verification logic rule corresponding to the application verification task.

[0111] In the embodiment of the present application, the task execution server summarizes the execution results of the executed sub-verification tasks to obtain the verification execution result of the application verification task, and feeds back the verification execution result to the publishing verification platform. After receiving the verification execution result, the publishing verification platform performs logical calculation on the verification execution result based on the verification logic criteria corresponding to the application verification task to obtain the application verification result of the application verification task.

[0112] The technical solution provided in this embodiment is to receive an application verification task sent by a publishing verification platform, wherein the application verification task includes multiple verification use cases; parse the application verification task into multiple sub-verification tasks based on multiple verification use cases and the first execution parameter corresponding to each verification use case, wherein each sub-verification task corresponds to a verification use case; execute multiple sub-verification tasks to obtain the verification execution result of the application verification task; and feed back the verification execution result to the publishing verification platform, so that the publishing verification platform determines the application verification result of the application verification task based on the verification execution result and the verification logic criteria corresponding to the application verification task. This application verifies the application system by automatically executing the application verification task, which can not only make up for the shortcomings of low execution efficiency, poor controllability and inability to ensure execution as required of manual verification and script verification, but also can be flexibly reused in various business systems or publishing scenarios to quickly and efficiently verify the results of application publishing, thereby improving publishing efficiency and ensuring the stable operation of the application system.

[0113] The following further describes the task execution method provided by the embodiment of the present application. Figure 5The fourth flow diagram of a task execution method provided in the embodiment of the present application is as follows: The task execution server in the present embodiment provides a detailed explanation of the execution process of the application publishing task.

[0114] See also Figure 5 The method of this embodiment includes but is not limited to the following steps:

[0115] S410: Receive an application publishing task sent by a publishing verification platform.

[0116] The application publishing task includes multiple publishing operation steps, which respectively correspond to the publishing operations included in the publishing orchestration template.

[0117] In an embodiment of the present application, the release verification platform pre-creates a plurality of release orchestration templates corresponding to different release scenarios. After determining the application scenario of the application system, the corresponding release orchestration template is selected according to the application scenario. The release verification platform configures the release orchestration template with instantiation parameters such as the address of the version package, the decompression path of the version package, and the parameters of the execution script to obtain the application release task. The release verification platform sends the application release task to the task execution server, and the task execution server receives the application release task sent by the release verification platform.

[0118] S420: Parse the application publishing task into multiple sub-publishing tasks based on multiple publishing operation steps and a second execution parameter corresponding to each publishing operation step.

[0119] The second execution parameter in this embodiment is a parameter used to configure the execution task for the sub-releasing task.

[0120] In this embodiment, the application release task is decomposed into the same number of sub-release tasks according to the number of release operation steps included in the application release task, and each sub-release task corresponds to a release operation step; and then the parameters for executing the task are configured for the corresponding sub-release task according to the second execution parameter, so as to complete the parsing of the application release task into multiple sub-release tasks. Among them, the execution order of the multiple sub-release tasks is determined by the arrangement order of the release operation steps in the application release task.

[0121] S430: Execute multiple sub-release tasks to obtain the release execution result of the application release task.

[0122] In an optional embodiment, a plug-in that can automatically execute sub-publishing tasks is pre-installed on the host where the application system is installed, and the task execution server sends multiple sub-publishing tasks that can be automatically executed to the host, which actually executes the multiple sub-publishing tasks.

[0123] In another optional embodiment, a first sub-release task to be executed with priority is determined from multiple sub-release tasks; the first sub-release task is executed to obtain a first execution result; when the first execution result is successful, the execution agent of the control host executes the remaining sub-release tasks to obtain the execution results of the remaining sub-release tasks; the release execution result of the application release task is determined according to the first execution result and the execution results of the remaining sub-release tasks; wherein the remaining sub-release tasks are the sub-release tasks other than the first sub-release task among the multiple sub-release tasks. Exemplarily, some sub-release tasks (such as testing the network connectivity with the host or testing the status of the execution agent) are prerequisites for executing other sub-release tasks, which are directly executed by the task execution server, and other sub-release tasks can be issued normally only after the execution is correct.

[0124] Optionally, if a sub-release task fails to execute, the application release task is determined to be a release failure and is suspended, and an operator intervenes or terminates the application release.

[0125] S440: Feedback the release execution result to the release verification platform.

[0126] In the embodiment of the present application, the task execution server summarizes the execution results of the executed sub-release tasks, obtains the release execution results of the application release task, and feeds the release execution results back to the release verification platform. It can be understood that only after the application release task is successfully released, the subsequent application verification work will be triggered.

[0127] The technical solution provided in this embodiment receives an application publishing task sent by a publishing verification platform; parses the application publishing task into multiple sub-publishing tasks based on multiple publishing operation steps and the second execution parameter corresponding to each publishing operation step; executes multiple sub-publishing tasks to obtain the publishing execution result of the application publishing task; and feeds back the publishing execution result to the publishing verification platform. This application parses the application publishing task into multiple sub-publishing tasks through automation, and controls the execution agent of the host to automatically execute multiple sub-publishing tasks. This application can execute application publishing quickly and efficiently, and ensure the stable operation of the application system.

[0128] Figure 6A schematic diagram of the overall process of the application publishing and verification process provided for the embodiment of the present application. The figure illustrates that the publishing and verification platform includes an application publishing system and an application verification system. The application publishing system sends an application publishing task to the task execution server. The task execution server parses the application publishing task into multiple sub-publishing tasks, and sends the multiple sub-publishing tasks to the host for execution. The task execution server feeds back the obtained publishing and execution results to the publishing and verification platform. Then, the application publishing system sends the application publishing parameters to the application verification system; the application verification system calls the verification orchestration template, creates an application verification task, and sends the application verification task to the task execution server. The task execution server parses the application verification task into multiple sub-verification tasks, and sends the multiple sub-verification tasks to the host for execution. The task execution server feeds back the obtained verification execution results to the publishing and verification platform.

[0129] Figure 7 Schematic diagram of signaling interaction of the application release verification process provided by the embodiment of the present application. The signaling interaction process corresponds to Figure 1 , Figure 3 , Figure 4 and Figure 5 Corresponding embodiments. Figure 7 As shown, the application publishing verification process provided in this embodiment includes the following steps:

[0130] S5001. The release verification platform determines a release orchestration template corresponding to a release scenario of the application system.

[0131] S5002: The publishing verification platform configures a second instantiation parameter for the publishing orchestration template to obtain an application publishing task corresponding to the publishing scenario.

[0132] S5003. The publishing verification platform sends the application publishing task to the task execution server.

[0133] S5004. The task execution server receives the application publishing task sent by the publishing verification platform, and parses the application publishing task into multiple sub-publishing tasks.

[0134] S5005. The task execution server executes multiple sub-release tasks and obtains the release execution result of the application release task.

[0135] S5006. The task execution server feeds back the publishing execution result to the publishing verification platform.

[0136] S5007. The publishing verification platform receives the publishing execution result fed back by the task execution server.

[0137] S5008. When the application publishing task is successfully published, the publishing verification platform receives the application publishing parameters sent by the task execution server.

[0138] S5009. The release verification platform builds an application verification task based on the application release parameters and the application release task.

[0139] S5010, the publishing verification platform sends the application verification task to the task execution server.

[0140] S5011. The task execution server receives the application verification task sent by the publishing verification platform, and parses the application verification task into multiple sub-verification tasks.

[0141] S5012. The task execution server executes multiple sub-verification tasks to obtain the verification execution result of the application verification task.

[0142] S5013. The task execution server feeds back the verification execution result to the publishing verification platform.

[0143] S5014: The publishing verification platform receives the verification execution result of the application verification task fed back by the task execution server, and performs logical calculation on the verification execution result to obtain the application verification result of the application verification task.

[0144] The application release verification process is Figure 1 , Figure 3 , Figure 4 and Figure 5 The implementation principles and technical effects of the application release verification process in the corresponding embodiments and various optional implementation methods are similar and will not be repeated here.

[0145] The present application also provides an application publishing verification system. Figure 8 The system diagram of the application publishing verification system provided by the embodiment of the present application is shown. The application publishing verification system 600 includes a publishing verification platform 610 and a task execution server 620. The publishing verification platform 610 is used to execute the application verification method as described in any one of the embodiments of the present application, and the task execution server 620 is used to execute the task execution method as described in any one of the embodiments of the present application. Please refer to the description of the previous embodiment for details, which will not be repeated here.

[0146] Fig. 9 A first structural diagram of an application verification device provided in an embodiment of the present application is shown in FIG. Fig. 9 As shown, the device 700 is integrated into a release verification platform and may include:

[0147] The first receiving module 710 is used to receive application publishing parameters sent by the task execution server when the application publishing task is successfully published;

[0148] A task generation module 720, configured to construct an application verification task based on the application publishing parameters and the application publishing task, wherein the application verification task includes a plurality of verification use cases;

[0149] A task sending module 730, used to send the application verification task to the task execution server, so that the task execution server executes the application verification task;

[0150] The second receiving module 740 is used to receive the verification execution result of the application verification task fed back by the task execution server, where the verification execution result is obtained by the task execution server executing the sub-verification tasks corresponding to each of the multiple verification use cases;

[0151] The application verification module 750 is used to obtain the verification logic criteria corresponding to the application verification task for determining whether the application verification task is successfully executed, and to perform logical calculations on the verification execution result based on the verification logic criteria to obtain the application verification result of the application verification task.

[0152] Furthermore, the above-mentioned task generation module 720 can be specifically used to: determine the application scenario corresponding to the application release task based on the application release parameters; call the verification case library interface to obtain a verification orchestration template matching the application scenario; configure the first instantiation parameter for the verification case in the verification orchestration template based on the application release parameters to obtain an application verification task.

[0153] Furthermore, the above-mentioned application verification module 750 can be specifically used to: determine the first sub-verification task that has a parallel relationship among the multiple sub-verification tasks included in the application verification task from the verification logic criteria; determine the execution result of each sub-verification task in the multiple sub-verification tasks based on the verification execution result; when the execution result corresponding to the first sub-verification task satisfies the and relationship, perform logical calculations on the execution results corresponding to the remaining sub-verification tasks to obtain the application verification result of the application verification task, and the remaining sub-verification tasks are the sub-verification tasks in the multiple sub-verification tasks except the first sub-verification task.

[0154] Furthermore, the above-mentioned application verification module 750 can also be specifically used to: determine whether the remaining sub-verification tasks have been fully executed; if not fully executed, determine that the application verification result is a verification failure; if all executed, compare the execution result of each sub-verification task in the remaining sub-verification tasks with the corresponding standard result to obtain a comparison result; if there is at least one sub-verification task corresponding to an incorrect comparison result, determine that the application verification result is a verification failure; if the comparison results corresponding to all sub-verification tasks are correct, determine that the application verification result is a verification success.

[0155] Furthermore, the above-mentioned application verification module 750 can also be specifically used for: when it is determined that the application verification result is a verification failure, determining the first verification case that caused the verification failure of the application verification task from the verification cases included in the application verification task; determining the type of the first verification case, which includes a technical verification case or a business verification case; and determining the reason for the verification failure of the application verification task based on the type and the execution result corresponding to the first verification case.

[0156] Furthermore, the above-mentioned application verification device may also include: an application publishing module;

[0157] The application publishing module is used to determine the publishing orchestration template corresponding to the publishing scenario of the application system before the application publishing task is successfully published; configure the second instantiation parameter of the publishing orchestration template to obtain the application publishing task corresponding to the publishing scenario; send the application publishing task to the task execution server so that the task execution server executes the application publishing task; and receive the publishing execution result fed back by the task execution server.

[0158] Further, the above-mentioned application publishing module can be specifically used to: after obtaining the application publishing task corresponding to the publishing scenario, in response to the user selecting the verification orchestration template for the application publishing task, obtain the identification number of the verification orchestration template; associate the identification number of the verification orchestration template with the application publishing task to obtain association information;

[0159] Correspondingly, the task generation module 720 may also be used to construct an application verification task based on the associated information, the application publishing parameters and the application publishing task.

[0160] Furthermore, the above-mentioned task generation module 720 can be specifically used to: determine the identification number of the verification orchestration template corresponding to the application release task based on the associated information; call the verification case library interface to obtain the verification orchestration template based on the identification number of the verification orchestration template; configure the first instantiation parameter for the verification case in the verification orchestration template based on the application release parameters to obtain the application verification task.

[0161] In one embodiment, a verification orchestration template is created for a release scenario in the following manner: multiple initial verification use cases corresponding to the release scenario are determined, the multiple initial verification use cases include at least one technical verification use case and at least one business verification use case; each initial verification use case is associated with an automated execution script or manual operation notification information to obtain multiple target verification use cases; an orchestration order of the multiple target verification use cases is determined; an execution condition and result judgment logic for each target verification use case is determined; and the multiple target verification use cases are orchestrated based on the orchestration order, the execution condition and the result judgment logic to obtain a verification orchestration template corresponding to the release scenario.

[0162] The application verification device provided in this embodiment can be applied to the application verification method provided in any of the above embodiments, and has corresponding functions and beneficial effects.

[0163] Fig.10 A second structural diagram of a task execution device provided in an embodiment of the present application is shown in FIG. Fig.10 As shown, the device 800 is integrated in the task execution server and may include:

[0164] The task receiving module 810 is used to receive an application verification task sent by the publishing verification platform, wherein the application verification task includes multiple verification use cases;

[0165] A task decomposition module 820, configured to parse the application verification task into a plurality of sub-verification tasks based on the plurality of verification cases and a first execution parameter corresponding to each verification case, wherein each sub-verification task corresponds to a verification case;

[0166] The verification task execution module 830 is used to execute the multiple sub-verification tasks and obtain the verification execution result of the application verification task;

[0167] The result feedback module 840 is used to feed back the verification execution result to the publishing verification platform, so that the publishing verification platform determines the application verification result of the application verification task based on the verification execution result and the verification logic criterion corresponding to the application verification task.

[0168] Furthermore, the above-mentioned verification task execution module 830 can be specifically used for: for the current sub-verification task among the multiple sub-verification tasks, controlling the host on which the application system is installed to execute the current sub-verification task and obtaining the execution result of the current sub-verification task; determining whether the execution condition of the next sub-verification task is met based on the execution result of the current sub-verification task and the corresponding result judgment logic, and the verification case corresponding to each sub-verification task has an execution condition and a result judgment logic; if met, controlling the host to execute the next sub-verification task; traversing each sub-verification task among the multiple sub-verification tasks, obtaining the execution result of each sub-verification task, and determining the verification execution result of the application verification task according to the execution result of each sub-verification task.

[0169] Furthermore, the above-mentioned verification task execution module 830 can also be specifically used for: if the current sub-verification task is a sub-verification task associated with an automated execution script, the execution agent of the control host executes the current sub-verification task, and obtains the execution result of the current sub-verification task fed back by the execution agent; if the current sub-verification task is a sub-verification task associated with manual operation notification information, the control host sends operation notification information to the docking personnel corresponding to the current sub-verification task, and receives the input operation of the docking personnel on the execution result, so as to obtain the execution result of the current sub-verification task.

[0170] Furthermore, the above-mentioned verification task execution module 830 can also be specifically used for: after determining whether the execution conditions of the next sub-verification task are met based on the execution result of the current sub-verification task and the corresponding result judgment logic, if the execution conditions of the next sub-verification task are not met, stopping the execution of the application verification task; determining the verification execution result of the application verification task based on the execution result of the current sub-verification task and the execution result of the successfully executed sub-verification task; the arrangement order of the successfully executed sub-verification task is before the current sub-verification task.

[0171] Furthermore, the task execution device may further include: a task execution module for issuing tasks;

[0172] The publishing task execution module is used to receive an application publishing task sent by the publishing verification platform before receiving the application verification task sent by the publishing verification platform, wherein the application publishing task includes multiple publishing operation steps; parse the application publishing task into multiple sub-publishing tasks based on the multiple publishing operation steps and the second execution parameter corresponding to each publishing operation step; execute the multiple sub-publishing tasks to obtain the publishing execution result of the application publishing task; and feed back the publishing execution result to the publishing verification platform.

[0173] Furthermore, the above-mentioned publishing task execution module can be specifically used to: determine a first sub-publishing task for priority execution from the multiple sub-publishing tasks; execute the first sub-publishing task to obtain a first execution result; when the first execution result is successful execution, the execution agent of the control host executes the remaining sub-publishing tasks to obtain the execution results of the remaining sub-publishing tasks; determine the publishing execution result of the application publishing task based on the first execution result and the execution results of the remaining sub-publishing tasks; wherein the remaining sub-publishing tasks are sub-publishing tasks among the multiple sub-publishing tasks except the first sub-publishing task.

[0174] The task execution device provided in this embodiment can be applied to the task execution method provided in any of the above embodiments, and has corresponding functions and beneficial effects.

[0175] Fig.11 It is a block diagram of an electronic device for implementing an application verification method or a task execution method of an embodiment of the present application. Electronic device 10 is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. Electronic devices 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 application described and / or required herein.

[0176] like Fig.11 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

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

[0178] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 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, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The processor 11 executes the various methods and processes described above, such as an application verification method or a task execution method.

[0179] In some embodiments, the application verification method or the task execution method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the application verification method or the task execution method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to execute the application verification method or the task execution method in any other appropriate manner (e.g., by means of firmware).

[0180] Various embodiments 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 embodiments may 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.

[0181] The computer programs for implementing the methods of the present application 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 programs are executed by the processor, the functions / operations specified in the flow charts and / or block diagrams are implemented. The computer programs 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.

[0182] In the context of the present application, a computer readable storage medium may be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, device, or equipment. A computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, 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.

[0183] 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).

[0184] The systems and techniques described herein can 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 can 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.

[0185] 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.

[0186] An embodiment of the present application also provides a computer program product, including a computer program, which, when executed by a processor, implements an application verification method as described in any one of the embodiments of the present invention, or implements a task execution method as described in any one of the embodiments of the present invention.

[0187] 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).

[0188] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. An application verification method, characterized in that: Applied to release verification platform, including: When the application publishing task is successfully published, the application publishing parameters sent by the task execution server are received; Building an application verification task based on the application publishing parameters and the application publishing task, wherein the application verification task includes a plurality of verification use cases; Sending the application verification task to the task execution server so that the task execution server executes the application verification task; Receiving a verification execution result of the application verification task fed back by the task execution server, wherein the verification execution result is obtained by the task execution server executing the sub-verification tasks corresponding to each of the multiple verification use cases; A verification logic criterion corresponding to the application verification task for determining whether the application verification task is successfully executed is obtained, and a logic calculation is performed on the verification execution result based on the verification logic criterion to obtain an application verification result of the application verification task.

2. The method according to claim 1, characterized in that The constructing the application verification task based on the application publishing parameter and the application publishing task includes: Determine the application scenario corresponding to the application publishing task based on the application publishing parameters; Call the verification case library interface to obtain a verification orchestration template that matches the application scenario; Based on the application release parameter, a first instantiation parameter is configured for the verification use case in the verification orchestration template to obtain an application verification task.

3. The method according to claim 1, characterized in that The performing logical calculation on the verification execution result based on the verification logic rule to obtain the application verification result of the application verification task includes: Determine, from the verification logic criteria, a first sub-verification task in a parallel relationship among a plurality of sub-verification tasks included in the application verification task; Determining an execution result of each of the plurality of sub-verification tasks based on the verification execution result; When the execution result corresponding to the first sub-verification task satisfies the and relationship, a logical calculation is performed on the execution results corresponding to the remaining sub-verification tasks to obtain the application verification result of the application verification task. The remaining sub-verification tasks are the sub-verification tasks among the multiple sub-verification tasks except the first sub-verification task.

4. The method according to claim 3, characterized in that: The performing logical calculation on the execution results corresponding to the remaining sub-verification tasks to obtain the application verification result of the application verification task includes: Determine whether all remaining sub-verification tasks have been completed; If all the executions are not completed, determining that the application verification result is a verification failure; If all executions are completed, then the execution results of each sub-verification task in the remaining sub-verification tasks are compared with the corresponding standard results to obtain a comparison result; If there is at least one sub-verification task corresponding to a comparison result that is wrong, determining the application verification result as verification failure; If the comparison results corresponding to all sub-verification tasks are correct, the application verification result is determined to be a successful verification.

5. The method according to claim 4, characterized in that When it is determined that the application verification result is a verification failure, the method further includes: Determine, from the verification cases included in the application verification task, a first verification case that causes the verification of the application verification task to fail; Determine a type of the first verification case, where the type includes a technical verification case or a business verification case; The verification failure reason of the application verification task is determined according to the type and the execution result corresponding to the first verification case.

6. The method according to claim 1, characterized in that Before the application publishing task is successfully published, it also includes: Determine the release orchestration template corresponding to the release scenario of the application system; Configuring a second instantiation parameter for the release orchestration template to obtain an application release task corresponding to the release scenario; Sending the application publishing task to the task execution server so that the task execution server executes the application publishing task; Receive the publishing execution result fed back by the task execution server.

7. The method according to claim 6, characterized in that After obtaining the application publishing task corresponding to the publishing scenario, the method further includes: In response to a user selecting a verification orchestration template for the application publishing task, obtaining an identification number of the verification orchestration template; Associating the identification number of the verification orchestration template with the application publishing task to obtain association information; Accordingly, constructing the application verification task based on the application publishing parameter and the application publishing task includes: An application verification task is constructed based on the association information, the application publishing parameters and the application publishing task.

8. The method according to claim 7, characterized in that The constructing the application verification task based on the association information, the application publishing parameter and the application publishing task includes: Determine the identification number of the verification orchestration template corresponding to the application publishing task based on the association information; Calling the verification case library interface to obtain the verification orchestration template based on the identification number of the verification orchestration template; Based on the application release parameter, a first instantiation parameter is configured for the verification use case in the verification orchestration template to obtain an application verification task.

9. The method according to claim 7, characterized in that: Create a validation orchestration template for the release scenario as follows: Determine a plurality of initial verification use cases corresponding to the release scenario, wherein the plurality of initial verification use cases include at least one technical verification use case and at least one business verification use case; Associating each initial verification case with an automated execution script or manual operation notification information to obtain multiple target verification cases; Determining an arrangement order of the multiple target verification use cases; Determine the execution conditions and result judgment logic for each target verification case; The multiple target verification use cases are arranged based on the arrangement order, the execution conditions and the result judgment logic to obtain a verification arrangement template corresponding to the release scenario.

10. A task execution method, characterized in that: Applied to the task execution server, including: Receive an application verification task sent by a publishing verification platform, wherein the application verification task includes multiple verification use cases; Parsing the application verification task into a plurality of sub-verification tasks based on the plurality of verification cases and a first execution parameter corresponding to each verification case, each sub-verification task corresponding to a verification case; Execute the multiple sub-verification tasks to obtain the verification execution result of the application verification task; The verification execution result is fed back to the publishing verification platform, so that the publishing verification platform determines the application verification result of the application verification task based on the verification execution result and the verification logic criterion corresponding to the application verification task.

11. The method according to claim 10, characterized in that The executing the plurality of sub-verification tasks to obtain the verification execution result of the application verification task includes: For a current sub-verification task among the multiple sub-verification tasks, controlling a host on which an application system is installed to execute the current sub-verification task, and obtaining an execution result of the current sub-verification task; Determine whether the execution condition of the next sub-verification task is met based on the execution result of the current sub-verification task and the corresponding result judgment logic, and the verification case corresponding to each sub-verification task has an execution condition and a result judgment logic; If satisfied, control the host to execute the next sub-verification task; Each sub-verification task in the multiple sub-verification tasks is traversed to obtain the execution result of each sub-verification task, and the verification execution result of the application verification task is determined according to the execution result of each sub-verification task.

12. The method according to claim 11, characterized in that The controlling the host computer on which the application system is installed to execute the current sub-verification task and obtaining the execution result of the current sub-verification task includes: If the current sub-verification task is a sub-verification task associated with an automated execution script, the execution agent of the control host executes the current sub-verification task, and obtains the execution result of the current sub-verification task fed back by the execution agent; If the current sub-verification task is a sub-verification task associated with manual operation notification information, the control host sends operation notification information to the docking personnel corresponding to the current sub-verification task, and receives the docking personnel's input operation on the execution result to obtain the execution result of the current sub-verification task.

13. The method according to claim 11, characterized in that After determining whether the execution condition of the next sub-verification task is met based on the execution result of the current sub-verification task and the corresponding result judgment logic, the method further includes: If the execution condition of the next sub-verification task is not met, then the execution of the application verification task is stopped; The verification execution result of the application verification task is determined based on the execution result of the current sub-verification task and the execution result of the successfully executed sub-verification task; the arrangement order of the successfully executed sub-verification task is located before the current sub-verification task.

14. The method according to claim 10, characterized in that Before receiving the application verification task sent by the publishing verification platform, the method further includes: Receiving an application publishing task sent by the publishing verification platform, wherein the application publishing task includes multiple publishing operation steps; Parsing the application publishing task into multiple sub-publishing tasks based on the multiple publishing operation steps and a second execution parameter corresponding to each publishing operation step; Execute the multiple sub-release tasks to obtain the release execution result of the application release task; The release execution result is fed back to the release verification platform.

15. The method according to claim 14, characterized in that The executing the plurality of sub-publishing tasks to obtain a publishing execution result of the application publishing task includes: Determine a first sub-releasing task to be executed with priority from among the multiple sub-releasing tasks; Execute the first sub-releasing task to obtain a first execution result; When the first execution result is successful execution, the execution agent of the control host executes the remaining sub-release tasks to obtain the execution results of the remaining sub-release tasks; Determining a publishing execution result of the application publishing task according to the first execution result and the execution results of the remaining sub-publishing tasks; The remaining sub-publishing tasks are sub-publishing tasks other than the first sub-publishing task among the multiple sub-publishing tasks.

16. An application release verification system, characterized in that: The system includes a publishing verification platform and a task execution server; Wherein, the release verification platform is used to execute the application verification method according to any one of claims 1 to 9; The task execution server is used to execute the task execution method as described in any one of claims 10 to 15.

17. An application verification device, characterized in that: Integrated into the release verification platform, including: A first receiving module, used for receiving application publishing parameters sent by the task execution server when the application publishing task is successfully published; A task generation module, used to construct an application verification task based on the application release parameters and the application release task, wherein the application verification task includes a plurality of verification use cases; A task sending module, used for sending the application verification task to the task execution server, so that the task execution server executes the application verification task; A second receiving module is used to receive the verification execution result of the application verification task fed back by the task execution server, where the verification execution result is obtained by the task execution server executing the sub-verification tasks corresponding to each of the multiple verification use cases; The application verification module is used to obtain the verification logic criteria corresponding to the application verification task for determining whether the application verification task is successfully executed, and to perform logical calculations on the verification execution result based on the verification logic criteria to obtain the application verification result of the application verification task.

18. A task execution device, characterized in that: Integrated in the task execution server, including: A task receiving module, used to receive an application verification task sent by a publishing verification platform, wherein the application verification task includes multiple verification use cases; A task decomposition module, used for parsing the application verification task into a plurality of sub-verification tasks based on the plurality of verification cases and a first execution parameter corresponding to each verification case, each sub-verification task corresponding to a verification case; A verification task execution module, used to execute the multiple sub-verification tasks and obtain the verification execution result of the application verification task; The result feedback module is used to feed back the verification execution result to the publishing verification platform, so that the publishing verification platform determines the application verification result of the application verification task based on the verification execution result and the verification logic criterion corresponding to the application verification task.

19. An electronic device, characterized in that: It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the application verification method as described in any one of claims 1 to 9 is implemented, or the task execution method as described in any one of claims 10 to 15 is implemented.

20. A computer-readable storage medium storing computer instructions, characterized in that: The computer instructions are used to enable a processor to implement the application verification method according to any one of claims 1 to 9, or to implement the task execution method according to any one of claims 10 to 15 when executed.

21. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the computer program implements the application verification method according to any one of claims 1 to 9, or implements the task execution method according to any one of claims 10 to 15.

Images