Testing methods, electronic devices, and storage media for financial business applications

Abstract

This application relates to the financial and computer technology fields, and in particular to a testing method, electronic device, and storage medium for financial business applications. The testing method according to embodiments of this application requires first obtaining test requirement information; determining a test script program based on the test requirement information; running the test script program on the financial business application to cause the application to execute multiple test sub-tasks according to a task test sequence; during the execution of multiple test sub-tasks according to the task test sequence, in response to the existence of dependent tasks belonging to different application platforms than the currently executing task among the multiple test sub-tasks, the task test sequence is exited, and the dependent tasks of the corresponding application platform are executed through the interfaces of each platform, returning to the task test sequence to execute the remaining test sub-tasks excluding the dependent tasks. In this way, the interaction and data synchronization between different application platforms can be improved during automated testing.

Description

Technical Field

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

[0002] In the financial business sector, the technical challenges faced by automated testing solutions for financial business applications mainly lie in multiple aspects such as multi-application platform interaction, complex business logic, high concurrency and performance testing, compatibility and cross-device testing.

[0003] In related technologies, testing of financial business applications is often limited to a single application platform, such as mobile applications (app), web applications (web), or backend services (APIs). However, in more complex business scenarios, financial business applications may need to run on multiple application platforms. There are currently no mature solutions for the interaction and data synchronization between these application platforms in automated testing of financial business applications. Therefore, how to improve the interaction and data synchronization between different application platforms during automated testing has become a pressing technical problem in the industry. Summary of the Invention

[0004] This application aims to address at least one of the technical problems existing in the prior art. To this end, this 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 automated testing.

[0005] A testing method for a financial business application according to an embodiment of the first aspect of this application includes:

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

[0007] The test script program is determined based on the test requirements 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 sub-tasks in the financial business application;

[0008] The test script program is run on the financial business application so that the financial business application executes multiple test sub-tasks according to the task test sequence;

[0009] During the execution of multiple test subtasks according to the task test sequence, in response to the existence of dependent tasks in the multiple test subtasks that belong to different application platforms from the currently executed task, the task test sequence is exited, and the dependent tasks of the corresponding application platform are executed through the interface of each platform.

[0010] After all the aforementioned dependent tasks have been completed, the test subtasks other than the dependent tasks are executed according to the task test sequence.

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

[0012] The test requirement information is parsed to obtain test process information, dependency constraints, and interface requirement information;

[0013] Based on the test process information, the execution order of multiple test sub-tasks is determined for the financial business application to generate the task test sequence;

[0014] Based on the dependency association constraints, configure the corresponding dependency association tasks for each test subtask 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 based on the task test sequence, each test subtask, the dependent tasks corresponding to each test subtask, and the platform interface corresponding to each test subtask.

[0017] According to some embodiments of this application, determining the execution order of multiple test sub-tasks 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, the execution order of multiple test sub-tasks is determined for the financial business application;

[0019] Based on the execution order of each test subtask, the test subtasks are assembled into corresponding test scenario cases to obtain the task test sequence.

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

[0021] The test requirement information is parsed to obtain the test process information;

[0022] The test requirement information is parsed for dependency association requirements to obtain the dependency association constraints. The test requirement information is then parsed for platform interface requirements to obtain the interface requirement information.

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

[0024] The test requirement information is parsed to obtain the dynamic test parameters;

[0025] The step of generating the test script program based on the task test sequence, each test subtask, the dependent tasks corresponding to each test subtask, and the platform interface corresponding to each test subtask includes:

[0026] The test script program is generated based on the task test sequence, each test subtask, the dependent associated tasks corresponding to each test subtask, the platform interface corresponding to each test subtask, and the test dynamic parameters.

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

[0028] The test requirement information is parsed to obtain the program version information;

[0029] The step of generating the test script program based on the task test sequence, each test subtask, the dependent tasks corresponding to each test subtask, and the platform interface corresponding to each test subtask includes:

