Testing method for financial service application program, electronic equipment and storage medium

Abstract

The invention relates to the field of finance and the technical field of computers, in particular to a test method for a financial service application program, electronic equipment and a storage medium. According to the test method provided by the embodiment of the invention, the test demand information needs to be acquired firstly; determining a test script program based on the test demand information; running a test script program for the financial service application program to enable the financial service application program to execute a plurality of test sub-tasks according to the task test sequence; in the process of executing the plurality of test sub-tasks according to the task test sequence, responding to the dependency association tasks belonging to different application platforms from the currently executed task in the plurality of test sub-tasks, jumping out of the task test sequence, and executing the dependency association tasks of the corresponding application platforms through the platform interfaces, and returning to execute the test sub-tasks except the dependency association task according to the task test sequence. In this way, the interaction and data synchronization effect between different application platforms can be improved in the automatic testing process.

Description

Technical Field

[0001] The present application relates to the fields of finance and computer technology, and in particular to a testing method, electronic equipment, and storage medium for financial business applications. Background Art

[0002] In the financial business field, the technical problems faced by the automated testing solutions for financial business applications are mainly reflected in multiple application platform interactions, complex business logic, high concurrency and performance testing, compatibility and cross-device testing, etc.

[0003] In the related art, the testing of financial business applications is often limited to a single application platform, such as mobile applications (app side), web applications (web side) or back-end services (interfaces). However, in more complex business scenarios, financial business applications may need to run on multiple application platforms. There is no mature solution for the interaction and data synchronization between these application platforms in the automated testing of financial business applications. Therefore, how to improve the interaction and data synchronization between different application platforms in the process of automated testing has become a technical problem that needs to be solved urgently in the industry. Summary of the invention

[0004] The present application aims to solve at least one of the technical problems existing in the prior art. To this end, the present application proposes a testing method, electronic device, and storage medium for financial business applications, which can improve the interaction and data synchronization effects between different application platforms during the automated testing process.

[0005] According to the first aspect of the present application, a testing method for a financial service application includes:

[0006] Acquire test requirement information of a financial business application; wherein the test requirement information is used to reflect the test requirements corresponding to the financial business application;

[0007] Determine a test script program based on the test requirement information; wherein the test script program is configured with a task test sequence and a plurality of platform interfaces adapted to different application platforms, and the task test sequence is used to determine the execution order of a plurality of test subtasks in the financial business application;

[0008] Running the test script program for the financial business application program so that the financial business application program executes the plurality of test subtasks according to the task test sequence;

[0009] In the process of executing the plurality of test subtasks according to the task test sequence, in response to the presence of dependent associated tasks belonging to different application platforms from the currently executed task in the plurality of test subtasks, the task test sequence is jumped out, and the dependent associated tasks corresponding to the application platform are executed through each of the platform interfaces;

[0010] After all the dependent and associated tasks are completed, the test subtasks other than the dependent and associated tasks are executed again according to the task test sequence.

[0011] According to some embodiments of the present application, determining a test script program based on the test requirement information includes:

[0012] Performing requirement analysis on the test requirement information to obtain test process information, dependency association constraints and interface requirement information;

[0013] Based on the test process information, determining the execution order of the plurality of test subtasks for the financial business application to generate the task test sequence;

[0014] Based on the dependency constraints, configuring corresponding dependency tasks for each of the test subtasks in the task test sequence;

[0015] Based on the interface requirement information, configure the corresponding platform interface for each of the test subtasks;

[0016] The test script program is generated according to the task test sequence, each of the test subtasks, the dependent-associated tasks corresponding to each of the test subtasks, and the platform interface corresponding to each of the test subtasks.

[0017] According to some embodiments of the present application, determining the execution order of the plurality of test subtasks for the financial business application based on the test process information to generate the task test sequence includes:

[0018] Based on the test process information, determining an execution order of the plurality of test subtasks for the financial business application;

[0019] According to the execution order of each of the test subtasks, each of the test subtasks is assembled into a corresponding test scenario case to obtain the task test sequence.

[0020] According to some embodiments of the present application, the step of performing requirement parsing on the test requirement information to obtain test process information, dependency association constraints and interface requirement information includes:

[0021] Performing test process requirement analysis on the test requirement information to obtain the test process information;

[0022] The test requirement information is subjected to dependency association requirement analysis to obtain the dependency association constraint. The test requirement information is subjected to platform interface requirement analysis to obtain the interface requirement information.

[0023] According to some embodiments of the present application, the requirement parsing of the test requirement information to obtain the test process information, dependency association constraints and interface requirement information further includes:

[0024] Performing parameter requirement analysis on the test requirement information to obtain test dynamic parameters;

[0025] The generating of the test script program according to the task test sequence, each of the test subtasks, the dependent associated tasks corresponding to each of the test subtasks, and the platform interface corresponding to each of the test subtasks includes:

[0026] The test script program is generated according to the task test sequence, each of the test subtasks, the dependent-associated tasks corresponding to each of the test subtasks, the platform interface corresponding to each of the test subtasks, and the test dynamic parameters.

[0027] According to some embodiments of the present application, the requirement parsing of the test requirement information to obtain the test process information, dependency association constraints and interface requirement information further includes:

