Coverage rate visualization method and device, equipment, storage medium and program product

Abstract

The invention discloses a coverage rate visualization method and device, equipment, a storage medium and a program product, and relates to the technical field of software security, and the method comprises the steps: obtaining a service key value and an application version number; according to the service key value and a service final state attribute field in the application version number, verifying and counting the application version number meeting the expected result, and obtaining an application version number coverage rate meeting the expected result; and converting the application version number coverage rate meeting the expected result into a visual result. According to the scheme, the application version number corresponding to each business scene is verified and counted, so that the gray-scale conversion type process can be judged and intervened, the dependence of manual judgment is reduced, the risk of manual judgment errors is reduced, personalized specifications are customized for each verification process, and the stability of a business system is improved. And the coverage rate of various business indexes is visually displayed, so that the generated verification problem can be found and solved in time, and the method has important significance for ensuring the quality and the stability of the product.

Description

Technical Field

[0001] The present application relates to the field of software testing technology, and in particular to a coverage visualization method, apparatus, device, storage medium, and program product. Background Art

[0002] With the development of the Internet and the growth of business volume, the risk of business system changes and releases is gradually increasing. The importance of blue-green release, grayscale release, and grayscale verification in practical applications is also gradually becoming more prominent. In actual production environments, multiple versions are often managed, which increases the complexity of the system. If all business scenarios are not fully covered, the grayscale version will be changed to a formal version, which may cause production problems of varying degrees:

[0003] (1) There is no unified standard for comprehensive analysis of coverage verification scenarios for normal business processes and changes. To achieve sustained stability, developers are required to have a high level of business understanding.

[0004] (2) Whether various indicators such as business success rate and coverage rate meet expectations requires manual statistics. There are many business scenarios, and manual operations are cumbersome. In addition, there are no visualization tools to intuitively display the business operation status and scenario coverage.

[0005] (3) In the production environment, non-core but necessary business scenarios may have unknown coverage gaps and potential risks due to lack of attention.

[0006] (4) The threshold for transitioning from grayscale to official release is unclear. There is no unified standard for grayscale release and verification, function optimization, and change verification. There is no clear specification for the level of traffic required to transition to official release. There is no effective management and control of problems in the grayscale verification phase, which makes it easy for defects that could have been avoided in the grayscale environment to be exposed in the official environment. Summary of the invention

[0007] The main purpose of this application is to provide a coverage visualization method, device, equipment, storage medium and program product, aiming to solve the technical problem of how to visualize the coverage of business scenarios while ensuring the standardization of grayscale release and verification processes.

[0008] To achieve the above objectives, the present application proposes a coverage visualization method, which includes:

[0009] Get the business key value and application version number;

[0010] Verify and count the application version numbers that meet the expected result according to the business key value and the business final state attribute field in the application version number, and obtain the coverage rate of the application version numbers that meet the expected result;

[0011] The application version number coverage that meets the expected result is converted into a visual result.

[0012] In one embodiment, the step of verifying and counting application version numbers that meet expected results based on the business key value and the business final state attribute field in the application version number, and obtaining the coverage rate of application version numbers that meet expected results includes:

[0013] According to the business final state attribute field in the application version number, verify whether the business scenario corresponding to the application version number has successfully covered the preset business scenario;

[0014] If the verification is successful, the business key value is used to count the number of application version numbers that have successfully covered the preset business scenarios, and the coverage rate of the application version numbers that have successfully covered the preset business scenarios is calculated.

[0015] In one embodiment, the step of verifying whether the business scenario corresponding to the application version number has successfully covered the preset business scenario according to the business final state attribute field in the application version number includes:

[0016] Get the business final state attribute fields of the preset business scenario;

[0017] Determine whether the service final state attribute field in the application version number is consistent with the service final state attribute field of the preset service scenario;

[0018] If so, it means that the business scenario corresponding to the application version number has successfully covered the preset business scenario.

[0019] In one embodiment, the step of calculating the coverage rate of the application version numbers that have successfully covered the preset business scenarios includes:

[0020] The application version number that has successfully covered the preset business scenario is marked with the first preset color;