[0030] The test script program is generated based on the task test sequence, each test subtask, the dependent tasks corresponding to each test subtask, the platform interface corresponding to each test subtask, and the program version information.

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

[0032] The test requirements information is parsed to obtain the test equipment information;

[0033] The step of generating the test script program based on the task test sequence, each test subtask, the dependent tasks corresponding to each test subtask, and the platform interface corresponding to each test subtask includes:

[0034] The test script program is generated based on the task test sequence, each test subtask, the dependent associated tasks corresponding to each test subtask, the platform interface corresponding to each test subtask, and the test device information.

[0035] According to some embodiments of this application, the step of responding to the existence of dependent tasks belonging to different application platforms from the currently executing task in multiple test subtasks, exiting the task test sequence, and executing the dependent tasks corresponding to the application platform through the interfaces of each platform includes:

[0036] In response to the existence of dependent tasks belonging to different application platforms from the currently executing task in multiple test subtasks, the task test sequence is exited and a pre-configured associated task table is scanned to identify the dependent tasks that have not yet been executed as candidate subtasks.

[0037] The pre-defined script subroutine is invoked to execute the candidate subtask and update the associated task table. The process then returns to scan the associated task table until all dependent associated tasks belonging to different application platforms from the currently executing task have been executed.

[0038] Secondly, embodiments of this application provide an electronic device, including: a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the testing method for financial business applications as described in any one of the embodiments of the first aspect of this application.

[0039] Thirdly, embodiments of this application provide a computer-readable storage medium storing a program that is executed by a processor to implement the testing method for a financial business application as described in any one of the embodiments of the first aspect of this application.

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

[0041] According to the testing method for a financial business application according to the first aspect of this application, it is necessary to first obtain the testing requirement information of the financial business application; wherein, the testing requirement information is used to reflect the testing requirements corresponding to the financial business application; a test script program is determined based on the testing 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 sub-tasks in the financial business application; the test script program is run for the financial business application, so that the financial business application executes multiple test sub-tasks according to the task test sequence; during the execution of multiple test sub-tasks according to the task test sequence, in response to the existence of dependent tasks in multiple test sub-tasks belonging to different application platforms from the currently executed task, the task test sequence is exited, and the dependent tasks of the corresponding application platform are executed through the respective platform interfaces; after all dependent tasks have been completed, the test sub-tasks other than the dependent tasks are executed according to the task test sequence. In this way, the interaction and data synchronization effect between different application platforms can be improved during the automated testing process.

[0042] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

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

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

[0045] Figure 2 Another flowchart illustrating the testing method for financial business applications provided in this application embodiment;

[0046] Figure 3 Another flowchart illustrating the testing method for financial business applications provided in this application embodiment;

[0047] Figure 4 Another flowchart illustrating the testing method for financial business applications provided in this application embodiment;

[0048] Figure 5 Another flowchart illustrating the testing method for financial business applications provided in this application embodiment;

[0049] Figure 6 Another flowchart illustrating the testing method for financial business applications provided in this application embodiment;

[0050] Figure 7 Another flowchart illustrating the testing method for financial business applications provided in this application embodiment;

[0051] Figure 8 Another flowchart illustrating the testing method for financial business applications provided in this application embodiment;

[0052] Figure 9 This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0053] The embodiments of this application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting this application.

[0054] In the description of this application, "several" means one or more, "more than" means two or more, "greater than," "less than," and "exceeding" are understood to exclude the stated number, while "above," "below," and "within" are understood to include the stated number. The use of "first" and "second" in the description is merely for distinguishing technical features and should not be construed as indicating or implying relative importance, or implicitly indicating the number of indicated technical features, or implicitly indicating the order of the indicated technical features.

[0055] In the description of this application, it should be understood that the orientation descriptions, such as up, down, left, right, front, and back, are based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this application.

