A full-link service scenario coverage test method and device

Abstract

The embodiment of the application provides a full-link service scenario coverage test method and device, which can be used in the field of artificial intelligence technology, and the method comprises the following steps: obtaining file information of an updated patch file, wherein the file information comprises an update field; querying a corresponding service scenario according to the update field through a pre-constructed full-link service scenario linkage list; sending a service scenario coverage test request to a service terminal corresponding to the service scenario, and receiving a service scenario coverage test result returned by the service terminal; constructing the full-link service scenario linkage list; and calling the service terminal to automatically perform the service scenario coverage test, so that the comprehensiveness and accuracy of the coverage test are improved, the test efficiency is improved, the requirement for the test timeliness of service personnel is reduced, and the performance risk of the application is reduced.

Description

Technical Field

[0001] This invention relates to the field of computer technology, particularly to the field of artificial intelligence technology, and especially to a method and apparatus for coverage testing of a full-link business scenario. Background Technology

[0002] In public entry applications of open platforms, there are numerous integrator applications, and patch files iterate rapidly. Traditionally, updated patches are manually tested across various business scenarios to determine if they successfully cover the desired scenarios. However, as the number of integrator applications and patch file versions increases, manual coverage testing becomes insufficient to meet the testing needs of all business scenarios. This results in poor comprehensiveness and accuracy of coverage testing, low testing efficiency, and high demands on the timeliness of testing by business personnel, ultimately leading to higher application performance risks. Summary of the Invention

[0003] One objective of this invention is to provide a method for full-link business scenario coverage testing. This method constructs a linked list of full-link business scenarios and automatically calls business terminals to perform business scenario coverage testing. This improves the comprehensiveness and accuracy of coverage testing, increases testing efficiency, reduces the timeliness requirements for testing by business personnel, and thus reduces application performance risks. Another objective of this invention is to provide a device for full-link business scenario coverage testing. A further objective of this invention is to provide a computer-readable medium. A final objective of this invention is to provide a computer device.

[0004] To achieve the above objectives, this invention discloses a coverage testing method for a full-link business scenario, comprising:

[0005] Retrieve file information for the updated patch file, including the update field;

[0006] By using a pre-built list of interconnected business scenarios across the entire value chain, the corresponding business scenario can be retrieved based on the updated fields.

[0007] Send a business scenario coverage test request to the business terminal corresponding to the business scenario, and receive the business scenario coverage test results returned by the business terminal.

[0008] Preferably, before retrieving the corresponding business scenario based on the updated field from a pre-built list of end-to-end business scenarios, the process also includes:

[0009] Obtain business logs, interface services corresponding to various business scenarios, and business terminal information;

[0010] Construct a scenario interface relationship table based on each business scenario, the corresponding interface service, and business terminal information;

[0011] Extract key element combinations from business logs according to preset key element identifiers;

[0012] Based on the combination of key elements and the relationship table of scenario interfaces, construct a list of linkages for the entire business scenario.

[0013] Preferably, the key element combination includes channel number, region code, device number, service method name, and exception code;

[0014] Based on the key element combinations and scenario interface relationship table, construct a full-link business scenario linkage list, including:

[0015] Match the service method name with the interface service to obtain the business scenario and business terminal information corresponding to the combination of key elements;

[0016] Based on the combination of key elements, the corresponding business scenarios, business terminal information, and corresponding interface services, a full-link business scenario linkage list is generated.

[0017] Preferably, the exception code includes either a success overwrite flag or a failure overwrite flag;

[0018] The method also includes:

[0019] By using the full-link business scenario linkage list, the business terminal information corresponding to the coverage failure identifier can be queried.

[0020] Send a warning message about coverage failure to the service terminal indicated by the queried service terminal information.

[0021] Preferably, the full-chain business scenario linkage list includes multiple business scenarios and the corresponding interface services for each business scenario;