[0021] The coverage rate of the application version numbers marked with the first preset color that have successfully covered the preset business scenarios is calculated.

[0022] In one embodiment, the step of visualizing the application version number coverage that meets the expected result as a result includes:

[0023] Converting the coverage rate of the application version number marked with the first preset color and having successfully covered the preset business scenario into a coverage rate chart;

[0024] The coverage chart is displayed through a statistical interface.

[0025] In one embodiment, after the step of converting the application version number coverage that meets the expected result into a visualization result, the method further includes:

[0026] Set the corresponding expected success rate threshold according to the application version number coverage in different business scenarios;

[0027] The application version number coverage and the corresponding expected success rate threshold in the different business scenarios are marked and displayed using a second preset color.

[0028] In addition, to achieve the above purpose, the present application also proposes a coverage visualization device, the coverage visualization device comprising:

[0029] The acquisition module is used to obtain the business key value and application version number;

[0030] A processing module, configured to verify and count application version numbers that meet the expected result according to the business key value and the business final state attribute field in the application version number, and obtain the coverage rate of application version numbers that meet the expected result;

[0031] The conversion module is used to convert the application version number coverage that meets the expected result into a visual result.

[0032] In addition, to achieve the above-mentioned purpose, the present application also proposes a coverage visualization device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the coverage visualization method described above.

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

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

[0035] The embodiments of the present application provide a coverage visualization method, apparatus, device, storage medium, and program product, which obtains business key values ​​and application version numbers; verifies and counts application version numbers that meet expected results based on business key values ​​and business final state attribute fields in application version numbers, obtains application version number coverage that meets expected results; and converts application version number coverage that meets expected results into visualization results. By verifying and counting application version numbers corresponding to each business scenario, the solution can determine and intervene in the grayscale-to-formal process, thereby reducing reliance on manual judgment, reducing the risk of manual judgment errors, customizing personalized specifications for each verification process, and improving the stability of the business system. And by visually displaying the coverage of various business indicators, it provides greater convenience for users. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0037] In order to more clearly illustrate the technical solutions in the embodiments of the present application or 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.

[0038] Figure 1 A schematic diagram of a process flow provided for Embodiment 1 of the coverage visualization method of this application;

[0039] Figure 2 This is a schematic diagram of the process of recording business key values ​​and application version numbers involved in the first embodiment of the present application;

[0040] Figure 3 This is a schematic diagram of visualization of statistical data involved in Example 1 of the present application;

[0041] Figure 4 A flow chart of Embodiment 2 of the coverage visualization method of this application;

[0042] Figure 5 A schematic diagram showing the visualization of the coverage rate and the expected success rate threshold involved in the second embodiment of the present application;

[0043] Figure 6 A brief flowchart of the coverage visualization method provided in Example 1 of the present application;

[0044] Figure 7 This is a schematic diagram of the module structure of the coverage visualization device according to an embodiment of the present application;

[0045] Figure 8Schematic diagram of the device structure of the hardware operating environment involved in the coverage visualization method in the embodiment of the present application.

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

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

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

[0049] The main solution of the embodiment of the present application is: obtain the business key value and application version number; verify and count the application version numbers that meet the expected results based on the business key value and the business final state attribute field in the application version number, and obtain the application version number coverage that meets the expected results; convert the application version number coverage that meets the expected results into a visual result.

[0050] In this embodiment, for ease of description, the following description is made by taking the identification coverage statistics tool as the execution subject.

[0051] The risk of business system changes and releases is gradually increasing. The importance of blue-green release, grayscale release, and grayscale verification in practical applications is gradually becoming more prominent. In actual production environments, multiple versions are often managed, which increases the complexity of the system. If all business scenarios are not fully covered, the grayscale version will be changed to the official version, which may cause production problems of varying degrees:

[0052] (1) There is no unified standard for comprehensive analysis of coverage verification scenarios for normal business processes and changes. To achieve sustained stability, developers are required to have a high level of business understanding.

[0053] (2) Whether various indicators such as business success rate and coverage rate meet expectations requires manual statistics. There are many business scenarios, and manual operations are cumbersome. In addition, there are no visualization tools to intuitively display the business operation status and scenario coverage.

