Project processing method and device

Abstract

The embodiments of this specification provide a project processing method and device, wherein the project processing method includes: at the end of the current round of target projects, first determine the number of project scenes covered by the current round of target projects; then determine the coverage rate of the current round of project scenes based on the coverage number and the total number of project scenes; then update the weight of the uncovered container project model in the preset container project model library based on the coverage rate of the current round of project scenes; finally, based on the weight of each container project model in the preset container project model library, select the container project model covered by the next round of target projects to process the next round of target projects. In this way, the weight of the uncovered container project model is increased, thereby guiding the coverage of the uncovered container project model when processing the next round of target projects, avoiding a large amount of repeated processing, and realizing the test of the stability of the container project model while improving the efficiency and accuracy of target project processing.

Description

Technical Field

[0001] The embodiments of the present specification relate to the field of computer technology, and in particular to a project processing method. Background Art

[0002] With the continuous development of computer technology, open source container technology has emerged. Container technology originated from the open source community and is widely used in various technical fields of cloud native. Major Internet vendors have successively provided container-based products to the outside world. Based on this, higher requirements are put forward for container technology. However, there is a lack of stability testing for open source container technology. Therefore, an effective solution is urgently needed to solve the above problems. Summary of the invention

[0003] In view of this, the present specification provides a project processing method. One or more embodiments of the present specification also relate to a project processing device, a computing device, a computer-readable storage medium and a computer program to solve the technical defects existing in the prior art.

[0004] According to a first aspect of an embodiment of this specification, a project processing method is provided, including:

[0005] At the end of the current round of target projects, determine the project scenes covered by the current round of target projects and the number of covered project scenes, wherein each of the project scenes is composed of a preset number of container project models;

[0006] Determine the coverage rate of the current round of project scenarios based on the coverage quantity and the total number of project scenarios;

[0007] According to the current round of project scenario coverage, update the weight of the uncovered container project model in the preset container project model library, wherein the weight represents the probability that the container project model is covered in the processing target project;

[0008] Based on the weight of each container project model in the preset container project model library, the container project model covered by the next round of target projects is selected to process the next round of target projects.

[0009] Optionally, determining the number of project scenarios covered by the current round of target projects includes:

[0010] Deduplication processing is performed on the project scenes covered by the current round target project, and the number of the deduplicated project scenes is determined as the coverage number of the project scenes covered by the current round target project.

[0011] Optionally, determining the coverage rate of the current round of project scenarios according to the coverage quantity and the total number of project scenarios includes:

[0012] Divide the coverage number by the total number of project scenarios to obtain the coverage rate of the current round of project scenarios.

[0013] Optionally, updating the weight of the uncovered container project model in the preset container project model library according to the current round of project scenario coverage includes:

[0014] Determine the total coverage rate of project scenarios according to the coverage rate of the current round of project scenarios and the total number of project scenarios;

[0015] Determining, according to the total coverage of the project scenarios, the container project models that are not covered in the preset container project model library;

[0016] Based on the coverage feedback weight updating rule, the weights of the uncovered container project models in the container project model library are updated.

[0017] Optionally, before determining the project scenarios covered by the current round of target projects and the number of project scenarios covered, the method further includes:

[0018] Receive a current round target project processing instruction, wherein the current round target project processing instruction carries a specified number of container project models covered by the current round target project;

[0019] Based on the weight of each container project model in the preset container project model library, the specified number of container project models are selected from the preset container project model library, and the specified number of container project models are run concurrently.

[0020] Optionally, the preset container project model library includes a preset container library and a preset container configuration library, and each of the container project models consists of a container and container configuration data;

[0021] The selecting the specified number of container project models from the preset container project model library based on the weight of each container project model in the preset container project model library comprises:

[0022] Based on the weight of each container project model, container configuration data is selected from the preset container configuration library for each of the specified number of containers in the preset container library to obtain the specified number of container project models.

[0023] Optionally, it also includes:

[0024] In the process of processing the current round target project, if a processing error is reported, determining the error container project model in the current round target project;

[0025] Based on the error feedback weight update rule, the weight of the error reporting container project model in the preset container project model library is updated.

[0026] Optionally, if an error is processed, determining the error container project model in the current round target project includes:

[0027] If an error is reported during processing, use analysis tools to determine the error path;

[0028] On the error reporting path, the error reporting container project model in the current round target project is determined.

[0029] Optionally, it also includes:

[0030] When the current round of target projects ends, if the processing is normal, determine whether there is a historical error container project model in the current round of target projects;

[0031] If so, when the update interval of the weight of the historical error reporting container project model is greater than the preset update duration, the weight of the historical error reporting container project model is restored to a default value in the preset container project model library.

[0032] According to a second aspect of an embodiment of this specification, there is provided a project processing device, including:

[0033] A first determination module is configured to determine, when a current round of target projects ends, project scenarios covered by the current round of target projects and the number of project scenarios covered, wherein each of the project scenarios is composed of a preset number of container project models;

[0034] A second determination module is configured to determine the coverage rate of the current round of project scenarios according to the coverage quantity and the total number of project scenarios;

[0035] An updating module is configured to update the weight of the uncovered container project model in the preset container project model library according to the current round of project scenario coverage, wherein the weight represents the probability of the container project model being covered in the processing target project;

[0036] The processing module is configured to select the container project model covered by the next round of target projects to process the next round of target projects based on the weight of each container project model in the preset container project model library.

[0037] Optionally, the first determining module is further configured to:

[0038] Deduplication processing is performed on the project scenes covered by the current round target project, and the number of the deduplicated project scenes is determined as the coverage number of the project scenes covered by the current round target project.

[0039] Optionally, the second determining module is further configured to:

[0040] Divide the coverage number by the total number of project scenarios to obtain the coverage rate of the current round of project scenarios.

[0041] Optionally, the update module is further configured to:

[0042] Determine the total coverage rate of project scenarios according to the coverage rate of the current round of project scenarios and the total number of project scenarios;

[0043] Determining, according to the total coverage of the project scenarios, the container project models that are not covered in the preset container project model library;

[0044] Based on the coverage feedback weight updating rule, the weights of the uncovered container project models in the container project model library are updated.

[0045] Optionally, the device further comprises an operation module configured to:

[0046] Receive a current round target project processing instruction, wherein the current round target project processing instruction carries a specified number of container project models covered by the current round target project;

[0047] Based on the weight of each container project model in the preset container project model library, the specified number of container project models are selected from the preset container project model library, and the specified number of container project models are run concurrently.

[0048] Optionally, the preset container project model library includes a preset container library and a preset container configuration library, and each of the container project models consists of a container and container configuration data;

[0049] The operation module is further configured to:

[0050] Based on the weight of each container project model, container configuration data is selected from the preset container configuration library for each of the specified number of containers in the preset container library to obtain the specified number of container project models.