[0056] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "illustrative embodiment," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0057] In the description of this application, it should be noted that, unless otherwise explicitly defined, terms such as "setting," "installation," and "connection" should be interpreted broadly. Those skilled in the art can reasonably determine the specific meaning of the above terms in this application based on the specific content of the technical solution. Furthermore, the identification of specific steps in the following text does not imply a limitation on the order of steps or execution logic. The execution order and logic between each step should be understood and inferred from the content described in the embodiments.

[0058] In the financial business sector, the technical challenges faced by automated testing solutions for financial business applications mainly manifest in the following aspects:

[0059] First, financial business applications typically need to run on multiple application platforms and devices, including mobile applications (apps), web applications (web), and backend services (interfaces). The interaction and data synchronization between these application platforms present a challenge for automated testing. For example, a user might start an insurance application process on a mobile app, then continue filling in details on a webpage, and finally complete the application via an API call. This cross-application platform interaction requires automated testing to seamlessly switch and verify across different application platforms.

[0060] Secondly, given the complexity of financial business applications, automated testing needs to be able to understand and simulate complex business processes. These processes may include multiple stages such as risk assessment, premium calculation, and claims processing, each potentially involving different application platforms. Automated testing needs to cover these complex business logics to ensure the correctness and consistency of the entire process.

[0061] Furthermore, high concurrency and performance testing are also crucial aspects of financial business applications. During peak periods, 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 the applications can still function normally under high load.

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

[0063] In summary, the technical challenges that need to be addressed in automated testing of financial business applications can include multiple aspects such as multi-application platform interaction, complex business logic, high concurrency and performance testing, compatibility and cross-device testing.

[0064] This application aims to address at least one of the technical problems existing in the prior art. To this end, this 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 automated testing.

[0065] The following explanation is based on the accompanying drawings.

[0066] Reference Figure 1 The testing method for financial business applications according to the embodiments of this application may include:

[0067] Step S101: Obtain test requirement information for the financial business application; wherein, the test requirement information is used to reflect the test requirements corresponding to the financial business application.

[0068] Step S102: 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 sub-tasks in the financial business application;

[0069] Step S103: Run the test script program for the financial business application so that the financial business application executes multiple test sub-tasks according to the task test sequence;

[0070] Step S104: During the execution of multiple test subtasks according to the task test sequence, in response to the existence of dependent tasks in multiple test subtasks that belong to different application platforms than the currently executed task, the task test sequence is exited, and the dependent tasks of the corresponding application platform are executed through the interfaces of each platform.

[0071] Step S105: After all dependent and related tasks have been completed, return to the task test sequence and execute the test subtasks other than the dependent and related tasks.

[0072] According to the testing method for financial business applications in this application, the method first obtains the testing requirements information of the financial business application. This testing requirements information reflects the testing needs corresponding to the financial business application. A test script is then determined based on the testing requirements information. The test script is configured with a task test sequence and multiple platform interfaces adapted to different application platforms. The task test sequence determines the execution order of multiple test sub-tasks in the financial business application. The test script is run on the financial business application so that the application executes multiple test sub-tasks according to the task test sequence. During the execution of multiple test sub-tasks according to the task test sequence, if there are dependent tasks among the multiple test sub-tasks belonging to different application platforms than the currently executing task, the method exits the task test sequence and executes the dependent tasks of the corresponding application platform through each platform interface. After all dependent tasks have been completed, the method returns to executing the remaining test sub-tasks according to the task test sequence. This improves the interaction and data synchronization between different application platforms during automated testing.

[0073] In some embodiments, step S101 involves obtaining test requirement information for a financial business application; wherein the test requirement information reflects the test requirements corresponding to the financial business application.

[0074] This application begins by obtaining the testing requirements information for the financial business application. This step is fundamental to the entire testing process, ensuring that the starting point of the testing is clear and specific. The testing requirements information reflects the testing needs for the financial business application, providing a basis for determining the subsequent test scripts.

