Method, device and equipment for evaluating application software and storage medium

Abstract

The application relates to the technical field of software testing, and provides an evaluation method and device of application software, equipment and a storage medium, the method comprising the following steps: obtaining an interactive test case for testing a target function of application software, wherein the interactive test case comprises a plurality of interactive steps for testing the target function; entering and analyzing a graphical user interface of the application software to obtain interface data of the graphical user interface; determining target controls for executing the plurality of interactive steps from the interface data of the graphical user interface; sequentially interacting with the plurality of target controls according to the plurality of interactive steps, and recording test results obtained after the interaction with the plurality of target controls; and evaluating the test results corresponding to the plurality of target controls to obtain an evaluation result of the application software. The method can be used for evaluating application software in the fields of financial technology and medical health, and solves the problems of incomplete evaluation of application software and poor evaluation effect in the prior art.

Description

Technical Field

[0001] This application relates to the technical field of software testing, and can be used in the fields of fintech and healthcare, and particularly to an evaluation method, apparatus, device and storage medium for application software. Background Technology

[0002] With the development of internet technology, more and more technologies are being applied in the fintech field. For example, bank staff can directly process user transactions through application software, providing users with efficient and convenient services. Therefore, evaluating and testing application software is essential to avoid significant economic losses or data leaks. Currently, when testers evaluate application software, they often cannot capture the dynamic behavior of the software during actual operation, resulting in an incomplete evaluation and poor evaluation results. For example, when evaluating healthcare application software, testers usually only perform static checks on the interface display and basic functions, but this cannot capture the dynamic behavior of the software in real-world operating scenarios such as actual patient reception and health monitoring. Therefore, the evaluation of healthcare application software is not comprehensive enough, resulting in poor evaluation results. Thus, how to improve the evaluation effectiveness of application software has become a critical issue that urgently needs to be addressed. Summary of the Invention

[0003] The main purpose of this application is to provide an evaluation method, apparatus, device, and storage medium for application software, which can be applied to the fields of fintech and healthcare, and aims to solve the problems that the existing technology for evaluating application software is not comprehensive enough and the evaluation effect is poor.

[0004] Firstly, this application provides an evaluation method for application software, the evaluation method comprising: Obtain interactive test cases for testing the target functionality of the application software, wherein the interactive test cases include multiple interactive steps for testing the target functionality; Access and parse the graphical user interface of the application software to obtain the interface data of the graphical user interface; Determine the target control for performing the multiple interaction steps from the interface data of the graphical user interface; According to the multiple interaction steps, the system sequentially interacts with the multiple target controls and records the test results obtained after interacting with the multiple target controls. The test results corresponding to multiple target controls are evaluated to obtain the evaluation result of the application software.

[0005] Secondly, this application also provides an application software evaluation apparatus, the application software evaluation apparatus comprising: The data acquisition module is used to acquire interactive test cases for testing the target function of the application software. The interactive test cases include multiple interactive steps for testing the target function. The data parsing module is used to access and parse the graphical user interface of the application software to obtain the interface data of the graphical user interface. The determining module is used to determine, based on the interface data of the graphical user interface, the target control in the graphical user interface used to perform multiple interaction steps; The data interaction module is used to interact with multiple target controls sequentially based on multiple interaction steps, and to record the test results obtained after interacting with multiple target controls; The result evaluation module is used to evaluate the test results corresponding to multiple target controls to obtain the evaluation result of the application software.

[0006] Thirdly, this application also provides a computer device, the computer device including a processor, a memory, and a computer program stored in the memory and executable by the processor, wherein when the computer program is executed by the processor, it implements the steps of the application software evaluation method as described above.

[0007] Fourthly, this application also provides a computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, it implements the steps of the application software evaluation method described above.

[0008] This application provides an evaluation method, apparatus, device, and storage medium for application software. First, it acquires interactive test cases (each including multiple interactive steps) for testing the target functions of the application software and parses the graphical user interface (GUI) to obtain interface data. Next, based on the GUI data, it determines the target controls for executing the multiple interactive steps. Then, according to the multiple interactive steps, it sequentially interacts with the multiple target controls, capturing the dynamic behavior of the application software in real time during actual operation. This solves the problem that static checks cannot effectively verify the behavior of application software during actual operation. Finally, by comprehensively evaluating the test results obtained after interaction, it avoids the situation where the software's overall functionality is mistakenly considered to meet requirements due to the passing of partial functional tests, achieving a comprehensive evaluation of the application software and thus improving the evaluation effect. Attached Figure Description

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

[0010] Figure 1 This is a schematic diagram of an application environment for an application software evaluation method according to an embodiment of this application; Figure 2 A flowchart illustrating the steps of the application software evaluation method provided in this application embodiment; Figure 3 for Figure 2 A schematic diagram illustrating an application scenario of the evaluation methods for application software. Figure 4 for Figure 2 A flowchart illustrating a sub-step of the application software evaluation method; Figure 5 for Figure 2 A flowchart illustrating another sub-step of the application software evaluation method; Figure 6 for Figure 2 A flowchart illustrating another sub-step of the application software evaluation method; Figure 7 A schematic block diagram of an application software evaluation device provided in an embodiment of this application; Figure 8 This is a schematic block diagram of the structure of a computer device provided in an embodiment of this application.