[0051] Optionally, the device further includes an error reporting module configured to:

[0052] In the process of processing the current round target project, if a processing error is reported, determining the error container project model in the current round target project;

[0053] Based on the error feedback weight update rule, the weight of the error reporting container project model in the preset container project model library is updated.

[0054] Optionally, the error reporting module is further configured to:

[0055] If an error is reported during processing, use analysis tools to determine the error path;

[0056] On the error reporting path, the error reporting container project model in the current round target project is determined.

[0057] Optionally, the device further includes a recovery module configured to:

[0058] When the current round of target projects ends, if the processing is normal, determine whether there is a historical error container project model in the current round of target projects;

[0059] If so, when the update interval of the weight of the historical error reporting container project model is greater than the preset update duration, the weight of the historical error reporting container project model is restored to a default value in the preset container project model library.

[0060] According to a third aspect of an embodiment of this specification, a computing device is provided, including:

[0061] Memory and processor;

[0062] The memory is used to store computer-processable instructions, and the processor is used to process the computer-processable instructions:

[0063] At the end of the current round of target projects, determine the project scenes covered by the current round of target projects and the number of covered project scenes, wherein each of the project scenes is composed of a preset number of container project models;

[0064] Determine the coverage rate of the current round of project scenarios based on the coverage quantity and the total number of project scenarios;

[0065] According to the current round of project scenario coverage, update the weight of the uncovered container project model in the preset container project model library, wherein the weight represents the probability that the container project model is covered in the processing target project;

[0066] Based on the weight of each container project model in the preset container project model library, the container project model covered by the next round of target projects is selected to process the next round of target projects.

[0067] According to a fourth aspect of the embodiments of this specification, a computer-readable storage medium is provided, which stores computer-executable instructions, and when the instructions are executed by a processor, the steps of any one of the project processing methods are implemented.

[0068] According to a fifth aspect of the embodiments of this specification, a computer program is provided, wherein when the computer program is executed in a computer, the computer is caused to execute the steps of the above-mentioned project processing method.

[0069] An embodiment of the present specification provides a project processing method, which determines the project scenarios covered by the current round of target projects and the coverage quantity of the covered project scenarios at the end of the current round of target projects, wherein each of the project scenarios is composed of a preset number of container project models; then determines the coverage rate of the current round of project scenarios based on the coverage quantity and the total number of project scenarios; then updates the weights of the uncovered container project models in the preset container project model library based on the coverage rate of the current round of project scenarios, wherein the weights represent the probability of the container project models being covered in the project scenarios; and then updates the weights of the container project models in the preset container project model library based on the coverage rate of the current round of project scenarios. The weight of the model is determined, and the container project model covered by the next round of target projects is selected to process the next round of target projects. A measurement scheme for the adequacy of target project processing is provided. At the end of each round of target project scenarios, the coverage rate of the current round of project scenarios is determined, and the uncovered container project models in the preset container project model library are updated according to the coverage rate of the current round of project scenarios. The weight of the uncovered container project models is increased, thereby guiding the coverage of the uncovered container project models when processing the next round of target projects, avoiding a large amount of repeated processing, and realizing the test of the stability of the container project model while improving the efficiency and accuracy of target project processing. BRIEF DESCRIPTION OF THE DRAWINGS

[0070] Figure 1 is a flow chart of a project processing method provided by an embodiment of this specification;

[0071] Figure 2 It is a schematic diagram of a processing process of a project processing method provided by an embodiment of this specification;

[0072] Figure 3 It is a processing diagram of another project processing method provided by an embodiment of this specification;

[0073] Figure 4 It is a process flow chart of a project scenario testing method provided by an embodiment of this specification;

[0074] Figure 5 It is a structural schematic diagram of a project processing device provided by an embodiment of this specification;

[0075] Figure 6 It is a structural block diagram of a computing device provided by an embodiment of this specification. DETAILED DESCRIPTION

[0076] Many specific details are described in the following description to facilitate a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the connotation of this specification, so this specification is not limited to the specific implementation disclosed below.

[0077] The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms of "a", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in one or more embodiments of this specification refers to any or all possible combinations of one or more associated listed items.

[0078] It should be understood that although the terms first, second, etc. may be used to describe various information in one or more embodiments of this specification, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0079] First, the terms involved in one or more embodiments of this specification are explained.

[0080] Container lifecycle: the duration or entire process from container creation to deletion.

[0081] Container project model: refers to the combination of all operations and configuration data within the life cycle of a single container.

[0082] Project scenario: A specified number of container project models run concurrently, simulating the scenario in which multiple container project models run concurrently in a real project, that is, a combination of a specified number of container project models.

[0083] Fuzz testing (fuzz testing, fuzzing): is a test that discovers software security vulnerabilities and detects software robustness. It is achieved by inputting a large number of random and illegal fields into the software and observing whether the tested software is abnormal. It can solve the problems of test inputs that cannot be exhaustively listed and manual testing that is not comprehensive. It generates test input combinations based on feedback mechanism mutations to improve test efficiency. At present, fuzz testing is one of the most effective means in the field of software testing and vulnerability mining.

[0084] Next, the basic concept of the project scenario processing method provided in this manual is briefly described.

[0085] Common fuzz testing increases coverage by randomly generating a large number of test cases, but also introduces a large number of invalid tests, and even the test data is too large, resulting in test explosion. Mainstream fuzz testing frameworks test source code and binary programs. In order to improve the effectiveness of test data and test efficiency, feedback is used, such as coverage guidance and driving fuzz testing. However, the collection of coverage requires compiling and plugging the source code, which is not suitable for testing closed-source software, or implementing specific functions such as statistics, recording, tracking, and monitoring through additional hardware or software tools. And the above methods are all implemented for binary programs.

[0086] The container project model stability test scheme based on rule-based fuzz testing technology limits the tested container library and container configuration data to a valid range by defining rules, ensuring that the subsequent randomly generated simulation project scenarios are as close to the real project scenarios as possible, but invalid tests cannot be avoided. However, it does not have runtime information as feedback, and the newly generated project scenarios are not targeted, so it cannot guarantee that the randomly generated simulation project scenarios are not repeated, and it cannot be determined whether the project scenarios are fully covered and whether the tests are sufficient. The test accuracy and test efficiency are low. Therefore, the project processing method provided in this specification dynamically adjusts the weight of the container project model based on the coverage of the current round of project scenarios, combined with the feedback information such as the coverage of the current round of project scenarios and the error-reporting container project model, and quickly increases the number of covered container project models, thereby improving test accuracy and test efficiency.

[0087] In this specification, a project processing method is provided. This specification also involves a project processing device, a computing device, and a computer-readable storage medium, which are described in detail one by one in the following embodiments.

[0088] Figure 1 A flowchart of a project processing method provided according to an embodiment of the present specification is shown, which specifically includes the following steps.