[0022] By using a pre-built list of interconnected business scenarios across the entire value chain, the corresponding business scenarios can be queried based on the updated fields, including:

[0023] The updated fields are matched with the interface service to obtain the corresponding business scenario.

[0024] Preferably, the document information also includes the production launch time and delivery time, and the business scenario coverage test results include the most recent coverage test time;

[0025] After receiving the business scenario coverage test results returned by the business terminal, the following is also included:

[0026] Determine if the most recent coverage test time is less than the delivery time;

[0027] If so, send a warning message about coverage failure to the business terminal corresponding to the business scenario;

[0028] If not, deploy the updated patch files according to the deployment time.

[0029] Preferably, after receiving the business scenario coverage test results returned by the business terminal, the following steps are also included:

[0030] Generate a project functional test schedule based on the test results covering multiple business scenarios.

[0031] Visualize the project's functional testing schedule.

[0032] This invention also discloses a coverage testing device for a full-link service scenario, comprising:

[0033] The file information acquisition unit is used to acquire the file information of the updated patch file, including the update field.

[0034] The business scenario query unit is used to query the corresponding business scenario based on the updated fields by using a pre-built list of full-link business scenario linkages.

[0035] The transceiver unit is used to send business scenario coverage test requests to the business terminals corresponding to the business scenarios, and to receive the business scenario coverage test results returned by the business terminals.

[0036] The present invention also discloses a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the method described above.

[0037] The present invention also discloses a computer device, including a memory and a processor, wherein the memory is used to store information including program instructions, and the processor is used to control the execution of the program instructions, wherein the processor executes the program to implement the method described above.

[0038] The present invention also discloses a computer program product, including a computer program / instructions, which, when executed by a processor, implement the method described above.

[0039] This invention obtains file information of updated patch files, including update fields; it queries the corresponding business scenarios based on the update fields using a pre-built full-link business scenario linkage list; it sends a business scenario coverage test request to the business terminal corresponding to the business scenario and receives the business scenario coverage test results returned by the business terminal, thus constructing a full-link business scenario linkage list and automatically calling the business terminal to perform business scenario coverage testing. This improves the comprehensiveness and accuracy of coverage testing, increases testing efficiency, reduces the timeliness requirements for testing by business personnel, and thereby reduces application performance risks. Attached Figure Description

[0040] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0041] Figure 1 A flowchart illustrating a full-link service scenario coverage testing method provided in an embodiment of the present invention;

[0042] Figure 2 A flowchart illustrating another coverage testing method for a full-link business scenario provided by an embodiment of the present invention;

[0043] Figure 3 A schematic diagram of the structure of a coverage testing device for a full-link service scenario provided in an embodiment of the present invention;

[0044] Figure 4 This is a schematic diagram of the structure of a computer device provided in an embodiment of the present invention. Detailed Implementation

[0045] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0046] It should be noted that the coverage testing method and apparatus for a full-link business scenario disclosed in this application can be used in the field of artificial intelligence technology, or in any field other than artificial intelligence technology. The application field of the coverage testing method and apparatus for a full-link business scenario disclosed in this application is not limited.

[0047] To facilitate understanding of the technical solution provided in this application, the relevant content of the technical solution will be explained below. Currently, in application testing, there are many access points for public entry-level applications. This leads to problems such as comprehensiveness and low efficiency in functional testing, regression testing, and performance testing. Most business scenarios require verification from all access points individually, making project management difficult. Furthermore, patch file delivery is currently quite flexible, and version iteration is very rapid. To avoid the risk exposure caused by untimely testing, this invention provides a full-link business scenario coverage testing method, achieving full-link business scenario coverage testing from a project management perspective.

[0048] The following example uses a coverage testing device for a full-link business scenario as the execution subject to illustrate the implementation process of the coverage testing method for a full-link business scenario provided in this embodiment of the invention. It is understood that the execution subject of the coverage testing method for a full-link business scenario provided in this embodiment of the invention includes, but is not limited to, a coverage testing device for a full-link business scenario.