[0075] In some embodiments, step S102 involves determining a test script program based on test requirement information. The test script program is configured with a task test sequence and multiple platform interfaces adapted to different application platforms. The task test sequence is used to determine the execution order of multiple test sub-tasks in the financial business application.

[0076] It should be noted that, based on the testing requirements, the embodiments of this application define the test script programs. These test script programs not only configure task test sequences but also adapt to multiple platform interfaces of different application platforms. The task test sequence is the core of the testing process, determining the execution order of multiple test sub-tasks in the financial business application, which is crucial for simulating real user operation processes and business logic. Platform interface adaptation ensures that the test script programs can run seamlessly on different application platforms, whether it's a mobile application, a web application, or a backend service interface.

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

[0078] Step S201: Perform requirement parsing on the test requirement information to obtain test process information, dependency constraints, and interface requirement information;

[0079] Step S202: Based on the test process information, determine the execution order of multiple test sub-tasks for the financial business application to generate a task test sequence;

[0080] Step S203: Based on dependency and association constraints, configure corresponding dependency and association tasks for each test subtask in the task test sequence;

[0081] Step S204: Based on the interface requirement information, configure the corresponding platform interface for each test subtask;

[0082] Step S205: Generate test script programs based on the task test sequence, each test subtask, the dependent tasks corresponding to each test subtask, and the platform interfaces corresponding to each test subtask.

[0083] In some embodiments, step S201 involves parsing the test requirement information to obtain test process information, dependency constraints, and interface requirement information.

[0084] It should be noted that the purpose of requirements analysis is to conduct an in-depth analysis of the testing requirements of financial business applications, in order to extract test process information, dependency constraints, and interface requirements. This information forms the foundation for building test scripts. Specifically, the test process information reflects each stage of the test, dependency constraints reflect the dependencies between test tasks, and interface requirements reflect the interfaces needed to interact with different application platforms.

[0085] Reference Figure 3 According to some embodiments of this application, step S201 involves parsing the test requirement information to obtain test process information, dependency constraints, and interface requirement information, which may include:

[0086] Step S301: Perform test process requirement analysis on the test requirement information to obtain test process information;

[0087] Step S302 involves performing dependency and association requirement parsing on the test requirement information to obtain dependency and association constraints. Step S303 involves performing platform interface requirement parsing on the test requirement information to obtain interface requirement information. In some embodiments of this application, requirement parsing of the test requirement information is a crucial step in determining the test script program. It involves in-depth analysis of the test requirements of the financial business application to extract test process information, dependency and association constraints, and interface requirement information. This process ensures the comprehensiveness and accuracy of the test, providing necessary foundational information for subsequent test script program generation.

[0088] In some embodiments, step S301 involves parsing the test requirement information to obtain test process information. This step aims to determine the business logic and user operation flow of the financial application, thereby identifying the start and end points 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 application, as well as the order and relationship between these test points. This information is crucial for generating a test script program that can comprehensively cover the functions of the financial application.

[0089] In some embodiments, step S302 involves parsing the test requirement information to obtain dependency constraints. In automated testing, many test tasks have sequential dependencies; for example, a user may need to log in to the system before performing other operations. Dependency constraints define the dependencies between these tasks, ensuring that the test script executes the test tasks in the correct order and avoiding test failures due to improper handling of dependencies.

[0090] In step S303 of some embodiments, the test requirement information is parsed using platform interface requirements to obtain interface requirement information. Financial business applications typically 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 test scripts to simulate user operations and verify the correctness of interactions between systems.

[0091] Through the embodiments of this application shown in steps S301 to S303, all the key information required to build the test script program can be obtained, thereby generating an automated test script program in subsequent steps that can accurately simulate user operations, verify business logic, handle task dependencies, and simulate platform interactions. This approach not only improves the efficiency and accuracy of testing but also ensures that testing covers all key aspects of financial business applications.

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

[0093] Step S401: Analyze the test requirement information to obtain the test dynamic parameters;