[0011] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

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

[0013] The flowchart shown in the attached diagram is for illustrative purposes only and does not necessarily include all content and operations / steps, nor does it necessarily have to be performed in the order described. For example, some operations / steps can be broken down, combined, or partially merged, so the actual execution order may change depending on the actual situation.

[0014] This application provides an evaluation method, apparatus, device, and storage medium for application software. The evaluation method can be applied to computer devices, which can be electronic devices with data processing and program execution capabilities, such as servers, desktop computers, laptops, tablets, or mobile terminals. For example, it can be applied to intelligent agents within the computer device, such as testing agents, automated execution agents, large-scale model agents, or business detection agents—processing units with interactive control and result analysis capabilities. This intelligent agent can simulate user interaction with application software and can be used to evaluate the functionality of applications in fields such as healthcare and fintech.

[0015] For example, the application software evaluation method provided in this application embodiment can be applied to, for example, Figure 1 In this application environment, the mobile terminal communicates with the server via a network. The server receives an application software evaluation request initiated by the mobile terminal via the network and evaluates the application software involved in the request. The server first obtains interactive test cases for testing the target functions of the application software. These interactive test cases include multiple interactive steps for testing the target functions. Next, it enters and parses the graphical user interface (GUI) of the application software to obtain the GUI's interface data. Then, it determines the target controls for executing the multiple interactive steps from the GUI's interface data. Based on the multiple interactive steps, it interacts with the multiple target controls sequentially and records the test results obtained after interacting with the multiple target controls. Finally, it evaluates the test results corresponding to the multiple target controls to obtain the application software's evaluation result, and returns the evaluation result to the mobile terminal.

[0016] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0017] Please refer to Figure 2 , Figure 2 This is a flowchart illustrating the steps of an application software evaluation method provided in an embodiment of this application.

[0018] like Figure 2 As shown, the evaluation method for this application software includes steps S101 to S105.

[0019] Step S101: Obtain interactive test cases for testing the target function of the application software. The interactive test cases include multiple interactive steps for testing the target function.

[0020] Interactive test cases are test cases that require real-time intervention during the testing process. They can include multiple interactive steps, emphasizing the interactive process and real-time feedback after the interaction. They can be used to verify whether the target function of the application software can be implemented normally. Interactive test cases can include one or more.

[0021] The application software can include healthcare, fintech, and other related applications. The target functions of the application software can include the functions it aims to achieve. For example, the target functions of healthcare applications could include online consultations, vital sign monitoring, prescription management, and health report generation (e.g., users consulting about their medical conditions through the software); the target functions of fintech applications could include premium calculation and quote generation (e.g., users calculating insurance premiums through the software).

[0022] In one embodiment, obtaining interactive test cases for testing application software functions includes: obtaining the functional requirements of the application software; preprocessing the functional requirements of the application software based on a large language model to obtain initial interactive test cases; loading a preset knowledge base; constraining the initial interactive test cases according to the preset knowledge base to obtain final interactive test cases; and using the final interactive test cases as interactive test cases for testing application software functions.

[0023] Preprocessing may include at least one of the following operations: removing redundant information, standardizing formats, and identifying key fields. The pre-defined knowledge base may include business rules and compliance checks. Business rules may include industry logic that the application software must follow, and compliance checks may include legal, regulatory, and security standards that the application software must meet.

[0024] It should be noted that constraining the initial interactive test cases based on the preset knowledge base is to ensure that the test cases meet the constraints of the application software in terms of industry logic, laws and regulations, and supervision.

[0025] For example, the functional requirement of the application software is: "Calculate car insurance premiums based on the user's driving experience and generate a quotation that complies with regulatory requirements." Based on a large language model, this functional requirement is processed by removing redundant descriptions and extracting key fields, generating initial interactive test cases: "Interaction Objective: Verify the car insurance premium calculation and quotation generation function; Test Steps: Input user's driving experience information; Click the premium calculation button; Expected Feedback: The system calculates and displays the premium amount." A preset knowledge base is loaded, and the initial interactive test cases are constrained according to "Business Rules: For users with less than 1 year of driving experience, the premium is increased by 20% above the base rate; Compliance Check: The quotation must include a disclaimer." The final interactive test cases are: "Interaction Objective: Verify the car insurance premium calculation and quotation generation function; Test Steps: Enter '6 months' in the driving experience input box; Click the 'Calculate Premium' button; Expected Feedback: The system calculates and displays the corresponding premium based on a 20% increase above the base rate; The generated quotation includes a disclaimer." These final interactive test cases are used to test the application software's functionality.

[0026] It should be noted that the process involves obtaining the functional requirements of the application software, preprocessing these requirements based on a large language model to obtain initial interactive test cases, loading a pre-defined knowledge base, and constraining the initial interactive test cases according to the knowledge base to obtain final interactive test cases. These final interactive test cases are then used to test the functionality of the application software. This process improves the efficiency of interactive test case generation, avoids errors caused by manual writing, and ensures that the interactive test cases comply with business logic and compliance requirements.