[0049] Figure 1 A flowchart of a coverage testing method for a full-link business scenario provided by an embodiment of the present invention is shown below. Figure 1 As shown, the method includes:

[0050] Step 101: Obtain the file information of the updated patch file, including the update field.

[0051] Step 102: Using the pre-built full-link business scenario linkage list, query the corresponding business scenario based on the updated fields.

[0052] In this embodiment of the invention, the full-link business scenario linkage list includes multiple business scenarios and the corresponding interface services for each business scenario.

[0053] Step 103: Send a business scenario coverage test request to the business terminal corresponding to the business scenario, and receive the business scenario coverage test results returned by the business terminal.

[0054] In the technical solution provided by this invention, file information of the updated patch file is obtained, including update fields; based on the update fields, the corresponding business scenario is queried through a pre-built full-link business scenario linkage list; a business scenario coverage test request is sent to the business terminal corresponding to the business scenario, and the business scenario coverage test results returned by the business terminal are received; a full-link business scenario linkage list is constructed, and the business terminal is automatically called to perform business scenario coverage testing. This can improve the comprehensiveness and accuracy of coverage testing, increase testing efficiency, reduce the timeliness requirements for testing by business personnel, and thus reduce the performance risk of the application.

[0055] Figure 2 A flowchart of another coverage testing method for a full-link business scenario provided by an embodiment of the present invention is shown below. Figure 2 As shown, the method includes:

[0056] Step 201: Obtain business logs, interface services corresponding to each business scenario, and business terminal information.

[0057] In this embodiment of the invention, each step is executed by a full-link business scenario coverage testing device.

[0058] In this embodiment of the invention, business logs are stored in a database, and business logs for each business can be retrieved from the database. The interface services corresponding to each business scenario can be extracted from the actual processing of the business within each scenario. For example, the interface service corresponding to the business scenario "My - Personal Profile - Face Recognition Service - Collection" is "Prequery+Compare". The business terminal information corresponding to each business scenario includes the business personnel and their email addresses. This business terminal information is pre-set according to actual needs, and this invention does not impose any limitations on it. For example, the business personnel corresponding to the business scenario "My - Personal Profile - Face Recognition Service - Collection" is "User A", and the corresponding email address is 123@xxx.com.

[0059] Step 202: Construct a scenario interface relationship table based on each business scenario, the corresponding interface service, and the business terminal information.

[0060] In this embodiment of the invention, a mapping relationship between business scenarios, interface services, and business terminal information is constructed based on multiple business scenarios, the corresponding interface services for each business scenario, and the corresponding business terminal information for each business scenario; a scenario interface relationship table is constructed based on multiple mapping relationships. For example, the scenario interface relationship table is shown in Table 1:

[0061] Table 1

[0062] In this system, there is a one-to-one correspondence between business scenarios, interface services, business personnel, and their email addresses. For example, the business scenario "My Profile - Face Recognition Service - Collection" corresponds to the interface service "Prequery+Compare", the corresponding business personnel is "User A", and the corresponding email address is 123@xxx.com; the business scenario "Credit Card - Credit Report - Face Recognition Inquiry" corresponds to the interface service "userInfo+Prequery+Compare", the corresponding business personnel is "User B", and the corresponding email address is 456@xxx.com.

[0063] Step 203: Extract key element combinations from business logs according to preset key element identifiers.

[0064] In this embodiment of the invention, the key element identifiers can be set according to actual needs, and this embodiment of the invention does not limit this. As an optional solution, the key element identifiers include channel identifiers, region identifiers, device identifiers, service method identifiers, and exception code identifiers.