[0089] Step 102: When the current round of target projects ends, determine the project scenes covered by the current round of target projects and the number of covered project scenes, wherein each of the project scenes is composed of a preset number of container project models.

[0090] Specifically, a project can be a test for a project scenario, or an execution for a project scenario. The target project refers to the project that needs to be processed. The project scenario refers to running multiple container project models to simulate the real project scenario, thereby achieving the effect of testing the project scenario, and also testing the stability of the container project model; processing can also be a test, such as a project scenario test, or an execution, such as executing a certain project scenario; the project scenario covered by the current round of target projects refers to the project scenario composed of the container project models run when processing the current round of target projects; the coverage number refers to the number of project scenarios processed when processing the current round of target projects.

[0091] In actual applications, in order to ensure the comprehensiveness of target project processing and the comprehensiveness of container project model processing, multiple rounds of target projects will be processed. At the end of each round of target project processing, the processing process is the same. In this implementation, the processing of the current round of target projects is taken as an example to illustrate the processing of target projects. At the end of the current round of target projects, all project scenarios used in the current round of target projects are first counted, that is, the project scenarios covered by the current round of target projects are determined, and then the coverage number of the covered project scenarios is determined.

[0092] For example, when the current round of target projects is completed, statistics show that the project scenarios covered by the current round of target projects are: project scenario a1, project scenario a2 and project scenario a3, with a coverage quantity of 3.

[0093] It should be noted that the same project scenario may be used repeatedly in processing a certain round of target projects. At the end of the round of target projects, the determined covered project scenarios will be repeated. At this time, it is necessary to remove the duplications and obtain the coverage quantity to ensure the accuracy of the data, thereby improving the accuracy of processing the target projects. That is, the specific implementation process of determining the coverage quantity of the project scenarios covered by the current round of target projects is as follows:

[0094] Deduplication processing is performed on the project scenes covered by the current round target project, and the number of the deduplicated project scenes is determined as the coverage number of the project scenes covered by the current round target project.

[0095] Specifically, deduplication processing refers to the process of retaining one of the same project scenarios and removing the other same project scenarios.

[0096] In actual applications, after counting the project scenes covered by the current round of target projects, these project scenes are deduplicated, that is, the same project scenes are deleted from these project scenes, and only one of them is retained. Then the number of remaining project scenes is the coverage number. For example, when the current round of target projects ends, it is statistically concluded that the project scenes covered by the current round of target projects are: project scene b1, project scene b1, project scene b2, and project scene b1. After deduplicating the covered project scenes, the remaining project scenes include: project scene b2 and project scene b1, and the coverage number is 2.

[0097] In order to improve processing efficiency, a preset container project model can be pre-built, that is, a preset container project model, so that when processing the target project, the container project model covered by the current round of target projects can be selected from the preset container project model, so that the project scene processing is as close to the real industry project scene as possible, avoiding the random generation of invalid project scenes. That is, before determining the project scenes covered by the current round of project scenes and the number of covered project scenes, it also includes:

[0098] Receive a current round target project processing instruction, wherein the current round target project processing instruction carries a specified number of container project models covered by the current round target project;

[0099] Based on the weight of each container project model in the preset container project model library, the specified number of container project models are selected from the preset container project model library, and the specified number of container project models are run concurrently.

[0100] Specifically, the current round of target project processing instructions refer to the instructions corresponding to starting a new round of target projects; the weight refers to the probability that the container project model will be covered in the processing of the target project. The larger the weight, the greater the probability that the container project model will be covered; the preset container project model library refers to a pre-set collection of all container project models and the running project status of each container project model.

[0101] In actual applications, before starting a new round of target projects, you will receive instructions corresponding to starting processing the target projects in this round, that is, the current round of target project processing instructions. The current round of target project processing instructions carry a specified number, which represents the number of container project models covered by the current round of target projects. Then, according to the weight of each container project model in the preset container project model library, a specified number of container project models are selected from the preset container project model library. There are many selection methods, such as hierarchical selection and random selection. Then run the selected specified number of container project models.

[0102] For example, a current round target project processing instruction is received, and the specified number carried in the current round target project processing instruction is 3, and there are 10 container project models in the preset container project model library, as described in Table 1, which shows the weights of each container project model in the preset container project model library, wherein the weight of container project model C1 is 0.3, the weight of container project model C2 is 0.6, the weight of container project model C3 is 0.3, the weight of container project model C4 is 0.9, the weight of container project model C5 is 0.5, the weight of container project model C6 is 0.3, the weight of container project model C7 is 0.4, the weight of container project model C8 is 0.8, the weight of container project model C9 is 0.4, and the weight of container project model C10 is 0.5. Based on the weights of each container project model, 3 container project models are randomly selected from the preset container project model library, and the proportions are: container project model C4, container project model C8 and container project model C6. Then, the container project model C4, the container project model C8 and the container project model C6 are run concurrently, and the processing of the current round of target projects begins.

[0103] Table 1 Weights of each container project model in the preset container project model library

[0104]

[0105] In order to further improve the processing efficiency, the preset container project model library can also be divided into a preset container library and a preset container configuration library, wherein many containers are set in the preset container library, and the preset container configuration library is configured with multiple container configuration data, and the containers and different container configuration data form different container project models. This further makes the target project closer to the real industry project scene and avoids the random generation of invalid target projects. That is, based on the weight of each container project model in the preset container project model library, the specified number of container project models are selected from the preset container project model library. The specific implementation process can be as follows:

[0106] Based on the weight of each container project model, container configuration data is selected from the preset container configuration library for each of the specified number of containers in the preset container library to obtain the specified number of container project models.

[0107] Specifically, the preset container configuration library refers to a pre-set collection of all container configuration data; the container configuration data is used to configure and start the container, and constitutes a container project model with the container. The container configuration data affects the operation mode of the container project model.

[0108] In actual applications, according to the weight of each container project model, a specified number of containers are selected from the preset container library and the container configuration data corresponding to the specified number of containers are selected from the preset container configuration library to obtain a specified number of container configuration models, so as to facilitate the setting, startup and operation of the container configuration model. Based on the preset container library and the preset container configuration library, a specified number of container configuration models are obtained, and then the hardware resources such as CPU, memory, etc. are simulated to dynamically determine the size of the concurrent thread pool. Each thread randomly selects a container and container configuration data to start the container, simulating a real project scenario where multiple containers are running concurrently. During the operation, the container configuration data changes randomly without interruption, and the thread randomly operates a single or multiple containers. With the end of the container life cycle, the thread randomly creates different types of containers.

[0109] It should be noted that a set of container configuration data can be selected for each container of the specified data, or multiple sets of container configuration data can be selected for a specified number of containers. In addition, a weight can also be set for each set of container configuration data. When selecting the configuration container data, the selection can be made based on the weight of each set of container configuration data. The weight of the container configuration data refers to the probability of the set of container configuration data being selected in the processing target project. The weight of each set of container configuration data is positively correlated with the weight of the container business model.

