AIX system-based online transaction automation test system and method

Abstract

This invention provides an automated online transaction testing system and method based on the AIX system, comprising: a test case interpreter / executor module: taking test case files written according to a predefined syntax as input, interpreting and executing the test case files, and outputting a test report file after execution; and a test case manager module: generating test case tar packages, and reusing, managing, and maintaining test cases based on these tar packages. The automated online transaction testing solution for banks provided by this invention standardizes online transaction testing; supports the writing of personalized test case content through preset syntax tags; and supports the automation of online transaction testing through the syntax interpretation and execution of test cases. This invention implements four main functions—test case packaging, test case unpacking, test case storage, and test case retrieval—through the test case manager, achieving centralized maintenance and management of test cases.

Description

Technical Field

[0001] This invention relates to the technical field of transaction testing, specifically to an automated online transaction testing system and method based on the AIX system. Background Technology

[0002] The current online transaction testing process for core banking systems suffers from the following problems: duplicate transaction messages, static test data, test results requiring comparison and verification, scattered test cases, non-reusable test data, and cumbersome test report writing. Disadvantages include difficulty in getting started, high skill requirements for testers, heavy workload, low reusability, and lack of test automation, necessitating manual intervention. Summary of the Invention

[0003] In view of the deficiencies in the existing technology, the purpose of this invention is to provide an automated testing system and method for online transactions based on the AIX system.

[0004] An automated online transaction testing system based on the AIX system, provided by the present invention, includes:

[0005] Test case interpreter and executor module: Obtains test case files written according to the specified syntax, interprets and translates the test case files and executes them, and outputs a test report file after execution;

[0006] Test Case Manager Module: Generates test case tar packages, and reuses, manages, and maintains test cases based on these tar packages.

[0007] Preferably, the test case interpreter module includes a syntax recognition module, a variable parsing module, a parameter filling module, a command execution module, and a data collection module;

[0008] The syntax recognition module parses the input case file content line by line, identifies the meaning of each line in the file through syntax tags, calls the variable parsing module to process it based on whether it contains variable definition-related content, calls the parameter filling module based on whether it contains variable placeholder-related content, and calls the command execution module to execute the corresponding syntax statement command after each line and variable-related content has been processed. After the statement command is executed, the data collection module is called to output the execution process and result data to the user terminal.

[0009] Preferably, the variable parsing module defines variables for command lines containing variable definitions and assigns values ​​to variables according to the labels of the corresponding command lines. The assignment methods include retrieving data from the database, retrieving data from the script, and random generation.

[0010] Preferably, the parameter filling module reads a list of defined variables for a command line containing variable placeholders, obtains the variable value corresponding to the variable name used by the placeholder in the command line, replaces the placeholder in the command line with the variable value, and generates an executable command.

[0011] Preferably, the command execution module executes statements, including SQL execution, message distribution, and script execution, after the syntax recognition module has finished processing the current case content and generated an executable command line, and records the execution results.

[0012] Preferably, the test case manager module includes a test case packaging module, a test case unpacking module, a test case storage module, and a test case retrieval module;

[0013] The test case packaging module compresses and packages the test case-related files to generate a test case tar package;

[0014] The test case unpacking module decompresses the test case tar package and outputs a directory containing transaction code. The directory contains test case files and related files. The output of the test case unpacking module is used as the input of the test case interpreter module.

[0015] The test case entry module implements the test case submission function. By inputting the tar package name, the packaged file is submitted to the management directory, and corresponding tag information is generated.

[0016] The test case export module is used to view and export test cases.

[0017] Preferably, the test case packaging module parses the input test case file, traverses the test case file line by line, parses the shell, bwtxt, and file syntax tags, parses the dependent files contained in the test case tags in the test case library and adds them to the list to be packaged, and adds the current test case file to the packaging list.

[0018] Preferably, the test case entry module determines whether the transaction, author, and history directory to which the submitted file belongs exist; otherwise, it creates a new directory, saves the submitted tar package file, and reads the case list contained in the file according to the contents of the tar package, and merges it into the main list of the transaction branch.

[0019] Preferably, viewing test cases in the test case library involves listing all test cases in the test case library by listing the folders under the test case library directory, and displaying a list of test cases based on the user's selection; removing test cases from the library involves, based on the user's selection, entering the folder directory where the test cases are located in the test case library, copying the test case tar package to the directory where the test case removal command is executed to complete the removal of the test cases from the library.

[0020] An automated testing method for online transactions based on the AIX system, provided by the present invention, includes:

[0021] Test case interpreter executor steps: Obtain test case files written according to the specified syntax, interpret and execute the test case files, and output a test report file after execution;

