Version upgrading method and device, storage medium and electronic equipment

Abstract

The invention discloses a version upgrading method and device, a storage medium and electronic equipment, and relates to the technical field of data processing, and the method comprises the steps: firstly obtaining a version upgrading demand of a system version; then, according to the number of use cases of the version upgrading demand, the version capacity occupied by the version upgrading demand is evaluated; evaluating the demand capacity accommodated by the system version according to the number of the use cases and the upgrading resources corresponding to the system version; and finally, based on the demand capacity and the version capacity, determining a target upgrading demand of the system version, and upgrading the system version according to the target upgrading demand. According to the method and the device, when the version upgrading demand is obtained, the target upgrading demand is determined according to the version capacity and the demand capacity which can be accommodated by the system version, so that the risk that the version capacity occupied by the target upgrading demand exceeds the demand capacity is reduced, the problem of demand excess is reduced, and the influence of the demand excess on the version upgrading progress is reduced.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a version upgrade method, device, storage medium and electronic device. Background Art

[0002] System version upgrade means updating the existing system (software, hardware or a combination of both) from one system version to a new version to obtain new features, improved performance, better user experience or fix known problems.

[0003] At present, related technologies usually carry out system development according to the corresponding iteration cycle, package the developed new version into an installation package or deployment package, and then upgrade the version.

[0004] However, the related technology determines the final included upgrade requirements during the new version packaging phase, which easily leads to a mismatch between the upgrade requirements and the upgrade resources of the current version, resulting in excessive requirements, which in turn affects the progress of the version upgrade. Summary of the invention

[0005] In view of this, the present application provides a version upgrade method, device, storage medium and electronic device, the main purpose of which is to improve the current related technology in which the final upgrade requirements are determined during the new version packaging stage, which is prone to excessive requirements and thus affects the progress of the version upgrade.

[0006] In a first aspect, the present application provides a version upgrade method, comprising:

[0007] Get the system version upgrade requirements;

[0008] According to the number of test cases of the version upgrade requirement, the total time consumption of the test cases corresponding to the version upgrade requirement is evaluated;

[0009] According to the number of use cases and the upgrade resources corresponding to the system version, evaluate the required capacity accommodated by the system version;

[0010] Based on the required capacity and the version capacity, a target upgrade requirement of the system version is determined, and the system version is upgraded according to the target upgrade requirement, and the version capacity occupied by the target upgrade requirement is smaller than the required capacity.

[0011] In a second aspect, the present application provides a data processing device, comprising:

[0012] An acquisition module is configured to acquire a version upgrade requirement of a system version;

[0013] An evaluation module is configured to evaluate the total time consumption of the test cases corresponding to the version upgrade requirement according to the number of test cases of the version upgrade requirement;

[0014] An evaluation module configured to evaluate the demand capacity accommodated by the system version according to the number of use cases and the upgrade resources corresponding to the system version;

[0015] The upgrade module is configured to determine the target upgrade requirement of the system version based on the required capacity and the version capacity, and upgrade the system version according to the target upgrade requirement, and the version capacity occupied by the target upgrade requirement is less than the required capacity.

[0016] In a third aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the version upgrade method described in the first aspect.

[0017] In a fourth aspect, the present application provides an electronic device, comprising a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, wherein the processor implements the version upgrade method described in the first aspect when executing the computer program.

[0018] By means of the above technical scheme, the present application provides a version upgrade method, device, storage medium and electronic device, which first obtain the version upgrade requirements of the system version; then evaluate the total time consumption of the test cases corresponding to the version upgrade requirements according to the number of use cases of the version upgrade requirements; then evaluate the demand capacity results accommodated by the system version based on the number of use cases and the upgrade resources corresponding to the system version; finally, based on the demand capacity and the version capacity, determine the target upgrade requirements of the system version, and upgrade the system version according to the target upgrade requirements, wherein the version capacity occupied by the target upgrade requirements is less than the demand capacity. Compared with the current existing technology, the present application can first obtain the version upgrade requirements of the system version, and then evaluate the version capacity occupied by the version upgrade requirements and the demand capacity that the system version can accommodate based on the number of use cases of the version upgrade requirements and the upgrade resources of the system version, and determine the target upgrade requirements based on the version capacity occupied by the version upgrade requirements and the demand capacity, so that when obtaining the version upgrade requirements, the target upgrade requirements are determined based on the version capacity occupied by the version upgrade requirements and the demand capacity that the system version can accommodate, wherein the version capacity occupied by the target upgrade requirements is less than the demand capacity, thereby reducing the risk that the version capacity occupied by the target upgrade requirements exceeds the demand capacity, thereby reducing the problem of excess demand and reducing the impact of excess demand on the progress of the version upgrade.