[0110] Step 104: Determine the coverage rate of the current round of project scenarios based on the coverage quantity and the total number of project scenarios.

[0111] After determining the project scenarios covered by the current round of target projects and the number of project scenarios covered, further, based on the number of coverage and the total number of project scenarios, the coverage rate of the current round of project scenarios is determined.

[0112] Specifically, the current round of project scenario coverage rate refers to the proportion of project scenarios covered when processing the current round of target projects relative to the total number of project scenarios.

[0113] In practical applications, after obtaining the coverage quantity, the total number of project scenarios that can be combined with a preset number of container project models is first obtained, and then the coverage rate of the current round of project scenarios is determined based on the coverage quantity and the total number of project scenarios.

[0114] Preferably, in order to ensure the accuracy of the coverage rate of the current round of project scenarios and thus improve the accuracy of processing the target project, the coverage rate of the current round of project scenarios is determined according to the coverage quantity and the total number of project scenarios as follows:

[0115] Divide the coverage number by the total number of project scenarios to obtain the coverage rate of the current round of project scenarios.

[0116] For example, the number of project scenarios covered by the current round of target projects is 5, and the total number of project scenarios is 50, then the coverage rate of the current round of project scenarios is 5 / 50=0.1.

[0117] It should be noted that in addition to determining the coverage of the current round of project scenarios, you can also determine the coverage of the current round of container project models. The specific process is as follows:

[0118] Obtain the processed number of container project models covered by the current round of target projects and the total number of container project models in the preset container project model library;

[0119] The processing quantity is divided by the total quantity to obtain the model coverage of the container project in the current round.

[0120] In practical applications, when the current round of target projects ends, the container project models covered by the current round of target projects and the number of processed container project models covered can be determined, and the total number of container project models in the preset container project model library can be obtained. The number of processed models is then divided by the total number to obtain the current round of container project model coverage. Then, the weights of the uncovered container project models in the preset container project model library can be updated according to the current round of container project model coverage.

[0121] For example, the number of container project models covered by the current round of target projects is 2, and the total number of container project models in the preset container project model library is 10, then the current round of container project model coverage is 2 / 10=0.2.

[0122] In addition, when obtaining the processing quantity of container project models covered by the current round of target projects, these container project models may be clustered and deduplicated, and then the number of deduplicated container project models may be determined as the processing quantity.

[0123] Step 106: According to the current round of project scenario coverage, the weights of uncovered container project models in the preset container project model library are updated, wherein the weights represent the probability of the container project models being covered in the project scenario processing.

[0124] On the basis of determining the coverage rate of the current round of project scenarios based on the coverage quantity and the total number of project scenarios, further, according to the coverage rate of the current round of project scenarios, the weights of the uncovered container project models in the preset container project model library are updated.

[0125] Specifically, the uncovered container project model refers to the container project model that is not used in processing the target project, and each container project model has a corresponding weight.

[0126] In practical applications, after obtaining the coverage rate of the current round of project scenes, the uncovered container project models in the preset container project model library can be determined based on the coverage rate of the current round of project scenes, and further, the weights of these uncovered container project models can be updated. When updating the weight of the uncovered container project model, the weight of the uncovered container project model can be increased or decreased according to demand. Using the coverage rate of the current round of project scenes as feedback, the covered container project models in the preset container project model library can be determined, and the processing can be more accurate and the processing convergence can be completed faster. Therefore, the feedback of the coverage rate of the current round of project scenes is introduced. Before each processing, the weight of the uncovered container project model is increased, so that it has a greater probability of being selected in the random processing of the next round of target projects. After each processing, the coverage rate of the current round of project scenes is calculated, and the total coverage rate of the project scenes is updated according to the coverage rate of the current round of project scenes, and the uncovered container project models are found at the same time.

[0127] In one or more optional embodiments, in order to accurately locate the uncovered container project models in the preset container project model library and improve the accuracy of updating the weights of the uncovered container project models, the uncovered project models in the preset container project model library are first determined based on the current round of project scene coverage and the total number of project scenes, and then the weights of the uncovered container project models are updated based on the coverage feedback weight update rule. That is, the weights of the uncovered container project models in the preset container project model library are updated according to the current round of project scene coverage, and the specific implementation process can be:

[0128] Determine the total coverage rate of project scenarios according to the coverage rate of the current round of project scenarios and the total number of project scenarios;

[0129] Determining, according to the total coverage of the project scenarios, the container project models that are not covered in the preset container project model library;

[0130] Based on the coverage feedback weight updating rule, the weights of the uncovered container project models in the container project model library are updated.

[0131] Specifically, the total project scenario coverage rate may refer to the sum of the project scenario coverage rates of the current round and before the current round, or it may be the ratio of the current round project scenario coverage rate to the total number of project scenarios; the coverage feedback weight update rule refers to the weight update rule for uncovered container project models based on the feedback coverage rate, i.e., the current round project scenario coverage rate and / or the total project scenario coverage rate.

[0132] In actual applications, after determining the coverage rate of the current round of project scenarios, the total coverage rate of the project scenarios can be updated based on the coverage rate of the current round of project scenarios. According to the updated total coverage rate of the project scenarios, the container project models that are not covered in the preset container project model library can be found. Then, according to the pre-set coverage feedback weight update rules, the weights of the container project models that are not covered in the preset container project model library can be updated.

[0133] In one or more optional embodiments, in order to accurately locate the uncovered container project models in the preset container project model library and improve the accuracy of updating the weights of the uncovered container project models, firstly update the total coverage of the container project models based on the current round of container project model coverage, then determine the uncovered container project models in the preset container project model library based on the updated total coverage of the container project models, and then update the weights of the uncovered container project models according to the coverage feedback weight update rule. That is:

[0134] Determine the total container project model coverage rate according to the current round container project model coverage rate and the historical container project model coverage rate;

[0135] Determining uncovered container project models in the preset container project model library according to the total coverage rate of the container project models;

[0136] Based on the coverage feedback weight update rule, the weights of the uncovered container project models in the preset container project model library are updated.

[0137] Specifically, the historical container project model coverage rate refers to the container project model coverage rate after processing each round of target project scenarios before processing the current round of target projects; the total container project model coverage rate is the ratio of the number of remaining container project models after deduplication of container project models covered by all target projects in the current round and before the current round to the total number of container project models in the preset container project model library; for example, a total of two rounds of target projects are processed, where the container project models covered by the first round of target projects are D1 and D2, and the container project models covered by the second round of target projects are D2 and D3, and the total number of container project models in the preset container project model library is 5, then the total container project model coverage rate is 0.6; the coverage rate feedback weight update rule refers to the weight update rule for uncovered container project models set based on the feedback coverage rate, that is, the current round of container project model coverage rate and / or the total container project model coverage rate.