[0054] (3) In the production environment, non-core but necessary business scenarios may have unknown coverage gaps and potential risks due to lack of attention.

[0055] (4) The threshold for transitioning from grayscale to official release is unclear. There is no unified standard for grayscale release and verification, function optimization, and change verification. There is no clear specification for the level of traffic required to transition to official release. There is no effective management and control of problems in the grayscale verification phase, which makes it easy for defects that could have been avoided in the grayscale environment to be exposed in the official environment.

[0056] This application provides a solution that standardizes the release verification process by customizing business verification scenarios, coverage, and success rate thresholds to solve the dependence of grayscale verification on manual judgment. The complex and subjective grayscale verification process of manual judgment is transformed into a systematic and automated operation, thereby reducing the dependence on manual judgment and the risk of manual judgment errors. Customizing personalized specifications for each online verification process can improve the stability of the business system and improve user experience. At the same time, data statistics are automated to solve the problem of cumbersome manual statistical data. The coverage corresponding to each business scenario is visualized in two dimensions: graph and data, which can provide great convenience for business personnel, developers, and testers.

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

[0058] Based on this, the present application embodiment provides a coverage visualization method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the coverage visualization method of the present application.

[0059] In this embodiment, the coverage visualization method includes steps S10 to S30:

[0060] Step S10, obtaining the business key value and application version number;

[0061] It should be noted that the business key value is used to count business scenarios; the application version is used to distinguish between blue and green versions, that is, the new and old versions.

[0062] In addition, it should be noted that this embodiment provides a coverage statistics tool that can easily access the business system without any impact on the performance of the business system, and can visually display the coverage of business scenarios and grayscale verification coverage scenarios.

[0063] Please refer to Figure 2 , Figure 2 The following is a flow chart of recording business key values ​​and application version numbers involved in the coverage visualization method of this embodiment, specifically:

[0064] When the business starts, the business event is triggered first. When the business event is triggered, the business system records the current application version number and business key value without any sense. That is, in the entire process of business execution, whenever a key node or important event is encountered, the corresponding business key value is recorded, and each time the business key value is recorded, the application version number is recorded at the same time. When the business process is completed, stop recording the business key value and application version number. All business key values ​​and application version numbers recorded in the business process will be saved for subsequent version number verification and statistics.

[0065] Step S20, verifying and counting the application version numbers that meet the expected result according to the business key value and the business final state attribute field in the application version number, and obtaining the coverage rate of the application version numbers that meet the expected result;

[0066] It should be noted that the business final state attribute field refers to the relevant attributes or fields involved when a transaction or task reaches the final state in the business process. In different business scenarios, these attribute fields can have different meanings, but their common feature is that they indicate that a business activity has been completed and will not change again.

[0067] It is worth noting that in the process of software development and release, the standardization of verification scenarios is a crucial step to improve test efficiency and accuracy and reduce risks. Therefore, in this embodiment, by verifying whether the business corresponding to the application version number has been completed and whether the verification result meets expectations, the release verification process can be standardized, the grayscale verification's reliance on manual judgment can be resolved, and the efficiency of testing and verification can be improved.

[0068] In a feasible implementation, step S20 may include steps S21 to S22:

[0069] Step S21, verifying whether the business scenario corresponding to the application version number has successfully covered the preset business scenario according to the business final state attribute field in the application version number;

[0070] It should be noted that the application version number includes the new and old version numbers.

[0071] Optionally, obtain the current time as the reference time point, then query the version number online record based on the reference time point, and find out the application version numbers that were launched before and after the time point. Define the latest version number before the reference time point as the old version number; define the first version number after the reference time point as the new version number. After obtaining the old and new version numbers, distinguish different business scenarios based on the business end state attribute fields associated with the preset business scenarios, and determine whether the new and old version businesses have been completed, and verify whether the results meet expectations.

[0072] Based on the above, step S21 "verifying whether the business scenario corresponding to the application version number has successfully covered the preset business scenario according to the business final state attribute field in the application version number" further includes steps S211 to S213:

[0073] Step S211 obtains the business final state attribute field of the preset business scenario;