[0019] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0022] Figure 1 A schematic diagram of a process flow of a version upgrade method provided in an embodiment of the present application is shown;

[0023] Figure 2 A schematic diagram of a process flow of a version upgrade method provided in an embodiment of the present application is shown;

[0024] Figure 3 A schematic diagram of an example process provided by an embodiment of the present application is shown;

[0025] Figure 4 A schematic diagram of an example process provided by an embodiment of the present application is shown;

[0026] Figure 5 A schematic diagram of an example process provided by an embodiment of the present application is shown;

[0027] Figure 6 A schematic diagram of the structure of a version upgrade device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0028] The embodiments of the present application will be described in more detail below with reference to the accompanying drawings. It should be noted that the embodiments and features in the embodiments of the present application can be combined with each other without conflict.

[0029] In order to improve the current related technology in the new version packaging stage to determine the final included upgrade requirements, it is easy to have excessive requirements, thereby affecting the technical problem of version upgrade progress. This embodiment provides a version upgrade method, such as Figure 1 As shown, the method includes:

[0030] Step 101: Obtain the system version upgrade requirement.

[0031] The version upgrade requirements may include but are not limited to regular requirements within the system version iteration cycle and emergency requirements caused by emergencies. In specific application scenarios, regular requirements for system versions within the current iteration cycle can be collected through market research, customer feedback, risk assessment, etc. Regular upgrades for regular requirements can effectively improve system performance.

[0032] Step 102: Evaluate the version capacity occupied by the version upgrade requirements according to the number of use cases of the version upgrade requirements.

[0033] In specific application scenarios, the corresponding number of use cases can be designed first according to the version upgrade requirements to match the various operating scenarios corresponding to the version upgrade requirements. The number of use cases for the version upgrade requirements can be determined based on the detailed description of each version upgrade requirement through steps such as requirement list, use case modeling, use case quantity assessment, and adjustment of requirement scope. The number of use cases reflects the complexity and workload of the requirements. Then, the version capacity occupied by the version upgrade requirements can be assessed based on the number of use cases for the version upgrade requirements to obtain the version capacity required for the upgrade version before the upgrade, thereby reducing the problem of the version capacity occupied by the version upgrade requirements not matching the upgrade resources of the current version. Among them, the version capacity can be the capacity required for system upgrades according to the version upgrade requirements.

[0034] Step 103: Evaluate the required capacity of the system version based on the number of use cases and the upgrade resources corresponding to the system version.

[0035] Among them, upgrade resources may include but are not limited to human resources (such as weekly upgrade personnel, testers, developers, etc.), tool resources (such as automated testing tools, performance testing tools, version control tools, etc.), technical resources (such as test environment, database, network equipment, hardware resources, etc.), time resources (such as upgrade cycle, upgrade period, version backtracking time, etc.), etc.; among them, the demand capacity may include the demand capacity that can be accommodated by the current system version (maximum demand capacity), etc.

[0036] For this embodiment, before the system is upgraded, a capacity assessment can be performed based on the number of use cases and current upgrade resources to assist operation and maintenance managers in determining upgrade requirements, thereby reducing the problem of version capacity occupied by version upgrade requirements exceeding the required capacity.

[0037] Step 104: Based on the required capacity and the version capacity, determine the target upgrade requirement of the system version, and upgrade the system version according to the target upgrade requirement.

[0038] Among them, the version capacity occupied by the target upgrade requirement is smaller than the required capacity.

[0039] In specific application scenarios, by comparing the demand capacity and version capacity, the target upgrade demand that does not exceed the demand capacity can be determined, thereby reducing the problem of excess demand and the impact of excess demand on the version upgrade progress, ensuring the smooth upgrade of the version, and improving system performance and user experience.

