Business verification method and device, electronic equipment and computer readable medium

Abstract

The invention discloses a service verification method and device, electronic equipment and a computer readable medium, and relates to the technical field of computers, and the method comprises the steps: receiving a service verification request, obtaining a test scene identifier, and generating a service verification task; obtaining a business verification keyword portrait corresponding to the test scene identifier, identifying meaningless words in a business verification step, dividing the business verification step based on the meaningless words, obtaining each segmented word, matching each segmented word with each tag in the business verification keyword portrait, and determining the matched tag as a keyword in the business verification step; determining an operation type based on the keyword; according to the operation type and the business verification step, simulating user operation to execute a business verification task, and obtaining execution result data; if the execution result data corresponds to business verification failure, obtaining a verification failure step identifier; and sending the verification failure step identifier to the target service processing node. And the service verification efficiency and the accuracy of the service verification result are improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a business verification method, device, electronic device and computer-readable medium. Background Art

[0002] In the field of disaster recovery switchover drill business verification, disaster recovery switchover drills are a key step to ensure business continuity and are crucial to verifying the effectiveness of the disaster recovery system. The drill process is usually divided into five stages: pre-switch preparation, switchover, switchover verification, switchback, and switchback verification. Switchover and switchback verification are further divided into technical verification and business verification. Business verification is crucial in disaster switchover drills. It not only tests the effectiveness of the technical disaster switchover tool system and the switchover plan, but also comprehensively evaluates business continuity and the stability of disaster switchover. However, business verification in traditional drills mainly relies on manual operation of business systems, which has low efficiency and poor consistency of results. Summary of the invention

[0003] In view of this, the embodiments of the present application provide a business verification method, device, electronic device and computer-readable medium, which can solve the problem that business verification in existing traditional drills mainly relies on manual operation of the business system, with low efficiency and poor result consistency.

[0004] To achieve the above-mentioned purpose, according to one aspect of an embodiment of the present application, a business verification method is provided, including: receiving a business verification request, obtaining a corresponding test scenario identifier, and then generating a corresponding business verification task; extracting keywords in a business verification step corresponding to the business verification task, and determining an operation type based on the keywords; extracting keywords in a business verification step corresponding to the business verification task, including: obtaining a business verification keyword portrait corresponding to the test scenario identifier, identifying meaningless words in the business verification step, dividing the business verification step based on the meaningless words to obtain each participle, matching each participle with each label in the business verification keyword portrait, and then determining the label in the matched business verification keyword portrait as the keyword in the business verification step corresponding to the business verification task; simulating user operations according to the operation type and the corresponding business verification step to execute the business verification task, and then obtaining execution result data; in response to the execution result data corresponding to a business verification failure, obtaining a corresponding verification failure step identifier; and sending the verification failure step identifier to a target business processing node.

[0005] Optionally, generating a corresponding business verification task includes: determining a corresponding business verification step according to a test scenario identifier; and generating a corresponding single business verification task based on each business verification step.

[0006] Optionally, extracting keywords in a business verification step corresponding to the business verification task includes: identifying action words in the business verification step corresponding to the business verification task, determining the action words as keywords in the business verification step corresponding to the business verification task; and extracting keywords.

[0007] Optionally, determining the operation type according to the keywords includes: clustering the keywords to obtain clusters; and determining the operation type based on the clusters.

[0008] Optionally, according to the operation type and the corresponding business verification steps, user operations are simulated to perform business verification tasks, and then execution result data is obtained, including: determining the target operation location according to the business verification steps corresponding to the operation type; executing the operation method corresponding to the operation type at the target operation location to simulate user operations, perform business verification tasks, and obtain execution result data.

[0009] Optionally, the method further includes: automatically generating a business verification report according to a specific template based on the execution result data, and visually displaying the business verification report in real time.

[0010] In addition, the present application also provides a business verification device, including: a receiving unit, configured to receive a business verification request, obtain a corresponding test scenario identifier, and then generate a corresponding business verification task; an extraction unit, configured to extract keywords in a business verification step corresponding to the business verification task, and determine the operation type based on the keywords; extracting keywords in a business verification step corresponding to the business verification task, including: obtaining a business verification keyword portrait corresponding to the test scenario identifier, identifying meaningless words in the business verification step, dividing the business verification step based on the meaningless words to obtain each participle, matching each participle with each label in the business verification keyword portrait, and then determining the label in the matched business verification keyword portrait as the keyword in the business verification step corresponding to the business verification task; a simulation unit, configured to simulate user operations to execute the business verification task according to the operation type and the corresponding business verification step, and then obtain execution result data; an acquisition unit, configured to obtain a corresponding verification failure step identifier in response to the execution result data corresponding to a business verification failure; a sending unit, configured to send the verification failure step identifier to a target business processing node.

[0011] Optionally, the receiving unit is further configured to: determine a corresponding business verification step according to the test scenario identifier; and generate a corresponding single business verification task based on each business verification step.