[0138] In practical applications, the historical container project model coverage can be obtained first, and then the total container project model coverage can be determined in combination with the current round of container project model coverage. Furthermore, according to the total container project model coverage, the uncovered container project models in the preset container project model library are found, and then the weights of the uncovered container project models in the preset container project model library are updated according to the pre-set coverage feedback weight update rules.

[0139] Preferably, in order to avoid a large amount of repeated processing and improve the efficiency and accuracy of project scenario processing, based on the coverage feedback weight update rule, the weight of the uncovered container project model in the preset container project model library is updated as follows: Based on the coverage feedback weight update rule, the weight of the uncovered container project model in the preset container project model library is increased, thereby guiding the coverage of the uncovered container project model when processing the next round of target projects. The coverage feedback weight update rule can increase the weight of the uncovered container project model by a preset value, such as an increase of 0.1, then the uncovered weight is originally 0.5, and after the update, it becomes 0.5+0.1=0.6. In addition, based on the coverage feedback weight update rule, the weight of the uncovered container configuration data in the preset container configuration library, or the weight of the container configuration data corresponding to the uncovered container, can also be updated.

[0140] Step 108: Based on the weight of each container project model in the preset container project model library, select the container project model covered by the next round of target projects to process the next round of target projects.

[0141] After updating the weights of uncovered container project models in the preset container project model library according to the coverage rate of the current round of project scenarios, further, based on the weights of each container project model in the preset container project model library, the container project models covered by the next round of target projects are selected to process the next round of target projects.

[0142] In actual applications, before starting the next round of target projects, it is necessary to select the container project models covered by the next round of target projects from the preset container project model library according to the weights of each container project model in the preset container project model library, and then process the next round of target projects according to the selected container project model. The process of processing the next round of target projects is the same as that of processing the current round of target projects, and you can refer to the content of the current round of target projects mentioned above.

[0143] In addition, according to project processing experience, the place where the problem occurs is generally more likely to hide more problems. Therefore, in addition to updating the weight of the uncovered container project model through the current round of project scenario coverage feedback to guide the processing of the next round of target projects, error feedback can be introduced to update the weight of the error container project model to improve the efficiency of discovering new problems. That is:

[0144] In the process of processing the current round target project, if a processing error is reported, determining the error container project model in the current round target project;

[0145] Based on the error feedback weight update rule, the weight of the error reporting container project model in the preset container project model library is updated.

[0146] Specifically, the error container project model refers to a container project model that has problems in the process of processing the current round of target projects, such as causing the processing of the current round of target projects to stop, making the processing time of the current round of target projects too long, etc.; the error feedback weight update rule refers to the weight update rule for the error container project model based on the error processing situation.

[0147] In actual applications, in the process of processing the current round of target projects, if a processing error occurs, it is necessary to determine the container project model in which the error occurs in the container project model covered by the current round of target projects, that is, the error container project model, and further obtain the error feedback weight update rule, and then update the weight of the error container project model in the preset container project model library based on the error feedback weight update rule.

[0148] In addition, the weight of the container configuration data corresponding to the error reporting container project model in the preset container configuration library may be updated based on the error reporting feedback weight update rule.

[0149] In order to improve the efficiency and accuracy of determining the error container project model, and thus improve the accuracy of processing the target project, when processing an error, you can use an analysis tool to first find the error path, that is, the error path, and then determine the error container project model on the error path. That is, if you process an error, determine the error container project model in the current round of project scenario processing. The specific implementation process can be as follows:

[0150] If an error is reported during processing, use analysis tools to determine the error path;

[0151] On the error reporting path, the error reporting container project model in the current round target project is determined.

[0152] Specifically, the error path refers to the path where the error occurs; the analysis tool is also a processing analysis tool or a test analysis tool, such as monitoring, alarm and log analysis tools configured during the processing process, which are used to timely discover errors, collect and process error paths.

[0153] In actual applications, when processing errors, the current round target project can be analyzed through the analysis tool configured in the process of processing the current round target project to find the error path, and then find the container project model on the error path, or find the container project model that uses the error path to run, and determine these container project models as error container project models.

[0154] For example, in the case of a test error, the error paths found by the test analysis tool are L1 and L2, where the container project models running on the error path L1 are R1, R2 and R3, and the container project models running on the error path L2 are R2 and R4, then the container project models R1, R2, R3 and R4 are all error container project models. For another example, in the case of a test error, the error path found by the test tool is L3, where the container project models R5, R6 and R7 use the error path L3, then the container project models R5, R6 and R7 are all error container project models.

[0155] It should be noted that the analysis tool can also be used to determine the container configuration data corresponding to the error container project model, and further, based on the error feedback weight update rule, update the weight of the container configuration data corresponding to the error container project model in the preset container configuration library. In order to avoid a large amount of repeated processing and improve the processing efficiency and accuracy of the target project, based on the coverage feedback weight update rule, the weight of the uncovered container project model in the preset container project model library is updated as follows: Based on the error feedback weight update rule, increase the weight of the error container project model in the preset container project model library, thereby guiding the coverage of the error container project model when processing the next round of target projects. In addition, based on the error feedback weight update rule, the weight of the container configuration data corresponding to the error container project model in the preset container configuration library can be increased, thereby guiding the coverage of the container configuration data corresponding to the error container project model when processing the next round of target projects.

[0156] The weight of the error container project model needs to be updated. However, for the historical error container project model, if the historical error container project model does not continue to report errors within the specified time, that is, a new problem occurs, the default weight of the historical error container project model needs to be restored, that is:

[0157] When the current round of target projects ends, if the processing is normal, determine whether there is a historical error container project model in the current round of target projects;

[0158] If so, when the update interval of the weight of the historical error reporting container project model is greater than the preset update duration, the weight of the historical error reporting container project model is restored to a default value in the preset container project model library.

[0159] Specifically, the historical error container project model refers to the error container project model before the current round of target project processing, that is, the container project model whose weight is updated; the update interval refers to the interval from the last time the weight was modified to the current time; the preset update duration refers to the pre-set threshold for detecting whether the historical error container project model can be restored to a normal container project model, that is, the validity period of the weight modification; the default value refers to the value corresponding to the weight of the historical error container project model before it is modified. The weight of each container project model has a default value, and the default values ​​of the weights of different container project models can be the same or different.