[0028] Performing program version analysis on the test requirement information to obtain program version information;

[0029] The generating of the test script program according to the task test sequence, each of the test subtasks, the dependent associated tasks corresponding to each of the test subtasks, and the platform interface corresponding to each of the test subtasks includes:

[0030] The test script program is generated according to the task test sequence, each of the test subtasks, the dependent-associated tasks corresponding to each of the test subtasks, the platform interface corresponding to each of the test subtasks, and the program version information.

[0031] According to some embodiments of the present application, the requirement parsing of the test requirement information to obtain the test process information, dependency association constraints and interface requirement information further includes:

[0032] Performing parameter requirement analysis on the test requirement information to obtain test equipment information;

[0033] The generating of the test script program according to the task test sequence, each of the test subtasks, the dependent associated tasks corresponding to each of the test subtasks, and the platform interface corresponding to each of the test subtasks includes:

[0034] The test script program is generated according to the task test sequence, each of the test subtasks, the dependent-associated tasks corresponding to each of the test subtasks, the platform interface corresponding to each of the test subtasks, and the test equipment information.

[0035] According to some embodiments of the present application, in response to the presence of a dependency-associated task in a plurality of the test subtasks that belongs to a different application platform than the currently executed task, jumping out of the task test sequence, and executing the dependency-associated task corresponding to the application platform through each of the platform interfaces includes:

[0036] In response to the presence of the dependent associated task belonging to a different application platform from the currently executed task in the plurality of test subtasks, jumping out of the task test sequence and scanning a pre-configured associated task table to determine the dependent associated task that has not yet been executed as a candidate subtask;

[0037] Call a preset script subroutine to execute the candidate subtask, update the associated task table, and return to execute and scan the associated task table until all the dependent associated tasks belonging to different application platforms from the currently executed task are executed.

[0038] In a second aspect, an embodiment of the present application provides an electronic device, comprising: a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, it implements a testing method for a financial business application as described in any one of the embodiments of the first aspect of the present application.

[0039] In a third aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the storage medium stores a program, and the program is executed by a processor to implement a testing method for a financial business application as described in any one of the embodiments of the first aspect of the present application.

[0040] The testing method, electronic device, and storage medium for financial service applications according to the embodiments of the present application have at least the following beneficial effects:

[0041] According to the testing method for financial business applications of the first aspect of the present application, it is necessary to first obtain the test requirement information of the financial business application; wherein the test requirement information is used to reflect the test requirements corresponding to the financial business application; determine the test script program based on the test requirement information; wherein the test script program is configured with a task test sequence and multiple platform interfaces adapted to different application platforms, and the task test sequence is used to determine the execution order of multiple test subtasks in the financial business application; run the test script program for the financial business application so that the financial business application executes multiple test subtasks according to the task test sequence; in the process of executing multiple test subtasks according to the task test sequence, in response to the presence of dependent associated tasks in the multiple test subtasks that belong to different application platforms with the currently executed task, jump out of the task test sequence, and execute the dependent associated tasks of the corresponding application platform through each platform interface; after each dependent associated task is completed, return to execute the test subtasks except the dependent associated tasks according to the task test sequence. In this way, the interaction and data synchronization effects between different application platforms can be improved in the process of automated testing.

[0042] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the description of the embodiments in conjunction with the following drawings, in which:

[0044] Figure 1 A flowchart of a testing method for a financial business application provided in an embodiment of the present application;

[0045] Figure 2 Another flowchart of a testing method for a financial business application provided in an embodiment of the present application;

[0046] Figure 3 Another flowchart of a testing method for a financial business application provided in an embodiment of the present application;

[0047] Figure 4 Another flowchart of a testing method for a financial business application provided in an embodiment of the present application;

[0048] Figure 5 Another flowchart of a testing method for a financial business application provided in an embodiment of the present application;

[0049] Figure 6 Another flowchart of a testing method for a financial business application provided in an embodiment of the present application;

[0050] Figure 7 Another flowchart of a testing method for a financial business application provided in an embodiment of the present application;

[0051] Figure 8 Another flowchart of a testing method for a financial business application provided in an embodiment of the present application;

[0052] Fig. 9 It is a schematic diagram of the hardware structure of the electronic device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0053] The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and cannot be understood as limiting the present application.

[0054] In the description of this application, "several" means one or more, "more" means more than two, "greater than", "less than", "exceed", etc. are understood to exclude the number itself, and "above", "below", "within", etc. are understood to include the number itself. If there is a description of "first" or "second", it is only used for the purpose of distinguishing technical features, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features or implicitly indicating the order of the indicated technical features.

[0055] In the description of the present application, it should be understood that descriptions involving orientation, such as up, down, left, right, front, back, etc., indicating orientations or positional relationships, are based on the orientations or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as a limitation on the present application.

[0056] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "illustrative embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials, or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0057] In the description of this application, it should be noted that, unless otherwise clearly defined, the terms such as setting, installing, connecting, etc. should be understood in a broad sense, and technicians in the relevant technical field can reasonably determine the specific meanings of the above terms in this application in combination with the specific content of the technical solution. In addition, the identification of specific steps below does not represent a limitation on the order of steps and execution logic. The execution order and execution logic between each step should be understood and inferred with reference to the contents described in the embodiment.