[0065] In this embodiment of the invention, data is extracted from the business logs according to the key element identifiers to obtain the key element combinations corresponding to the key element identifiers. Specifically, fields in the business logs are matched according to the key element identifiers to obtain key element combinations. For example: matching the channel identifier (chn) from the business logs yields channel number 01; matching the region identifier (trxzone) from the business logs yields region number AA; matching the device identifier (DEVICEID) from the business logs yields device number 123; matching the service method identifier (ServiceName) from the business logs yields service method name Compare; and matching the exception code identifier (excode) from the business logs yields exception code 1. The key element combinations are shown in Table 2.

[0066] Table 2

[0067] In this system, there is a one-to-one correspondence between the business scenario, the combination of key elements, the business personnel, and their email addresses. For example, the key element combination for the business scenario "My Profile - Personal Information - Face Recognition Service - Collection" is "01+AA+123+Compare+1", the corresponding business personnel is "User A", and the corresponding email address is 123@xxx.com; the key element combination for the business scenario "Credit Card - Credit Report - Face Recognition Inquiry" is "02+AA+456+Compare+0", the corresponding business personnel is "User B", and the corresponding email address is 456@xxx.com.

[0068] Since public application logs do not record the scenarios of access channels, it is necessary to extract key elements from business logs to map business scenarios to key elements. The business logs are then used to determine whether a certain business scenario of the channel is covered. The combination of key elements includes exception code, which facilitates the statistical analysis of business scenarios that have failed to be covered, thereby making it convenient and efficient to filter out uncovered business scenarios.

[0069] Step 204: Based on the combination of key elements and the scenario interface relationship table, construct a full-link business scenario linkage list.

[0070] In this embodiment of the invention, the key element combination includes a channel number, a region number, a device number, a service method name, and an exception code. The channel number represents the channel through which the business is processed, the region number represents the region where the business is processed, the device number represents the device used for the business processing, the service method name represents the service method called during the business processing, and the exception code represents either a successful overwrite flag (1) or a failed overwrite flag (0).

[0071] In this invention, step 204 specifically includes:

[0072] Step 2041: Match the service method name with the interface service to obtain the business scenario and business terminal information corresponding to the key element combination.

[0073] In this embodiment of the invention, the service method name is matched with multiple interface services in the scenario interface relationship table to match the corresponding business scenario and business terminal information; the business scenario and business terminal information correspond to the service method name, that is, there is a one-to-one correspondence between the key element combination, interface service, business scenario and business terminal information where the service method name is located.

[0074] Step 2042: Generate a full-link business scenario linkage list based on the combination of key elements, the corresponding business scenarios, business terminal information, and the corresponding interface services.

[0075] In this embodiment of the invention, a mapping relationship is constructed between key element combinations, business scenarios, interface services, and business terminal information corresponding to each key element combination. Based on these mapping relationships, a full-link business scenario linkage list is generated. For example, the full-link business scenario linkage list is shown in Table 3.

[0076] Table 3

[0077] In this system, there is a one-to-one correspondence between business scenarios, key element combinations, interface services, business personnel, and business personnel email addresses. For example, the key element combination for the business scenario "My Profile - Personal Information - Face Recognition Service - Collection" is "01+AA+123+Compare+1", the corresponding interface service is "Compare", the corresponding business personnel is "User A", and the corresponding business personnel email address is 123@xxx.com; the key element combination for the business scenario "Credit Card - Credit Report - Face Recognition Inquiry" is "02+AA+456+Compare+0", the corresponding interface service is "Compare", the corresponding business personnel is "User B", and the corresponding business personnel email address is 456@xxx.com.

[0078] In this embodiment of the invention, the exception code includes a successful overwrite flag (1) or a failed overwrite flag (0).

[0079] Furthermore, by using the full-link business scenario linkage list, the business terminal information corresponding to the coverage failure identifier can be queried, that is: filtering out the business personnel and their email addresses corresponding to the business scenarios with an exception code of 0; and sending a coverage failure warning message to the business terminal indicated by the queried business terminal information, that is: sending a warning message to the business personnel's email address to notify the business personnel that the coverage of the business scenario has failed.

[0080] Step 205: Obtain the file information of the updated patch file, which includes the update field, deployment time, and delivery time.