[0012] Optionally, the extraction unit is further configured to: identify action words in the business verification step corresponding to the business verification task, determine the action words as keywords in the business verification step corresponding to the business verification task; and extract keywords.

[0013] Optionally, the extraction unit is further configured to: cluster the keywords to obtain clusters; and determine the operation type based on the clusters.

[0014] Optionally, the simulation unit is further configured to: determine the target operation position according to the business verification step corresponding to the operation type; execute the operation method corresponding to the operation type at the target operation position to simulate the user operation, perform the business verification task, and obtain the execution result data.

[0015] Optionally, the device further comprises a report generating unit configured to: automatically generate a business verification report according to a specific template based on the execution result data, and visually display the business verification report in real time.

[0016] In addition, the present application also provides a business verification electronic device, including: one or more processors; a storage device for storing one or more programs, when the one or more programs are executed by one or more processors, the one or more processors implement the business verification method as described above.

[0017] In addition, the present application also provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, the business verification method as described above is implemented.

[0018] To achieve the above objective, according to another aspect of the embodiments of the present application, a computer program product is provided.

[0019] A computer program product according to an embodiment of the present application includes a computer program, and when the program is executed by a processor, the service verification method provided by the embodiment of the present application is implemented.

[0020] An embodiment of the above invention has the following advantages or beneficial effects: the application receives a business verification request, obtains a corresponding test scenario identifier, and then generates a corresponding business verification task; extracts keywords in the business verification step corresponding to the business verification task, and determines the operation type based on the keywords; extracts keywords in the business verification step corresponding to the business verification task, including: obtaining a business verification keyword portrait corresponding to the test scenario identifier, identifying meaningless words in the business verification step, dividing the business verification step based on the meaningless words to obtain each segmented word, matching each segmented word with each label in the business verification keyword portrait, and then determining the matched label in the business verification keyword portrait as the keyword in the business verification step corresponding to the business verification task; according to the operation type and the corresponding business verification step, simulates the user operation to execute the business verification task, and then obtains the execution result data; in response to the execution result data corresponding to the business verification failure, obtains the corresponding verification failure step identifier; and sends the verification failure step identifier to the target business processing node. Thereby improving the efficiency of business verification and the accuracy of business verification results.

[0021] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with the specific implementation manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The accompanying drawings are used to better understand the present application and do not constitute an improper limitation on the present application.

[0023] Figure 1 It is a schematic diagram of the main process of the service verification method according to an embodiment of the present application;

[0024] Figure 2 It is a schematic diagram of the main process of the service verification method according to an embodiment of the present application;

[0025] Figure 3 This is a schematic diagram of the association relationship between a business verification case and an RPA script according to a business verification method of an embodiment of the present application;

[0026] Figure 4 is a schematic diagram of an automated business verification function of a business verification method according to an embodiment of the present application;

[0027] Figure 5 It is a schematic diagram of automated business verification data flow of a business verification method according to an embodiment of the present application;

[0028] Figure 6 is a schematic diagram of the main units of the service verification device according to an embodiment of the present application;

[0029] Figure 7 is an exemplary system architecture diagram to which the embodiments of the present application can be applied;

[0030] Figure 8 It is a structural diagram of a computer system of a terminal device or server suitable for implementing an embodiment of the present application. DETAILED DESCRIPTION

[0031] The following is a description of the exemplary embodiments of the present application in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding, and they should be considered as merely exemplary. Therefore, those of ordinary skill in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. Similarly, for the sake of clarity and conciseness, the description of known functions and structures is omitted in the following description. It should be noted that the acquisition, transmission, storage, use, and processing of data in the technical solution of the present application are in compliance with the relevant provisions of national laws and regulations. It should be noted that in the embodiments of the present application, certain software, components, models, and other existing solutions in the industry may be mentioned, which should be considered as exemplary, and their purpose is only to illustrate the feasibility of the implementation of the technical solution of the present application, but it does not mean that the applicant has or must have used the solution. In the technical solution of the present application, the collection, analysis, use, transmission, storage, and other aspects of the user's personal information involved are in compliance with the provisions of relevant laws and regulations, and are used for legal and reasonable purposes, and are not shared, leaked, or sold outside of these legal uses, and are subject to supervision and management by regulatory authorities. Take necessary measures to prevent illegal access to such personal information, ensure that persons with access to personal information comply with relevant laws and regulations, and ensure the security of personal information. Once such personal information is no longer needed, risks should be minimized by limiting or even prohibiting data collection and / or deleting data.

[0032] When used, including in certain related applications, user privacy is protected by de-identifying data, such as by removing specific identifiers when used, controlling the amount or specificity of data stored, controlling how data is stored, and / or other methods of de-identification.

[0033] Figure 1 is a schematic diagram of the main process of the service verification method according to an embodiment of the present application, such as Figure 1 As shown, the service verification method mainly includes the following steps S101 to S105.