[0058] In the financial business field, the technical problems faced by the automated testing solutions for financial business applications are mainly reflected in the following aspects:

[0059] First, financial business applications usually need to run on multiple application platforms and devices, including mobile applications (app side), web applications (web side), and backend services (interfaces). The interaction and data synchronization between these application platforms is a challenge in automated testing. For example, a user may start an insurance application process on a mobile app, then continue to fill in details on the web page, and finally complete the application through an interface call. This cross-application platform interaction requires automated testing to be able to seamlessly switch and verify between different application platforms.

[0060] Secondly, in view of the complexity of financial business applications, automated testing needs to be able to understand and simulate complex business processes. These business processes may include risk assessment, premium calculation, claims processing and other links, each of which may involve different application platforms. Automated testing needs to be able to cover these complex business logics to ensure the correctness and consistency of the entire process.

[0061] In addition, high concurrency and performance testing is also an important aspect in the financial business field. During peak hours, financial business applications may need to handle a large number of concurrent requests. Automated testing needs to be able to simulate high-concurrency scenarios, evaluate the performance and stability of financial business applications, and ensure that financial business applications can still operate normally under high load.

[0062] Finally, financial business applications need to run on a variety of devices and operating systems, including different mobile phones, tablets, and browsers. Automated testing needs to be able to cover these different environments to ensure application compatibility and user experience.

[0063] In summary, the technical problems that need to be solved for automated testing of financial business applications may include multi-application platform interaction, complex business logic, high concurrency and performance testing, compatibility and cross-device testing, and other aspects.

[0064] The present application aims to solve at least one of the technical problems existing in the prior art. To this end, the present application proposes a testing method, electronic device, and storage medium for financial business applications, which can improve the interaction and data synchronization effects between different application platforms during the automated testing process.

[0065] Further explanation is given below based on the accompanying drawings.

[0066] Reference Figure 1 According to the testing method for the financial service application program of the embodiment of the present application, the testing method may include:

[0067] Step S101, obtaining test requirement information of a financial business application; wherein the test requirement information is used to reflect the test requirements corresponding to the financial business application;

[0068] Step S102, determining a test script program based on the test requirement information; wherein the test script program is configured with a task test sequence and a plurality of platform interfaces adapted to different application platforms, and the task test sequence is used to determine the execution order of a plurality of test subtasks in the financial business application;

[0069] Step S103, running the test script program for the financial business application program, so that the financial business application program executes a plurality of test subtasks according to the task test sequence;

[0070] Step S104, in the process of executing multiple test subtasks according to the task test sequence, in response to the presence of dependent associated tasks belonging to different application platforms from the currently executed task in the multiple test subtasks, jump out of the task test sequence and execute the dependent associated tasks corresponding to the application platform through each platform interface;

[0071] Step S105, after all dependent and associated tasks are executed, return to execute the test subtasks except the dependent and associated tasks according to the task test sequence.

[0072] According to the testing method for financial business applications in the embodiment of the present application, it is necessary to first obtain the test requirement information of the financial business application; wherein the test requirement information is used to reflect the test requirements corresponding to the financial business application; determine the test script program based on the test requirement information; wherein the test script program is configured with a task test sequence and multiple platform interfaces adapted to different application platforms, and the task test sequence is used to determine the execution order of multiple test subtasks in the financial business application; run the test script program for the financial business application so that the financial business application executes multiple test subtasks according to the task test sequence; in the process of executing multiple test subtasks according to the task test sequence, in response to the presence of dependent associated tasks in multiple test subtasks that belong to different application platforms with the currently executed task, jump out of the task test sequence, and execute the dependent associated tasks of the corresponding application platform through each platform interface; after each dependent associated task is completed, return to execute the test subtasks except the dependent associated tasks according to the task test sequence. In this way, the interaction and data synchronization effects between different application platforms can be improved in the process of automated testing.

[0073] In some embodiments, step S101 is to obtain test requirement information of a financial service application program; wherein the test requirement information is used to reflect the test requirements corresponding to the financial service application program;

[0074] The embodiment of the present application first starts with obtaining the test requirement information of the financial business application. This step is the basis of the entire test process, which ensures that the starting point of the test is clear and specific. The test requirement information reflects the test requirements for the financial business application and provides a basis for the determination of the subsequent test script program.

[0075] In step S102 of some embodiments, a test script program is determined based on the test requirement information; wherein the test script program is configured with a task test sequence and a plurality of platform interfaces adapted to different application platforms, and the task test sequence is used to determine the execution order of a plurality of test subtasks in the financial business application program;

[0076] It should be noted that, based on the test requirement information, the embodiment of the present application determines the test script program. These test script programs not only configure the task test sequence, but also adapt to multiple platform interfaces of different application platforms. The task test sequence is the core of the test process, which determines the execution order of multiple test subtasks in the financial business application, which is crucial for simulating real user operation processes and business logic. The adaptation of the platform interface ensures that the test script program can run seamlessly on different application platforms, whether it is a mobile application, a web application or a back-end service interface.

[0077] Reference Figure 2According to some embodiments of the present application, step S102 of determining a test script program based on test requirement information may include:

[0078] Step S201, performing requirement analysis on the test requirement information to obtain test process information, dependency association constraints and interface requirement information;