[0040] Compared with the current existing technology, this embodiment can first obtain the version upgrade requirements of the system version, and then evaluate the version capacity occupied by the version upgrade requirements and the demand capacity that the system version can accommodate based on the number of use cases of the version upgrade requirements and the upgrade resources of the system version, and determine the target upgrade requirements based on the version capacity occupied by the version upgrade requirements and the demand capacity, so that when obtaining the version upgrade requirements, the target upgrade requirements are determined based on the version capacity occupied by the version upgrade requirements and the demand capacity that the system version can accommodate, wherein the version capacity occupied by the target upgrade requirements is less than the demand capacity, thereby reducing the risk that the version capacity occupied by the target upgrade requirements exceeds the demand capacity, thereby reducing the problem of excess demand and reducing the impact of excess demand on the progress of the version upgrade.

[0041] In order to further illustrate the specific implementation process of the method of this embodiment, this embodiment provides the following Figure 2 The specific method shown includes:

[0042] Step 201: Obtain the system version upgrade requirement.

[0043] For example, when emergencies such as changes in the external environment, user feedback, security vulnerabilities, etc. occur, temporarily increased emergency needs can be determined in response to the emergencies, the version capacity of the emergency needs can be evaluated, and an upgrade plan can be determined to timely improve the system performance and user experience, and upgrades can be performed based on emergency needs without affecting the normal development of system business.

[0044] Step 202: Evaluate the version capacity occupied by the version upgrade requirements according to the number of use cases of the version upgrade requirements.

[0045] Among them, the version capacity can be used to determine the number of requirements for this system version upgrade, and ensure the maximum demand release based on the version quality. For example, the number of use cases corresponding to each requirement in the version upgrade requirement can be counted, the total number of use cases of the version upgrade requirement can be determined, the upgrade version capacity value occupied by each version upgrade requirement can be calculated, and then the version capacity occupied by the version upgrade requirement can be evaluated based on the total number of use cases.

[0046] Step 203: Evaluate the required capacity of the system version based on the number of use cases and the upgrade resources corresponding to the system version.

[0047] For example, you can first evaluate the upgrade resources of the current system version to obtain the number of upgraders within the current version upgrade cycle (such as the number of upgraders this week), available working time and other resource investment situations, and then evaluate the demand capacity accommodated by the system version based on the number of use cases and the number of upgraders this week, to obtain the maximum demand range that the upgrade team can handle under the current time and personnel resource constraints, and the maximum demand that the system version can accommodate.

[0048] Step 204: Based on the required capacity and the version capacity, determine the target upgrade requirement of the system version, and upgrade the system version according to the target upgrade requirement.

[0049] Exemplarily, the required capacity and version capacity can be compared. If the version capacity exceeds the required capacity, the demand is exceeded and the required range needs to be adjusted or upgrade resources need to be increased. If the version capacity does not exceed the required capacity, the demand is not exceeded and all version upgrade requirements can be completed.

[0050] As a possible implementation method, the number of demands that the current system version can accommodate can be calculated based on the demand capacity that the current system version can accommodate and the version capacity occupied by the demand use cases, and then the number of demands for version upgrades can be compared with the number of demands that can be accommodated. If the number of demands for version upgrades exceeds the number of demands that can be accommodated, the demand is exceeded and it is necessary to adjust the demand range or increase upgrade resources; if the number of demands for version upgrades does not exceed the number of demands that can be accommodated, the demand is not exceeded and all version upgrade requirements can be completed.

[0051] Step 205: using a preset evaluation model, evaluate the upgrade time for upgrading the system version according to the target upgrade requirement.

[0052] Optionally, step 205 may specifically include: obtaining the upgrade status during the system version upgrade process; using a preset evaluation model to evaluate the verification time corresponding to the upgrade status; and determining the longest verification time among the verification times as the upgrade time corresponding to the target upgrade requirement.