[0034] Step S101, receiving a business verification request, obtaining a corresponding test scenario identifier, and then generating a corresponding business verification task.

[0035] In this embodiment, the execution subject of the business verification method (for example, a server) can receive a business verification request through a wired connection or a wireless connection. After receiving the business verification request, the execution subject can obtain the test scenario identifier carried in the request. The test scenario identifier is used to characterize the business verification scenario. The execution subject can configure a series or parallel business verification case according to the business verification scenario corresponding to the test scenario identifier to obtain a business verification solution. The corresponding business verification task is generated according to the obtained business verification solution, thereby improving the accuracy of the generated business verification task.

[0036] Step S102, extracting keywords in the business verification step corresponding to the business verification task, and determining the operation type based on the keywords; extracting keywords in the business verification step corresponding to the business verification task, including: obtaining a business verification keyword portrait corresponding to the test scenario identifier, identifying meaningless words in the business verification step, dividing the business verification step based on the meaningless words to obtain each participle, matching each participle with each label in the business verification keyword portrait, and then determining the label in the matched business verification keyword portrait as the keyword in the business verification step corresponding to the business verification task.

[0037] The business verification scheme includes multiple business verification cases in series or in parallel. Each business verification case may correspond to a business verification step. Each business verification step generates a corresponding single business verification task according to parameters. The execution subject may extract keywords in the business verification step corresponding to the business verification task, for example, the verbs included in the business verification step corresponding to the business verification task.

[0038] In some embodiments, the execution subject can obtain the business verification keyword portrait corresponding to the test scenario identifier, and the business verification keyword portrait is used to characterize the correspondence between business data and keyword tags. After determining the business verification step corresponding to the business verification task, the execution subject can identify the meaningless words in the business verification step, delete each meaningless word from the business verification step, and display the position of each meaningless word deleted in the business verification step as a space, and use each space as a boundary to divide the business verification step after deleting each meaningless word to obtain each participle, so that each participle obtained is more accurate and more practical, avoiding the waste of meaningless computing resources, and facilitating more accurate business verification. After obtaining each participle, the execution subject can match each participle with each tag in the business verification keyword portrait for semantic similarity, and the obtained similarity can be cosine similarity, and the tag in the business verification keyword portrait corresponding to the similarity greater than the preset threshold is determined as the tag in the matched business verification keyword portrait, that is, the keyword in the business verification step corresponding to the business verification task.

[0039] Specifically, determining the operation type according to the keywords includes: clustering the keywords to obtain clusters; and determining the operation type based on the clusters.

[0040] Multiple keywords can correspond to the same operation type, such as add, delete, modify, and query, which correspond to the same operation type: click operation. Operation types can also include scrolling operations, form filling operations, etc. The embodiments of the present application do not specifically limit the operation types. By clustering each keyword based on the preset operation type, the operation type corresponding to the operation required for the business verification task can be accurately obtained, so as to facilitate the loading of related resources in advance and improve the efficiency of business verification.

[0041] Step S103, according to the operation type and the corresponding business verification step, simulate the user operation to perform the business verification task, and then obtain the execution result data.

[0042] Specifically, according to the operation type and the corresponding business verification steps, the user operation is simulated to perform the business verification task, and then the execution result data is obtained, including: according to the business verification steps corresponding to the operation type, the target operation position is determined; at the target operation position, the operation method corresponding to the operation type is executed to simulate the user operation, perform the business verification task, and obtain the execution result data.

[0043] For example, the operation type may be a click operation, the target operation position may be the position of S on the page, and the operation method corresponding to the operation type may be a click() method. Simulating user operation is to simulate the execution of the click() method at the position of S on the page to complete the click operation on the position of S on the page. By simulating user operation, the effectiveness of the technical disaster switching tool system and the switching plan can be tested, and the stability of business continuity and disaster switching can be more comprehensively evaluated.

[0044] Step S104, in response to the execution result data corresponding to the business verification failure, obtaining the corresponding verification failure step identifier.

[0045] When the business verification of the simulated user operation fails, the verification failure step identifier is obtained to determine the failed step and related business information.

[0046] Step S105: Send the verification failure step identifier to the target business processing node.

[0047] The verification failed step identifier is sent to the target business processing node to help business optimization.

[0048] This embodiment receives a business verification request, obtains a corresponding test scenario identifier, and then generates a corresponding business verification task; extracts keywords in the business verification step corresponding to the business verification task, and determines the operation type based on the keywords; simulates user operations according to the operation type and the corresponding business verification step to perform the business verification task, and then obtains execution result data; in response to the execution result data corresponding to the business verification failure, obtains the corresponding verification failure step identifier; and sends the verification failure step identifier to the target business processing node. This improves the business verification efficiency and the accuracy of the business verification results.

[0049] Figure 2 is a schematic diagram of the main process of a service verification method according to an embodiment of the present application, such as Figure 2 As shown, the service verification method mainly includes the following steps S201 to S207.