[0079] Step S202, based on the test process information, determining the execution order of multiple test subtasks for the financial business application to generate a task test sequence;

[0080] Step S203, configuring corresponding dependent-associated tasks for each test subtask in the task test sequence based on the dependent-associated constraints;

[0081] Step S204, configuring a corresponding platform interface for each test subtask based on the interface requirement information;

[0082] Step S205 , generating a test script program according to the task test sequence, each test subtask, the dependent and associated tasks corresponding to each test subtask, and the platform interface corresponding to each test subtask.

[0083] In step S201 of some embodiments, the test requirement information is parsed to obtain the test process information, dependency association constraints and interface requirement information;

[0084] It should be noted that the purpose of parsing the test requirement information is to conduct an in-depth analysis of the test requirements of financial business applications to extract test process information, dependency constraints and interface requirement information. This information is the cornerstone of building a test script program, where the test process information reflects each link of the test, the dependency constraints reflect the dependency relationship between test tasks, and the interface requirement information reflects the interface required for interaction with different application platforms.

[0085] Reference Figure 3 According to some embodiments of the present application, step S201 performs requirement analysis on the test requirement information to obtain the test process information, dependency association constraints and interface requirement information, which may include:

[0086] Step S301, performing test process requirement analysis on the test requirement information to obtain test process information;

[0087] Step S302, perform dependency association requirement analysis on the test requirement information to obtain dependency association constraints. Step S303, perform platform interface requirement analysis on the test requirement information to obtain interface requirement information. In some embodiments of the present application, performing requirement analysis on the test requirement information is a key step in determining the test script program, which involves an in-depth analysis of the test requirements of the financial business application program to extract the test process information, dependency association constraints and interface requirement information. This process ensures the comprehensiveness and accuracy of the test and provides the necessary basic information for the subsequent test script program generation.

[0088] In step S301 of some embodiments, the test requirement information is analyzed for the test process requirement to obtain the test process information. This step is intended to determine the business logic and user operation process of the financial business application, thereby determining the starting point and end point of the test, as well as the key steps in the test process. The test process information includes the test points of each functional module in the financial business application, as well as the order and relationship between these test points. This information is crucial for generating a test script program that can fully cover the functions of the financial business application.

[0089] In step S302 of some embodiments, the test requirement information is subjected to dependency association requirement analysis to obtain dependency association constraints. In automated testing, there are sequential dependencies between many test tasks. For example, a user may need to log in to the system before performing other operations. Dependency association constraints define the dependencies between these tasks, ensuring that the test script program can execute the test tasks in the correct order and avoiding test failures caused by improper dependency handling.

[0090] In step S303 of some embodiments, the test requirement information is parsed for platform interface requirements to obtain interface requirement information. Financial business applications usually need to interact with multiple platforms, including mobile applications, web applications, and backend service interfaces. The interface requirement information defines these interaction points, including the APIs to be called, data formats, authentication methods, etc. This information is crucial for the test script to simulate user operations and verify the correctness of the interaction between systems.

[0091] Through the embodiment of the present application shown in step S301 to step S303, all key information required for building a test script program can be obtained, so as to generate an automated test script program that can accurately simulate user operations, verify business logic, process task dependencies, and simulate platform interactions in subsequent steps. This approach not only improves the efficiency and accuracy of the test, but also ensures that the test can cover all key aspects of the financial business application.

[0092] Reference Figure 4According to some embodiments of the present application, step S201 performs requirement analysis on the test requirement information to obtain the test process information, dependency association constraints and interface requirement information, and may also include:

[0093] Step S401, performing parameter requirement analysis on the test requirement information to obtain test dynamic parameters;

[0094] In step S205, generating a test script program according to the task test sequence, each test subtask, the dependent associated task corresponding to each test subtask, and the platform interface corresponding to each test subtask may include:

[0095] Step S402, generating a test script program according to the task test sequence, each test subtask, the dependent associated task corresponding to each test subtask, the platform interface corresponding to each test subtask, and the test dynamic parameters.

[0096] In some embodiments of the present application, the process of parsing the test requirement information is not limited to extracting the test process information, dependency association constraints and interface requirement information, but may also include parsing parameter requirements to obtain test dynamic parameters. This step ensures that the test script program can adapt to different test scenarios and conditions.

[0097] In some embodiments, step S401 performs parameter requirement analysis on the test requirement information to obtain test dynamic parameters. In automated testing, the use of test dynamic parameters is crucial because they allow the test script program to simulate various user inputs and operations in different test environments. These parameters may include user ID, transaction amount, insurance period, etc., which may change according to actual conditions during the test process. By parsing the parameter requirements in the test requirement information, these dynamic parameters can be configured for the test script program, making the test script program more flexible and configurable.

[0098] In some embodiments, step S402, the process of generating a test script program also includes generating a test script program according to the task test sequence, each test subtask, the dependent associated task corresponding to each test subtask, the platform interface corresponding to each test subtask, and the test dynamic parameters. This means that when generating a test script program, not only the logic of the task and the interaction of the platform should be considered, but also how to use the test dynamic parameters to simulate different test conditions should be considered. Such a test script program can better adapt to various test scenarios and improve the coverage and effectiveness of the test.