[0074] Optionally, since each business scenario has a set of predefined business attribute fields, and different business scenarios have different final state attribute fields, in this embodiment, a set of business final state attribute fields are defined according to the preset business scenarios. These fields may include completion time, cancellation reason, status code, etc.

[0075] Step S212, determining whether the service end state attribute field in the application version number is consistent with the service end state attribute field of the preset service scenario;

[0076] Optionally, the service end state attribute field in the new and old version numbers is extracted, and the service end state attribute field of the extracted new and old version numbers is compared with the service end state attribute field associated with the preset service scenario to see whether they are consistent. Through this method, the service system can determine whether the new and old version services have completed the preset scenario services.

[0077] In addition, it should be emphasized that since business scenario verification is not a one-time thing and changes with the development of the business, it is necessary to regularly update and reset the verification business scenario, that is, update the preset business scenario.

[0078] Step S213: If yes, it means that the business scenario corresponding to the application version number has successfully covered the preset business scenario.

[0079] Optionally, through step S212, if the judgment result is that the business end state attribute field of the new and old version numbers is consistent with the business end state attribute field associated with the preset business scenario, then it means that the business scenario corresponding to the new and old version numbers already includes the functions or states required by the preset business scenario.

[0080] Step S22: If the verification is successful, the business key value is used to count the number of application version numbers that have successfully covered the preset business scenarios, and the coverage rate of the application version numbers that have successfully covered the preset business scenarios is calculated.

[0081] Optionally, first, the business system uses the business key value to count the number of new and old version numbers that are considered to have successfully covered the preset business scenario during the verification process through the accessed statistical tool. In addition, during the statistical process, the new and old version numbers that have successfully covered the preset business scenario are marked with a preset color. In this embodiment, light green can be used to mark the new and old version numbers that have successfully covered the preset business scenario, and gray can be used to mark the new and old version numbers that have not successfully covered the preset business scenario.

[0082] Then, calculate the ratio of the number of new and old version numbers that have successfully covered the preset business scenarios to the total number of version numbers. The formula can be used: Coverage = (number of new and old version numbers that have successfully covered the preset business scenarios / total number of version numbers) * 100%. Based on this formula, the coverage rate of application version numbers that have successfully covered the preset business scenarios can be calculated. Since the new and old version numbers that have successfully covered the preset business scenarios have been marked with a preset color (i.e., light green), the corresponding coverage rate is also marked with light green.

[0083] Through the above steps, we can effectively verify and count the coverage of the application version number for the preset business scenarios and obtain the coverage rate. By instantly comparing the preset business scenarios with the business scenarios corresponding to the actual application version number and identifying any deviations or problems, we can ensure that new functions or changes run stably during the grayscale testing phase without verification crashes or performance issues, which can greatly improve the stability of the system.

[0084] Step S30, converting the application version number coverage that meets the expected result into a visual result.

[0085] It is worth noting that in the actual production environment, the coverage and execution of business scenarios are often opaque, especially for those business scenarios that are not the main process but are still important. Due to the lack of effective tools and technical means to monitor and visualize the execution of these business scenarios in real time, it is difficult for testers to fully grasp the business coverage in actual production, which may further cause potential problems to exist in the production environment for a long time without being discovered, increasing maintenance costs and risks for the business.

[0086] Therefore, in this embodiment, a method for visualizing coverage and verification degree is proposed to ensure that key business data indicators perform normally during the grayscale testing phase without significant negative impact. The coverage and success rate of the verification scenarios are intuitively displayed in the form of charts and data. The coverage and success rate of preset business scenarios are automatically counted, and it is automatically determined whether the success rate meets expectations, which improves the efficiency of statistical verification scenarios and reduces omissions and errors in manual judgment. Verification problems can be discovered and solved in a timely manner, which is of great significance for ensuring product quality and stability.

[0087] Optionally, in this embodiment, the business system uses a statistical tool to convert the application version numbers that meet the expected results into visual results in the form of charts and display them on the interface of the statistical tool. Similarly, the coverage rates corresponding to the application version numbers that meet the expected results can also be displayed visually.