[0050] Step S201, receiving a service verification request and obtaining a corresponding test scenario identifier.

[0051] Step S202: Determine the corresponding service verification step according to the test scenario identifier.

[0052] The execution subject may call the business verification manual to determine the corresponding execution steps in the business verification manual according to the test scenario corresponding to the test scenario identifier, and the execution steps include one or more business verification steps.

[0053] For example, the test scenario corresponding to the test scenario identifier may be a bill financing application, and the corresponding execution steps in the business verification manual may be: Step 1, dealer account login; Step 2, dealer fills in the bill financing application information; Step 3, financing application submission. The above steps 1, 2, and 3 are the business verification steps.

[0054] Step S203: Based on each business verification step, a corresponding single business verification task is generated.

[0055] The execution entity can improve the efficiency and accuracy of business verification by generating a corresponding single business verification task for each business verification step.

[0056] Step S204, extracting keywords in the business verification step corresponding to the business verification task, and determining the operation type based on the keywords; extracting keywords in the business verification step corresponding to the business verification task, including: obtaining a business verification keyword portrait corresponding to the test scenario identifier, identifying meaningless words in the business verification step, dividing the business verification step based on the meaningless words to obtain each participle, matching each participle with each label in the business verification keyword portrait, and then determining the label in the matched business verification keyword portrait as the keyword in the business verification step corresponding to the business verification task.

[0057] The executing entity can first embed each word segmentation to obtain each word segmentation vector, and calculate the label vector corresponding to each label in the business verification keyword portrait, calculate the cosine similarity of each word segmentation vector with each label vector respectively, to obtain each cosine similarity, and determine the label corresponding to the label vector corresponding to the cosine similarity greater than the preset similarity threshold as the keyword in the business verification step, thereby improving the efficiency and accuracy of extracting the keywords in the business verification step.

[0058] Specifically, extracting keywords in the business verification step corresponding to the business verification task includes: identifying action words in the business verification step corresponding to the business verification task, determining the action words as keywords in the business verification step corresponding to the business verification task; and extracting keywords.

[0059] In some embodiments, the executing entity may also perform word segmentation processing on the business verification step to obtain individual word segments; calculate the similarity between each word segment and the name of a preset operation type to obtain each similarity, and determine the word segment corresponding to the similarity greater than a preset threshold as a keyword in the business verification step, so as to accurately extract the keyword and accurately determine the operation type corresponding to the keyword at the same time, thereby improving the accuracy of business verification.

[0060] Step S205 , according to the operation type and the corresponding business verification step, simulate the user operation to execute the business verification task, and then obtain the execution result data.

[0061] For example, the operation type may be a sliding operation, the target operation position may be the position where T of the page is located, and the operation method corresponding to the operation type may be a swipe() method. Simulating user operation is to simulate the execution of the swipe() method at the T position of the page to complete the sliding operation at the T position of the page. By simulating user operation, the effectiveness of the technical disaster switching tool system and the switching plan can be tested, and the stability of business continuity and disaster switching can be more comprehensively evaluated.

[0062] Step S206, in response to the execution result data corresponding to the business verification failure, obtain the corresponding verification failure step identifier.

[0063] Step S207: Send the verification failure step identifier to the target business processing node.

[0064] Specifically, the method also includes: automatically generating a business verification report according to a specific template based on the execution result data, and visually displaying the business verification report in real time.

[0065] For example, the result summary and drill report: The result summary module centrally summarizes and displays the overall execution results of the business verification plan, allowing personnel to count the verification status of the corresponding plan, and automatically generates a drill report (i.e., business verification report) according to a specific template, and provides the display, export, and download functions of the drill report (i.e., business verification report).

[0066] Figure 3 This is a schematic diagram of the association between business verification cases and RPA scripts according to a business verification method according to an embodiment of the present application.

[0067] The embodiment of the present application uses robotic process automation (RPA) technology to implement an automated business verification method during a disaster recovery switching drill, which is used to improve the automated business verification capabilities of disaster recovery switching drills in the financial industry. Disaster recovery switching drills are a key step in ensuring business continuity and are crucial to verifying the effectiveness of the disaster recovery system. The drill process is usually divided into five stages: pre-switching preparation, tangent, tangent verification, back-cut, and back-cut verification. Among them, tangent and back-cut verification are further subdivided into technical verification and business verification. Business verification is crucial in disaster switching drills. It not only tests the effectiveness of the technical disaster switching tool system and switching plan, but also comprehensively evaluates business continuity and the stability of disaster switching. The embodiment of the present application uses RPA technology to convert manual business verification operation case codes into RPA execution scripts to achieve business verification, and also combines automatic execution scheduling engines and process orchestration to achieve automated, visual, and controllable execution.