[0081] In this embodiment of the invention, the updated patch file is a patch file that has been deployed on the application. The file information includes, but is not limited to, update fields, deployment time, and delivery time. The update fields are the fields updated in the patch file; the deployment time is a fixed time when the patch file is delivered to the data center for user access; and the delivery time is the time the updated patch file is received.

[0082] Step 206: Match the updated fields with the interface service to obtain the corresponding business scenario.

[0083] Specifically, the updated field is matched with the interface services in the full-link business scenario linkage list to identify the corresponding business scenario. Taking the full-link business scenario linkage list shown in Table 3 as an example, if the updated field is Compare, then Compare is matched with the interface services to filter out all business scenarios that include Compare, namely: "My - Personal Profile - Face Recognition Service - Collection" and "Credit Card - Credit Report - Face Recognition Inquiry".

[0084] Step 207: Send a business scenario coverage test request to the business terminal corresponding to the business scenario, and receive the business scenario coverage test results returned by the business terminal.

[0085] In this embodiment of the invention, the matched business scenario is the scenario where the patch file needs to be tested for successful coverage. Specifically, through the full-link business scenario linkage list, the corresponding business terminal information is matched according to the business scenario to be tested; a business scenario coverage test request is sent to the business terminal indicated by the business terminal information, notifying the business personnel to perform coverage verification of the business scenario to be tested, and the business scenario coverage test result is returned.

[0086] In this embodiment of the invention, the business scenario coverage test results include, but are not limited to, the patch number that uniquely identifies a patch file, the business scenario, the most recent coverage test time, and the test results.

[0087] Furthermore, based on the test results covering multiple business scenarios, a project functional test schedule is generated and visualized. The project functional test schedule includes multiple patch numbers, each corresponding to a business scenario, test results, and the most recent coverage test time. By viewing the project functional test schedule, the project manager can intuitively obtain the test progress and results of each patch in various business scenarios. The performance test results are centralized, facilitating project management.

[0088] Furthermore, the testing results of the scenarios are analyzed, including the time differences in testing across different channels and the richness of business scenarios, in order to optimize the list of linked tasks.

[0089] The time differences in testing across channels are primarily statistically analyzed using the test times of each patch in the task list. By analyzing these time differences, the testing progress and style of the business lead can be determined, allowing for the creation of precise testing style profiles for project team members, thereby achieving better project organization. As an optional solution, through... For each business scenario, the test time, total number of business scenarios, verification time of business personnel, and number of scenarios currently being tested are calculated to obtain the current channel test profile score. A higher profile score indicates a more proactive testing style among the business personnel of that channel; a lower profile score indicates a more passive testing style. Here, T represents the average test time for each business scenario, and T0 represents the average test time for each business scenario. i Let S be the test time for the i-th business scenario, n be the total number of business scenarios, P be the current channel test profile score, and S be the test time for the i-th business scenario. j Let k be the verification time for the j-th business person, and k be the number of scenarios currently being tested.

[0090] The richness of test business scenarios is primarily assessed through a scenario statistics list. The business scenarios for each channel and each task activation differ. By analyzing the richness of these scenarios, key channels and scenarios can be identified, enabling precise positioning and analysis of project priorities. As an alternative solution, [further details can be added]. The business scenario richness is calculated by analyzing the current channel test profile score, each business scenario, and the number of times each business scenario is invoked. Here, P represents the current channel test profile score, n represents the total number of business scenarios, and X represents the total number of business scenarios. i For the i-th business scenario, W i Let Q be the number of times the i-th business scenario is invoked, and let Q be the richness of the business scenarios.

[0091] Step 208: Determine if the most recent coverage test time is less than the delivery time. If yes, proceed to step 209; otherwise, proceed to step 210.

[0092] Specifically, if the most recent coverage test time is less than the delivery time, it indicates that the business scenario has not been covered after the patch file was delivered, and step 209 continues; if the most recent coverage test time is greater than or equal to the delivery time, it indicates that the business scenario has been covered after the patch file was delivered, and step 210 continues.