[0088] For further information, please refer to Figure 3 , Figure 3 The following is a diagram for visualizing statistical data. On the interface of the statistical tool, you can select business statistics for the old and new versions to determine whether the business verification of the old and new versions meets expectations, whether the old and new versions are compatible, and whether the business volume of the old and new versions meets expectations. At the same time, the preset color indicates whether the business scenario corresponding to the application version number has been verified, that is, whether the business scenario corresponding to the application version number has covered the preset business scenario. By intuitively displaying the execution of the business scenario corresponding to the application version number, the access control rules for converting grayscale traffic to formal traffic can be visualized, thereby determining whether these application versions can smoothly transition from the grayscale environment to the formal environment.

[0089] Through the above steps, data statistics can be visualized, business statistical indicators can be customized, business scenarios and various indicators can be combined for visualization, and two dimensions of pictures and data can be displayed simultaneously. Data statistics are automated to solve the problem of tedious manual statistical data.

[0090] The above-mentioned embodiment method specifically obtains the business key value and the application version number; verifies and counts the application version number that meets the expected result according to the business key value and the business final state attribute field in the application version number, and obtains the coverage rate of the application version number that meets the expected result; converts the coverage rate of the application version number that meets the expected result into a visual result. By verifying and counting the application version number corresponding to each business scenario, this solution can judge and intervene in the process of grayscale conversion to formal, thereby reducing the reliance on manual judgment, reducing the risk of manual judgment errors, customizing personalized specifications for each verification process, and improving the stability of the business system. And by visually displaying the coverage rate of various business indicators, timely discovering and solving the verification problems generated is of great significance for ensuring the quality and stability of the product, and providing greater convenience for users.

[0091] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction, and will not be repeated in the following. Figure 4 Before step S30, the coverage visualization method further includes steps S301 to S302:

[0092] Step S301, setting a corresponding expected success rate threshold according to the application version number coverage in different business scenarios;

[0093] It should be noted that the expected success rate threshold refers to the minimum percentage of application version number coverage that should be achieved in a specific business scenario, which is used as the criterion for judging whether the version number is successful.

[0094] Optionally, for each business scenario, an expected success rate threshold is set based on its actual operation and importance. This threshold represents the minimum percentage that the application version number coverage must reach in this business scenario to ensure that the version number can be considered successful.

[0095] Step S302: The application version number coverage in the different business scenarios and the corresponding expected success rate threshold are marked and displayed using a second preset color.

[0096] Please refer to Figure 5 , Figure 5 A diagram showing the coverage rate and expected success rate threshold visualization. Specifically, preset colors are used to intuitively show whether the application version number coverage rate in different business scenarios has reached the expected success rate threshold. For example, green can be used to indicate that the coverage rate has reached the expected threshold, red to indicate that it has not reached it, and gray to indicate that it is close to but has not fully reached the threshold.

[0097] This color marking and display method enables relevant testers to quickly understand the coverage of each business scenario and its comparison with the expected goals.

[0098] Assume that there are two business scenarios: order processing and user registration, and different expected success rate thresholds are set for each. The expected success rate threshold for order processing is 95%, and the current coverage rate is 88%; the expected success rate threshold for user registration is 90%, and the current coverage rate is 88%.

[0099] Since the current coverage rate of order processing is 97% and exceeds the expected success rate threshold of 95%, it can be marked in green and displayed on the interface of the statistical tool. However, since the current coverage rate of user registration is 88% and does not reach the expected success rate threshold of 90%, it can be marked in gray and displayed on the interface of the statistical tool.

[0100] Through the above-mentioned embodiment method, relevant testers can quickly understand whether the application version coverage in different business scenarios has reached the expected success rate threshold. By counting the preset business scenario coverage and success rate, it is automatically determined whether the success rate meets expectations, which improves the efficiency of statistical verification scenarios and reduces omissions and errors in manual judgment. Verification problems can be discovered and solved in a timely manner, which is of great significance for ensuring product quality and stability.

[0101] For example, to help understand the implementation process of the coverage visualization method obtained by combining this embodiment with the above-mentioned embodiment 1, please refer to Figure 6 , Figure 6 A brief flowchart of the coverage visualization method is provided, specifically:

[0102] It should be noted that this coverage visualization method is implemented by combining the business system with a coverage statistics tool. The statistical tool can be easily connected to the business system, will not have any impact on the performance of the business system, and provides a visualization display function.