[0027] Step S102: Enter and parse the graphical user interface of the application software to obtain the interface data of the graphical user interface.

[0028] The interface data of the graphical user interface may include visual data presented in a visual form in the graphical user interface, as well as data used to describe the hierarchical structure of the graphical user interface.

[0029] For example, when the intelligent agent launches the "Auto Insurance Quotation System" application, the corresponding graphical user interface after entering the "Auto Insurance Quotation System" application is as follows: Figure 3As shown, the intelligent agent recognizes text labels such as "vehicle brand" and "contact information" through optical character recognition (OCR), then determines the positions of input boxes and buttons. Next, it calls a pre-set parsing tool to parse the UI structure tree of the application software's current graphical user interface (GUI) to obtain visual data presented in the current GUI, such as "Vehicle Quotation System," "Vehicle Information," "Vehicle Number," "Purchase Year," "Personal Information," "Name," "Contact Information," "Package Selection," "Basic Package," "Upgrade Package," and "Get Quote," as well as data describing the hierarchical structure of the GUI, such as the hierarchical relationship between the page and the "Vehicle Information," "Personal Information," and "Package Selection" modules, and the interaction states of input boxes and buttons under each module. The interaction states characterize whether interface data is operable, including visible, inputtable, clickable, selected, and disabled states.

[0030] It should be noted that by entering and parsing the graphical user interface of the application software, the interface data of the graphical user interface can be obtained without relying on fixed element IDs, thus making it more robust.

[0031] Step S103: Determine the target control for performing multiple interactive steps from the interface data of the graphical user interface.

[0032] In one embodiment, such as Figure 4 As shown, the target control for performing multiple interactive steps is determined from the interface data of the graphical user interface, including steps S1031 to S1033: Step S1031: Obtain control information of multiple controls from the interface data, and obtain the keywords corresponding to each of the multiple interaction steps.

[0033] The control information may include the control type (such as input box, button, radio button), the control's text content (such as "vehicle brand" "get quote"), the control's interactive state (such as clickable, inputtable, visible), and the control's hierarchical structure and position information in the graphical user interface.

[0034] In one embodiment, obtaining the keywords corresponding to each of the multiple interaction steps includes: inputting the multiple interaction steps into a pre-trained large language model, and having the large language model perform semantic understanding and text parsing on each interaction step to obtain the keywords corresponding to each of the multiple interaction steps.

[0035] For example, the interactive test case includes multiple interactive steps: "Interaction step A: Enter vehicle information and personal information; Interaction step B: Select 'Basic Package'; Interaction step C: Click the 'Get Quote' button." The large language model performs semantic understanding and text parsing on each interactive step, and the keywords for interaction step A are "vehicle information" and "personal information"; the keywords for interaction step B are "Basic Package" and the keywords for interaction step C are "Get Quote".

[0036] Step S1032: Match the control information of each control with the keywords corresponding to each interaction step to obtain multiple matching information.

[0037] The matching information may include matching the control information of each control with the keywords corresponding to each interaction step to obtain a matching score and matching level that represent the degree of matching.

[0038] For example, the keywords corresponding to interaction step D include "vehicle brand". The graphical user interface contains controls E (control information includes: control type: input box, control text content: "vehicle brand", control interaction state: inputtable) and F (control information includes: control type: button, control text content: "get quote", control interaction state: clickable). Matching the text content of controls E and F with the keywords corresponding to interaction step D yields the following matching information: control E has a matching score of 0.98 with the keyword "vehicle brand", indicating a high matching level; control F has a matching score of 0.02 with the keyword "vehicle brand", indicating a low matching level.

[0039] Step S1033: Determine the control corresponding to the matching information that meets the set conditions as the target control.

[0040] The set conditions are used to filter out matching results that meet the requirements from multiple matching information. The set conditions include, but are not limited to: the matching score is not lower than the preset matching score threshold and the matching level is not lower than the preset level.

[0041] It should be noted that by determining the target control for performing multiple interaction steps from the interface data, without relying on fixed element IDs or fixed coordinates, the target control to be interacted with can be accurately found from the multiple controls contained in the graphical user interface, avoiding misoperation and ensuring that subsequent interaction steps can be executed stably.

[0042] Step S104: Based on multiple interaction steps, interact with multiple target controls sequentially, and record the test results obtained after interacting with multiple target controls.

[0043] It should be noted that by sequentially interacting with multiple target controls according to the multiple interaction steps and recording the test results obtained after interacting with multiple target controls, on the one hand, no manual intervention is required, reducing the probability of operational errors; on the other hand, it does not rely on fixed element IDs or fixed coordinates, and can capture the dynamic behavior of the application software during actual operation, thereby achieving a comprehensive evaluation of the application software and improving the evaluation effect of the application software.

[0044] In one embodiment, such as Figure 5 As shown, multiple interaction steps are performed sequentially with multiple target controls, including steps S1041 to S1043: Step S1041: Obtain the operation rules for each interaction step.

[0045] Among them, the operation rules are a set of rules used to guide or constrain the execution of interaction steps. They belong to the constraints at the execution level and include, but are not limited to, security boundary rules and execution methods.