[0068] The embodiment of the present application uses RPA technology to achieve automated business verification after the disaster recovery switch drill. A standardized verification case library is used to compile RPA scripts, which are interpreted and executed by the RPA executor using the disaster recovery automation execution engine. The execution engine and the business verification view are combined to achieve automated and visual execution of business verification. A business verification manual is written for business scenarios, a standardized verification process that includes operating guidelines and expected results, to ensure business stability and continuity after the system is switched; according to the business verification manual, RPA scripts are written in python, js and other code languages ​​or according to RPA syntax and configured to the case warehouse; multiple business verification cases are combined in series or parallel into a business verification plan according to the business verification scenario requirements, and verification tasks are generated for the plan. The tasks are executed through the scheduler, and the corresponding RPA scripts are sent to the business verification service; the business verification service simulates user operations and reads page element content through RPA executor decoding, and returns the execution results of the business verification. Business Verification Manual:

[0069] According to the business scenario, a business verification manual is written under the premise of considering automation. A standardized operation guide includes specific operation steps, expected results and other elements for each business, guiding business verification personnel to complete the post-cut system business reliability and stability verification. In the process of writing the verification manual, attention should be paid to clear goals, systematic methods, comprehensive coverage, strong repeatability, traceability, clear language, flexible adaptation to changes, priority processing of high-risk tasks, and other aspects to ensure the professionalism and practicality of the manual. The following table shows an example of a business verification manual:

[0070]

[0071] Case warehouse:

[0072] Developers maintain scripted business verification cases in the case warehouse function module. The script content is developed according to the business verification steps in the business verification manual. The RPA operation script supports multiple languages ​​(Python / JS / Shell). The script content simulates various operations of users in the browser, including clicking, scrolling, filling out forms, etc. These operations are mainly executed by sending corresponding JavaScript commands to the browser. For example, simulating a click can be done by finding a specific location of an element and executing the click() method. The following is an example of the first verification step in the table above:

[0073] Test scenario: Bill financing application

[0074] Main verification channel: broker interface

[0075] Verification purpose: Verify whether the broker can initiate a bill financing application

[0076] Execution steps:

[0077] 1. Broker account login

[0078] 2. Broker fills in bill financing application information

[0079] 3. Submit a financing application

[0080] Expected result: The broker can initiate a financing application normally

[0081] https: / / broker.com / login

[0082] input('username') = 'Broker Username'

[0083] input('password') = 'Broker password'

[0084] Click 'Login'

[0085] / / Fill in the bill financing application information

[0086] input('invoice_number') = 'Invoice number'

[0087] input('amount') = 'Amount'

[0088] select 'currency' = 'RMB'

[0089] click 'Submit'

[0090] / / After switching, verify whether the broker can initiate a financing application

[0091] check text('Financing application has been successfully submitted')

[0092] like Figure 3 As shown in the figure, a verification case is added to the case repository, and the RPA script is maintained in the case accordingly. A verification case in the business verification manual corresponds to an RPA script. The scripts and cases in the business verification case library also have a one-to-one correspondence. For example, verification case 1 corresponds to RPA script 1, verification case 2 corresponds to RPA script 2, and verification case 3 corresponds to RPA script 3.

[0093] Figure 4 FIG. 1 is a schematic diagram of an automated service verification function of a service verification method according to an embodiment of the present application. Figure 4As shown in the figure, after obtaining the business verification document, the execution subject writes the RPA script according to the business verification case and configures it to the case warehouse. The multiple business verification cases in the case warehouse are configured into a business verification scheme in series or parallel according to the business verification scenario requirements. The execution engine schedules the business verification service to execute the business verification scheme according to the serial or parallel arrangement configured in the business verification scheme and obtains the execution result returned by the business verification service, and displays the execution result in the execution view. The business verification service receives the HTTP request sent by the execution engine, schedules the RPA agent to interpret and execute the RPA script corresponding to the business verification scheme corresponding to the serial or parallel orchestrated business verification case, and returns the execution result. The results are summarized based on the execution view and a drill report is generated.

[0094] For example, after configuring the RPA script written according to the business verification case to the case warehouse, the verification plan is executed: This function module uses a list display method. Users can see the current list of all plans. There is a tree classification for different types of plan types on the left, which is convenient for users to view by category. The plan owner who is the current user can view, modify, delete, roll back, and apply for review. The review owner can review. The rest of the plans can only be viewed, and the plans can be defined as invalid or valid. The configuration of the plan mainly includes a three-layer structure of process nodes, steps, and parameters. The configuration of the entire process is completed by adding, deleting, and modifying process nodes, steps, and parameters. Execution view and execution engine: The execution engine executes the scheduling process configured according to the verification plan. Each process node and step have a 1:N correspondence relationship, and each step generates a corresponding single task according to the parameters. The process task execution engine sends the script and parameter initialization HTTP POST request corresponding to the task to the business verification service and obtains the information returned by the verification service execution script. The entire process is executed in accordance with the orchestration string\parallel. At the same time, the task status and return results processed by the process task execution engine are fed back in real time and displayed on the execution view. Business verification service: accepts HTTP requests sent by the execution engine, parses RPA scripts and schedules RPA executors. RPA executors are lightweight implementations of RPA's Python development kit to interpret and execute business verification operation RPA scripts. With the help of Chromium and HTMLXPATH path positioning, web page loading and interaction functions are realized, page content is read, and multiple operations of users in a browser environment, such as clicks, scrolling, and form filling, are simulated. Result overview and drill report: The result summary module centrally summarizes and displays the overall execution results of the business verification plan, so that personnel can count the verification status of the corresponding plan, and automatically generate drill reports according to specific templates, and provide export and download functions for drill reports.