[0160] In actual applications, when the processing is normal, the historical error container project model is searched from the container project models covered by the current round of target projects. If it is not found, no processing is performed; if the historical error container project model is found, the time interval between the historical error container project model and the last weight update, that is, the update interval, is obtained. The update interval is compared with the preset update duration: if the update interval is less than or equal to the preset update duration, the weight of the historical error container project model is not processed; if the update interval is greater than the preset update duration, the weight of the historical error container project model is restored to the default value. In this way, if the historical error container reports an error again within the preset update duration, the update of the weight of the historical error container project model helps to improve the coverage of the current round of project scenarios or discover new processing problems, then the weight of the historical error container project model will be further improved. If the historical error container project model has no error within the preset update duration, the weight of the historical error container project model is restored to the default value. In this way, the problems of the container project model can be discovered faster and the stability of the container project model can be improved.

[0161] In addition, when the weight of the historical error reporting container item model is restored to the default value, the weight of the container configuration data corresponding to the historical error reporting container item model may also be restored to the default value.

[0162] It should be noted that before processing each round of target projects, the weight of the container will be adjusted from two dimensions. One is the feedback on the coverage of the current round of project scenarios, and the other is the feedback on the error container project model. These two feedback methods are independent of each other, but the modifications to the weight of the container project model will be superimposed.

[0163] See also Figure 2 , Figure 2A schematic diagram of the processing process of a project processing method provided by an embodiment of the present specification is shown, that is, a processing method of a project scenario test based on the feedback of the current round of project scenario coverage: first start a new round of project scenario testing, and at the end of the current round of project scenario testing, determine the current round of project scenario coverage, and then determine the total project scenario coverage based on the current round of project scenario coverage, and find uncovered container project models based on the total project scenario coverage, and update the weights of the uncovered container project models. Then, based on the weights of each container project model, start a new round of project scenario testing, and repeat this process.

[0164] See also Figure 3 , Figure 3 A schematic diagram of the processing process of another project processing method provided by an embodiment of the present specification is shown, namely, a processing method for project scenario testing based on feedback from an error container project model: when processing the current round of project scenario testing, determine whether the test reports an error. If the test reports an error, determine the error path, and then determine the error container project model based on the error path, that is, determine the error container project model in the error path, further update the weight of the error container project model, and start the next round of project scenario testing, that is, execute the step of "processing the current round of project scenario testing"; if the test does not report an error, determine whether there is a historical error container project model. If not, start the next round of project scenario testing, that is, execute the step of "processing the current round of project scenario testing". If so, determine the update interval of the weight of the historical error container project model. Next, compare the update interval with the preset update duration, that is, determine whether the update interval is greater than the preset update duration. If so, restore the weight of the historical error container project model to the default value, and then start the next round of project scenario testing, that is, execute the step of "processing the current round of project scenario testing". If not, start the next round of project scenario testing directly, and execute the step of "processing the current round of project scenario testing".

[0165] One or more embodiments of this specification use fuzz testing to test project scenarios. Based on the rule-based fuzz testing concept, the container project model stability test scheme uses the fuzz testing concept for project scenario stability testing. This specification provides a general target project stability test, thereby realizing the test of the stability of the container project model. It not only inherits the advantage of fuzz testing in effectively mining container project model problems, but also realizes the combination of container and container configuration data through the preset container library and the preset container configuration library, so that the processed target project is close to the real project scenario, avoiding the conventional fuzz testing from generating a large number of invalid tests.

[0166] An embodiment of the present specification provides a project processing method, which determines the project scenarios covered by the current round of target projects and the coverage quantity of the covered project scenarios at the end of the current round of target projects, wherein each of the project scenarios is composed of a preset number of container project models; then determines the coverage rate of the current round of project scenarios based on the coverage quantity and the total number of project scenarios; then updates the weights of the uncovered container project models in the preset container project model library based on the coverage rate of the current round of project scenarios, wherein the weights represent the probability of the container project models being covered in the project scenarios; and then updates the weights of the container project models in the preset container project model library based on the coverage rate of the current round of project scenarios. The weight of the model is determined, and the container project model covered by the next round of target projects is selected to process the next round of target projects. A measurement scheme for the adequacy of target project processing is provided. At the end of each round of target project scenarios, the coverage rate of the current round of project scenarios is determined, and the uncovered container project models in the preset container project model library are updated according to the coverage rate of the current round of project scenarios. The weight of the uncovered container project models is increased, thereby guiding the coverage of the uncovered container project models when processing the next round of target projects, avoiding a large amount of repeated processing, and realizing the test of the stability of the container project model while improving the efficiency and accuracy of target project processing.

[0167] In addition, this solution is also combined with the analysis of the error container project model, and the weight of the error container project model is improved during the operation process, so that the error container project model is covered as much as possible during the next round of target project processing, and the problems of the container project model are further excavated. If the feedback of the error container project model is invalid within the preset update time, the default value of the historical error container project model weight is restored. If the feedback of the error container project model is valid, the target project continues to be guided to go deeper in the specified direction. The weight of the container project model is dynamically adjusted in combination with the feedback information such as the coverage rate of the current round of project scenarios and the error container project model, the number of covered project scenarios is quickly increased, and the accuracy and processing efficiency of the target project processing are further improved, and the stability of the container project model is tested. The method provided in this embodiment can also be applied to other scenarios suitable for selecting container project models for processing through multiple rounds of weight adjustment.

[0168] The following combination Figure 4 , taking the application of the project processing method in project scenario testing as an example, the project processing method is further explained. Figure 4 A process flow chart of a project scenario testing method provided by an embodiment of the present specification is shown, which specifically includes the following steps.

[0169] Step 402: Receive the current round of project scenario test instructions, where the project scenario test instructions carry a specified number of container project models covered by the test.

[0170] Each project scene consists of a preset number of container project models.

[0171] Step 404: Based on the weight of each container project model, container configuration data is selected from the preset container configuration library for each of the specified number of containers in the preset container library to obtain the specified number of container project models.

[0172] Step 406: Run a specified number of container project models concurrently.

[0173] Step 408: During the current round of project scenario testing, if a test error occurs, the error path is determined through the testing tool.

[0174] Step 410: on the error path, determine the error container project model in the current round of project scenario testing.

[0175] Step 412: Based on the error feedback weight update rule, the weight of the error reporting container project model in the preset container project model library is updated.

[0176] Thereafter, step 430 is executed.

[0177] Step 414: When the current round of project scenario testing ends, if the test is normal, determine whether there is a historical error container project model in the current round of project scenario testing.

[0178] Step 416: If yes, when the update interval of the weight of the historical error container project model is greater than the preset update duration, the weight of the historical error container project model is restored to the default value in the preset container project model library.

[0179] Thereafter, step 430 is executed.

[0180] Step 418: When the current round of project scenario testing ends, determine the project scenarios covered by the current round of project scenario testing.

[0181] Step 420: perform deduplication processing on the project scenarios covered by the current round of project scenario testing, and determine the number of the deduplicated project scenarios as the coverage number of the project scenarios covered by the current round of project scenario testing.

[0182] Step 422: Divide the coverage quantity by the total number of project scenes to obtain the current round container coverage rate.