[0099] The embodiment of the present application shown by step S401 to step S402 provides a comprehensive, flexible and efficient automated testing solution for financial business applications. This method can not only ensure the comprehensiveness of the test, but also adjust the test script program according to the actual test requirements, thereby improving the adaptability and accuracy of the test. This is particularly important for the financial business industry, because they need to ensure that financial business applications can run stably in various complex and changing business scenarios.

[0100] Reference Figure 5 According to some embodiments of the present application, step S201 performs requirement analysis on the test requirement information to obtain the test process information, dependency association constraints and interface requirement information, and may also include:

[0101] Step S501, performing program version analysis on the test requirement information to obtain program version information;

[0102] In step S205, generating a test script program according to the task test sequence, each test subtask, the dependent associated task corresponding to each test subtask, and the platform interface corresponding to each test subtask may include:

[0103] Step S502, generating a test script program according to the task test sequence, each test subtask, the dependent associated task corresponding to each test subtask, the platform interface corresponding to each test subtask, and the program version information.

[0104] In some embodiments of the present application, the process of parsing the test requirement information is further extended to include parsing the program version, thereby obtaining the program version information. This step is an important part of the comprehensive parsing of the test requirement information, which ensures that the test script program can be customized and executed for a specific financial business application version, thereby improving the relevance and effectiveness of the test.

[0105] In step S501 of some embodiments, program version parsing is performed on the test requirement information to obtain program version information. In the process of software development and maintenance, financial business applications usually undergo multiple versions of iteration and updates. Each version may introduce new features, fix known problems, or change existing behaviors. Therefore, understanding the specific version targeted by the test is crucial to ensuring the accuracy of the test results. By parsing the program version requirements in the test requirement information, the corresponding version information can be configured for the test script program so that the test script program can be tested against a specific version of the financial business application.

[0106] In step S502 of some embodiments, a test script program is generated according to the task test sequence, each test subtask, the dependent associated task corresponding to each test subtask, the platform interface corresponding to each test subtask, and the program version information. This step is to convert the parsed information into an actual test script program, which will guide the automated testing tool to perform the predetermined test tasks. When generating the test script program, it is necessary to consider the execution order between tasks, the dependency relationship, the interaction with different platforms, and the test requirements for a specific program version.

[0107] The embodiment of the present application shown by steps S501 to S502 provides a comprehensive, flexible and efficient automated testing solution for financial business applications. This method can not only ensure the comprehensiveness of the test, but also adjust the test script program according to the actual test requirements, thereby improving the adaptability and accuracy of the test. This is particularly important for the financial business industry, because they need to ensure that financial business applications can run stably in various complex and changing business scenarios, and that each version update can be fully tested and verified. In this way, the quality of financial business applications can be effectively managed and controlled to ensure that end users can obtain a reliable and consistent experience.

[0108] Reference Figure 6 According to some embodiments of the present application, step S201 performs requirement analysis on the test requirement information to obtain the test process information, dependency association constraints and interface requirement information, and may also include:

[0109] Step S601, performing parameter requirement analysis on the test requirement information to obtain the test equipment information;

[0110] In step S205, generating a test script program according to the task test sequence, each test subtask, the dependent associated task corresponding to each test subtask, and the platform interface corresponding to each test subtask may include:

[0111] Step S602, generating a test script program according to the task test sequence, each test subtask, the dependent associated task corresponding to each test subtask, the platform interface corresponding to each test subtask, and the test device information.

[0112] In some embodiments of the present application, the process of parsing the test requirement information is further expanded to include parsing the test equipment information, thereby obtaining the test equipment information. This step is an important part of the comprehensive parsing of the test requirement information, which ensures that the test script program can be customized and executed for a specific test environment, thereby improving the relevance and effectiveness of the test.

[0113] In step S601 of some embodiments, parameter requirements are parsed for the test requirement information to obtain test device information. In automated testing, the selection of test equipment is crucial to the accuracy and reliability of the test results. Different devices may have different operating system versions, screen sizes, resolutions, and hardware configurations, all of which may affect the performance and behavior of financial business applications. Therefore, understanding the specific device targeted by the test is crucial to ensuring the accuracy of the test results. By parsing the device requirements in the test requirement information, the corresponding device information can be configured for the test script program so that the test script program can test the financial business application for a specific device.

[0114] In step S602 of some embodiments, a test script is generated according to the task test sequence, each test subtask, the dependent associated task corresponding to each test subtask, the platform interface corresponding to each test subtask, and the test device information. This step is to convert the parsed information into an actual test script program, which will guide the automated test tool to perform the predetermined test tasks. When generating the test script program, it is necessary to consider the execution order between tasks, dependencies, interactions with different platforms, and test requirements for specific test devices.

[0115] The embodiment of the present application shown by steps S601 to S602 provides a comprehensive, flexible and efficient automated testing solution for financial business applications. This method can not only ensure the comprehensiveness of the test, but also adjust the test script program according to the actual test requirements, thereby improving the adaptability and accuracy of the test. This is particularly important for the financial business industry, because they need to ensure that financial business applications can run stably in various complex and changing business scenarios, and can provide a consistent user experience on different devices. In this way, the quality of financial business applications can be effectively managed and controlled to ensure that end users can obtain a reliable and consistent experience.