[0053] Among them, the upgrade status can be determined according to the progress of the upgrade, for example, ideal status, non-ideal status that can be resolved, non-ideal status that requires rollback, etc., according to the quantitative (such as preset time coefficient, preset ratio) and variable (such as the number of upgraders, version capacity, number of use cases) in the upgrade process, and the total upgrade time corresponding to the occurrence of relevant situations is estimated. Correspondingly, the ideal status can be used to indicate that all verifications in the upgrade process have passed, without any rollback or modification, the non-ideal status that can be resolved can be used to indicate that problems occurred during the verification process and were resolved, and the non-ideal status that requires rollback can be used to indicate that problems occurred during the verification process but could not be resolved, involving any rollback operation.

[0054] Exemplarily, a preset evaluation model can be used to evaluate the verification times corresponding to an ideal state, a solvable non-ideal state, and a non-ideal state that requires rollback, and obtain the longest verification time among the verification times for different states as the upgrade time corresponding to the target upgrade requirements, to assist system managers (such as project managers and operation and maintenance managers) in determining whether there is a risk of timeout for this upgrade to avoid affecting business operations.

[0055] Optionally, using a preset evaluation model to evaluate the verification time corresponding to the upgrade status may specifically include: based on version capacity and upgrade resources, using a preset calculation formula corresponding to the upgrade status in the preset evaluation model to calculate the verification time corresponding to the upgrade status.

[0056] Exemplarily, the preset calculation formula is as follows:

[0057] Total upgrade time = implementation of updated environment (90 minutes) + test and verify upgraded content (version capacity * 2 minutes / number of upgraders that week) + development and modification of upgraded content issues (version capacity * 2 minutes * 20%) + implementation of updated production environment (version capacity * 2 minutes * 10%) + test and verify generation process (300 minutes / number of upgraders that week) + development and sorting of rollback code packages (30 minutes) + implementation of updated production environment (30 minutes) + test and verify production process (60 minutes);

[0058] In the formula, the total upgrade duration can be used to represent the verification time corresponding to the upgrade status. Based on the version capacity and upgrade resources, the duration corresponding to the upgrade stages such as implementing the update environment, testing and verifying the upgrade content, developing and modifying upgrade content issues, implementing the update of the production environment, testing and verifying the production process, developing and organizing the rollback code package, implementing the update of the production environment, and testing and verifying the production process can be calculated, and finally the verification time can be added up.

[0059] Optionally, based on version capacity and upgrade resources, a preset calculation formula corresponding to the upgrade status in a preset evaluation model is used to calculate the verification time corresponding to the upgrade status, which may specifically include: obtaining the upgrade stage corresponding to the upgrade status; determining the stage time corresponding to the upgrade stage based on version capacity and upgrade resources; and generating the verification time corresponding to the upgrade status based on the stage time.

[0060] For example, Figure 3 As shown, the verification time calculation process under ideal conditions is shown, which may specifically include upgrade stages such as implementing an updated environment, testing and verifying the upgraded content, and testing and verifying the generation process. The stage times corresponding to the upgrade stages such as implementing an updated environment, testing and verifying the upgraded content, and testing and verifying the generation process are calculated separately, and the verification time under ideal conditions is obtained by adding them up.

[0061] For example, Figure 4As shown, the verification time calculation process under the non-ideal solvable state is shown, which may specifically include upgrading stages such as implementing the update environment, testing and verifying the upgrade content, solving verification problems, and testing and verifying the generation process. Among them, the time for solving the verification problem can be obtained by adding the development solution time and the implementation update time.

[0062] For example, Figure 5 As shown, the verification time calculation process under the non-ideal state that requires rollback is shown, which may specifically include implementing the update environment, testing and verifying the upgrade content, verifying problem resolution, testing and verifying the generation process, rollback environment and other upgrade stages. Among them, the time for verifying problem resolution can be obtained by adding the development resolution time and the update implementation time. The time for the rollback environment may include the time for developing and organizing the rollback code package, the time for implementing the update environment, the time for verifying the environment, etc. A detailed rollback plan can be formulated to ensure that the old version can be quickly restored in the event of a problem to reduce the impact on users.

[0063] Optionally, based on the version capacity and upgrade resources, a preset calculation formula is used to determine the stage time corresponding to the upgrade stage, which may specifically include: obtaining the number of testers and the version capacity in the upgrade resources, and calculating the stage time corresponding to the upgrade stage using a preset calculation formula; and / or obtaining the preset production time corresponding to the upgrade stage as the stage time corresponding to the upgrade stage.