[0183] Step 424: Determine the total coverage of project scenarios based on the current round of project scenario coverage and the total number of project scenarios.

[0184] Step 426: According to the total coverage of the project scenarios, the uncovered container project models in the preset container project model library are determined.

[0185] Step 428: based on the coverage feedback weight update rule, update the weight of the uncovered container project model in the container project model library;

[0186] Step 430: Based on the weight of each container project model in the preset container project model library, select the container project model covered by the next round of project scenario testing to process the next round of project scenario testing.

[0187] An embodiment of the present specification provides a project scenario testing method, which determines the project scenarios covered by the current round of project scenario testing and the number of covered project scenarios at the end of the current round of project scenario testing, wherein each of the project scenarios is composed of a preset number of container project models; then determines the coverage rate of the current round of project scenarios based on the coverage number and the total number of project scenarios; then updates the weights of uncovered container project models in a preset container project model library based on the current round of project scenario coverage, wherein the weights represent the probability of a container project model being covered in the project scenario testing; and then updates the weights of the container project models in the preset container project model library based on the coverage rate of the current round of project scenarios. The weight of the model is determined, and the container project model covered by the next round of project scenario testing is selected to process the next round of project scenario testing. This provides a measurement scheme for the adequacy of project scenario testing. At the end of each round of project scenario testing, the coverage rate of the current round of project scenarios is determined, and according to the coverage rate of the current round of project scenarios, the uncovered container project models in the preset container project model library are updated, thereby increasing the weight of the uncovered container project models, thereby guiding the next round of project scenario testing to cover the uncovered container project models, avoiding a large number of repeated tests, and realizing the testing of the stability of the container project models while improving the efficiency and accuracy of the project scenario testing.

[0188] Corresponding to the above method embodiment, this specification also provides a project scenario testing device embodiment, Figure 5 FIG. 1 shows a schematic diagram of a project processing device provided by an embodiment of the present specification. Figure 5 As shown, the device comprises:

[0189] The first determination module 502 is configured to determine the project scenes covered by the current round of target projects and the number of covered project scenes when the current round of target projects ends, wherein each of the project scenes is composed of a preset number of container project models;

[0190] The second determination module 504 is configured to determine the coverage rate of the current round of project scenarios according to the coverage quantity and the total number of project scenarios;

[0191] An updating module 506 is configured to update the weight of the uncovered container project model in the preset container project model library according to the current round of project scenario coverage, wherein the weight represents the probability of the container project model being covered in the processing target project;

[0192] The processing module 508 is configured to select the container project model covered by the next round of target projects to process the next round of target projects based on the weight of each container project model in the preset container project model library.

[0193] Optionally, the first determining module 502 is further configured to:

[0194] Deduplication processing is performed on the project scenes covered by the current round target project, and the number of the deduplicated project scenes is determined as the coverage number of the project scenes covered by the current round target project.

[0195] Optionally, the second determining module 504 is further configured to:

[0196] Divide the coverage number by the total number of project scenarios to obtain the coverage rate of the current round of project scenarios.

[0197] Optionally, the updating module 506 is further configured to:

[0198] Determine the total coverage rate of project scenarios according to the coverage rate of the current round of project scenarios and the total number of project scenarios;

[0199] Determining, according to the total coverage of the project scenarios, the container project models that are not covered in the preset container project model library;

[0200] Based on the coverage feedback weight updating rule, the weights of the uncovered container project models in the container project model library are updated.

[0201] Optionally, the device further comprises an operation module configured to:

[0202] Receive a current round target project processing instruction, wherein the current round target project processing instruction carries a specified number of container project models covered by the current round target project;

[0203] Based on the weight of each container project model in the preset container project model library, the specified number of container project models are selected from the preset container project model library, and the specified number of container project models are run concurrently.

[0204] Optionally, the operation module is further configured to:

[0205] Based on the weight of each container project model, container configuration data is selected from the preset container configuration library for each of the specified number of containers in the preset container library to obtain the specified number of container project models.

[0206] Optionally, the device further includes an error reporting module configured to:

[0207] In the process of processing the current round target project, if a processing error is reported, determining the error container project model in the current round target project;

[0208] Based on the error feedback weight update rule, the weight of the error reporting container project model in the preset container project model library is updated.

[0209] Optionally, the error reporting module is further configured to:

[0210] If an error is reported during processing, use analysis tools to determine the error path;

[0211] On the error reporting path, the error reporting container project model in the current round target project is determined.

[0212] Optionally, the device further includes a recovery module configured to:

[0213] When the current round of target projects ends, if the processing is normal, determine whether there is a historical error container project model in the current round of target projects;

[0214] If so, when the update interval of the weight of the historical error reporting container project model is greater than the preset update duration, the weight of the historical error reporting container project model is restored to a default value in the preset container project model library.

[0215] An embodiment of the present specification provides a project processing device, which determines the project scenarios covered by the current round of target projects and the coverage quantity of the covered project scenarios when the current round of target projects ends, wherein each of the project scenarios is composed of a preset number of container project models; then determines the coverage rate of the current round of project scenarios based on the coverage quantity and the total number of project scenarios; then updates the weights of the uncovered container project models in the preset container project model library based on the coverage rate of the current round of project scenarios, wherein the weights represent the probability of the container project models being covered in the project scenarios; and then updates the weights of the uncovered container project models in the preset container project model library based on the coverage rate of the current round of project scenarios. The weight of the model is determined, and the container project model covered by the next round of target projects is selected to process the next round of target projects. A measurement scheme for the adequacy of target project processing is provided. At the end of each round of target project scenarios, the coverage rate of the current round of project scenarios is determined, and the uncovered container project models in the preset container project model library are updated according to the coverage rate of the current round of project scenarios. The weight of the uncovered container project models is increased, thereby guiding the coverage of the uncovered container project models when processing the next round of target projects, avoiding a large amount of repeated processing, and realizing the test of the stability of the container project model while improving the efficiency and accuracy of target project processing.

[0216] The above is a schematic scheme of a project processing device of this embodiment. It should be noted that the technical scheme of the project processing device and the technical scheme of the project processing method described above are of the same concept, and the details not described in detail in the technical scheme of the project processing device can be referred to the description of the technical scheme of the project processing method described above.

[0217] Figure 6 The block diagram of a computing device 600 according to an embodiment of the present specification is shown. The components of the computing device 600 include but are not limited to a memory 610 and a processor 620. The processor 620 is connected to the memory 610 via a bus 630, and the database 650 is used to store data.

[0218] The computing device 600 also includes an access device 640 that enables the computing device 600 to communicate via one or more networks 660. Examples of these networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 640 may include one or more of any type of network interface (e.g., a network interface card (NIC)) of wired or wireless, such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a world-wide interoperability for microwave access (Wi-MAX) interface, an Ethernet interface, a universal serial bus (USB) interface, a cellular network interface, a Bluetooth interface, a near field communication (NFC) interface, and the like.