[0116] In step S202 of some embodiments, based on the test process information, determining the execution order of multiple test subtasks for the financial business application to generate a task test sequence;

[0117] It should be noted that based on the test process information, the execution order of multiple test subtasks is determined for the financial business application to generate a task test sequence. This step ensures the logic and sequence of the test, so that the test can be carried out according to the preset process, thereby effectively simulating the user's operation process and business logic.

[0118] In step S203 of some embodiments, based on the dependency constraints, corresponding dependency-associated tasks are configured for each test subtask in the task test sequence;

[0119] It should be noted that, based on dependency constraints, corresponding dependency tasks are configured for each test subtask in the task test sequence. This step deals with the dependency relationship between test tasks, ensuring that all necessary pre-tasks have been completed before executing a test subtask. This dependency management is a key link in automated testing, which ensures the consistency and correctness of the test.

[0120] In step S204 of some embodiments, a corresponding platform interface is configured for each test subtask based on the interface requirement information;

[0121] It should be noted that, based on the interface requirement information, the corresponding platform interface is configured for each test subtask. This step ensures that the test script program can interact with different application platforms, whether it is a mobile application, a web application or a backend service interface. By adapting these platform interfaces, the test script program can simulate real user operations, thereby verifying the functions and performance of the application on different platforms.

[0122] In step S205 of some embodiments, a test script program is generated according to the task test sequence, each test subtask, the dependent associated tasks corresponding to each test subtask, and the platform interface corresponding to each test subtask.

[0123] It should be noted that in step S205, a test script is generated according to the task test sequence, each test subtask, the dependent associated tasks corresponding to each test subtask, and the platform interface corresponding to each test subtask. This test script is an automated testing tool that integrates all test requirements and configurations. It can execute test tasks according to a predetermined test process, handle dependencies between tasks, and interact with different application platforms.

[0124] The embodiment of the present application shown by steps S201 to S205 provides a structured and systematic testing solution for financial business applications, which not only improves the efficiency and accuracy of testing, but also ensures that the testing can cover all key aspects of financial business applications, thereby providing strong technical support for the development of the financial business industry.

[0125] Reference Figure 7 According to some embodiments of the present application, step S202 determines the execution order of multiple test subtasks for the financial business application based on the test process information to generate a task test sequence, which may include:

[0126] Step S701, determining the execution order of multiple test subtasks for the financial business application based on the test process information;

[0127] Step S702: assemble each test subtask into a corresponding test scenario case according to the execution order of each test subtask to obtain a task test sequence.

[0128] In some embodiments of the present application, the process of determining the execution order of multiple test subtasks for a financial business application based on the test process information and generating a task test sequence is a key step to ensure that automated testing can accurately simulate real business processes.

[0129] In step S701 of some embodiments, based on the test process information, the execution order of multiple test subtasks is determined for the financial business application. This step involves an in-depth understanding of the business logic and user operation process of the financial business application, as well as a detailed analysis of the test requirements. The execution order of the test subtasks reflects the operation steps that the user may take when actually using the financial business application, as well as the sequence of each link in the business process.

[0130] In step S702 of some embodiments, each test subtask is assembled into a corresponding test scenario case according to the execution order of each test subtask to obtain a task test sequence. This step is the process of converting an abstract test subtask into a specific, executable test case. The test scenario case may include not only the execution order of the test subtasks, but also detailed information such as specific operation steps, expected results, and exception handling. These test cases constitute a task test sequence, which provides a clear execution path and goal for automated testing.

[0131] The embodiment of the present application provided through step S701 to step S702 can generate a comprehensive, orderly and closely integrated task test sequence with the actual business process. This task test sequence can not only cover the key functional points of the financial business application, but also simulate the user's operations in different scenarios, thereby ensuring that the financial business application can operate normally in various situations. This approach improves the efficiency and coverage of the test, and also provides strong support for discovering and fixing potential problems.

[0132] In step S103 of some embodiments, a test script program is run for the financial business application program, so that the financial business application program performs a plurality of test subtasks according to a task test sequence;

[0133] It should be noted that when the test script program is actually run, the financial business application program will execute multiple test subtasks according to the task test sequence.

[0134] In step S104 of some embodiments, in the process of executing multiple test subtasks according to the task test sequence, in response to the presence of a dependent associated task belonging to a different application platform from the currently executed task in the multiple test subtasks, the task test sequence is jumped out, and the dependent associated task corresponding to the application platform is executed through each platform interface;

[0135] It should be pointed out that when a financial business application executes multiple test subtasks according to the task test sequence, if there are dependent tasks, that is, some test subtasks need to be completed on other application platforms, the test process will respond to this demand, jump out of the current task test sequence, and execute these dependent tasks through the corresponding platform interface. This flexibility is the key to solving cross-platform interaction problems. It allows the test process to smoothly transition between different platforms, ensuring data synchronization and task continuity.

[0136] Reference Figure 8 According to some embodiments of the present application, in step S104, in response to the presence of a dependency-associated task belonging to a different application platform from the currently executed task in the multiple test subtasks, jumping out of the task test sequence and executing the dependency-associated task of the corresponding application platform through each platform interface may include:

[0137] Step S801, in response to the presence of a dependent associated task belonging to a different application platform from the currently executed task in the plurality of test subtasks, jumping out of the task test sequence and scanning a pre-configured associated task table to determine the dependent associated task that has not been executed as a candidate subtask;

[0138] Step S802, calling a preset script subroutine to execute the candidate subtask, and updating the associated task table, returning to execute the scan associated task table, until all dependent associated tasks belonging to different application platforms of the currently executed task are executed.

[0139] In some embodiments of the present application, the mechanism for handling cross-platform dependent tasks is a key link in automated testing, especially in the testing of financial business applications. This mechanism ensures that the test process can be seamlessly switched and executed between different application platforms. When a test subtask is encountered during the test process, and its corresponding dependent task needs to be executed on a different application platform, the test script program will respond to this situation and jump out of the current task test sequence.

[0140] In step S801 of some embodiments, the test script program scans the pre-configured associated task table to determine the dependent associated tasks that have not yet been executed, and marks these tasks as candidate subtasks. This step is necessary because it allows the test system to identify all cross-platform tasks that need to be executed, even if they are not in the current task test sequence. In this way, the test system can ensure that all key dependent tasks are taken into account and executed in the correct order.

[0141] In step S802 of some embodiments, the test script program calls preset script subroutines to execute these candidate subtasks. These script subroutines are specially designed to handle tasks for specific platforms, and they can interact with the corresponding platform interfaces to perform necessary operations. After executing the candidate subtasks, the test script program updates the associated task table to reflect the execution status of the tasks. This update is important because it helps the test system track which tasks have been completed and which tasks are still waiting to be executed.

[0142] Finally, the test script program will return and continue to scan the associated task table, repeating the above process until all dependent associated tasks belonging to different application platforms from the currently executed task are executed. This cyclic execution method ensures the continuity and integrity of the test process, and can ensure the accuracy and effectiveness of the test even in the face of complex cross-platform dependencies. Through this mechanism, the test method of the embodiment of the present application can flexibly handle cross-platform dependent tasks in financial business applications, improving the adaptability and coverage of the test. This is particularly important for financial business applications because they usually need to run on multiple platforms and devices, and need to handle complex user interactions and data exchanges. In this way, it can be ensured that financial business applications can run stably and safely in various business scenarios.

[0143] In step S105 of some embodiments, after all dependent and associated tasks are completed, the process returns to execute test subtasks other than the dependent and associated tasks according to the task test sequence.

[0144] It should be noted that after all dependent tasks are completed, the test process will return and continue to execute other test subtasks in the task test sequence. This not only improves the efficiency of the test, but also ensures the comprehensiveness and accuracy of the test, because it can cover all key test points of financial business applications on different application platforms.

[0145] To sum up, the testing method of the embodiment of the present application provides a comprehensive and efficient solution for the automated testing of financial business applications by clarifying testing requirements, adapting to multi-platform interfaces, and flexibly handling dependent tasks. It effectively solves the technical problems of multi-platform interaction and data synchronization, and greatly improves the testing quality and efficiency of financial business applications.

[0146] Reference Fig. 9 , Fig. 9 The hardware structure of an electronic device of another embodiment is illustrated, and the electronic device includes:

[0147] The processor 901 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application;

[0148] The memory 902 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 902 can store an operating system and other applications. When the technical solution provided in the embodiments of this specification is implemented by software or firmware, the relevant program code is stored in the memory 902, and the processor 901 calls and executes the test method for the financial business application in the embodiments of this application;

[0149] Input / output interface 903, used to implement information input and output;

[0150] Communication interface 904, used to realize communication interaction between the device and other devices, which can be realized through wired mode (such as USB, network cable, etc.) or wireless mode (such as mobile network, WI FI, Bluetooth, etc.);

[0151] A bus 905 that transmits information between various components of the device (e.g., the processor 901, the memory 902, the input / output interface 903, and the communication interface 904);

[0152] The processor 901 , the memory 902 , the input / output interface 903 and the communication interface 904 are connected to each other in communication within the device via a bus 905 .

[0153] The embodiment of the present application further provides a computer program product, which includes a computer program. A processor of a computer device reads and executes the computer program, so that the computer device executes and implements the above-mentioned testing method for financial business applications.

[0154] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present disclosure described herein can, for example, be implemented in an order other than those illustrated or described herein. In addition, the terms "comprises" and "comprising" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0155] It should be understood that in the present disclosure, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, which may include any combination of single items or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0156] It should be understood that in the description of the embodiments of the present application, the meaning of multiple (or multiple items) is more than two, greater than, less than, exceed, etc. are understood to not include the number, and above, below, within, etc. are understood to include the number.

[0157] In the several embodiments provided in the present disclosure, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0158] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0159] In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0160] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present disclosure, or the part that contributes to the prior art or all or part of the technical solution, can be embodied in the form of a software product, and the computer software product is stored in a storage medium, which may include several instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the various embodiments of the present disclosure. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store program codes.

[0161] It should also be understood that the various implementations provided in the embodiments of the present application can be combined arbitrarily to achieve different technical effects.

[0162] The above is a specific description of the implementation methods of the present disclosure, but the present disclosure is not limited to the above implementation methods. Technical personnel familiar with the art can also make various equivalent modifications or substitutions without violating the spirit of the present disclosure. These equivalent modifications or substitutions are all included in the scope defined by the claims of the present disclosure.