[0094] In step S205, a test script program is generated based on the task test sequence, each test subtask, the dependent tasks corresponding to each test subtask, and the platform interface corresponding to each test subtask. This may include:

[0095] Step S402: Generate test script programs based on the task test sequence, each test subtask, the dependent tasks corresponding to each test subtask, the platform interfaces corresponding to each test subtask, and the test dynamic parameters.

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

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

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

[0099] The embodiments of this application shown in steps S401 to S402 provide a comprehensive, flexible, and efficient automated testing solution for financial business applications. This approach not only ensures the comprehensiveness of testing but also allows for the adjustment of test scripts according to actual testing needs, thereby improving the adaptability and accuracy of testing. This is particularly important for the financial industry, as it needs to ensure that financial business applications operate stably under various complex and changing business scenarios.

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

[0101] Step S501: Parse the program version information of the test requirement information to obtain the program version information;

[0102] In step S205, a test script program is generated based on the task test sequence, each test subtask, the dependent tasks corresponding to each test subtask, and the platform interface corresponding to each test subtask. This may include:

[0103] Step S502: Generate test script programs based on the task test sequence, each test subtask, the dependent tasks corresponding to each test subtask, the platform interfaces corresponding to each test subtask, and the program version information.

[0104] In some embodiments of this application, the process of parsing test requirement information is further extended to include parsing the program version to obtain program version information. This step is an important component of comprehensive test requirement information parsing, ensuring that test scripts can be customized and executed for specific financial business application versions, thereby improving the relevance and effectiveness of the tests.

[0105] In some embodiments, step S501 involves parsing the program version information from the test requirement information to obtain program version information. During software development and maintenance, financial business applications typically undergo multiple version iterations and updates. Each version may introduce new features, fix known issues, or change existing behavior. Therefore, understanding the specific version being tested is crucial for ensuring the accuracy of 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, enabling the test script program to test specific versions of the financial business application.

[0106] In some embodiments, step S502 involves generating test script programs based on the task test sequence, each test subtask, the dependent tasks corresponding to each test subtask, the platform interfaces corresponding to each test subtask, and the program version information. This step transforms the parsed information into actual test script programs, which will guide automated testing tools to execute predetermined test tasks. When generating test script programs, it is necessary to consider the execution order between tasks, dependencies, interactions with different platforms, and testing requirements for specific program versions.

[0107] The embodiments of this application, illustrated in steps S501 to S502, provide a comprehensive, flexible, and efficient automated testing solution for financial business applications. This approach not only ensures comprehensive testing but also allows for the adjustment of test scripts according to actual testing needs, thereby improving the adaptability and accuracy of the tests. This is particularly important for the financial industry, which needs to ensure that financial business applications operate stably under various complex and changing business scenarios, and that each version update is thoroughly tested and verified. In this way, the quality of financial business applications can be effectively managed and controlled, ensuring that end users receive a reliable and consistent experience.

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

[0109] Step S601: Analyze the test requirements information to obtain the test equipment information;

[0110] In step S205, a test script program is generated based on the task test sequence, each test subtask, the dependent tasks corresponding to each test subtask, and the platform interface corresponding to each test subtask. This may include:

[0111] Step S602: Generate a test script program based on the task test sequence, each test subtask, the dependent tasks corresponding to each test subtask, the platform interface corresponding to each test subtask, and the test device information.

[0112] In some embodiments of this application, the process of parsing test requirement information is further extended to include parsing test equipment information to obtain test equipment information. This step is an important component of comprehensive test requirement information parsing, ensuring that test scripts can be customized and executed for specific test environments, thereby improving the relevance and effectiveness of testing.

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

[0114] In some embodiments, step S602 involves generating test script programs based on the task test sequence, each test subtask, the dependent tasks corresponding to each test subtask, the platform interfaces corresponding to each test subtask, and the test device information. This step transforms the parsed information into actual test script programs, which will guide automated testing tools to execute predetermined test tasks. When generating test script programs, it is necessary to consider the execution order between tasks, dependencies, interactions with different platforms, and testing requirements for specific test devices.