[0095] Figure 5 FIG. 1 is a schematic diagram of automated business verification data flow according to a business verification method according to an embodiment of the present application. Figure 5As shown in the figure, during the automated business verification process, the data flow is as follows:

[0096] ① The business verification view initiates an execution request for the business verification RPA script through the automatic scheduling execution engine.

[0097] ② The channel is sent to the agent with the RPA Python environment package installed, that is, the process task execution engine distributes the request to the agent with the RPA environment, usually the server with the RPA Python environment installed.

[0098] ③The business verification service executes the RPA script, accesses the application system Web front-end interface, and performs business operations.

[0099] ④The business verification service collects the RPA script, reads the browser page elements, obtains the execution results, and executes and returns.

[0100] ⑤The script execution returns, and the business verification service returns the execution result to the execution engine.

[0101] ⑥The execution engine summarizes the results and returns them to the business verification view, providing business verification information.

[0102] The entire process realizes closed-loop automated operations from business verification requests to script execution. RPA (Robotic Process Automation): A software technology that realizes the automated execution of repetitive tasks by simulating human operations. Disaster recovery: Disaster backup and recovery refers to the realization of data recovery and business continuity through pre-established plans and measures when a system fails or a disaster occurs. Business verification: A standardized operation guide includes specific operation steps, expected results and other elements for each business, guiding business verification personnel to complete the post-cut system business reliability and stability verification. The embodiment of the present application simulates manual operations through RPA scripts, does not rely on business system logs, avoids business verification result deviations caused by missing or incomplete logs, and improves the reliability of verification results. Compared with the automated verification method that relies on API interfaces, RPA technology does not need to consider the availability and functional completeness of the interface. Even if the interface is changed or the function is incomplete, the verification can be completed through interface operations, reducing the maintenance cost caused by interface problems. It avoids the risk of data leakage caused by directly reading logs and calling interfaces, improves security, and simplifies permission management by using the permission configuration and management of the business system. Providing a view to display the verification progress and results, the entire verification process can be controlled, simplifying the fault location process when the automated verification fails and improving the efficiency of problem solving. To achieve full process automation of business verification, RPA technology combined with a standardized verification case library supports full process automation execution from disaster recovery to business verification, greatly improving the efficiency and consistency of business verification. Lightweight scripting and multi-language support are adopted to lower the development threshold and improve the reusability and flexibility of scripts. Through the RPA execution channel, RPA scripts can be sent to the agent machine equipped with the RPA environment to achieve automated operations on the application system Web interface, such as simulated clicks and inputs, to collect business verification information and complete automated verification. Combined with a standardized verification case library and solution arrangement design, the lightweight RPA script writing method can quickly respond to the verification requirements of different business scenarios without hard coding. With the help of the RPA Python development kit, the construction of business verification services can be lightweight and can interpret and execute RPA scripts in multiple languages. Through the disaster recovery automated task scheduling engine and automatic and visual execution views, the execution status of each node of the business verification solution is fed back in real time.

[0103] Figure 6 Schematic diagram of the main units of the service verification device according to an embodiment of the present application. Figure 6 As shown, the service verification device 600 includes a receiving unit 601 , an extracting unit 602 , a simulating unit 603 , an acquiring unit 604 and a sending unit 605 .

[0104] The receiving unit 601 is configured to receive a service verification request, obtain a corresponding test scenario identifier, and then generate a corresponding service verification task.

[0105] The extraction unit 602 is configured to extract keywords in the business verification step corresponding to the business verification task, and determine the operation type based on the keywords; extract the keywords in the business verification step corresponding to the business verification task, including: obtaining a business verification keyword portrait corresponding to the test scenario identifier, identifying meaningless words in the business verification step, dividing the business verification step based on the meaningless words to obtain each participle, matching each participle with each label in the business verification keyword portrait, and then determining the label in the matched business verification keyword portrait as the keyword in the business verification step corresponding to the business verification task.

[0106] The simulation unit 603 is configured to simulate the user operation to perform the business verification task according to the operation type and the corresponding business verification step, and then obtain the execution result data.

[0107] The acquisition unit 604 is configured to acquire a corresponding verification failure step identifier in response to the execution result data corresponding to a business verification failure.

[0108] The sending unit 605 is configured to send the verification failure step identifier to the target service processing node.

[0109] In some embodiments, the receiving unit 601 is further configured to: determine a corresponding business verification step according to the test scenario identifier; and generate a corresponding single business verification task based on each business verification step.