[0093] Step 209: Send a warning message about coverage failure to the business terminal corresponding to the business scenario, and the process ends.

[0094] In this embodiment of the invention, if the business scenario has not been covered after the patch file is delivered, a warning message indicating the coverage failure is sent to the business terminal indicated by the business terminal information corresponding to the business scenario, that is, a warning message is sent to the email address of the business personnel to notify the business personnel that the coverage of the business scenario has failed.

[0095] Step 210: Deploy the updated patch files according to the deployment time. The process ends.

[0096] In this embodiment of the invention, if the business scenario has undergone coverage testing after the patch file is delivered, it indicates that the business scenario has passed the test. The updated patch file is then deployed to production according to the production deployment time and subsequently made available for users to install and use.

[0097] It is worth noting that the acquisition, storage, use, and processing of data in the technical solution of this application all comply with relevant laws and regulations. The user information in the embodiments of this application was obtained through legal and compliant means, and the acquisition, storage, use, and processing of user information have been authorized and agreed upon by the users.

[0098] The technical solution of the end-to-end business scenario coverage testing method provided in this embodiment of the invention involves obtaining file information of the updated patch file, including update fields; querying the corresponding business scenario based on the update fields using a pre-built end-to-end business scenario linkage list; sending a business scenario coverage test request to the business terminal corresponding to the business scenario and receiving the business scenario coverage test results returned by the business terminal; constructing an end-to-end business scenario linkage list; and automatically calling the business terminal to perform business scenario coverage testing. This approach can improve the comprehensiveness and accuracy of coverage testing, increase testing efficiency, reduce the timeliness requirements for testing by business personnel, and thus reduce application performance risks.

[0099] Figure 3 This is a schematic diagram of a coverage testing device for a full-link service scenario provided in an embodiment of the present invention. This device is used to execute the coverage testing method for the aforementioned full-link service scenario. Figure 3 As shown, the device includes: a file information acquisition unit 11, a business scenario query unit 12, and a sending and receiving unit 13.

[0100] The file information acquisition unit 11 is used to acquire the file information of the updated patch file, including the update field.

[0101] The business scenario query unit 12 is used to query the corresponding business scenario based on the updated field by using a pre-built full-link business scenario linkage list.

[0102] The transceiver unit 13 is used to send a business scenario coverage test request to the business terminal corresponding to the business scenario, and to receive the business scenario coverage test result returned by the business terminal.

[0103] In this embodiment of the invention, the device further includes: a business information acquisition unit 14, a relationship table construction unit 15, an extraction unit 16, and a list construction unit 17.

[0104] The business information acquisition unit 14 is used to acquire business logs, interface services corresponding to each business scenario, and business terminal information.

[0105] The relationship table construction unit 15 is used to construct a scenario interface relationship table based on each business scenario, the corresponding interface service, and business terminal information.

[0106] Extraction unit 16 is used to extract key element combinations from business logs according to preset key element identifiers.

[0107] List building unit 17 is used to build a full-link business scenario linkage list based on the combination of key elements and the scenario interface relationship table.

[0108] In this embodiment of the invention, the key element combination includes channel number, region number, device number, service method name, and exception code; the list construction unit 17 is specifically used to match the service method name with the interface service to obtain the business scenario and business terminal information corresponding to the key element combination; and generate a full-link business scenario linkage list based on the key element combination, the corresponding business scenario, the business terminal information, and the corresponding interface service.

[0109] In this embodiment of the invention, the exception code includes a successful overwrite flag or a failed overwrite flag; the device also includes a business terminal query unit 18.

[0110] The business terminal query unit 18 is used to query the business terminal information corresponding to the coverage failure identifier through the full-link business scenario linkage list.

[0111] The transceiver unit 13 is also used to send a warning message of coverage failure to the service terminal indicated by the queried service terminal information.