[0115] The embodiments of this application shown in steps S601 to S602 provide a comprehensive, flexible, and efficient automated testing solution for financial business applications. This approach not only ensures the comprehensiveness of testing but also allows for the adjustment of test scripts according to actual testing needs, thereby improving the adaptability and accuracy of testing. This is particularly important for the financial industry, as it needs to ensure that financial business applications run stably under various complex and changing business scenarios and provide a consistent user experience across different devices. In this way, the quality of financial business applications can be effectively managed and controlled, ensuring that end users receive a reliable and consistent experience.

[0116] In some embodiments, step S202 involves determining the execution order of multiple test sub-tasks for the financial business application based on test process information, in order to generate a task test sequence.

[0117] It should be noted that, based on the test process information, the execution order of multiple test sub-tasks for the financial business application is determined to generate a task test sequence. This step ensures the logicality and sequence of the tests, enabling them to proceed according to the preset process, thereby effectively simulating user operation processes and business logic.

[0118] In some embodiments, step S203 involves configuring corresponding dependency-related tasks for each test subtask in the task test sequence based on dependency-related constraints.

[0119] It's important to note that, based on dependency constraints, corresponding dependency tasks are configured for each test subtask in the test sequence. This step handles the dependencies between test tasks, ensuring that all necessary prerequisite tasks are completed before executing a particular test subtask. This dependency management is a crucial aspect of automated testing, guaranteeing the consistency and correctness of the tests.

[0120] In some embodiments, step S204 involves configuring corresponding platform interfaces for each test subtask based on interface requirement information.

[0121] It's important to note that, based on the interface requirements, corresponding platform interfaces are configured for each test subtask. This step ensures that the test scripts can interact with different application platforms, whether mobile applications, web applications, or backend service interfaces. By adapting to these platform interfaces, the test scripts can simulate real user operations, thereby verifying the application's functionality and performance on different platforms.

[0122] In some embodiments, step S205 involves generating a test script program based on the task test sequence, each test subtask, the dependent 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 program is generated based on the task test sequence, each test subtask, the dependent tasks corresponding to each test subtask, and the platform interface corresponding to each test subtask. This test script program 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 embodiments of this application shown via steps S201 to S205 provide a structured and systematic testing solution for financial business applications. This not only improves the efficiency and accuracy of testing but also ensures that 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 this application, step S202, based on test process information, determines the execution order of multiple test sub-tasks for the financial business application to generate a task test sequence, and may include:

[0126] Step S701: Based on the test process information, determine the execution order of multiple test sub-tasks for the financial business application;

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

[0128] In some embodiments of this application, the process of determining the execution order of multiple test sub-tasks for a financial business application based on test process information and generating a task test sequence is a key step in ensuring that automated testing can accurately simulate real business processes.

[0129] In some embodiments, step S701 involves determining the execution order of multiple test sub-tasks for the financial business application based on test process information. This step involves a deep understanding of the business logic and user operation flow of the financial business application, as well as a detailed analysis of the test requirements. The execution order of the test sub-tasks reflects the operation steps that users may take when actually using the financial business application, and the sequential relationship between various stages in the business process.

[0130] In step S702 of some embodiments, the test subtasks are assembled into corresponding test scenario test cases according to their execution order to obtain a task test sequence. This step is the process of transforming abstract test subtasks into concrete, executable test cases. Test scenario test cases 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 the task test sequence, providing a clear execution path and objective for automated testing.

[0131] The embodiments of this application provided in steps S701 to S702 can generate a comprehensive, orderly task test sequence that is closely integrated with actual business processes. This task test sequence can not only cover the key functionalities of financial business applications, but also simulate user operations in different scenarios, thereby ensuring that financial business applications can operate normally under various conditions. This approach improves testing efficiency and coverage, while also providing 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 so that the financial business application executes multiple test sub-tasks according to the task test sequence.

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