[0046] For example, interaction step G: Input vehicle information and personal information. The operation rules for interaction step G include: {Execution method: Enter text content in the "Vehicle Information" and "Personal Information" input boxes; Security boundary rule: The input text content is prohibited from containing sensitive or malicious characters.} Step S1042: Based on the operation rules of each interaction step, convert each interaction step into a corresponding interface operation instruction.

[0047] In one embodiment, each interaction step is converted into a corresponding interface operation instruction according to the operation rules of each interaction step, including: parsing the operation rules of each interaction step to obtain the target control corresponding to each interaction step and the operation parameters corresponding to each target control; and generating the interface operation instruction corresponding to each interaction step based on the target control corresponding to each interaction step and the operation parameters corresponding to each target control.

[0048] The operation parameters may include the interactive actions to interact with the target control, the content to interact with the target control, and the constraints to interact with the target control.

[0049] The interactive actions that interact with the target control include, but are not limited to, clicking, long-pressing, inputting, swiping, and clearing; the content that interacts with the target control includes, but is not limited to, the input text information, the selected option identifier, and the triggered instruction data; the constraints that interact with the target control include, but are not limited to, input content format validation, prohibition of inputting sensitive or malicious characters, and operation execution latency requirements.

[0050] Among them, the interface operation instructions are used to instruct the agent to execute atomic operation commands on the graphical user interface.

[0051] For example, interaction step H: Input the vehicle purchase year no later than the current year. The operation rules for interaction step H include: {Execution method: Input text content in the "Vehicle Purchase Year" input box; Security boundary rule: The input text content is prohibited from containing sensitive or malicious characters.}. Parsing the operation rules of interaction step H, the target control corresponding to interaction step H is the "Vehicle Purchase Year" input box. The operation parameters corresponding to the "Vehicle Purchase Year" input box are: {Interaction action to interact with the target control - input, content to interact with the target control - 2031, constraint condition to interact with the target control: the input content does not contain sensitive or malicious characters}. Integrating and encapsulating the aforementioned target control, interaction action, interaction content, and interaction constraint condition, the interface operation instruction for interaction step H is obtained: {Input 2031 in the "Vehicle Purchase Year" input box, and ensure that the input content does not contain sensitive or malicious characters}.

[0052] It should be noted that by converting each interaction step into multiple interface operation instructions according to the operation rules of each interaction step, the manual cost is reduced and the efficiency and accuracy of software evaluation are improved.

[0053] Step S1043: Interact with multiple target controls sequentially according to the interface operation instructions corresponding to each interaction step.

[0054] For example, interaction step J is as follows: input the patient's symptoms, select the department to visit based on the patient's symptoms, and the interface operation instructions corresponding to interaction step J include: {input palpitations in the “symptom description” input box, and ensure that the input content does not contain sensitive or malicious characters}, {select “cardiovascular medicine” in the “department to visit” selection box, and ensure that the selection content conforms to the preset department range}. According to the interface operation instructions corresponding to interaction step J, determine the interaction order with multiple target controls, and interact with the “symptom description” input box and the “department to visit” selection box in sequence according to the interaction order.

[0055] It should be noted that by interacting with multiple target controls sequentially according to the interface operation instructions corresponding to each interaction step, interaction conflicts can be avoided, making the interaction process more stable.

[0056] In one embodiment, before interacting with multiple target controls sequentially according to multiple interaction steps, the method further includes: sensing whether the test environment is safe; if the test environment is safe, obtaining the position information of the multiple target controls in the graphical user interface; and interacting with the multiple target controls sequentially according to the order of the multiple interaction steps based on the position information of the multiple target controls.

[0057] The testing environment refers to the description of the software and hardware environment on which the test runs, as well as any other software that interacts with the software under test, including drivers and stubs. The testing environment encompasses all the computer hardware, software, network equipment, and historical data necessary to complete software testing. A stable and controllable testing environment allows testers to execute test cases in less time, without needing to spend additional time maintaining test cases and the testing process.

[0058] It should be noted that before interacting with multiple target controls sequentially according to multiple interaction steps, the security of the test environment is first assessed. If the test environment is secure, the position information of multiple target controls in the graphical user interface is obtained. Based on the position information of multiple target controls, the interaction with multiple target controls is performed sequentially according to the order of multiple interaction steps. This can effectively avoid external interference during the testing process, prevent test data from being tampered with or leaked, and thus improve the security of software evaluation.

[0059] In one embodiment, determining whether the test environment is secure includes: activating a preset virus detection tool to scan multiple code segments contained in the application software and determining the security risk coefficient of each code segment, wherein the security risk coefficient is used to characterize the security threat level of the code; determining whether the security risk coefficient of each code segment is less than or equal to a preset security risk coefficient threshold; if the security risk coefficient of each code segment is less than or equal to the preset security risk coefficient, then the test environment is determined to be secure.

[0060] The pre-defined virus detection tools may include a malware scanning engine. A malware scanning engine is a key component in application software security testing, used to detect and identify potential malicious code, determining whether the code or file contains security threats such as viruses, Trojans, and ransomware.