[0064] As a possible implementation method, the stage time corresponding to the upgrade stage can be calculated using a preset calculation formula based on variables in the version upgrade process. The calculation process is as follows:

[0065] The calculation formula for the phase time of test verification upgrade can be expressed as:

[0066] Test verification upgrade time = version capacity * 2 minutes / number of upgraders that week;

[0067] The calculation formula for the stage time of developing, modifying and upgrading the content can be expressed as:

[0068] Development solution time = version capacity * 2 minutes * 20%;

[0069] The calculation formula for the stage time of implementing the update of the production environment can be expressed as:

[0070] Update implementation time = version capacity * 2 minutes * 10%;

[0071] The calculation formula for the stage time of the test verification production process can be expressed as:

[0072] The duration of testing and verifying the production process = 300 minutes / number of upgraders in that week;

[0073] As a possible implementation method, a preset production time can be set for each upgrade stage as the stage time of the corresponding stage. For example, the preset production time for implementing the update environment can be set to 90 minutes; the preset production time for developing and organizing the rollback code package can be set to 30 minutes; the preset production time for implementing the update production environment can be set to 30 minutes; and the preset production time for testing and verifying the production process can be set to 60 minutes.

[0074] Optionally, the method of this embodiment may further include: obtaining the unit execution time of the test cases of the system version; and evaluating the total time consumption of the test cases corresponding to the version upgrade requirements based on the unit execution time and the number of cases.

[0075] Exemplarily, based on batch sampling analysis of system version test cases (such as daily single use cases), time consumption is measured and calculated for unit use cases to obtain unit execution time of system version test cases. Based on the number of use cases (total number) required for version upgrade and the unit execution time, the total time consumption of the test cases for this version is estimated, and a preset evaluation model (such as an upgraded version capacity model) is established.

[0076] Specifically, the upgrade duration can be divided according to the upgrade links, and divided into constant upgrade duration and variable duration according to the upgrade stages. The variable duration is determined by the required test cases and the number of testers, which constitute the upgrade capacity of this version. Determine the number of requirements for this version upgrade based on the version capacity, and ensure the maximum demand release based on the quality of the version. The upgrade version capacity model can be summarized as: total upgrade duration = constant duration + variable duration (test verification upgrade content duration and production process verification duration), which can specifically include the following steps:

[0077] 1. Take the average of a single manually executed test case to quantify the unit execution time;

[0078] 2. After designing use cases according to requirements, evaluate the version capacity occupied by the requirements based on the number of use cases;

[0079] 3. Calculate the capacity that this week's version can accommodate based on the number of testers and use cases;

[0080] 4. Calculate the number of requirements that the current version can accommodate based on steps 2 and 3;

[0081] 5. Based on the preset calculation formula provided by the upgrade version capacity model, the normal upgrade time of this version, the upgrade time when verification problems exist and the problems are solved, and the upgrade time when verification problems exist and the problems are not solved and the need to roll back is calculated. This can evaluate the latest completion time of the version upgrade and determine the timeliness risk of this version upgrade.

[0082] Optionally, a preset verification formula may be used to verify the estimated duration of each version, and the corresponding variables and constants may be regressively adjusted to reduce the calculation deviation of the upgraded version capacity model and improve the accuracy of the upgraded version capacity model in estimating the upgrade duration.

[0083] Step 206: Generate time-effectiveness risk information of system version upgrade based on the upgrade time.

[0084] Among them, timeliness risk information may include but is not limited to the upgrade time corresponding to different upgrade states, the response time for emergency repairs, the upgrade time required for each upgrade stage, etc. For example, the timeliness risk information can be fed back to the system administrator in the form of reports, etc., to assist the system administrator in determining whether there is a timeout risk in the current system version upgrade to avoid affecting the business development the next day. Users can also be notified of the upgrade time in advance and informed of possible service interruptions to reduce the impact on users.

[0085] Compared with the current existing technology, this embodiment can use a preset evaluation model to evaluate the verification time corresponding to different upgrade statuses, and determine the longest verification time among the verification times as the upgrade time corresponding to the target upgrade requirement, to assist system administrators in determining whether there is a timeout risk for this system version upgrade, to avoid affecting business development, and to reduce the impact on users.