[0134] In step S104 of some embodiments, during the execution of multiple test subtasks according to the task test sequence, in response to the existence of dependent tasks in the multiple test subtasks that belong to different application platforms from the currently executed task, the task test sequence is broken, and the dependent tasks of the corresponding application platform are executed through the interface of each platform.

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

[0136] Reference Figure 8 According to some embodiments of this application, in step S104, in response to the existence of dependent tasks belonging to different application platforms than the currently executing task among multiple test subtasks, the task test sequence is exited, and the dependent tasks of the corresponding application platforms are executed through the interfaces of each platform. This may include:

[0137] Step S801: In response to the existence of dependent tasks belonging to different application platforms from the currently executing task in multiple test subtasks, the task test sequence is exited and the pre-configured associated task table is scanned to identify the dependent tasks that have not yet been executed as candidate subtasks.

[0138] Step S802: Call the preset script subroutine to execute the candidate subtask and update the associated task table. Return to the execution and scan the associated task table until all dependent associated tasks belonging to different application platforms from the currently executed task have been executed.

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

[0140] In step S801 of some embodiments, the test script program scans a pre-configured list of associated tasks to identify dependent 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 critical 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 specifically designed to handle tasks for a particular platform; they can interact with the corresponding platform interface and perform necessary operations. After executing the candidate subtasks, the test script program updates the associated task table to reflect the task execution status. 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 returns and continues scanning the associated task table, repeating the above process until all dependent tasks belonging to different application platforms as the currently executing task have been executed. This cyclical execution method ensures the continuity and integrity of the testing process, guaranteeing the accuracy and effectiveness of the tests even when faced with complex cross-platform dependencies. Through this mechanism, the testing method of this application embodiment can flexibly handle cross-platform dependency tasks in financial business applications, improving the adaptability and coverage of the tests. This is particularly important for financial business applications, as they typically need to run on multiple platforms and devices and handle complex user interactions and data exchanges. This approach ensures that financial business applications can operate stably and securely in various business scenarios.

[0143] In some embodiments, step S105 involves returning to execute test subtasks other than the dependent tasks after all dependent tasks have been completed.

[0144] It should be noted that after all dependent tasks have been completed, the test process returns and continues executing other test subtasks in the task test sequence. This not only improves testing efficiency but also ensures the comprehensiveness and accuracy of the tests, as it covers all key test points of the financial business application across different application platforms.

[0145] In summary, the testing method of this application provides a comprehensive and efficient solution for the automated testing of financial business applications by clarifying test 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 Figure 9 , Figure 9 The hardware structure of an electronic device according to another embodiment is illustrated. The electronic device includes:

[0147] The processor 901 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, 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 this application.

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

[0149] The input / output interface 903 is used to implement information input and output;

[0150] The communication interface 904 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

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

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

[0153] This application also provides a computer program product, which includes a computer program. A processor of a computer device reads and executes the computer program, causing the computer device to perform the aforementioned testing method for a financial business application.

[0154] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in this disclosure and the foregoing drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “including,” and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatuses.

[0155] It should be understood that in this disclosure, "at least one item" means one or more, and "more than one" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, which can include any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0156] It should be understood that in the description of the embodiments of this application, "multiple" means two or more, "greater than", "less than", "exceeding" etc. are understood to exclude the number itself, and "above", "below", "within" etc. are understood to include the number itself.

[0157] In the several embodiments provided in this disclosure, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.

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

[0159] Furthermore, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0160] If the integrated unit is implemented as 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 this disclosure, in essence, 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. This computer software product is stored in a storage medium and may include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0161] It should also be understood that the various implementation methods provided in this application can be combined arbitrarily to achieve different technical effects.