[0022] Test Case Manager steps: Generate test case tar packages, and reuse, manage, and maintain test cases based on the test case tar packages.

[0023] Compared with the prior art, the present invention has the following beneficial effects:

[0024] 1. This invention provides an automated testing solution for online bank transactions, which standardizes online transaction testing; supports the creation of personalized test cases using preset syntax tags; and supports the automation of online transaction testing through the syntax interpretation and execution of test cases.

[0025] 2. This invention implements four main functions through a test case manager: test case packaging, test case unpacking, test case storage, and test case retrieval, thereby achieving centralized maintenance and management of test cases.

[0026] 3. This invention designs a standardized test case syntax, test case lifecycle control, and corresponding test case execution interpreter, and generates a set of test case management tools to support test case submission and download. This simplifies and standardizes the testing process, while also supporting personalized test content, improving the reusability of test scripts, and greatly enhancing the level of automated testing for online transactions. Attached Figure Description

[0027] Other features, objects, and advantages of the present invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0028] Figure 1 This is a structural diagram of an online transaction automation testing system.

[0029] Figure 2 The executor module diagram is explained for the test case;

[0030] Figure 3 This is a flowchart for automated testing.

[0031] Figure 4 Here is a diagram of the Test Case Manager module structure;

[0032] Figure 5 Flowchart for packaging test cases;

[0033] Figure 6 Flowchart for the test case unpacking module;

[0034] Figure 7 Flowchart for the test case entry module;

[0035] Figure 8 This is a flowchart of the test case outbound module. Detailed Implementation

[0036] The present invention will now be described in detail with reference to specific embodiments. These embodiments will help those skilled in the art to further understand the present invention, but do not limit the invention in any way. It should be noted that those skilled in the art can make several changes and improvements without departing from the concept of the present invention. These all fall within the protection scope of the present invention.

[0037] This invention provides an automated testing system for online transactions based on the AIX system, referring to... Figure 1 As shown, this system includes two modules: a test case interpreter and executor module, and a test case manager module.

[0038] The test case execution interpreter module can take a test case file written according to the agreed syntax as input, interpret and translate the test case file and execute it. After execution, it outputs a test report file, thus completing the entire online transaction automation testing process.

[0039] Specifically, refer to Figure 2 and Figure 3 As shown, the test case execution interpreter module includes a syntax recognition module, a variable parsing module, a parameter filling module, a command execution module, and a data collection module. The workflow of each module will be further explained below.

[0040] (1) The syntax recognition module is responsible for parsing the input case file content line by line using regular expressions. Through the agreed syntax tags, it identifies the meaning of each line in the file. It calls the variable parsing module to process the variable definition-related content based on whether it contains variable placeholder-related content. After each line and variable-related content is processed, it calls the command execution module to execute the corresponding syntax statement command. After the statement command is executed, it calls the data collection module to output the execution process and result data to the screen and test report.

[0041] (2) For command lines containing variable definitions, the variable parsing module calls the variable parsing module to define variables and assigns values ​​to variables according to the corresponding command line label. It supports assignment methods such as database data retrieval, script data retrieval, and random generation.

[0042] (3) The parameter filling module calls the parameter filling module for the command line containing variable placeholders, reads the list of currently defined variables, obtains the variable value corresponding to the variable name used by the placeholder in the command line, replaces the placeholder in the command line with the variable value, and generates an executable command.

[0043] (4) After the syntax recognition submodule has finished processing the current case content and generated an executable command line, the command execution module calls the command execution module to execute the statement, supports operations such as SQL execution, message distribution, and script execution, and records the execution results.

[0044] (5) After all the statements in the case file have been executed, the data collection module calls the data collection module to summarize and format the results of the executed statements and the output content of the statements, and generate the test report file for this execution.

[0045] The following section provides a further explanation of the specific implementation of the test case executor module.

[0046] The test case interpreter executor simulates manual online transaction testing steps by inputting test case templates containing syntax tags such as variables, SQL, shell, and transaction message sending. It completes variable initialization, assignment, calculation, dynamic generation of test messages, and automatically performs data queries and comparisons before and after the online transaction. Upon completion, it automatically generates and outputs a test report.

[0047] The main logic of the test case interpreter executor is to read the input test case file, analyze the test cases contained in the file according to the case tags and generate a case list. The caller then specifies the cases to be executed in this test, and the execution phase begins.