[0086] Further, as Figure 1 and Figure 2 The specific implementation of the method shown in this embodiment provides a data processing device, such as Figure 6 As shown, the device includes: an acquisition module 31, an evaluation module 32, and an upgrade module 33.

[0087] An acquisition module 31 is configured to acquire a version upgrade requirement of a system version;

[0088] An evaluation module 32 is configured to evaluate the version capacity occupied by the version upgrade requirement according to the number of use cases of the version upgrade requirement;

[0089] An evaluation module 32 is configured to evaluate the required capacity accommodated by the system version according to the number of use cases and the upgrade resources corresponding to the system version;

[0090] The upgrade module 33 is configured to determine the target upgrade requirement of the system version based on the required capacity and the version capacity, and upgrade the system version according to the target upgrade requirement.

[0091] In some examples of this embodiment, the upgrade module 33 is further configured to use a preset evaluation model to evaluate the upgrade time of the system version upgrade according to the target upgrade requirement; and generate timeliness risk information of the system version upgrade based on the upgrade time.

[0092] In some examples of this embodiment, the upgrade module 33 is specifically configured to obtain the upgrade status during the system version upgrade process; use a preset evaluation model to evaluate the verification time corresponding to the upgrade status; and determine the longest verification time in the verification time as the upgrade time corresponding to the target upgrade requirement.

[0093] In some examples of this embodiment, the upgrade module 33 is specifically configured to calculate the verification time corresponding to the upgrade status based on the version capacity and the upgrade resources using the preset calculation formula corresponding to the upgrade status in the preset evaluation model.

[0094] In some examples of this embodiment, the upgrade module 33 is specifically configured to obtain the upgrade stage corresponding to the upgrade status; based on the version capacity and upgrade resources, determine the stage time corresponding to the upgrade stage using a preset calculation formula; and generate the verification time corresponding to the upgrade status based on the stage time.

[0095] In some examples of this embodiment, the upgrade module 33 is specifically configured to obtain the number of testers and version capacity in the upgrade resources, and calculate the stage time corresponding to the upgrade stage using a preset calculation formula; and / or obtain the preset production time corresponding to the upgrade stage as the stage time corresponding to the upgrade stage.

[0096] In some examples of this embodiment, the evaluation module 32 is specifically configured to obtain the unit execution time of the test cases of the system version; based on the unit execution time and the number of cases, the version capacity occupied by the version upgrade requirement is evaluated.

[0097] It should be noted that for other corresponding descriptions of the functional units involved in the data processing device provided in this embodiment, reference can be made to Figure 1 and Figure 2 The corresponding description in will not be repeated here.

[0098] Based on the above Figure 1 and Figure 2 The method shown in the embodiment also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the above-mentioned Figure 1 and Figure 2 The method shown.

[0099] Based on this understanding, the technical solution of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, USB flash drive, mobile hard disk, etc.), including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute the method of the implementation scenario of the present application.

[0100] Based on the above Figure 1 and Figure 2 The method shown, and Figure 6 In order to achieve the above-mentioned purpose, the embodiment of the present application further provides an electronic device, such as a personal computer or a server, which includes a storage medium and a processor; the storage medium is used to store a computer program; the processor is used to execute the computer program to achieve the above-mentioned Figure 1 and Figure 2 The method shown.

[0101] Optionally, the above-mentioned physical device may also include a user interface, a network interface, a camera, a radio frequency (RF) circuit, a sensor, an audio circuit, a WI-FI module, etc. The user interface may include a display, an input unit such as a keyboard, etc., and the optional user interface may also include a USB interface, a card reader interface, etc. The network interface may optionally include a standard wired interface, a wireless interface (such as a WI-FI interface), etc.

[0102] Those skilled in the art will appreciate that the above-mentioned physical device structure provided in this embodiment does not constitute a limitation on the physical device, and may include more or fewer components, or a combination of certain components, or different arrangements of components.