[0162] The above is a detailed description of the embodiments of this disclosure. However, this disclosure is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of this disclosure. All such equivalent modifications or substitutions are included within the scope defined by the claims of this disclosure.

Claims

1. A testing method for financial business applications, characterized in that, include: Obtain test requirement information for a financial business application; wherein the test requirement information is used to reflect the test requirements corresponding to the financial business application; The test requirement information is parsed to obtain test process information, dependency constraints, and interface requirement information; Based on the test process information, the execution order of multiple test sub-tasks is determined for the financial business application to generate a task test sequence; Based on the dependency association constraints, configure corresponding dependency association tasks for each test subtask in the task test sequence; Based on the interface requirement information, configure the corresponding platform interface for each of the test subtasks; A test script program is generated based on the task test sequence, each test subtask, the dependent tasks corresponding to each test subtask, and the platform interface corresponding to each test subtask. The test script program is run on the financial business application so that the financial business application executes multiple test sub-tasks according to the task test sequence; During the execution of multiple test subtasks according to the task test sequence, in response to the existence of dependent and associated tasks in the multiple test subtasks that belong to different application platforms from the currently executed task, the task test sequence is exited and a pre-configured associated task table is scanned to identify the dependent and associated tasks that have not yet been executed as candidate subtasks. The pre-set script subroutine is invoked to execute the candidate subtask and update the associated task table. The execution is then returned to scan the associated task table until all dependent associated tasks belonging to different application platforms from the currently executing task are executed. After all the aforementioned dependent tasks have been completed, the test subtasks other than the dependent tasks are executed according to the task test sequence.

2. The method according to claim 1, characterized in that, Based on the test process information, the execution order of multiple test sub-tasks for the financial business application is determined to generate a task test sequence, including: Based on the test process information, the execution order of multiple test sub-tasks is determined for the financial business application; Based on the execution order of each test subtask, the test subtasks are assembled into corresponding test scenario cases to obtain the task test sequence.

3. The method according to claim 2, characterized in that, The process of parsing the test requirement information to obtain test process information, dependency constraints, and interface requirement information includes: The test requirement information is parsed to obtain the test process information; The test requirement information is parsed for dependency association requirements to obtain the dependency association constraints. The test requirement information is parsed using platform interface requirements to obtain the interface requirement information.

4. The method according to claim 3, characterized in that, The step of parsing the test requirement information to obtain test process information, dependency constraints, and interface requirement information also includes: The test requirement information is parsed to obtain the dynamic test parameters; The step of generating the test script program based on the task test sequence, each test subtask, the dependent tasks corresponding to each test subtask, and the platform interface corresponding to each test subtask includes: The test script program is generated based on the task test sequence, each test subtask, the dependent associated tasks corresponding to each test subtask, the platform interface corresponding to each test subtask, and the test dynamic parameters.

5. The method according to claim 3, characterized in that, The step of parsing the test requirement information to obtain test process information, dependency constraints, and interface requirement information also includes: The test requirement information is parsed to obtain the program version information; The step of generating the test script program based on the task test sequence, each test subtask, the dependent tasks corresponding to each test subtask, and the platform interface corresponding to each test subtask includes: The test script program is generated based on the task test sequence, each test subtask, the dependent tasks corresponding to each test subtask, the platform interface corresponding to each test subtask, and the program version information.

6. The method according to claim 3, characterized in that, The step of parsing the test requirement information to obtain test process information, dependency constraints, and interface requirement information also includes: The test requirements information is parsed to obtain the test equipment information; The step of generating the test script program based on the task test sequence, each test subtask, the dependent tasks corresponding to each test subtask, and the platform interface corresponding to each test subtask includes: The test script program is generated based on the task test sequence, each test subtask, the dependent associated tasks corresponding to each test subtask, the platform interface corresponding to each test subtask, and the test device information.

7. An electronic device, characterized in that, include: A memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the testing method for a financial business application as described in any one of claims 1 to 6.

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

Images