[0061] For example, a virus detection tool is launched, and multiple code segments contained in the application software are loaded into the scanning environment for scanning. Based on a trained regression model (such as random forest or neural network), the security risk coefficient of each code segment is calculated. If the security risk coefficient of each code segment is less than or equal to the preset security risk coefficient threshold, the test environment is deemed safe.

[0062] It should be noted that by inspecting multiple code segments contained in the application software, the interference of risky code on the test environment can be eliminated from the source, thereby ensuring that the entire evaluation process is in a safe state.

[0063] Step S105: Evaluate the test results corresponding to multiple target controls to obtain the evaluation results of the application software.

[0064] Interactive test cases also include expected feedback results, which include the test results expected after the interactive test cases are completed.

[0065] It should be noted that the test results for multiple target controls can be obtained from the final graphical user interface displayed after the agent has completed all interactive operations on the multiple target controls.

[0066] For example, the interactive test case includes interactive steps K1, K2, and K3. After the agent completes interactive step K1, the graphical user interface displayed is L1. After the agent completes interactive step K2, the graphical user interface displayed is L2. After the agent completes interactive step K3, the graphical user interface displayed is L3. The graphical user interface L3 records the test results corresponding to multiple target controls.

[0067] In one embodiment, such as Figure 6 As shown, the test results corresponding to multiple target controls are evaluated to obtain the evaluation results of the application software, including steps S1051 to S1054: Step S1051: Match the expected feedback results with the test results corresponding to multiple target controls.

[0068] For example, matching the expected feedback result with the test results corresponding to multiple target controls includes: performing optical character recognition on the graphical user interface that records the test results to obtain the text data of the test results; extracting keywords from the text data of the test results and keywords from the text data of the preset expected feedback result according to the large language model; matching the keywords corresponding to the test results with the keywords corresponding to the preset expected feedback result to determine the degree of matching between the two.

[0069] Step S1052: If the matching degree is greater than or equal to the preset matching degree threshold, the interactive test case is determined to pass the verification, and the comprehensive score of the interactive test case is determined. The comprehensive score is used to characterize the operation of the target function of the application software.

[0070] It should be noted that determining the overall score of interactive test cases includes: determining the score corresponding to the matching degree according to a preset score mapping table, and using the score corresponding to the matching degree as the overall score of the interactive test cases. The preset score mapping table records the scores corresponding to different matching degree ranges.

[0071] For example, a preset score mapping table is shown in Table 1:

[0072] If the expected feedback result is matched with the test results corresponding to multiple target controls, the calculated matching degree is 0.85, which is greater than the preset matching degree threshold of 0.5. According to the preset score mapping table, the comprehensive score of the interactive test case can be determined to be 85 points.

[0073] It should be noted that, in one embodiment, if an interactive test case passes verification but its overall score is less than a preset overall score threshold, it is necessary to further determine the reason why the overall score of the interactive test case is less than the preset overall score threshold based on the interaction record. The interaction record includes the graphical user interface corresponding to each interactive step.

[0074] For example, the keyword corresponding to the test result is "premium amount", and the keyword corresponding to the preset expected feedback result is "download quotation" and "display premium". The keyword corresponding to the test result is matched with the keyword corresponding to the preset expected feedback result. The matching degree is calculated to be 0.6, which is equal to the preset matching degree threshold of 0.6. The interactive test case is deemed to have passed the verification. According to the preset score mapping table, the comprehensive score of the interactive test case is determined to be 60 points, which is less than the preset comprehensive score threshold of 80 points. According to the interaction record, the reason why the comprehensive score of the interactive test case is less than the preset comprehensive score threshold is that the "download quotation" control was not loaded normally.

[0075] It should be noted that, in one embodiment, if an interactive test case passes verification and its overall score is greater than or equal to a preset overall score threshold, it is necessary to further determine the reason why the overall score of the interactive test case is greater than or equal to the preset overall score threshold based on the interaction record. The interaction record includes the graphical user interface corresponding to each interactive step.

[0076] For example, the keywords corresponding to the test results are "premium amount" and "download quotation". The keywords corresponding to the preset expected feedback results are "download quotation" and "display premium". The keywords corresponding to the test results are matched with the keywords corresponding to the preset expected feedback results. The matching degree is calculated to be 0.9, which is greater than the preset matching degree threshold of 0.5. The interactive test case is deemed to have passed the verification. According to the preset score mapping table, the comprehensive score of the interactive test case is determined to be 95 points, which is greater than the preset comprehensive score threshold of 80 points. According to the interaction record, the reason why the comprehensive score of the interactive test case is greater than the preset comprehensive score threshold is that the premium amount is displayed normally and the "download quotation" control is fully displayed.

[0077] Step S1053: If the matching degree is less than the preset matching degree threshold, determine that the interactive test case has failed the verification and determine the reason for the failure of the interactive test case verification.

[0078] It should be noted that the reason for the failure of interactive test case verification can be determined by reviewing the interaction log, which includes the graphical user interface corresponding to each interactive step.