[0103] The storage medium may also include an operating system and a network communication module. The operating system is a program that manages the hardware and software resources of the above-mentioned physical device, and supports the operation of the information processing program and other software and / or programs. The network communication module is used to realize the communication between the components inside the storage medium, and the communication with other hardware and software in the information processing physical device.

[0104] Through the description of the above implementation methods, those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary general hardware platform, or by hardware. By applying the technical solution of this embodiment, the preset evaluation model can be used to evaluate the verification time corresponding to different upgrade states, and the longest verification time among the verification times can be determined as the upgrade time corresponding to the target upgrade requirement, to assist system managers in determining whether there is a timeout risk in this system version upgrade, to avoid affecting business development, and to reduce the impact on users.

[0105] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0106] The above is only a specific implementation of the present application, so that those skilled in the art can understand or implement the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments described herein, but will conform to the widest scope consistent with the principles and novel features applied for herein.

Claims

1. A version upgrade method, characterized in that: include: Get the system version upgrade requirements; According to the number of test cases of the version upgrade requirement, the total time consumption of the test cases corresponding to the version upgrade requirement is evaluated; According to the number of use cases and the upgrade resources corresponding to the system version, evaluate the required capacity accommodated by the system version; Based on the required capacity and the version capacity, a target upgrade requirement of the system version is determined, and the system version is upgraded according to the target upgrade requirement, and the version capacity occupied by the target upgrade requirement is smaller than the required capacity.

2. The method according to claim 1, characterized in that After determining the target upgrade requirement of the system version based on the required capacity and the version capacity, and upgrading the system version according to the target upgrade requirement, the method further includes: Using the preset evaluation model, evaluating the upgrade time of the system version upgrade according to the target upgrade requirement; According to the upgrade time, the timeliness risk information of the system version upgrade is generated.

3. The method according to claim 2, characterized in that The using the preset evaluation model to evaluate the upgrade time corresponding to the target upgrade requirement includes: Obtaining the upgrade status of the system version during the upgrade process; Using the preset evaluation model, evaluating the verification time corresponding to the upgrade status; The longest verification time among the verification times is determined as the upgrade time corresponding to the target upgrade requirement.

4. The method according to claim 3, characterized in that The using the preset evaluation model to evaluate the verification time corresponding to the upgrade state includes: Based on the version capacity and the upgrade resources, the verification time corresponding to the upgrade status is calculated using a preset calculation formula corresponding to the upgrade status in the preset evaluation model.

5. The method according to claim 4, characterized in that The calculating the verification time corresponding to the upgrade state based on the version capacity and the upgrade resource and using the preset calculation formula corresponding to the upgrade state in the preset evaluation model includes: Obtaining the upgrade stage corresponding to the upgrade status; Based on the version capacity and the upgrade resources, determining the stage time corresponding to the upgrade stage by using the preset calculation formula; A verification time corresponding to the upgrade status is generated according to the stage time.

6. The method according to claim 5, characterized in that The determining the stage time corresponding to the upgrade stage by using the preset calculation formula based on the version capacity and the upgrade resource includes: Obtaining the number of testers and the version capacity in the upgrade resources, and calculating the stage time corresponding to the upgrade stage using the preset calculation formula; and / or, A preset production time corresponding to the upgrade stage is obtained as the stage time corresponding to the upgrade stage.

7. The method according to claim 1, characterized in that The method further comprises: Obtaining the unit execution time of the test case of the system version; Based on the unit execution time and the number of test cases, the total time consumption of the test cases corresponding to the version upgrade requirement is evaluated.

8. A data processing device, characterized in that: include: An acquisition module is configured to acquire a version upgrade requirement of a system version; An evaluation module is configured to evaluate the total time consumption of the test cases corresponding to the version upgrade requirement according to the number of test cases of the version upgrade requirement; An evaluation module configured to evaluate the demand capacity accommodated by the system version according to the number of use cases and the upgrade resources corresponding to the system version; The upgrade module is configured to determine the target upgrade requirement of the system version based on the required capacity and the version capacity, and upgrade the system version according to the target upgrade requirement, and the version capacity occupied by the target upgrade requirement is smaller than the required capacity.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

10. An electronic device comprising a storage medium, a processor, and a computer program stored in the storage medium and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 7 is implemented.

Images