[0110] In some embodiments, the extraction unit 602 is further configured to: identify action words in the business verification step corresponding to the business verification task, determine the action words as keywords in the business verification step corresponding to the business verification task; and extract keywords.

[0111] In some embodiments, the extraction unit 602 is further configured to: cluster the keywords to obtain clusters; and determine the operation type based on the clusters.

[0112] In some embodiments, the simulation unit 603 is further configured to: determine the target operation location according to the business verification step corresponding to the operation type; execute the operation method corresponding to the operation type at the target operation location to simulate the user operation, perform the business verification task, and obtain the execution result data.

[0113] In some embodiments, the service verification device further includes Figure 6 The report generation unit not shown in the figure is configured to: automatically generate a business verification report according to the execution result data and a specific template, and perform real-time visual display of the business verification report.

[0114] It should be noted that the business verification method and business verification device of the present application have a corresponding relationship in terms of specific implementation content, so the repeated content will not be explained again.

[0115] Figure 7 An exemplary system architecture 700 is shown to which the service verification method or service verification device according to the embodiment of the present application can be applied.

[0116] like Figure 7 As shown, system architecture 700 may include terminal devices 701, 702, 703, network 704 and server 705. Network 704 is used to provide a medium for communication links between terminal devices 701, 702, 703 and server 705. Network 704 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0117] The user can use the terminal devices 701, 702, 703 to interact with the server 705 through the network 704 to receive or send messages, etc. Various communication client applications can be installed on the terminal devices 701, 702, 703, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only for example).

[0118] The terminal devices 701, 702, and 703 may be various electronic devices having a service verification processing screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

[0119] The server 705 may be a server that provides various services, such as a background management server that provides support for business verification requests submitted by users using terminal devices 701, 702, and 703 (only as an example). The background management server may receive a business verification request, obtain a corresponding test scenario identifier, and then generate a corresponding business verification task; extract keywords in the business verification step corresponding to the business verification task, and determine the operation type based on the keywords; extract keywords in the business verification step corresponding to the business verification task, including: obtaining a business verification keyword portrait corresponding to the test scenario identifier, identifying meaningless words in the business verification step, dividing the business verification step based on the meaningless words to obtain each segmentation, matching each segmentation with each label in the business verification keyword portrait, and then determining the matched label in the business verification keyword portrait as the keyword in the business verification step corresponding to the business verification task; simulating user operations according to the operation type and the corresponding business verification step to execute the business verification task, and then obtaining execution result data; in response to the execution result data corresponding to the business verification failure, obtaining the corresponding verification failure step identifier; and sending the verification failure step identifier to the target business processing node. This improves the efficiency of business verification and the accuracy of business verification results.

[0120] It should be noted that the service verification method provided in the embodiment of the present application is generally executed by the server 705 , and accordingly, the service verification device is generally arranged in the server 705 .

[0121] It should be understood that Figure 7 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0122] Reference below Figure 8 , which shows a schematic diagram of the structure of a computer system 800 of a terminal device suitable for implementing an embodiment of the present application. Figure 8 The terminal device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0123] like Figure 8 As shown, the computer system 800 includes a central processing unit (CPU) 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage part 808 into a random access memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the computer system 800 are also stored. The CPU 801, the ROM 802, and the RAM 803 are connected to each other via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0124] The following components are connected to the I / O interface 805: an input section 806 including a keyboard, a mouse, etc.; an output section 807 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN card, a modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the I / O interface 805 as needed. A removable medium 811, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 810 as needed, so that a computer program read therefrom is installed into the storage section 808 as needed.

[0125] 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 contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 809, and / or installed from the removable medium 811. When the computer program is executed by the central processing unit (CPU) 801, the above-mentioned functions defined in the system of the present application are executed.

[0126] It should be noted that the computer-readable medium shown in the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. Computer-readable storage media may include, for example, but are not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices 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 the present application, a 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, device or device. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0127] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the above-mentioned module, program segment or a part of a 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 or flow chart, and the combination of the boxes in the block diagram or flow chart 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.

[0128] The units involved in the embodiments described in the present application may be implemented by software or hardware. The units described may also be set in a processor, for example, it may be described as: a processor includes a receiving unit, an extraction unit, a simulation unit, an acquisition unit, and a sending unit. The names of these units do not constitute limitations on the units themselves in some cases.

[0129] As another aspect, the present application also provides a computer-readable medium, which may be included in the device described in the above embodiment; or it may exist independently and not be assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device receives a business verification request, obtains a corresponding test scenario identifier, and then generates a corresponding business verification task; extracts keywords in the business verification step corresponding to the business verification task, and determines the operation type based on the keywords; extracts keywords in the business verification step corresponding to the business verification task, including: obtaining a business verification keyword portrait corresponding to the test scenario identifier, identifying meaningless words in the business verification step, dividing the business verification step based on the meaningless words to obtain each segmentation, matching each segmentation with each label in the business verification keyword portrait, and then determining the label in the matched business verification keyword portrait as the keyword in the business verification step corresponding to the business verification task; according to the operation type and the corresponding business verification step, simulating user operations to execute the business verification task, and then obtaining execution result data; in response to the execution result data corresponding to the business verification failure, obtaining the corresponding verification failure step identifier; sending the verification failure step identifier to the target business processing node.