[0112] In this embodiment of the invention, the full-link business scenario linkage list includes multiple business scenarios and the interface service corresponding to each business scenario; the business scenario query unit 12 is specifically used to match the update field with the interface service to obtain the corresponding business scenario.

[0113] In this embodiment of the invention, the file information also includes the production launch time and delivery time, and the business scenario coverage test results include the most recent coverage test time; the device also includes: a judgment unit 19 and a production launch unit 20.

[0114] The judgment unit 19 is used to determine whether the most recent coverage test time is less than the delivery time.

[0115] The transceiver unit 13 is also used to send a warning message about coverage failure to the business terminal corresponding to the business scenario if the most recent coverage test time is less than the delivery time.

[0116] Production unit 20 is used to produce updated patch files according to the production time if the most recent coverage test time is greater than or equal to the delivery time.

[0117] In this embodiment of the invention, the device further includes a schedule generation unit 21 and a visualization unit 22.

[0118] The schedule generation unit 21 is used to generate a project functional test schedule based on the test results of multiple business scenarios.

[0119] Visualization unit 22 is used to visualize the project's functional testing schedule.

[0120] In the solution of this embodiment of the invention, the file information of the updated patch file is obtained, and the file information includes the update field; the corresponding business scenario is queried according to the update field by using a pre-built full-link business scenario linkage list; a business scenario coverage test request is sent to the business terminal corresponding to the business scenario, and the business scenario coverage test result returned by the business terminal is received; a full-link business scenario linkage list is constructed, and the business terminal is called to automatically perform business scenario coverage testing, which can improve the comprehensiveness and accuracy of coverage testing, improve testing efficiency, reduce the timeliness requirements of business personnel for testing, and thus reduce the performance risk of the application.

[0121] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer device, specifically, a computer device can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or any combination of these devices.

[0122] This invention provides a computer device, including a memory and a processor. The memory is used to store information including program instructions, and the processor is used to control the execution of the program instructions. When the program instructions are loaded and executed by the processor, they implement the steps of the embodiment of the coverage testing method for the above-described full-link business scenario. For a detailed description, please refer to the embodiment of the coverage testing method for the above-described full-link business scenario.

[0123] The following is for reference. Figure 4 It shows a schematic diagram of the structure of a computer device 600 suitable for implementing the embodiments of this application.

[0124] like Figure 4As shown, the computer device 600 includes a central processing unit (CPU) 601, which can perform various appropriate tasks and processes based on programs stored in read-only memory (ROM) 602 or programs loaded from storage section 608 into random access memory (RAM) 603. The RAM 603 also stores various programs and data required for the operation of the computer device 600. The CPU 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0125] The following components are connected to I / O interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including a cathode ray tube (CRT), liquid crystal feedback (LCD), etc., and speakers, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to I / O interface 605 as needed. A removable medium 611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 610 as needed so that computer programs read from it can be installed in storage section 608 as needed.

[0126] In particular, according to embodiments of the present invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of the present invention include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program including program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 609, and / or installed from removable medium 611.

[0127] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0128] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

[0129] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0130] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0131] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0132] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0133] The acquisition, storage, use, and processing of data in this application comply with relevant laws and regulations.

[0134] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0135] This application can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0136] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0137] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A coverage testing method for a full-link business scenario, characterized in that, The method includes: Obtain the file information of the updated patch file, including the update field; By using a pre-built list of interconnected full-link business scenarios, the corresponding business scenarios can be queried based on the updated fields. Send a business scenario coverage test request to the business terminal corresponding to the business scenario, and receive the business scenario coverage test results returned by the business terminal; Before retrieving the corresponding business scenario based on the updated field from the pre-built full-link business scenario linkage list, the process also includes: Obtain business logs, interface services corresponding to various business scenarios, and business terminal information; Based on each business scenario, the corresponding interface service, and the business terminal information, a mapping relationship is constructed between the business scenario, the interface service, and the business terminal information; based on multiple mapping relationships, a scenario interface relationship table is constructed. Based on preset key element identifiers, extract key element combinations from the business logs; the key element combinations include exception codes; the exception codes include overwrite success indicators or overwrite failure indicators. Based on the combination of key elements and the scenario interface relationship table, construct the full-link business scenario linkage list; The method further includes: By using the full-link business scenario linkage list, the business terminal information corresponding to the coverage failure identifier can be queried; Send a warning message about coverage failure to the service terminal indicated by the queried service terminal information.