[0079] For example, the keyword corresponding to the test result is "page error, unable to load", and the keyword corresponding to the preset expected feedback result is "download quotation". The keyword corresponding to the test result is matched with the keyword corresponding to the preset expected feedback result. The matching degree is calculated to be 0.1, which is less than the preset matching degree threshold of 0.5. Therefore, the interactive test case is determined to have failed the verification. According to the interaction record, the reason for the verification failure is determined to be: the interface crashed during the interaction.

[0080] Step S1054: Based on the comprehensive score of the interactive test cases or the reason for the verification failure, obtain the evaluation result of the application software.

[0081] It should be noted that interactive test cases used to test the target functionality of application software may include one or more.

[0082] For example, there is only one interactive test case used to test the target function of the application software. The comprehensive score of this interactive test case is matched with the score range in a preset function evaluation comparison table, and the matched evaluation conclusion is used as the evaluation result of the application software. The preset function evaluation comparison table is a pre-set and stored table that reflects the correspondence between the comprehensive score and the operation of the application software's target function.

[0083] For example, if there are multiple interactive test cases for testing the target function of the application software, the comprehensive scores of the multiple interactive test cases are summarized and their average value is calculated. The average value is then matched with the score range in the preset function evaluation comparison table, and the evaluation conclusion obtained from the matching is used as the evaluation result of the application software.

[0084] For example, a preset functional evaluation checklist is shown in Table 2:

[0085] For example, there is only one interactive test case for testing the target function of the application software. The overall score of this interactive test case is 85 points. According to the preset functional evaluation comparison table, the evaluation result of the application software can be obtained as: "The target function runs normally, the interaction process has no obvious abnormalities, and it basically meets the business rules and compliance requirements."

[0086] For example, there are two interactive test cases used to test the target function of the application software, with comprehensive scores of 85 and 70 respectively. The average of the two is 77.5 = [(85+70) / 2]. The average value is matched with the score range in the preset function evaluation comparison table, and the evaluation result of the application software is: "The target function runs basically normally, with a small number of non-critical interaction or logic problems, which do not affect the overall use."

[0087] For example, there is only one interactive test case used to test the target function of the application software. If the interactive test case fails to pass the verification, the reason for its failure is determined and the reason is used as the evaluation result of the application software.

[0088] For example, there are multiple interactive test cases used to test the target functions of the application software. If multiple interactive test cases fail to pass verification, the reasons for the failure of multiple interactive test cases are identified and summarized, and the multiple reasons are used as the evaluation results of the application software.

[0089] It should be noted that evaluating the test results of multiple target controls based on the above method to obtain the evaluation results of the application software can reduce the evaluation error of the application software and make the evaluation results more reliable.

[0090] The application software evaluation method provided in the above embodiments obtains interactive test cases (each interactive test case includes multiple interactive steps) for testing the target functions of the application software and parses the graphical user interface of the application software to obtain interface data. Then, based on the interface data of the graphical user interface, target controls for executing multiple interactive steps are determined. Next, according to the multiple interactive steps, interactions are sequentially performed with multiple target controls, capturing the dynamic behavior of the application software in real time during actual operation. This solves the problem that static checks cannot effectively verify the behavior of the application software during actual operation. Finally, by comprehensively evaluating the test results obtained after interaction, the method avoids the situation where the overall functionality of the software is mistakenly considered to meet the requirements due to the passing of partial functional tests, achieving a comprehensive evaluation of the application software and thus improving the evaluation effect of the application software.

[0091] Please refer to Figure 7 , Figure 7 This is a schematic block diagram of an application software evaluation device provided in an embodiment of this application.

[0092] like Figure 7 As shown, the evaluation device 300 for the application software includes: a data acquisition module 301, a data parsing module 302, a determination module 303, a data interaction module 304, and a result evaluation module 305.

[0093] The data acquisition module 301 is used to acquire interactive test cases for testing the target function of the application software. The interactive test cases include multiple interactive steps for testing the target function.

[0094] The data parsing module 302 is used to access and parse the graphical user interface of the application software to obtain the interface data of the graphical user interface.

[0095] The determining module 303 is used to determine the target control in the graphical user interface for performing multiple interactive steps based on the interface data of the graphical user interface.

[0096] The data interaction module 304 is used to interact with multiple target controls sequentially based on multiple interaction steps, and to record the test results obtained after interacting with multiple target controls.

[0097] The result evaluation module 305 is used to evaluate the test results corresponding to the multiple target controls to obtain the evaluation result of the application software.

[0098] It should be noted that those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the above-described device and its modules and units can be referred to the corresponding processes in the aforementioned application software evaluation method embodiments, and will not be repeated here.

[0099] The apparatus provided in the above embodiments can be implemented as a computer program, which can be used in, for example... Figure 8 It runs on the computer device shown.

[0100] Please see Figure 8 , Figure 8 This is a schematic block diagram of the structure of a computer device provided in an embodiment of this application.

[0101] like Figure 8 As shown, the computer device includes a processor, memory, and network interface connected via a system bus. The memory may include a storage medium and internal memory, and the storage medium may be non-volatile or volatile.

[0102] The storage medium can store the operating system and computer programs. These computer programs include program instructions that, when executed, cause the processor to perform an evaluation method for any application software.

[0103] The processor provides computing and control capabilities, supporting the operation of the entire computer device.