[0130] The computer program product of the present application includes a computer program, and when the computer program is executed by a processor, the service verification method in the embodiment of the present application is implemented.

[0131] According to the technical solution of the embodiment of the present application, the business verification efficiency and the accuracy of the business verification results can be improved.

[0132] The above specific implementations do not constitute a limitation on the protection scope of this application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of this application should be included in the protection scope of this application.

Claims

1. A service verification method, characterized in that: include: Receive a business verification request, obtain the corresponding test scenario identifier, and then generate the corresponding business verification task; Extracting keywords in the business verification step corresponding to the business verification task, and determining the operation type based on the keywords; The extracting of keywords in the business verification step corresponding to the business verification task includes: obtaining a business verification keyword portrait corresponding to the test scenario identifier, identifying meaningless words in the business verification step, dividing the business verification step based on the meaningless words to obtain individual participles, matching the individual participles with individual tags in the business verification keyword portrait, and then determining the tags in the matched business verification keyword portrait as keywords in the business verification step corresponding to the business verification task; According to the operation type and the corresponding business verification step, simulate the user operation to perform the business verification task, and then obtain the execution result data; In response to the execution result data corresponding to a business verification failure, obtaining a corresponding verification failure step identifier; The verification failure step identifier is sent to a target business processing node.

2. The method according to claim 1, characterized in that The generating of the corresponding business verification task includes: Determine the corresponding service verification steps according to the test scenario identifier; Based on each business verification step, a corresponding single business verification task is generated.

3. The method according to claim 2, characterized in that The extracting keywords in the business verification step corresponding to the business verification task includes: Identifying an action word in a business verification step corresponding to the business verification task, and determining the action word as a keyword in the business verification step corresponding to the business verification task; The keywords are extracted.

4. The method according to claim 1, characterized in that: The step of determining the operation type according to the keyword includes: Clustering the keywords to obtain clusters; Based on the clusters, an operation type is determined.

5. The method according to claim 1, characterized in that According to the operation type and the corresponding business verification step, simulating the user operation to perform the business verification task, and then obtaining the execution result data, includes: Determine the target operation location according to the business verification step corresponding to the operation type; An operation method corresponding to the operation type is executed at the target operation position to simulate a user operation, the business verification task is executed, and execution result data is acquired.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: Based on the execution result data, a business verification report is automatically generated according to a specific template, and the business verification report is visualized in real time.

7. A service verification device, characterized in that: include: A receiving unit is configured to receive a service verification request, obtain a corresponding test scenario identifier, and then generate a corresponding service verification task; an extraction unit configured to extract keywords in the business verification step corresponding to the business verification task, and determine an operation type based on the keywords; The extracting of keywords in the business verification step corresponding to the business verification task includes: obtaining a business verification keyword portrait corresponding to the test scenario identifier, identifying meaningless words in the business verification step, dividing the business verification step based on the meaningless words to obtain individual participles, matching the individual participles with individual tags in the business verification keyword portrait, and then determining the tags in the matched business verification keyword portrait as keywords in the business verification step corresponding to the business verification task; a simulation unit configured to simulate a user operation to perform the business verification task according to the operation type and the corresponding business verification step, and then obtain execution result data; An acquiring unit, configured to acquire a corresponding verification failure step identifier in response to the execution result data corresponding to a business verification failure; The sending unit is configured to send the verification failure step identifier to a target service processing node.

8. The device according to claim 7, characterized in that The receiving unit is further configured to: Determine the corresponding service verification steps according to the test scenario identifier; Based on each business verification step, a corresponding single business verification task is generated.

9. The device according to claim 8, characterized in that The extraction unit is further configured to: Identifying an action word in a business verification step corresponding to the business verification task, and determining the action word as a keyword in the business verification step corresponding to the business verification task; The keywords are extracted.

10. The device according to claim 7, characterized in that The extraction unit is further configured to: Clustering the keywords to obtain clusters; Based on the clusters, an operation type is determined.

11. The device according to claim 7, characterized in that The simulation unit is further configured to: Determine the target operation location according to the business verification step corresponding to the operation type; An operation method corresponding to the operation type is executed at the target operation position to simulate a user operation, the business verification task is executed, and execution result data is acquired.

12. The device according to any one of claims 7 to 11, characterized in that The apparatus further comprises a report generating unit configured to: Based on the execution result data, a business verification report is automatically generated according to a specific template, and the business verification report is visualized in real time.

13. A business verification electronic device, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 6.

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

15. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

Images