2. The coverage testing method for the entire business scenario according to claim 1, characterized in that, The key element combination includes channel number, region number, device number, and service method name; The step of constructing the full-link business scenario linkage list based on the key element combination and scenario interface relationship table includes: The service method name is matched with the interface service to obtain the business scenario and business terminal information corresponding to the key element combination; Based on the combination of key elements, the corresponding business scenarios, business terminal information, and the corresponding interface services, a full-link business scenario linkage list is generated.

3. The coverage testing method for the entire business scenario according to claim 1, characterized in that, The full-link business scenario linkage list includes multiple business scenarios and the corresponding interface services for each business scenario; The step of querying the corresponding business scenario based on the updated field from a pre-built list of full-link business scenarios includes: The updated field is matched with the interface service to obtain the corresponding business scenario.

4. The coverage testing method for the entire service scenario according to claim 1, characterized in that, The document information also includes the production launch time and delivery time, and the business scenario coverage test results include the most recent coverage test time; After receiving the service scenario coverage test results returned by the service terminal, the method further includes: Determine whether the most recent coverage test time is less than the delivery time; If so, send a warning message about coverage failure to the business terminal corresponding to the business scenario; If not, the updated patch file shall be put into production according to the stated production time.

5. The coverage testing method for the entire service scenario according to claim 1, characterized in that, After receiving the service scenario coverage test results returned by the service terminal, the method further includes: Generate a project functional test schedule based on the test results covering multiple business scenarios. The project's functional testing progress schedule is visualized.

6. A coverage testing device for a full-link business scenario, characterized in that, The device includes: The file information acquisition unit is used to acquire the file information of the updated patch file, the file information including the update field; The business scenario query unit is used to query the corresponding business scenario based on the updated field by using a pre-built full-link business scenario linkage list; The transceiver unit is used to send a business scenario coverage test request to the business terminal corresponding to the business scenario, and to receive the business scenario coverage test result returned by the business terminal. The business information acquisition unit is used to acquire business logs, interface services corresponding to various business scenarios, and business terminal information. The relationship table construction unit is used to construct the mapping relationship between the business scenario, the interface service, and the business terminal information according to each business scenario, the corresponding interface service, and the business terminal information; and to construct a scenario interface relationship table based on multiple mapping relationships. The extraction unit is used to extract key element combinations from business logs according to preset key element identifiers; the key element combinations include exception codes; the exception codes include overwrite success identifiers or overwrite failure identifiers; The list building unit is used to build a full-link business scenario linkage list based on the combination of key elements and the scenario interface relationship table; This also includes: The business terminal query unit is used to query the business terminal information corresponding to the coverage failure identifier through the full-link business scenario linkage list; The transceiver unit is also used to send a warning message about coverage failure to the service terminal indicated by the queried service terminal information.

7. A computer-readable medium having a computer program stored thereon, characterized in that, When executed by the processor, the program implements the full-link service scenario coverage testing method as described in any one of claims 1 to 5.

8. A computer device comprising a memory and a processor, the memory for storing information including program instructions, and the processor for controlling the execution of the program instructions, characterized in that, When the program instructions are loaded and executed by the processor, they implement the full-link service scenario coverage testing method as described in any one of claims 1 to 5.

9. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instruction is executed by the processor, it implements the full-link service scenario coverage testing method as described in any one of claims 1 to 5.

Images