[0104] Internal memory provides an environment for the execution of computer programs stored in storage media. When these computer programs are executed by the processor, the processor can perform any evaluation method for application software.

[0105] This network interface is used for network communication, such as sending assigned tasks. Those skilled in the art will understand that... Figure 7 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0106] It should be understood that the processor can be a Central Processing Unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among these, a general-purpose processor can be a microprocessor or any conventional processor.

[0107] In one embodiment, the processor is configured to run a computer program stored in memory to perform the following steps: Obtain interactive test cases for testing the target functionality of the application software, wherein the interactive test cases include multiple interactive steps for testing the target functionality; Access and parse the graphical user interface of the application software to obtain the interface data of the graphical user interface; Determine the target control for performing the multiple interaction steps from the interface data of the graphical user interface; According to the multiple interaction steps, the system sequentially interacts with the multiple target controls and records the test results obtained after interacting with the multiple target controls. The test results corresponding to multiple target controls are evaluated to obtain the evaluation result of the application software.

[0108] In one embodiment, when the processor implements the step of sequentially interacting with the multiple target controls according to the multiple interaction steps, it is configured to: Obtain the operation rules for each of the aforementioned interaction steps; Based on the operation rules of each interaction step, each interaction step is converted into a corresponding interface operation instruction; Based on the interface operation instructions corresponding to each interaction step, the system sequentially interacts with multiple target controls.

[0109] In one embodiment, when the processor implements the step of converting each interaction step into a corresponding interface operation instruction according to the operation rules of each interaction step, it is configured to: The operation rules of each interaction step are analyzed to obtain the target control corresponding to each interaction step and the operation parameters corresponding to each target control; Based on the target control corresponding to each interaction step and the operation parameters corresponding to each target control, interface operation instructions corresponding to each interaction step are generated.

[0110] In one embodiment, before implementing the step of sequentially interacting with the plurality of target controls according to the plurality of interaction steps, the processor is further configured to implement: The test environment is assessed for safety. If the test environment is safe, the position information of the multiple target controls in the graphical user interface is obtained. Based on the position information of the multiple target controls, the interaction is performed sequentially with the multiple target controls in the order of the multiple interaction steps.

[0111] In one embodiment, the processor, when determining whether the sensing test environment is safe, is configured to: The preset virus detection tool is activated to scan multiple code segments contained in the application software and determine the security risk coefficient of each code segment, wherein the security risk coefficient is used to characterize the security threat level of the code; Determine whether the security risk coefficient of each code segment is less than or equal to a preset security risk coefficient threshold. If the security risk coefficient of each code segment is less than or equal to the preset security risk coefficient, then the test environment is deemed secure.

[0112] In one embodiment, when the processor determines a target control for performing the plurality of interaction steps from the interface data of the graphical user interface, it is configured to: Obtain control information for multiple controls from the interface data, and obtain keywords corresponding to each of the multiple interaction steps; The control information of each control is matched with the keywords corresponding to each interaction step to obtain multiple matching information; The control corresponding to the matching information that meets the set conditions is determined as the target control.

[0113] In one embodiment, when the processor evaluates the test results corresponding to the plurality of target controls to obtain the evaluation result of the application software, it is configured to: The expected feedback result is matched with the test results corresponding to the multiple target controls; If the matching degree is greater than or equal to a preset matching degree threshold, the interactive test case is determined to pass the verification, and the comprehensive score of the interactive test case is determined. The comprehensive score is used to characterize the operation of the target function of the application software. If the matching degree is less than a preset matching degree threshold, the interactive test case is determined to have failed verification, and the reason for the failure of the interactive test case verification is determined. The evaluation result of the application software is obtained based on the comprehensive score of the interactive test cases or the reason for the verification failure.

[0114] It should be noted that those skilled in the art will understand that, for the sake of convenience and brevity, the specific working process of the computer equipment described above can be referred to the corresponding process in the aforementioned application software evaluation method embodiments, and will not be repeated here.

[0115] This application can be used in a wide variety of general-purpose or special-purpose computer system environments or configurations. Examples include: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, and distributed computing environments including any of the above systems or devices. This application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform specific tasks or implement specific abstract data types. 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.

[0116] This application also provides a computer-readable storage medium storing a computer program, the computer program including program instructions, and the method implemented when the program instructions are executed can refer to various embodiments of the application software evaluation method of this application.

[0117] The computer-readable storage medium may be an internal storage unit of the computer device described in the foregoing embodiments, such as the hard disk or memory of the computer device. The computer-readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, SmartMedia Card (SMC), Secure Digital (SD) card, or Flash Card equipped on the computer device.

[0118] Furthermore, the computer's usable storage medium may primarily include a stored program area and a stored data area. The stored program area may store the operating system, applications required for at least one function, etc.; the stored data area may store data created based on the use of blockchain nodes, etc. The blockchain referred to in this application is a novel application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms. A blockchain is essentially a decentralized database, a chain of data blocks linked using cryptographic methods. Each data block contains information about a batch of network transactions, used to verify the validity of the information (anti-counterfeiting) and generate the next block. A blockchain may include a blockchain underlying platform, a platform product service layer, and an application service layer, etc.