[0103] First, start the statistical release business process and record the application version number and associated key value generated in the entire process. The application version number includes the new version number and the old version number.

[0104] Then, the business final state attribute fields in the new and old version numbers are extracted, and it is verified whether the business final state attribute fields associated with the new and old version numbers meet the business final state attribute fields associated with the preset business scenario.

[0105] If the verification is successful, the corresponding business key values ​​are used to count the number of new and old version numbers, and the statistical results are integrated together to obtain the number of new and old version businesses that meet the preset business scenario. Subsequently, based on the statistical data, the coverage rate of the new and old version numbers that meet the preset business scenario is calculated.

[0106] The coverage of the old and new versions that meet the preset business scenarios is converted into visual results and displayed in the form of charts on the interface of the statistical tool. This can automatically realize the old version business statistics, determine whether the business verification meets expectations, whether the old and new versions are compatible, and whether the business volume meets expectations. At the same time, the old and new version numbers that meet the preset business scenarios are marked with preset colors.

[0107] In addition to the data volume statistics of the new and old version numbers, if the corresponding expected success rate threshold is preset, it can also be calculated and displayed on the statistical interface, and the preset color can be used to indicate whether the coverage of the new and old version numbers meets the expected success rate threshold.

[0108] Through the above-mentioned embodiment method, the grayscale verification statistics are guaranteed, the statistical method is more convenient and more efficient, the grayscale conversion is formally standardized, the expected results and actual results are compared in time, and any deviations or problems are identified. It can ensure that new functions or changes run stably during the grayscale testing phase without serious crashes or performance problems, and can greatly improve the stability of the system. Through the visualization of coverage and verification degree, it is ensured that key business data indicators perform normally during the grayscale testing phase without significant negative effects. The coverage and success rate of the verification scenario are intuitively displayed in the form of charts and data. Automatically count the coverage and success rate of preset business scenarios, and automatically determine whether the success rate meets expectations, which improves the efficiency of statistical verification scenarios, while reducing omissions and errors in manual judgment. Verification problems can be discovered early and solved in time, which is of great significance to ensuring product quality and stability. In addition, the automated verification process is closely integrated with the online release process to ensure that verification is automatically performed each time it is released online. Setting a success rate threshold and converting the preset success rate threshold into actual access control rules can standardize the verification scenario and ensure that each verification follows the same test cases and standards. This not only improves the effectiveness of the system's grayscale verification, but also prevents defects in the grayscale verification from being exposed to the formal environment, thereby playing a positive role in the stable operation and sustainable development of the system.

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

[0110] This application also provides a coverage visualization device, please refer to Figure 7 , the coverage visualization device comprises:

[0111] The acquisition module 10 is used to obtain the business key value and the application version number;

[0112] A processing module 20 is used to verify and count the application version numbers that meet the expected results according to the business key value and the business final state attribute field in the application version number, and obtain the coverage rate of the application version numbers that meet the expected results;

[0113] The conversion module 30 is used to convert the application version number coverage that meets the expected result into a visual result.

[0114] The coverage visualization device provided by the present application adopts the coverage visualization method in the above-mentioned embodiment, which can solve the technical problem of how to visualize the coverage of business scenarios under the premise of ensuring the standardization of grayscale release and verification process. Compared with the prior art, the beneficial effects of the coverage visualization device provided by the present application are the same as the beneficial effects of the coverage visualization method provided by the above-mentioned embodiment, and the other technical features in the coverage visualization device are the same as the features disclosed in the above-mentioned embodiment method, which will not be repeated here.

[0115] The present application provides a coverage visualization device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the coverage visualization method in the above-mentioned embodiment 1.

[0116] Reference below Figure 8 , which shows a schematic diagram of the structure of a coverage visualization device suitable for implementing the embodiment of the present application. The coverage visualization device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 8 The coverage visualization device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

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

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

[0119] The coverage visualization device provided by the present application adopts the coverage visualization method in the above embodiment, which can solve the technical problem of how to visualize the coverage of business scenarios under the premise of ensuring the standardization of grayscale release and verification process. Compared with the prior art, the beneficial effects of the coverage visualization device provided by the present application are the same as the beneficial effects of the coverage visualization method provided by the above embodiment, and the other technical features in the coverage visualization device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

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

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

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

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