[0048] The execution phase proceeds sequentially through three steps: global initialization, execution case, and global unloading and cleanup. Each step includes the following operations: parsing variable tags to define variables; parsing data extraction tags to generate data and assign values ​​to variables according to the specified data generation method; parsing arithmetic operation tags to assign values ​​to variables based on arithmetic operations; parsing shell tags to execute shell statements within the tags; and parsing message tags to fill in messages using variable values ​​based on placeholders in the message file, generate messages, and execute the message sending action.

[0049] After all steps are completed, a test report file will be automatically generated based on the execution results, including execution results of each tag, message sending results, and data comparison results before and after the transaction.

[0050] The test case manager module generates test case tar packages and uses these tar packages for test case reuse, management, and maintenance. (See reference...) Figure 4 As shown, the test case manager module includes a test case packaging module, a test case unpacking module, a test case import module, and a test case export module. The test case manager module reuses and manages test cases using test case tar packages. The workflow of each module is further explained below.

[0051] (1)Reference Figure 5 The test case packaging module is responsible for compressing and packaging test case-related files. It takes test case files as input and outputs a processed and compressed test case tar package. Other functions in the test case management module mainly revolve around the test case tar package. The output of the test case packaging module can be used as input to the test case unpacking module.

[0052] (2)Reference Figure 6 The test case unpacking module is responsible for decompressing the test case package. It takes the test case tar archive as input and outputs a directory containing transaction code. This directory contains the files from the file packaging list in the test case packaging function. The unpacked files contain the complete environment required for test case execution. The output of the test case unpacking module, including the test case files and related files, can be used as input to the test case interpreter / executor.

[0053] (3)Reference Figure 7 The test case submission module is responsible for implementing the test case submission function. By inputting a tarball name, it submits the packaged file to the management directory and generates tags such as author, case, and submission date. The main logic of the test case submission function is to determine if the transaction, author, and history directory to which the submitted file belongs exist; otherwise, it creates the corresponding directory and saves the submitted tarball file. It then reads the list of cases contained within the tarball file based on its contents and merges it into the main list of the corresponding transaction branch. The output of the test case submission module can be used as input to the test case output module.

[0054] (4)Reference Figure 8The test case export module comprises two parts: viewing test cases in the test case library and exporting test cases. Since the test case library primarily manages test cases using folders, the logic for viewing test cases involves listing all test cases in the library by enumerating the folders under the library directory, displaying a list of test cases based on the user's selection. Exporting test cases, based on the user's selection, navigates to the folder containing the test cases in the library, copies the test case tar archive to the directory where the export command is executed, and completes the export. The output of the test case export module includes test case files and related files, which can be used as input to the test case interpreter.

[0055] The following section provides a further explanation of the specific implementation of the test case management module.

[0056] (1) Test Case Packaging Module

[0057] This module compresses and packages test case files. It takes a test case file as input and outputs a compressed test case tarball. Other functions in the test case management module primarily revolve around this tarball. The main logic for packaging test cases is as follows: It parses the input test case file, iterates through the file line by line, parses shell, bwtxt, and file syntax tags, and adds dependent files contained within these tags to the list of files to be packaged. It then adds the current test case file to the list. Next, it creates an empty directory named after the transaction code to which the test case file belongs, copies the files from the list of files to be packaged to this directory, compresses them to generate the test case tarball, and the test case packaging process concludes.

[0058] (2) Test Case Unpacking Module

[0059] The test case package is decompressed. Input the test case tar package, and the final output is a directory containing the transaction code. This directory contains the files in the file packaging list of the test case packaging function. The unpacked files contain the complete environment required to execute the test case. The test case unpacking function ends here.

[0060] (3) Test case entry module

[0061] The test case submission function has been implemented. By inputting a tarball name, the user submits the packaged file to the management directory and generates tags such as author, case, and submission date. The main logic of the test case storage function is to check if the transaction, author, and history directory to which the submitted file belongs exist; otherwise, create the corresponding directory and save the submitted tarball file. Then, based on the contents of the tarball, it reads the list of cases contained in the file and merges it into the main list of the corresponding transaction branch.

[0062] (4) Test Case Output Module

[0063] It consists of two parts: viewing test cases in the test case library and removing test cases from the library. Since the test case library primarily uses folders to manage test cases, the logic for viewing test cases in the library is to list all test cases by listing the folders under the test case library directory, displaying a list of test cases based on the user's selection. Removing test cases from the library involves navigating to the folder containing the test cases in the library, copying the test case tar archive to the directory where the removal command is executed, and then removing the test cases from the library.

[0064] This invention also discloses an automated testing method for online transactions based on the AIX system. Those skilled in the art can understand this automated testing method for online transactions based on the AIX system as a preferred embodiment of the automated testing system for online transactions based on the AIX system. The specific testing method includes:

[0065] Test case interpreter executor steps: Take the test case file written according to the agreed syntax as input, interpret and execute the test case file, and output the test report file after execution;

[0066] Test Case Manager steps: Generate test case tar packages, and reuse, manage, and maintain test cases based on the test case tar packages.

[0067] Those skilled in the art will understand that, besides implementing the system and its various devices, modules, and units provided by this invention in the form of purely computer-readable program code, the same functions can be achieved entirely through logical programming of the method steps, making the system and its various devices, modules, and units of this invention function in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, the system and its various devices, modules, and units provided by this invention can be considered as a hardware component, and the devices, modules, and units included therein for implementing various functions can also be considered as structures within the hardware component; alternatively, the devices, modules, and units for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0068] In the description of this application, it should be understood that the terms "upper", "lower", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", etc., indicate the orientation or positional relationship 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.

[0069] Specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the specific embodiments described above, and those skilled in the art can make various changes or modifications within the scope of the claims, which do not affect the essence of the present invention. Unless otherwise specified, the embodiments and features described in this application can be arbitrarily combined with each other.

Claims

1. An AIX system based on-line transaction automation testing system, characterized in that, include: Test case interpreter and executor module: Obtains test case files written according to the specified syntax, interprets and translates the test case files and executes them, and outputs a test report file after execution; Test Case Manager module: Generates test case tar packages, and reuses, manages, and maintains test cases based on these tar packages; The test case interpreter module includes a syntax recognition module, a variable parsing module, a parameter filling module, a command execution module, and a data collection module; The syntax recognition module parses the input case file content line by line, identifies the meaning of each line in the file through syntax tags, calls the variable parsing module to process it based on whether it contains variable definition-related content, calls the parameter filling module based on whether it contains variable placeholder-related content, and calls the command execution module to execute the corresponding syntax statement command after each line and variable-related content has been processed. After the statement command is executed, the data collection module is called to output the execution process and result data to the user terminal. The variable parsing module defines variables for command lines containing variable definitions and assigns values ​​to variables according to the labels of the corresponding command lines. The assignment methods include retrieving data from the database, retrieving data from the script, and generating values ​​randomly. The parameter filling module reads the list of defined variables for command lines containing variable placeholders, obtains the variable value corresponding to the variable name used by the placeholder in the command line, replaces the placeholder in the command line with the variable value, and generates an executable command.

2. The AIX system based online transaction automation testing system as claimed in claim 1, wherein: The command execution module executes statements after the syntax recognition module has finished processing the current case content and generated an executable command line, including SQL execution, message distribution, and script execution, and records the execution results.

3. The online transaction automation testing system based on the AIX system according to claim 1, characterized in that: The test case manager module includes a test case packaging module, a test case unpacking module, a test case import module, and a test case export module; The test case packaging module compresses and packages the test case-related files to generate a test case tar package; The test case unpacking module decompresses the test case tar package and outputs a directory containing transaction code. The directory contains test case files and related files. The output of the test case unpacking module is used as the input of the test case interpreter module. The test case entry module implements the test case submission function. By inputting the tar package name, the packaged file is submitted to the management directory, and corresponding tag information is generated. The test case export module is used to view and export test cases.

4. The AIX system based online transaction automation testing system as claimed in claim 3, wherein: The test case packaging module parses the input test case file, traverses the test case file line by line, parses shell, bwtxt, and file syntax tags, parses the dependent files contained in the test case tags in the test case library and adds them to the list to be packaged, and adds the current test case file to the packaging list.

5. The AIX system based online transaction automation testing system as claimed in claim 3, wherein: The test case entry module determines whether the transaction, author, and history directory to which the submitted file belongs exist. If not, it creates the corresponding directory, saves the submitted tar package file, and reads the case list contained in the file according to the contents of the tar package, and merges it into the main list of the transaction branch.

6. The AIX system based online transaction automation testing system as claimed in claim 3, wherein: Viewing test cases in the test case library involves listing all test cases in the test case library directory by listing the folders under the test case library directory. The test case list is displayed based on the user's selection. The test case removal process involves entering the folder directory where the test cases are located in the test case library according to the user's selection, copying the test case tar package to the directory where the test case removal command is executed, and completing the removal of the test cases.

7. An AIX system-based online transaction automation testing method using the AIX system-based online transaction automation testing system according to any one of claims 1 to 6, characterized by, include: Test case interpreter executor steps: Obtain test case files written according to the specified syntax, interpret and execute the test case files, and output a test report file after execution; Test Case Manager steps: Generate test case tar packages, and reuse, manage, and maintain test cases based on the test case tar packages.

Images