[0119] It should be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the scope of the application. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0120] It should also be understood that the term "and / or" as used in this specification and the appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes such combinations. It should be noted that, herein, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system 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 system. 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 system that includes that element.

[0121] It should be noted that any AI models, software tools, or components not belonging to this company appearing in the embodiments of this application are merely illustrative examples and do not represent actual use. All user personal information involved in the embodiments of this application has been authorized (with the knowledge and consent) by the relevant parties or has been fully authorized by all parties, and the executing entity may obtain it through various legal and compliant means. The collection, storage, use, processing, transmission, provision, and disclosure of the information, data, and signals involved all comply with relevant laws and regulations and do not violate public order and good morals.

[0122] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments. The above descriptions are merely specific implementations of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for evaluating application software, characterized in that, include: Obtain interactive test cases for testing the target functionality of the application software, wherein the interactive test cases include multiple interactive steps for testing the target functionality; Access and parse the graphical user interface of the application software to obtain the interface data of the graphical user interface; Determine the target control for performing the multiple interaction steps from the interface data of the graphical user interface; According to the multiple interaction steps, the system sequentially interacts with the multiple target controls and records the test results obtained after interacting with the multiple target controls. The test results corresponding to multiple target controls are evaluated to obtain the evaluation result of the application software.

2. The application software evaluation method as described in claim 1, characterized in that, The step of sequentially interacting with multiple target controls according to multiple interaction steps includes: Obtain the operation rules for each of the aforementioned interaction steps; Based on the operation rules of each interaction step, each interaction step is converted into a corresponding interface operation instruction; Based on the interface operation instructions corresponding to each interaction step, the system sequentially interacts with multiple target controls.

3. The application software evaluation method as described in claim 2, characterized in that, The step of converting each interaction step into a corresponding interface operation instruction according to the operation rules of each interaction step includes: The operation rules of each interaction step are analyzed to obtain the target control corresponding to each interaction step and the operation parameters corresponding to each target control; Based on the target control corresponding to each interaction step and the operation parameters corresponding to each target control, an interface operation instruction corresponding to each interaction step is generated.

4. The evaluation method for application software as described in any one of claims 1-3, characterized in that, Before sequentially interacting with the multiple target controls according to the multiple interaction steps, the method further includes: The system detects whether the test environment is safe, and if the test environment is safe, it acquires the position information of multiple target controls in the graphical user interface. Based on the position information of the multiple target controls, the interaction is performed sequentially with the multiple target controls in the order of the multiple interaction steps.

5. The application software evaluation method as described in claim 4, characterized in that, Whether the perception testing environment is safe includes: The preset virus detection tool is activated to scan multiple code segments contained in the application software and determine the security risk coefficient of each code segment, wherein the security risk coefficient is used to characterize the security threat level of the code; Determine whether the security risk coefficient of each code segment is less than or equal to the preset security risk coefficient; If the security risk coefficient of each code segment is less than or equal to the preset security risk coefficient, then the test environment is deemed secure.

6. The evaluation method for application software as described in any one of claims 1-3, characterized in that, Determining the target control for performing the multiple interaction steps from the interface data of the graphical user interface includes: Obtain control information for multiple controls from the interface data, and obtain keywords corresponding to each of the multiple interaction steps; The control information of each control is matched with the keywords corresponding to each interaction step to obtain multiple matching information; The control corresponding to the matching information that meets the set conditions is determined as the target control.

7. The evaluation method for application software as described in any one of claims 1-3, characterized in that, The interactive test case also includes the expected feedback result, which includes the test result expected to be obtained after the interactive test case is completed. The evaluation of the test results corresponding to the multiple target controls to obtain the evaluation result of the application software includes: The expected feedback result is matched with the test results corresponding to the multiple target controls; If the matching degree is greater than or equal to a preset matching degree threshold, the interactive test case is determined to pass the verification, and the comprehensive score of the interactive test case is determined. The comprehensive score is used to characterize the operation of the target function of the application software. If the matching degree is less than a preset matching degree threshold, the interactive test case is determined to have failed verification, and the reason for the failure of the interactive test case verification is determined. The evaluation result of the application software is obtained based on the comprehensive score of the interactive test cases or the reason for the verification failure.

8. An evaluation device for application software, characterized in that, The application software evaluation device includes: The data acquisition module is used to acquire interactive test cases for testing the target function of the application software. The interactive test cases include multiple interactive steps for testing the target function. The data parsing module is used to access and parse the graphical user interface of the application software to obtain the interface data of the graphical user interface. A determining module is used to determine, based on the interface data of the graphical user interface, a target control in the graphical user interface for performing multiple interaction steps; The data interaction module is used to interact with multiple target controls sequentially based on multiple interaction steps, and to record the test results obtained after interacting with multiple target controls; The result evaluation module is used to evaluate the test results corresponding to multiple target controls to obtain the evaluation result of the application software.

9. A computer device, characterized in that, The computer device includes a processor, a memory, and a computer program stored in the memory and executable by the processor, wherein when the computer program is executed by the processor, it implements the evaluation method of the application software as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, it implements the evaluation method of the application software as described in any one of claims 1 to 7.

Images