[0124] The computer-readable storage medium may be included in the coverage visualization device; or may exist independently without being assembled into the coverage visualization device.

[0125] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the coverage visualization device, the coverage visualization device: obtains a business key value and an application version number;

[0126] Verify and count the application version numbers that meet the expected result according to the business key value and the business final state attribute field in the application version number, and obtain the coverage rate of the application version numbers that meet the expected result;

[0127] The application version number coverage that meets the expected result is converted into a visual result.

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

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

[0130] The modules involved in the embodiments of the present application may be implemented by software or hardware, wherein the name of the module does not limit the unit itself in some cases.

[0131] The readable storage medium provided in this application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned coverage visualization method, and can solve the technical problem of how to visualize the coverage of business scenarios under the premise of ensuring the standardization of grayscale release and verification processes. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the coverage visualization method provided in the above-mentioned embodiments, and will not be repeated here.

[0132] The present application also provides a computer program product, including a computer program, which implements the steps of the coverage visualization method as described above when the computer program is executed by a processor.

[0133] The computer program product provided by this application can solve the technical problem of how to visualize the coverage of business scenarios while ensuring the standardization of the grayscale release and verification process. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the coverage visualization method provided by the above embodiment, which will not be repeated here.

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

Claims

1. A coverage visualization method, characterized in that: The method comprises: Get the business key value and application version number; Verify and count the application version numbers that meet the expected result according to the business key value and the business final state attribute field in the application version number, and obtain the coverage rate of the application version numbers that meet the expected result; The application version number coverage that meets the expected result is converted into a visual result.

2. The method according to claim 1, characterized in that The step of verifying and counting application version numbers that meet the expected result based on the business key value and the business final state attribute field in the application version number, and obtaining the coverage rate of application version numbers that meet the expected result includes: According to the business final state attribute field in the application version number, verify whether the business scenario corresponding to the application version number has successfully covered the preset business scenario; If the verification is successful, the business key value is used to count the number of application version numbers that have successfully covered the preset business scenarios, and the coverage rate of the application version numbers that have successfully covered the preset business scenarios is calculated.

3. The method according to claim 2, characterized in that The step of verifying, according to the business final state attribute field in the application version number, whether the business scenario corresponding to the application version number has successfully covered the preset business scenario includes: Get the business final state attribute fields of the preset business scenario; Determine whether the service final state attribute field in the application version number is consistent with the service final state attribute field of the preset service scenario; If so, it means that the business scenario corresponding to the application version number has successfully covered the preset business scenario.

4. The method according to claim 2, characterized in that The step of calculating the coverage rate of the application version numbers that have successfully covered the preset business scenarios includes: The application version number that has successfully covered the preset business scenario is marked with the first preset color; The coverage rate of the application version numbers marked with the first preset color that have successfully covered the preset business scenarios is calculated.

5. The method according to claim 4, characterized in that The step of visualizing the application version number coverage that meets the expected result as a result comprises: Converting the coverage rate of the application version number marked with the first preset color and having successfully covered the preset business scenario into a coverage rate chart; The coverage chart is displayed through a statistical interface.

6. The method according to claim 1, characterized in that After the step of converting the application version number coverage that meets the expected result into a visualization result, the method further includes: Set the corresponding expected success rate threshold according to the application version number coverage in different business scenarios; The application version number coverage and the corresponding expected success rate threshold in the different business scenarios are marked and displayed using a second preset color.

7. A coverage visualization device, characterized in that: The device comprises: The acquisition module is used to obtain the business key value and application version number; A processing module, configured to verify and count application version numbers that meet the expected result according to the business key value and the business final state attribute field in the application version number, and obtain the coverage rate of application version numbers that meet the expected result; The conversion module is used to convert the application version number coverage that meets the expected result into a visual result.

8. A coverage visualization device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the coverage visualization method according to any one of claims 1 to 6.

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

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the coverage visualization method according to any one of claims 1 to 6 are implemented.

Images