[0219] In one embodiment of the present specification, the above components of the computing device 600 and Figure 6 Other components not shown in the figure may also be connected to each other, for example, via a bus. It should be understood that Figure 6 The computing device structure block diagram shown is only for the purpose of illustration, and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0220] The computing device 600 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smart phone), a wearable computing device (e.g., a smart watch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or PC. The computing device 600 may also be a mobile or stationary server.

[0221] The processor 620 is used to execute the following computer executable instructions, which, when executed by the processor, implement the steps of the above-mentioned project processing method.

[0222] The above is a schematic scheme of a computing device of this embodiment. It should be noted that the technical scheme of the computing device and the technical scheme of the above-mentioned project processing method belong to the same concept, and the details not described in detail in the technical scheme of the computing device can be referred to the description of the technical scheme of the above-mentioned project processing method.

[0223] An embodiment of the present specification also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the steps of the above-mentioned project processing method.

[0224] The above is a schematic scheme of a computer-readable storage medium of this embodiment. It should be noted that the technical scheme of the storage medium and the technical scheme of the above-mentioned project processing method belong to the same concept, and the details not described in detail in the technical scheme of the storage medium can be referred to the description of the technical scheme of the above-mentioned project processing method.

[0225] An embodiment of the present specification also provides a computer program, wherein when the computer program is executed in a computer, the computer is caused to execute the steps of the above-mentioned project processing method.

[0226] The above is a schematic scheme of a computer program of this embodiment. It should be noted that the technical scheme of the computer program and the technical scheme of the above-mentioned project processing method belong to the same concept, and the details not described in detail in the technical scheme of the computer program can be referred to the description of the technical scheme of the above-mentioned project processing method.

[0227] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0228] The computer instructions include computer program codes, which may be in source code form, object code form, executable files or some intermediate forms, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in the computer-readable medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0229] It should be noted that, for the above-mentioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of this specification are not limited by the order of the actions described, because according to the embodiments of this specification, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the embodiments of this specification.

[0230] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0231] The preferred embodiments of this specification disclosed above are only used to help explain this specification. The optional embodiments do not describe all the details in detail, nor do they limit the invention to only the specific implementation methods described. Obviously, many modifications and changes can be made according to the content of the embodiments of this specification. This specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the embodiments of this specification, so that technicians in the relevant technical field can well understand and use this specification. This specification is only limited by the claims and their full scope and equivalents.

Claims

1. A project processing method, comprising: At the end of the current round of target projects, determine the project scenarios covered by the current round of target projects and the number of covered project scenarios, wherein each of the project scenarios is composed of a preset number of container project models, and the container project model is a combination of all operations and configuration data within the life cycle of a single container; Determine the coverage rate of the current round of project scenarios based on the coverage quantity and the total number of project scenarios; According to the coverage rate of the current round of project scenarios, the weights of the uncovered container project models in the preset container project model library are updated, wherein the weights represent the probability of the container project models being covered in the processing target project, wherein the preset container project model library is a pre-set collection of all container project models and the running project status of each container project model; Based on the weight of each container project model in the preset container project model library, the container project model covered by the next round of target projects is selected to process the next round of target projects.

2. According to the method of claim 1, the determining the number of project scenarios covered by the current round of target projects comprises: Deduplication processing is performed on the project scenes covered by the current round target project, and the number of the deduplicated project scenes is determined as the coverage number of the project scenes covered by the current round target project.

3. The method according to claim 1 or 2, wherein determining the coverage rate of the current round of project scenarios based on the coverage quantity and the total number of project scenarios comprises: Divide the coverage number by the total number of project scenarios to obtain the coverage rate of the current round of project scenarios.

4. The method according to claim 1, wherein the weight of the uncovered container project model in the preset container project model library is updated according to the current round of project scenario coverage, comprising: Determine the total coverage rate of project scenarios according to the coverage rate of the current round of project scenarios and the total number of project scenarios; Determining, according to the total coverage of the project scenarios, the container project models that are not covered in the preset container project model library; Based on the coverage feedback weight updating rule, the weights of the uncovered container project models in the container project model library are updated.

5. The method according to claim 1, before determining the project scenes covered by the current round of target projects and the number of covered project scenes, further comprising: Receive a current round target project processing instruction, wherein the current round target project processing instruction carries a specified number of container project models covered by the current round target project; Based on the weight of each container project model in the preset container project model library, the specified number of container project models are selected from the preset container project model library, and the specified number of container project models are run concurrently.

6. The method according to claim 5, wherein the preset container project model library comprises a preset container library and a preset container configuration library, and each of the container project models consists of a container and container configuration data; The selecting the specified number of container project models from the preset container project model library based on the weight of each container project model in the preset container project model library comprises: Based on the weight of each container project model, container configuration data is selected from the preset container configuration library for each of the specified number of containers in the preset container library to obtain the specified number of container project models.

7. The method according to claim 1, further comprising: In the process of processing the current round target project, if a processing error is reported, determining the error container project model in the current round target project; Based on the error feedback weight update rule, the weight of the error reporting container project model in the preset container project model library is updated.

8. The method according to claim 7, wherein if an error is processed, determining the error container project model in the current round target project comprises: If an error is reported during processing, use analysis tools to determine the error path; On the error reporting path, the error reporting container project model in the current round target project is determined.

9. The method according to claim 7, further comprising: When the current round of target projects ends, if the processing is normal, determine whether there is a historical error container project model in the current round of target projects; If so, when the update interval of the weight of the historical error reporting container project model is greater than the preset update duration, the weight of the historical error reporting container project model is restored to a default value in the preset container project model library.

10. A project processing device, comprising: A first determination module is configured to determine, at the end of a current round of target projects, the project scenarios covered by the current round of target projects and the number of project scenarios covered, wherein each of the project scenarios is composed of a preset number of container project models, and the container project model is a combination of all operations and configuration data within a single container life cycle; A second determination module is configured to determine the coverage rate of the current round of project scenarios according to the coverage quantity and the total number of project scenarios; An updating module is configured to update the weights of uncovered container project models in a preset container project model library according to the current round of project scenario coverage, wherein the weights represent the probability of the container project model being covered in the processing target project, wherein the preset container project model library is a pre-set collection of all container project models and the running project status of each container project model; The processing module is configured to select the container project model covered by the next round of target projects to process the next round of target projects based on the weight of each container project model in the preset container project model library.

11. A computing device comprising: Memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the project processing method described in any one of claims 1 to 9 are implemented.

12. A computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the steps of the project processing method described in any one of claims 1 to 9.

13. A computer program product, comprising a computer program / instruction, which, when executed by a processor, implements the steps of the project processing method according to any one of claims 1 to 9.

Images