Claims

1. A testing method for a financial business application, characterized in that: include: Acquire test requirement information of a financial business application; wherein the test requirement information is used to reflect the test requirements corresponding to the financial business application; Determine a test script program based on the test requirement information; wherein the test script program is configured with a task test sequence and a plurality of platform interfaces adapted to different application platforms, and the task test sequence is used to determine the execution order of a plurality of test subtasks in the financial business application; Running the test script program for the financial business application program so that the financial business application program executes the plurality of test subtasks according to the task test sequence; In the process of executing the plurality of test subtasks according to the task test sequence, in response to the presence of dependent associated tasks belonging to different application platforms from the currently executed task in the plurality of test subtasks, the task test sequence is jumped out, and the dependent associated tasks corresponding to the application platform are executed through each of the platform interfaces; After all the dependent and associated tasks are completed, the test subtasks other than the dependent and associated tasks are executed again according to the task test sequence.

2. The method according to claim 1, characterized in that The step of determining a test script program based on the test requirement information includes: Performing requirement analysis on the test requirement information to obtain test process information, dependency association constraints and interface requirement information; Based on the test process information, determining the execution order of the plurality of test subtasks for the financial business application to generate the task test sequence; Based on the dependency constraints, configuring corresponding dependency tasks for each of the test subtasks in the task test sequence; Based on the interface requirement information, configure the corresponding platform interface for each of the test subtasks; The test script program is generated according to the task test sequence, each of the test subtasks, the dependent-associated tasks corresponding to each of the test subtasks, and the platform interface corresponding to each of the test subtasks.

3. The method according to claim 2, characterized in that The step of determining the execution order of the plurality of test subtasks for the financial business application based on the test process information to generate the task test sequence includes: Based on the test process information, determining an execution order of the plurality of test subtasks for the financial business application; According to the execution order of each of the test subtasks, each of the test subtasks is assembled into a corresponding test scenario case to obtain the task test sequence.

4. The method according to claim 3, characterized in that The test requirement information is parsed to obtain test process information, dependency association constraints and interface requirement information, including: Performing test process requirement analysis on the test requirement information to obtain the test process information; Perform dependency association requirement analysis on the test requirement information to obtain the dependency association constraints The test requirement information is parsed for platform interface requirements to obtain the interface requirement information.

5. The method according to claim 4, characterized in that The requirement analysis of the test requirement information to obtain the test process information, dependency association constraints and interface requirement information also includes: Performing parameter requirement analysis on the test requirement information to obtain test dynamic parameters; The generating of the test script program according to the task test sequence, each of the test subtasks, the dependent associated tasks corresponding to each of the test subtasks, and the platform interface corresponding to each of the test subtasks includes: The test script program is generated according to the task test sequence, each of the test subtasks, the dependent-associated tasks corresponding to each of the test subtasks, the platform interface corresponding to each of the test subtasks, and the test dynamic parameters.

6. The method according to claim 4, characterized in that The requirement analysis of the test requirement information to obtain the test process information, dependency association constraints and interface requirement information also includes: Performing program version analysis on the test requirement information to obtain program version information; The generating of the test script program according to the task test sequence, each of the test subtasks, the dependent associated tasks corresponding to each of the test subtasks, and the platform interface corresponding to each of the test subtasks includes: The test script program is generated according to the task test sequence, each of the test subtasks, the dependent-associated tasks corresponding to each of the test subtasks, the platform interface corresponding to each of the test subtasks, and the program version information.

7. The method according to claim 4, characterized in that The requirement analysis of the test requirement information to obtain the test process information, dependency association constraints and interface requirement information also includes: Perform parameter requirement analysis on the test requirement information to obtain test equipment information; The generating of the test script program according to the task test sequence, each of the test subtasks, the dependent associated tasks corresponding to each of the test subtasks, and the platform interface corresponding to each of the test subtasks includes: The test script program is generated according to the task test sequence, each of the test subtasks, the dependent-associated tasks corresponding to each of the test subtasks, the platform interface corresponding to each of the test subtasks, and the test equipment information.

8. The method according to claim 1, characterized in that In response to the presence of a dependent-associated task belonging to a different application platform from the currently executed task in the plurality of test subtasks, jumping out of the task test sequence, and executing the dependent-associated task corresponding to the application platform through each of the platform interfaces, comprises: In response to the presence of the dependent associated task belonging to a different application platform from the currently executed task in the plurality of test subtasks, jumping out of the task test sequence and scanning a pre-configured associated task table to determine the dependent associated task that has not yet been executed as a candidate subtask; Call a preset script subroutine to execute the candidate subtask, update the associated task table, and return to execute and scan the associated task table until all the dependent associated tasks belonging to different application platforms from the currently executed task are executed.

9. An electronic device, characterized in that: include: A memory and a processor, wherein the memory stores a computer program, and the processor implements the testing method for a financial business application as described in any one of claims 1 to 8 when executing the computer program.

10. A computer-readable storage medium, characterized in that: The storage medium stores a program, and the program is executed by a processor to implement the testing method for a financial business application as described in any one of claims 1 to 8.

Images