A test method and device for a friend query plug-in, an electronic device, and a medium

Abstract

The application discloses a kind of friend query plug-in test method, device, electronic equipment and medium, it is related to application test technical field.The specific implementation of the method includes: obtaining the test request of friend query plug-in;Obtain the test request of friend query plug-in;According to the query interface demand, the test points of friend query plug-in are analyzed, and the test script corresponding to the query condition included in test point is written;Test data and verification data are selected from historical transaction data, test data and test script are combined, and the test case of friend query plug-in is generated;In response to test request, execute test case, determine whether the execution result of test case is verification data, to obtain the test result of test request.The implementation can build friend query plug-in suitable for fund transaction platform, various transaction problems in transaction process are handled in time, and transaction cost and computing resources are saved.

Description

Technical Field

[0001] This invention relates to the field of application testing technology, and in particular to a testing method, apparatus, electronic device, and medium for a friend query plugin. Background Technology

[0002] A fund trading platform refers to a fund business processing system in the financial market. Platform users can process entrusted transactions through the fund trading platform, including creating new transactions, processing transaction data, reviewing transactions, confirming transactions, and clearing transactions.

[0003] In existing fund trading platforms, when users conduct transactions, they can usually only passively receive and process transaction-related information. However, various situations may occur during the transaction process, such as user errors in previous or subsequent operations, or failure to add new information, which may lead to transaction interruptions. These situations need to be reported to the platform for timely processing to prevent them from affecting subsequent processes.

[0004] In the process of realizing this invention, the inventors discovered at least the following problems in the prior art:

[0005] Because users cannot share information, correct errors, or update data in a timely manner, many transactions are interrupted, and even transactions that are about to be completed are terminated, requiring users to restart the entire transaction process. This greatly wastes human, time, and computing resources, resulting in a poor customer experience for the platform. Therefore, how to build a good communication mechanism between users on a money market trading platform and ensure that the communication mechanism is functioning properly has become a major challenge in the testing of existing money market trading platforms. Summary of the Invention

[0006] In view of this, embodiments of the present invention provide a testing method, apparatus, electronic device, medium, and program product for a friend query plugin, which can build a friend query plugin suitable for a financial trading platform, enabling users to find friend information through the friend query plugin and promptly handle various transaction issues during the transaction process, greatly saving transaction time costs, manpower costs, and computing resources, and improving the user experience of platform customers.

[0007] Furthermore, this embodiment of the invention provides an integration testing method for a fund trading platform including a friend query plugin. This method allows for joint testing of the connections between various modules of the fund trading platform to determine whether the interface calls between these modules meet requirements. It simulates the actual operation of the entire platform to accurately locate abnormal nodes, especially those with interdependent relationships, eliminating potential operational risks and ensuring a smooth launch. Compared to existing unit tests that only test the normal operation of a single module, specialized tests that only test a single function, and system tests that are typically non-functional (load, stress, performance, reliability, etc.), this method can comprehensively test operational interference between modules without dependencies, interaction failures between modules with dependencies, global data structures, the normality of the entire transaction process connecting multiple modules, and whether the final result meets the expectations of the entire business process. It efficiently and accurately locates testing problems and promptly remedies deviations, enabling the smooth launch and operation of a multi-module fund trading platform, significantly improving testing efficiency, platform launch efficiency, and platform operational security.

[0008] To achieve the above objectives, according to one aspect of the present invention, a testing method for a friend search plugin is provided, comprising:

[0009] Obtain the test request for the friend query plugin; wherein, the test request includes the friend query plugin requirements and historical transaction data of the friend query plugin, and the friend query plugin requirements include query interface requirements;

[0010] Based on the query interface requirements, analyze the key points of testing the friend query plugin, and write test scripts corresponding to the query conditions included in the key points of testing.

[0011] Test data and verification data are selected from the historical transaction data, and the test data and the test script are combined to generate test cases for the friend query plugin.

[0012] In response to the test request, the test case is executed, and it is determined whether the execution result of the test case is verification data, so as to obtain the test result of the test request.

[0013] Optionally, writing a test script corresponding to the query conditions included in the test points includes:

[0014] Construct the plugin data table for the friend query plugin;

[0015] Using the equivalence class partitioning method, generate the conditional statement for the query conditions;

[0016] Insert the plugin data table into the conditional statement to obtain the test script for the friend query plugin.

[0017] Optionally, the friend query plugin requirements also include information synchronization requirements and user permission requirements; the test script also includes:

[0018] Based on the information synchronization requirements and user permission requirements, analyze the key points of testing the friend query plugin, and determine the information synchronization conditions and user permission conditions.

[0019] Using the decision table method, conditional statements for the information synchronization condition and the user permission condition are generated respectively.

[0020] Optionally, the query interface requirements include adding a friend query interface, which includes a user name label, a user name input box, an organization name label, an organization name input box, and a query button.

[0021] The information synchronization requirements include adding an information synchronization button to the friend search interface; automatically synchronizing friend information when the friend search plugin is enabled; and allowing users to click the information synchronization button to synchronize friend information when the friend search plugin is enabled.

[0022] The user permission requirements include user permissions limited to the user's friend list.

[0023] Optionally, generating the conditional statement for the query conditions using the equivalence class partitioning method includes:

[0024] Using the equivalence class partitioning method, the input data type of the query condition is determined, and the condition statement of the query condition is obtained;

[0025] The method of using decision tables to generate conditional statements for the information synchronization condition and the user permission condition includes:

[0026] The on / off state of the friend query plugin and the click attribute of the information synchronization button are represented as conditional statements for the information synchronization conditions using the decision table method.

[0027] Based on the current user ID, the conditional statement for the user permission conditions is generated using the decision table method.

[0028] Optionally, the conditional statement for the query is:

[0029] Determine whether the data in the user name input box and / or the organization name input box is a string type; if so, determine whether the click attribute of the query button is empty.

[0030] If the click attribute of the query button is not empty, perform a search for the input content.

[0031] Optionally, the conditional statement for the information synchronization condition is:

[0032] Determine whether the friend query plugin is enabled. If it is, synchronize the friend information. If not, determine whether the click attribute of the information synchronization button is empty.

[0033] If the click attribute of the information synchronization button is not empty, the friend query plugin is enabled, and friend information is synchronized.

[0034] Optionally, the conditional statement for the user permission conditions is:

[0035] Construct a mapping relationship between the user IDs of all users and the friend information corresponding to the user IDs;

[0036] Find and display the friend information that matches the current user ID in the mapping relationship.

[0037] Optionally, inserting the plugin data table into the conditional statement includes:

[0038] When the friend query plugin is enabled, friend information is synchronized to the plugin's data table.

[0039] or,

[0040] If the friend query plugin is off and the click attribute of the information synchronization button is not empty, synchronize friend information to the plugin data table.

[0041] Optionally, the test request also includes a communication requirement between the friend query plugin and the fund trading platform. Before synchronizing friend information to the plugin's data table, the conditional statements for the interaction conditions corresponding to the communication requirement include:

[0042] Determine whether the communication between the friend query plugin and the fund trading platform is normal. If so, execute the synchronization of friend information from the fund trading platform to the plugin's data table.

[0043] Optionally, the test cases for generating the friend query plugin include:

[0044] Target data that conforms to the initial framework of the plugin data table is filtered from the historical transaction data; wherein, the initial framework of the plugin data table includes user ID, user name, friend ID, friend name, name of the organization to which the user belongs, and name of the organization to which the friend belongs;

[0045] Based on the test criteria, test data is selected from the target data, and boundary value analysis is used to determine the verification data corresponding to the test data.

[0046] The test data and the test script are combined to obtain test cases for the friend query plugin.

[0047] Optionally, for the query conditions, determining the verification data corresponding to the test data includes:

[0048] The test data includes multiple user names. The boundary value analysis method is used to perform precise matching of the multiple user names to determine the query results, which include the serial number, organization name, user name and user ID corresponding to the multiple user names, as verification data corresponding to the test data.

[0049] According to another aspect of the present invention, an integration testing method for a funds trading platform including a friend query plugin is provided, comprising:

[0050] Obtain the requirements analysis report and / or use case specification of the fund trading platform, and determine the functional testing points and process testing points of the fund trading platform; wherein, the fund trading platform includes a transaction management module, a confirmation management module, a message management module, a position management module, and a clearing and settlement management module for setting up the friend query plugin;

[0051] Based on the functional testing criteria, functional test cases for the user data module, transaction management module, confirmation management module, message management module, position management module, and clearing and settlement management module are written using equivalence class partitioning, boundary value analysis, or error guessing.

[0052] Based on the process testing points, use decision tables, scenario methods, or error guessing methods to write small process test cases within each module and large process test cases simulating interactions between each module.

[0053] The historical transaction data is divided into functional test data for each module, small process test data, and large process test data between the modules.

[0054] The functional test cases and the process test cases are reviewed. If the review result is "passed", the functional test data, the small process test data, and the large process test data are substituted into the functional test cases, the small process test cases, and the large process test cases respectively to test the fund trading platform and determine whether the module test results of each module and the interaction test results between the modules meet the expected test results.

[0055] Optionally, the test cases for the small process of the transaction management module include:

[0056] Log in to the aforementioned fund trading platform;

[0057] Click the "Initiate Inquiry" button to request an inquiry approval.

[0058] Redirecting to the approval form page, open the approval information corresponding to the inquiry approval request;

[0059] Click the "Terminate Transaction" button;

[0060] The expected test results of the aforementioned small-process test case include:

[0061] Login successful; Initiation successful; Open successful; Transaction terminated for approval order.

[0062] Optionally, the large-scale test cases between the transaction management module and the message management module include:

[0063] The confirmation management module sends a confirmation request message including a transaction identifier to the message management module;

[0064] The message management module sends the confirmation request message to the registration system and receives the confirmation response message returned by the registration system;

[0065] The message management module compares the confirmation request message and the confirmation response message, determines the matching result, and sends the matching result to the confirmation management module.

[0066] If the confirmation request message and the confirmation response message match successfully, the confirmation management module will change the confirmation status of the transaction corresponding to the transaction identifier to confirmed.

[0067] According to another aspect of the present invention, a testing apparatus for a friend query plugin is provided, comprising:

[0068] The acquisition module is used to acquire the test request of the friend query plugin; wherein, the test request includes the friend query plugin requirements and historical transaction data of the friend query plugin, and the friend query plugin requirements include query interface requirements;

[0069] A module is developed to analyze the test points of the friend query plugin based on the requirements of the query interface, and to develop test scripts corresponding to the query conditions included in the test points.

[0070] The generation module is used to select test data and verification data from the historical transaction data, combine the test data and the test script, and generate test cases for the friend query plugin.

[0071] The testing module is used to respond to the test request, execute the test case, determine whether the execution result of the test case is verification data, and obtain the test result of the test request.

[0072] According to another aspect of the present invention, an integrated testing apparatus for a funds trading platform including a friend query plugin is provided, comprising:

[0073] The acquisition module is used to acquire the requirements analysis report and / or use case specification of the fund trading platform, and to determine the functional test points and process test points of the fund trading platform; wherein, the fund trading platform includes a transaction management module, a confirmation management module, a message management module, a position management module, and a clearing and settlement management module for setting up the friend query plugin;

[0074] A module is configured to write functional test cases for the user data module, the transaction management module, the confirmation management module, the message management module, the position management module, and the clearing and settlement management module, respectively, based on the functional test points and using equivalence class partitioning, boundary value analysis, or error guessing.

[0075] The module is also used to write small process test cases within each module and large process test cases simulating interactions between each module, based on the process test points and using decision tables, scenario methods, or error guessing methods.

[0076] The data partitioning module is used to divide the historical transaction data into functional test data for each module, small process test data, and large process test data between the modules.

[0077] The testing module is used to review the functional test cases and the process test cases. If the review result is "passed", the functional test data, the small process test data, and the large process test data are respectively substituted into the functional test cases, the small process test cases, and the large process test cases to test the fund trading platform and determine whether the module test results of each module and the interaction test results between the modules meet the expected test results.

[0078] According to another aspect of the present invention, an electronic device for testing a friend search plugin is provided, comprising:

[0079] One or more processors;

[0080] Storage device for storing one or more programs.

[0081] When the one or more programs are executed by the one or more processors, the one or more processors implement the testing method for the friend query plugin provided by the present invention.

[0082] According to another aspect of the present invention, a computer-readable medium is provided having a computer program stored thereon, which, when executed by a processor, implements the testing method for the friend query plugin provided by the present invention.

[0083] One embodiment of the above invention has the following advantages or beneficial effects: By employing a technical approach that analyzes the testing points of the friend query plugin based on its query interface requirements, information synchronization requirements, user permission requirements, and historical transaction data, and writes test scripts corresponding to the query conditions, information synchronization conditions, and user permission conditions, combining the test data and test scripts into test cases for the friend query plugin, and using verification data to test the friend query plugin and determine the test results, this invention overcomes the existing problems of wasting human resources, time, and computing resources in fund trading platforms, resulting in a poor customer experience. Furthermore, how to build a good communication mechanism between users on a fund trading platform and ensure its normal online operation has become a major technical challenge in the testing of existing fund trading platforms. This invention achieves the technical effect of building a friend query plugin suitable for fund trading platforms, enabling users to find friend information through the plugin and promptly interact to handle various transaction issues during the trading process, greatly saving transaction time, human resources, and computing resources, and improving the user experience of platform customers.

[0084] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0085] The accompanying drawings are provided to better understand the invention and are not intended to unduly limit the scope of the invention. Wherein:

[0086] Figure 1 This is a schematic diagram of the main flow of the testing method for the friend query plugin according to an embodiment of the present invention;

[0087] Figure 2 This is a schematic diagram of the interface of the friend search plugin according to an embodiment of the present invention;

[0088] Figure 3 This is a schematic diagram of the main flow of the method for generating test scripts for a friend query plugin according to an embodiment of the present invention;

[0089] Figure 4This is a schematic diagram of the main process of generating test cases for the friend query plugin according to an embodiment of the present invention;

[0090] Figure 5 This is a schematic diagram of the main process of the integration testing method of a fund trading platform including a friend query plugin according to an embodiment of the present invention;

[0091] Figure 6 This is a schematic diagram of the main modules of a test device for a friend query plugin according to an embodiment of the present invention;

[0092] Figure 7 This is a schematic diagram of the main modules of an integrated testing device for a funds trading platform including a friend query plugin according to an embodiment of the present invention.

[0093] Figure 8 An exemplary system architecture diagram is shown for a testing method or a testing apparatus for a friend query plugin suitable for application in embodiments of the present invention.

[0094] Figure 9 This is a schematic diagram of the structure of a computer system suitable for implementing terminal devices or servers of the present invention. Detailed Implementation

[0095] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of the present invention, including various details to aid understanding. These details should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0096] Equivalence class partitioning: refers to a subset of an input domain in which all input data are equivalent in revealing errors in the software. It is divided into valid equivalence classes and invalid equivalence classes based on whether the condition is met.

[0097] Decision table method: A tool for analyzing and expressing different operations performed under multiple logical conditions.

[0098] Boundary value analysis: Test the boundary values ​​of the input or output, and design test cases by selecting data that are equal to, greater than, or less than the boundary values.

[0099] Scenario-based approach: This method uses scenarios to describe functions or processes, and designs test cases to traverse the scenarios in order to verify the correctness of the functions.

[0100] Error guessing: a method that uses experience and intuition to guess various errors that may exist in a test, and analyzes the results through testing experience.

[0101] Integration testing, also known as application assembly testing or joint testing, refers to the testing performed on a platform system by integrating all modules according to the design requirements of the structure diagram, based on unit testing.

[0102] Figure 1 This is a schematic diagram of the main flow of the testing method for the friend query plugin according to an embodiment of the present invention, as shown below. Figure 1 As shown, the testing method for the friend query plugin of the present invention includes the following steps:

[0103] In this embodiment of the invention, the testing method for the friend query plugin of the present invention is executed by the fund trading platform test server (hereinafter referred to as the "test server").

[0104] Step S101: Obtain the test request of the friend query plugin; wherein, the test request includes the friend query plugin requirements of the friend query plugin, and the friend query plugin requirements include query interface requirements and historical transaction data.

[0105] In this embodiment of the invention, the test request for the friend query plugin includes a requirements analysis report and a plugin use case specification. The test server analyzes the requirements analysis report to clarify the business requirements of the friend query plugin, ensuring that test cases comprehensively and effectively cover the functions and processes corresponding to these business requirements, thus verifying the business requirements of the friend query plugin. Accordingly, the business requirements of the friend query plugin include query interface requirements, information synchronization requirements, user permission requirements, and information export requirements.

[0106] Furthermore, the business requirements for the friend search plugin can also include friend addition and friend deletion.

[0107] In this embodiment of the invention, the user can be a trader using a fund trading platform.

[0108] In this embodiment of the invention, the test request of the friend query plugin also includes historical transaction data, which includes the transaction relationships between historical users, thereby identifying users with friend relationships and obtaining the user's friend information.

[0109] For example, the friend search plugin is named "iDEAL Friend Search," and the requirements analysis report for "iDEAL Friend Search" includes:

[0110] (1) Added an "iDEAL Friend Query" interface, such as Figure 2As shown, the "iDEAL Friend Query" interface includes a user name label, a user name input box, an institution name label, an institution name input box, and a query button; (2) The "iDEAL Friend Query" interface adds an "Information Synchronization" button. When "iDEAL Friend Query" is enabled, "iDEAL Friend Query" can automatically synchronize the friend information included in the historical transaction data of the fund trading platform; when "iDEAL Friend Query" is disabled, users can click the "Information Synchronization" button to synchronize the friend information included in the historical transaction data of the fund trading platform; (3) Users can only view their own iDEAL friend list; (4) The "iDEAL Friend Query" interface adds an "Export" button. Users can click the "Export" button to export the user's friend information; (5) The "iDEAL Friend Query" interface adds an "Add" button (not shown in the figure). Users can click the "Add" button to add friends; (6) The "iDEAL Friend Query" interface adds a "Delete" button (not shown in the figure). Users can click the "Delete" button to delete friends.

[0111] Accordingly, the query interface requirements include: ① adding a friend query interface; ② the friend query interface includes a user name label, a user name input box, an organization name label, an organization name input box, and a query button.

[0112] Information synchronization requirements include: ① Adding an information synchronization button to the friend search interface; ② When the friend search plugin is enabled, the friend search plugin should automatically synchronize friend information; when the friend search plugin is disabled, users can click the information synchronization button to synchronize friend information.

[0113] User permission requirements include: user permissions are limited to the user's friend list.

[0114] Information export requirements include: adding an export button to the friend search interface.

[0115] Friend addition requests include: adding an "add" button to the friend search interface.

[0116] The request to delete friends includes adding a delete button to the friend search interface.

[0117] Step S102: Based on the requirements of the query interface, analyze the test points of the friend query plugin and write test scripts corresponding to the query conditions included in the test points.

[0118] In this embodiment of the invention, the test server analyzes the business requirements based on the plugin use case specification of the friend query plugin, and lists the test conditions corresponding to the functions of each business requirement in the form of an outline to determine the key test points of the friend query plugin. The outline format is used to facilitate review by testers and ensure accurate positioning of the test points for complex business requirements. Accordingly, the key test points of the friend query plugin include query conditions, information synchronization conditions, user permission conditions, and information export conditions.

[0119] Furthermore, the key testing points for the friend search plugin can also include friend addition conditions and friend deletion conditions.

[0120] For example, the friend search plugin is named "iDEAL Friend Search," and the plugin use case description for "iDEAL Friend Search" includes:

[0121] (1) Search criteria: Institution name, User name;

[0122] (2) Information Synchronization Button: When "iDEAL Friend Query" is turned on, friend information will be automatically synchronized from the historical transaction data of the fund trading platform; or, regardless of whether "iDEAL Friend Query" is turned on or off, users can click the "Information Synchronization" button to synchronize the friend information included in the historical transaction data of the fund trading platform.

[0123] (3) User permissions: Users can only view their own friend list;

[0124] (4) Export button: Supports exporting the full list of query results. The list of query results includes serial number, organization name, user name, and user ID.

[0125] (5) Add button: Supports adding friends by searching by organization name or user name. After adding a friend, you need to close and reopen "iDEAL Friend Search";

[0126] (6) Delete button: Supports searching for and deleting friends by organization name or user name. After deleting a friend, you need to log out and log back into "iDEAL Friend Query".

[0127] Accordingly, the search criteria include: ① Institution name search; ② User name search.

[0128] Information synchronization conditions include: ① The friend query plugin is turned on, and friend information is automatically synchronized from the historical transaction data of the fund trading platform; ② The friend query plugin is turned on, and the friend information of the fund trading platform is synchronized by clicking the information synchronization button; ③ The friend query plugin is turned off, and the friend information of the fund trading platform is synchronized by clicking the information synchronization button.

[0129] User permission conditions include: only being able to view the friend list corresponding to the current user ID.

[0130] The conditions for exporting information include: ① The exported query result list includes serial number, organization name, user name, and user ID; ② The number of friends in the exported result list is the same as the number of friends obtained from the query.

[0131] The conditions for adding friends include: ① Searching for and adding friends by organization name or user name; ② After adding friends, you need to close and reopen the friend search plugin.

[0132] The conditions for deleting a friend include: ① searching for and deleting friends by organization name or user name; ② after deletion, you need to log out and log back in to the friend search plugin.

[0133] In this embodiment of the invention, the test server writes corresponding conditional statements and result statements based on the test points of the friend query plugin, including query conditions, information synchronization conditions, user permission conditions, information export conditions, friend addition conditions, and friend deletion conditions, and generates a test script.

[0134] In embodiments of the present invention, such as Figure 3 As shown, the method for generating the test script for the friend query plugin of the present invention includes the following steps:

[0135] Step S301: Construct the plugin data table for the friend query plugin.

[0136] In this embodiment of the invention, the initial framework of the plugin data table includes user ID, user name, friend ID, friend name, name of the user's organization, and name of the friend's organization. During the writing of the test script, the data values ​​of the plugin data table are empty. Test cases are generated after the corresponding plugin data is inserted later. The file size of the plugin data table can be calculated based on the total number of users using the financial trading platform. First, determine the storage space required to store the friend information of a single user, and then multiply it by a number greater than the total number of users to determine the file size of the plugin data table.

[0137] Step S302: Using the equivalence class partitioning method and the decision table method, conditional statements for the query conditions, the information synchronization conditions, and the user permission conditions are generated respectively.

[0138] Step S3021: Using the equivalence class partitioning method, determine the input data type of the query condition to obtain the condition statement of the query condition.

[0139] In this embodiment of the invention, according to step S102, it can be determined that the input data type of the query condition is a string type, the valid equivalence class is the string type, and the invalid equivalence class is other data types that are not strings. Accordingly, the conditional statement of the query condition can be expressed as:

[0140] Determine whether the data in the user name input box and / or organization name input box is a string type (i.e., string). If it is, determine whether the click attribute of the query button is empty.

[0141] If the click attribute of the search button is not empty, perform a search for the entered content; if the click attribute of the search button is empty, continue to wait.

[0142] If the data in the user name input box and / or organization name input box is not a string type, an error message will be displayed.

[0143] Step S3022: The on / off state of the friend query plugin and the click attribute of the information synchronization button are represented as conditional statements of the information synchronization conditions using the decision table method.

[0144] In this embodiment of the invention, according to step S102, the open / closed state of the friend query plugin can be either open or closed. Using binary values, when the friend query plugin is detected to be open, the value of the open / closed state is determined to be [1]; when the friend query plugin is detected to be closed, the value of the open / closed state is determined to be [0].

[0145] According to step S102, the click attribute of the information synchronization button can be either touch or empty. It is represented by a binary value. When the user clicks the information synchronization button, the value of the click attribute is determined to be [1]; when the user does not click the information synchronization button, the value of the click attribute is determined to be [0].

[0146] Accordingly, the conditional statement determined based on the on / off state of the friend query plugin and the click attribute of the information synchronization button can be expressed as:

[0147] Determine if the friend search plugin is enabled. If it is, synchronize friend information. If not, check if the click attribute of the information synchronization button is empty.

[0148] If the click attribute of the information synchronization button is empty, no operation is performed; if the click attribute of the information synchronization button is not empty, the friend query plugin is enabled and friend information is synchronized.

[0149] Step S3023: Based on the current user ID, generate the conditional statement for the user permission conditions using the decision table method.

[0150] In this embodiment of the invention, according to step S102, it can be determined that the user can only view the friend list corresponding to the current user ID, the input data type of the query condition is string type, and the conditional statement can be expressed as:

[0151] Construct a mapping relationship between the user IDs of all users and the friend information corresponding to the user IDs;

[0152] Find and display the friend information that matches the current user ID in the mapping relationship.

[0153] Step S303: Insert the conditional statement into the plugin data table to obtain the test script of the friend query plugin.

[0154] In this embodiment of the invention, the conditional statement for inserting query conditions into the plug-in data table is as follows:

[0155] Determine whether the data in the user name input box and / or organization name input box is a string type (i.e., string). If it is, determine whether the click attribute of the query button is empty.

[0156] If the click attribute of the search button is not empty, search the plugin data table for friend information that matches the input content; if the click attribute of the search button is empty, continue to wait.

[0157] If the data in the user name input box and / or organization name input box is not a string type, an error message will be displayed.

[0158] In this embodiment of the invention, the conditional statement for inserting information synchronization conditions into the plug-in data table is as follows:

[0159] Determine if the friend query plugin is enabled. If it is, synchronize friend information to the plugin's data table. If not, check if the click attribute of the information synchronization button is empty.

[0160] If the click attribute of the information synchronization button is empty, no operation is performed; if the click attribute of the information synchronization button is not empty, the friend query plugin is enabled, and friend information is synchronized to the plugin's data table.

[0161] In this embodiment of the invention, the conditional statement for inserting user permission conditions into the plugin data table is as follows:

[0162] Based on the plugin data table, construct a mapping relationship between the user IDs of all users and the friend information corresponding to the user IDs;

[0163] Find and display the friend information that matches the current user ID in the mapping relationship.

[0164] Furthermore, the test server combines the query conditions, information synchronization conditions, and user permission conditions of the inserted plugin data table to obtain the test script for the friend query plugin.

[0165] In this embodiment of the invention, before synchronizing friend information to the plugin data table, the method further includes:

[0166] Conditional statements for the interaction between the friend query plugin and the financial trading platform:

[0167] Determine if the communication between the friend query plugin and the fund trading platform is normal. If so, execute the synchronization of friend information from the fund trading platform to the plugin's data table.

[0168] In this embodiment of the invention, the test points also include result statements, which are combined with the condition statements corresponding to each condition to determine the scripts of each test point, so as to form the test script of the friend query plugin.

[0169] In this embodiment of the invention, the test script generation method for the friend query plugin of the present invention generates conditional statements and result statements for test points using methods such as equivalence class partitioning and decision tables. These statements include query conditions, information synchronization conditions, user permission conditions, friend addition conditions, and friend addition / deletion conditions. After inserting the plugin data table into the script statements of the test points, the test script for the friend query plugin is constructed to facilitate subsequent testing of the friend query plugin. This improves user data utilization and plugin testing efficiency, and facilitates unified user management on the financial transaction platform.

[0170] Step S103: Select test data and verification data from the historical transaction data, combine the test data and the test script to generate test cases for the friend query plugin.

[0171] In this embodiment of the invention, the test server uses boundary value analysis to select test data and verification data from historical transaction data, and combines the test data and test script to generate test cases for the friend query plugin; wherein, the test data and verification data correspond to each other, the test data is used to substitute into the test script, and the verification data is used to verify the execution results.

[0172] In embodiments of the present invention, such as Figure 4 As shown, the method for generating test cases for the friend query plugin of the present invention includes the following steps:

[0173] Step S401: Filter the target data that matches the plug-in data table from the historical transaction data.

[0174] In this embodiment of the invention, based on historical transaction data, our trader ID, our trader name, the counterparty trader ID, the counterparty trader name, our institution name, and the counterparty institution name are used as boundary values. Data containing boundary values ​​in each transaction are then filtered to obtain the user ID, user name, friend ID, friend name, the institution name of the user's institution, and the institution name of the friend's institution, thus obtaining the target data.

[0175] Step S402: Based on the test requirements, select test data from the target data, and use boundary value analysis to determine the verification data corresponding to the test data.

[0176] In this embodiment of the invention, test data is selected from the target data according to the test requirements, and the results of executing each conditional statement on the test data are used as verification data. Specifically, when executing each conditional statement, boundary value analysis is used to determine the verification data corresponding to the test data. For example, if the test data includes n user names and n organization names, boundary value analysis is used to perform precise matching of the test data, and the determined verification data includes the query results for the serial number, organization name, user name, and user ID corresponding to the n user names; or, the verification data includes the query results for the serial number, organization name, user name, and user ID corresponding to the n organization names.

[0177] Step S403: Combine the test data and the test script to obtain test cases for the friend query plugin.

[0178] In this embodiment of the invention, test data and test scripts are combined to obtain test cases, which are then executed to determine whether the expected test results can be obtained, thereby determining whether the friend query plugin can run.

[0179] In this embodiment of the invention, the test case generation method for the friend query plugin of the present invention is used to filter test data from historical transaction data, determine the corresponding verification data, use the verification data as the expected test result, combine the test data and test script, and generate test cases to test the friend query plugin, determine whether the friend query plugin can run normally, so as to integrate into the fund trading platform, better support the integration test of the fund trading platform, and facilitate the unified management of user data by the fund trading platform.

[0180] Step S104: In response to the test request, execute the test case, determine whether the execution result of the test case is verification data, and obtain the test result of the test request.

[0181] In this embodiment of the invention, the test server substitutes the test data from the test case into the test script, executes the test script, and determines whether the execution result is equal to the verification data. If the execution result is equal to the verification data, the test result of the test request is determined to be a successful test; if the execution result is not equal to the verification data, the test result of the test request is determined to be a failed test.

[0182] Furthermore, if the test request results in a test failure, the test case problem is identified based on the error data, and the test case is revised accordingly.

[0183] In this embodiment of the invention, before executing the test case, the test case is reviewed, and review comments are generated. If the review result is a review failure, the test case is revised according to the issues pointed out in the review comments.

[0184] Alternatively, during the testing process, if the testing requirements for the plugin change, including adding, deleting, or modifying test points, the test cases should be modified according to the changed testing requirements to ensure that all changes in requirements are covered by test cases, and that the expected test results of the test cases are consistent with the verification data.

[0185] In this embodiment of the invention, by obtaining a test request for the friend query plugin; wherein the test request includes the friend query plugin requirements and historical transaction data, and the friend query plugin requirements include query interface requirements; based on the query interface requirements, analyzing the test points of the friend query plugin, and writing test scripts corresponding to the query conditions included in the test points; selecting test data and verification data from the historical transaction data, combining the test data and the test scripts to generate test cases for the friend query plugin; responding to the test request, executing the test cases, and determining whether the execution result of the test cases is verification data to obtain the test result of the test request, etc., a friend query plugin suitable for a financial trading platform can be constructed, enabling users to find friend information through the friend query plugin and promptly handle various transaction issues during the transaction process, greatly saving transaction time costs, manpower costs, and computing resources, and improving the user experience of platform customers.

[0186] Figure 5 This is a schematic diagram of the main flow of an integration testing method for a funds trading platform including a friend query plugin according to an embodiment of the present invention, as shown below. Figure 5 As shown, the integration testing method for the fund trading platform of the present invention includes the following steps:

[0187] Step S501: Obtain the requirements analysis report and / or use case specification of the fund trading platform, and determine the functional testing points and process testing points of the fund trading platform; wherein, the fund trading platform includes a transaction management module, a confirmation management module, a message management module, a position management module, and a clearing and settlement management module for setting up the friend query plugin.

[0188] In this embodiment of the invention, the transaction management module is used to check the transaction rules elements of the transaction information; the verification management module is used to verify the legal and regulatory elements of the transaction; the message management module is used to check the messages sent and received on the platform; the position management module is used to control the investment risks of the transaction; and the clearing and settlement management module is used to manage the actual delivery cash flow generated by the transaction.

[0189] In this embodiment of the invention, before testing the fund trading platform, a test plan for the entire platform needs to be written to guide the entire testing process. As a guiding document, the test plan clarifies the testing background, testing objectives, purpose of writing the plan, terminology explanations, reference materials, organizational structure, division of responsibilities, internal and external communication mechanisms for the test implementation team, daily and weekly test reports, testing scope, testing environment, reference documents (including requirements analysis reports and test case specifications), test case execution and initiation strategies, test milestone plans, test parameters, security management of test data, defect flow process, defect severity judgment criteria, test conclusion evaluation criteria, and test deliverables. It can assess whether the functionality of individual modules (e.g., interface display and query functions) meets expectations, whether small processes combining multiple sub-functions can meet expected requirements, whether there are functional conflicts between modules, whether the global data structure is suitable, and whether large processes connecting multiple modules meet expectations, ensuring the stable operation of the fund trading platform after its launch.

[0190] In this embodiment of the invention, the testing architecture of the fund trading platform includes multiple test interfaces and test points. The test interfaces are used to access various modules, and the test points are used to verify the output of each module to determine whether the functions of each module are normal and whether the connection between each module is normal. In this embodiment, functional test results and process test results are stored in advance at each test point to verify the output of each module.

[0191] In this embodiment of the invention, the requirements analysis report and / or use case specification of the fund trading platform include the test requirements for each module of the fund trading platform and the test requirements for the interaction between the modules. The test server determines the functional test points of the fund trading platform based on the test requirements for each module, and determines the process test points of the fund trading platform based on the test requirements for the interaction between the modules. For example, the transaction management module includes functions such as friend query plugin, counterparty management, off-duty reminder script management, transaction strategy management, and proactive price inquiry, wherein:

[0192] The key functionalities of the friend lookup plugin include: ① After opening the plugin, friend information is synchronized; ② After adding a friend, the plugin needs to be closed and reopened; ③ Deleting a friend requires logging out and logging back in; ④ Only the user's own friend information can be queried, and exporting is supported.

[0193] Key testing points for counterparty management functionality include: ① Adding verification of whitelists and sanctions lists; ② Adding a "Does it include product accounts?" button. If yes, verify legal entity accounts and control credit limits in the conversation; ③ Adding a "Do it generate an intention form?" button. If yes, send an automatically generated intention form to the other party after they confirm our standard response.

[0194] Key functional testing points for managing off-duty reminder scripts include: ① Adding new off-duty reminder scripts; ② Responding according to the scripts when a user leaves their post.

[0195] Key functional testing points for trading strategy management include: ① Adding the function of agreeing to take effect for strategies; ② Adding the function of querying prices for specific users in the query and modification menu; ③ Adding an "Institution Type" button, so that a single strategy takes effect on the selected institution type simultaneously.

[0196] Key testing points for the proactive inquiry function include: ① Strategy query management – ​​add a proactive inquiry button; ② Inquiry interval is 30 minutes; ③ Add a “Proactive Inquiry Script” template to generate proactive inquiry scripts, while also supporting manual filling by users; ④ Add an institution selection drop-down arrow, with options including “All”, “Institution A”, “Institution B”, “Frequently Trading Institutions”, and “Custom Group”.

[0197] Step S502: Based on the functional test requirements, use equivalence class partitioning, boundary value analysis, or error guessing to write functional test cases for the user data module, the transaction management module, the confirmation management module, the message management module, the position management module, and the clearing and settlement management module, respectively.

[0198] In this embodiment of the invention, the test server writes test cases based on the identified functional test points. The types of test cases include interface test cases, functional test cases, process test cases, forward test cases, reverse test cases, regression test cases, etc. Commonly used test case writing methods include equivalence class partitioning, boundary value analysis, error guessing, cause-effect graphing, decision table composition, scenario-based methods, etc. The reference documents for UI test cases can be derived from use case specifications or UI prototypes, and common writing methods include equivalence class partitioning and boundary value analysis. The reference documents for functional test cases can be derived from use case specifications, and common writing methods include equivalence class partitioning, boundary value analysis, and error guessing. Process test cases are divided into small process test cases combining multiple sub-functions within a single module and large process test cases combining interactions between multiple modules. The reference documents for large process test cases can be derived from requirements analysis reports, and common writing methods include decision tables and scenario-based methods. The reference documents for small process test cases can be derived from requirements analysis reports or use case specifications, and common writing methods include decision tables, scenario-based methods, and error guessing. Regression test cases mainly target architecture upgrades and interface upgrades, and the common writing method is scenario-based methods, which can be designed based on impact analysis.

[0199] Furthermore, the types of test cases also include special test cases, supplementary scenario cases, and abnormal scenario cases.

[0200] In this embodiment of the invention, the test server uses equivalence class partitioning, boundary value analysis, or error guessing methods to write functional test cases corresponding to the functional test points of modules such as the user data module, transaction management module, confirmation management module, message management module, position management module, and clearing and settlement management module. For example, the functional test case for the friend query plugin of the transaction management module is shown in the test method for the friend query plugin of this invention; another example is the test script for the interface test case of the active price inquiry function of the transaction management module, which includes:

[0201] Add an "Active Inquiry" button to the upper left corner of the strategy query management interface; add a drop-down arrow to the institution type input box in the strategy query management interface;

[0202] For example, the test scripts for the functional test cases of the proactive price inquiry function in the transaction management module include:

[0203] Determine if the time interval between the current time and the last inquiry is equal to 30 minutes. If so, initiate an active inquiry request.

[0204] Step S503: Based on the process test points, use decision tables, scenario methods, or error guessing methods to write small process test cases within each module and large process test cases simulating interactions between each module.

[0205] In this embodiment of the invention, the test server uses decision tables, scenario-based methods, or error guessing to write small-scale test cases for the user data module, transaction management module, confirmation management module, message management module, position management module, and clearing and settlement management module. The test server also uses decision tables and scenario-based methods to write large-scale test cases simulating interactions between these modules. For example, the test script for terminating a transaction in the small-scale test case of the transaction management module includes: 1. Logging into the fund trading platform; 2. Clicking the "Active Inquiry" button to initiate an inquiry approval request; 3. Redirecting to the approval form writing page and opening the approval information corresponding to the inquiry approval request; 4. Clicking the "Terminate Transaction" button. Accordingly, the expected test results include: 1. Successful login; 2. Successful initiation; 3. Successful opening; 4. Before data is uploaded, if the counterparty has not modified or canceled the transaction, the transaction is terminated normally, and the approval form status is "Approval Rejected." After successfully terminating the transaction, the "Upstream Status" displays "Upstream Rejected."

[0206] For example, a test script for a small-scale process test case in the transaction management module, involving approval initiated by the other party and manual submission after the transaction is completed, includes: 1. Log in to the system; 2. The other party initiates approval, and we manually approve and complete the transaction (automatic submission is disabled); 3. Manually submit the approval form. Correspondingly, the expected test results include: 1. Successful login; 2. Statuses are: Approved, Not Submitted, Not Completed; 3. Manual submission successful, and the approval form status changes to "Submitted".

[0207] For example, a test script for a small-scale process in the transaction management module, involving the counterparty initiating approval, our side manually uploading the transaction after completion, and then terminating the transaction, includes: 1. Log in to the system; 2. The counterparty initiates approval, our side performs manual approval and completes the transaction (automatic uploading is disabled); 3. Manually upload the approval form; 4. Terminate the transaction for the approval form. Correspondingly, the expected test results include: 1. Successful login; 2. Successful execution with statuses of Approved, Not Uploaded, Not Completed; 3. Successful manual uploading, with the approval form status changing to Uploaded; 4. Successful transaction termination, with successful data uploading.

[0208] For example, a test script for a small process in the transaction management module, involving the counterparty initiating approval, our side completing the transaction, the counterparty modifying the interest rate, and the transaction being terminated, includes: 1. Logging into the system; 2. The counterparty initiates approval, our side performs manual approval and completes the transaction (automatic uplink switch is off, and the counterparty's interest rate modification is checked during uplink); 3. Terminate the transaction on the approval form. Correspondingly, the expected test results include: 1. Successful login; 2. Successful execution with statuses of approval passed, uplinked, and not yet completed; 3. Successful transaction termination and successful uplink data.

[0209] For example, a test script for a small process in the transaction management module, involving the other party initiating approval, our side completing the transaction, and the other party withdrawing the transaction, includes: 1. Logging into the system; 2. The other party initiates approval, our side performs manual approval and completes the transaction (automatic upward transfer is disabled, and the withdrawal of the other party is checked during upward transfer); 3. Checking each status of the approval form. Correspondingly, the expected test results include: 1. Successful login; 2. Successful execution; 3. Each status is: Approved, Not Uploaded, Not Completed.

[0210] For example, in the small-process test case of the transaction management module, the test script for our response price and the automatic upward movement of the approval initiated by the other party when the automatic upward movement switch is turned off includes: 1. Log in to the system; 2. The other party initiates the approval, and we manually approve and respond with a price (automatic upward movement switch off); 3. Check the status of each approval form. Accordingly, the expected test results include: 1. Login successful; 2. Manual approval passed; 3. Statuses are: Approved, Not Upward Movement, Not Transaction Completed.

[0211] For example, in the small-process test case of the transaction management module, the test script for the "not yet uploaded" status of the approval initiated by the other party and our response - manual upload includes: 1. Log in to the system; 2. The other party initiates the approval, we conduct manual approval and respond (automatic upload switch is off); 3. Manually upload the approval form. Correspondingly, the expected test results include: 1. Login successful; 2. Manual approval passed, upload status is "not yet uploaded"; 3. Manual upload successful, approval form status changes to "uploaded".

[0212] For example, the test script for a large-scale test case between the verification management module and the message management module includes: 1. The verification management module sends a verification request message including the transaction identifier to the message management module; 2. The message management module sends the verification request message to the registration system and receives the verification response message returned by the registration system; 3. The message management module compares the verification request message and the verification response message, determines the matching result, and sends the matching result to the verification management module; 4. If the matching result of the verification request message and the verification response message is successful, the verification management module changes the verification status of the transaction corresponding to the transaction identifier to "verified". Accordingly, the expected test results include: 1. The verification management module successfully sends the verification request message; 2. The message management module successfully sends the verification request message and receives the verification response message; 3. The message management module determines the matching result of the verification request message and the verification response message and sends the matching result successfully; 4. If the matching result is successful, the verification management module changes the verification status of the transaction corresponding to the transaction identifier to "verified".

[0213] Step S504: Divide the historical transaction data into functional test data for each module, small process test data, and large process test data between the modules.

[0214] In this embodiment of the invention, the test server divides the historical transaction data and selects module test data applicable to functional test cases of each module and interaction test data applicable to process test cases between modules.

[0215] Step S505: Review the functional test cases and the process test cases. If the review result is "passed", substitute the functional test data, the small process test data, and the large process test data into the functional test cases, the small process test cases, and the large process test cases respectively to test the fund trading platform and determine the module test results of each module and the interaction test results between the modules.

[0216] Test case review includes internal and external reviews. Internal review refers to the review by testers of a single module to determine whether functional test cases meet the requirements. External review refers to the review by testers of multiple modules, as well as requirements analysts (including development requirements analysts, product requirements analysts, etc.), to determine whether interaction test cases between various modules meet the requirements. In this embodiment of the invention, the test server pre-stores review rules for various types of internal and external reviews of test cases, which are used to review functional test cases and process test cases, determine the review results, and point out problems such as incomplete coverage, redundancy, or errors in test cases, so as to improve the quality of test cases. Revisions are made to ensure the comprehensiveness and completeness of test cases. The review rules can be in the form of a test case coverage checklist, including the serial number, launch date, review time, test requirement name, responsible person, test points, case type, language, and review elements corresponding to the case type (e.g., for UI cases, this includes the number of buttons, button locations, button-triggered navigation, dropdown content, etc.). The review results can be in the form of a review record table, including the test requirement name, review time, case type, test points, problem summary (e.g., the effective time value is incorrect, indicating non-immediate effect), and revision content (changing the effective time value to immediate effect).

[0217] Furthermore, if test requirements change during the testing process, the test server revises the test cases based on the received revised test requirements to ensure that there are test cases covering the revised test requirements. This guarantees that the functions implemented by the fund trading platform are consistent with the revised test requirements. The test requirement change corresponds to a test change record table, which includes the change number, description before the change, description after the change, reason for the change, person making the change, date of the change, document for the change, and technical personnel. For example, for the change of the proactive inquiry requirement, the description before the change was that the transaction direction was not correctly identified, and the description after the change was that the transaction initiation script was entered without amount and term. The reason for the change was script change, the document for the change was the use case specification, and the date of the change was 20210101.

[0218] In this embodiment of the invention, the integrated testing method for the fund trading platform can jointly test the connections between various modules of the fund trading platform to determine whether the interface calls between the various modules of the fund trading platform meet the requirements. It simulates the actual operation of the entire platform to accurately locate abnormal nodes, especially testing problems with interdependent relationships, eliminating potential operational risks of the fund trading platform and ensuring its smooth launch. Compared to existing unit testing, which can only test whether a single module operates normally, specialized testing, which only tests a single function, and system testing, which is usually non-functional load, stress, performance, and reliability testing, this method can comprehensively test operational interference between modules without dependencies, interaction failures between modules with dependencies, global data structures, the normality of the entire transaction process of multiple modules connected in series, and whether the final result meets the expectations of the entire business process. It efficiently and accurately locates testing problems and promptly remedies deviations to achieve the smooth launch and operation of a multi-module fund trading platform, greatly improving testing efficiency, platform launch efficiency, and platform operational security.

[0219] Figure 6 This is a schematic diagram of the main modules of a test device for a friend query plugin according to an embodiment of the present invention, as shown below. Figure 6 As shown, the testing device 600 for the friend query plugin of the present invention includes:

[0220] The acquisition module 601 is used to acquire the test request of the friend query plugin; wherein, the test request includes the friend query plugin requirements and historical transaction data of the friend query plugin, and the friend query plugin requirements include query interface requirements.

[0221] Module 602 is used to analyze the test points of the friend query plugin according to the requirements of the query interface, and write test scripts corresponding to the query conditions included in the test points.

[0222] The generation module 603 is used to select test data and verification data from the historical transaction data, combine the test data and the test script, and generate test cases for the friend query plugin.

[0223] The test module 604 is used to respond to the test request, execute the test case, determine whether the execution result of the test case is verification data, and obtain the test result of the test request.

[0224] In this embodiment of the invention, by using modules such as an acquisition module, a writing module, a generation module, and a testing module, a friend query plugin suitable for a fund trading platform can be constructed. This allows users to search for friend information through the friend query plugin and promptly handle various transaction issues during the transaction process, greatly saving transaction time, manpower, and computing resources, and improving the user experience of platform customers.

[0225] Figure 7 This is a schematic diagram of the main modules of an integrated testing device for a funds trading platform including a friend query plugin according to an embodiment of the present invention, as shown below. Figure 7 As shown, the integrated testing device 700 for the fund trading platform of the present invention includes:

[0226] The acquisition module 701 is used to acquire the requirements analysis report and / or use case specification of the fund trading platform, and to determine the functional test points and process test points of the fund trading platform; wherein, the fund trading platform includes a transaction management module, a confirmation management module, a message management module, a position management module, and a clearing and settlement management module for setting up the friend query plugin.

[0227] The module 702 is used to write functional test cases for the user data module, the transaction management module, the confirmation management module, the message management module, the position management module, and the clearing and settlement management module, respectively, based on the functional test points and using the equivalence class partitioning method, boundary value analysis method, or error guessing method.

[0228] The writing module 702 is also used to write small process test cases within each module and large process test cases simulating interactions between each module, based on the process test points and using decision tables, scenario methods, or error guessing methods.

[0229] The data partitioning module 703 is used to partition the historical transaction data into functional test data for each module, small process test data, and large process test data between the modules.

[0230] Test module 704 is used to review the functional test cases and the process test cases. If the review result is "pass", the functional test data, the small process test data and the large process test data are respectively substituted into the functional test cases, the small process test cases and the large process test cases to test the fund trading platform and determine whether the module test results of each module and the interaction test results between the modules meet the expected test results.

[0231] In this embodiment of the invention, a testing method suitable for a fund trading platform is constructed by using modules such as an acquisition module, a writing module, a data partitioning module, and a testing module to test the fund trading platform. This method can ensure that each module of the fund trading platform operates normally individually, and also ensure that the connection between the modules is normal after they are combined. It can perform comprehensive testing on various scenarios of the fund trading platform, eliminate potential operational risks, and ensure the stable operation of the fund trading platform.

[0232] Figure 8 An exemplary system architecture diagram is shown, illustrating a testing method or apparatus suitable for a friend query plugin applied to embodiments of the present invention. Figure 8 As shown, the exemplary system architecture of the testing method or testing device for the friend query plugin according to embodiments of the present invention includes:

[0233] like Figure 8 As shown, system architecture 800 may include terminal devices 801, 802, and 803, a network 804, and a server 805. Network 804 serves as the medium for providing communication links between terminal devices 801, 802, and 803 and server 805. Network 804 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0234] Users can use terminal devices 801, 802, and 803 to interact with server 805 via network 804 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 801, 802, and 803, such as testing applications, shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc.

[0235] Terminal devices 801, 802, and 803 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0236] Server 805 can be a server providing various services, such as a backend management server supporting test websites browsed by users using terminal devices 801, 802, and 803. The backend management server can analyze and process data such as test requests from the friend query plugin, and feed back the processing results (such as the test results of the friend query plugin) to terminal devices 801, 802, and 803.

[0237] It should be noted that the testing method for the friend query plugin provided in this embodiment of the invention is generally executed by server 805, and correspondingly, the testing device for the friend query plugin is generally set in server 805.

[0238] It should be understood that Figure 8 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0239] Figure 9 This is a schematic diagram of the structure of a computer system suitable for implementing terminal devices or servers of the present invention, such as... Figure 9 As shown, the computer system 900 of the terminal device or server in this embodiment of the invention includes:

[0240] The Central Processing Unit (CPU) 901 can perform various appropriate actions and processes based on programs stored in Read-Only Memory (ROM) 902 or programs loaded into Random Access Memory (RAM) 903 from Storage Section 908. RAM 903 also stores various programs and data required for the operation of system 900. CPU 901, ROM 902, and RAM 903 are interconnected via bus 904. Input / output (I / O) interface 905 is also connected to bus 904.

[0241] The following components are connected to I / O interface 905: an input section 906 including a keyboard, mouse, etc.; an output section 907 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN card, modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to I / O interface 905 as needed. A removable medium 911, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 910 as needed so that computer programs read from it can be installed into storage section 908 as needed.

[0242] In particular, according to the embodiments disclosed in this invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 909, and / or installed from removable medium 911. When the computer program is executed by central processing unit (CPU) 901, it performs the functions defined above in the system of this invention.

[0243] It should be noted that the computer-readable medium shown in this invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0244] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0245] The modules described in the embodiments of this invention can be implemented in software or hardware. The described modules can also be housed in a processor; for example, a processor can be described as including an acquisition module, a writing module, a generation module, and a testing module. The names of these modules do not necessarily limit the module itself; for example, the writing module can be described as "a module that analyzes the test points of the friend query plugin based on the query interface requirements and writes test scripts corresponding to the query conditions included in the test points."

[0246] In another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs, which, when executed by the device, cause the device to include: obtaining a test request for the friend query plugin; wherein the test request includes friend query plugin requirements and historical transaction data, and the friend query plugin requirements include query interface requirements; analyzing the test points of the friend query plugin according to the query interface requirements, and writing a test script corresponding to the query conditions included in the test points; selecting test data and verification data from the historical transaction data, combining the test data and the test script to generate test cases for the friend query plugin; and, in response to the test request, executing the test cases, and determining whether the execution result of the test cases is verification data, to obtain the test result of the test request.

[0247] According to the technical solution of the present invention, it can ensure that each module of the fund trading platform operates normally individually, and also ensure that the connection between the modules after combination is normal. It can conduct comprehensive testing on various scenarios of the fund trading platform, eliminate potential operational risks of the fund trading platform, and ensure the stable operation of the fund trading platform.

[0248] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A testing method for a friend search plugin, characterized in that, include: Obtain the test request for the friend query plugin; wherein, the test request includes the friend query plugin requirements and historical transaction data of the friend query plugin, and the friend query plugin requirements include query interface requirements; Based on the requirements of the query interface, analyze the key points of the friend query plugin test and write test scripts corresponding to the query conditions included in the key points of the test. Test data and verification data are selected from the historical transaction data, and the test data and the test script are combined to generate test cases for the friend query plugin. In response to the test request, the test case is executed, and it is determined whether the execution result of the test case is verification data, so as to obtain the test result of the test request; The step of writing test scripts corresponding to the query conditions included in the test points includes: Construct the plugin data table for the friend query plugin; Using the equivalence class partitioning method, generate the conditional statement for the query conditions; Insert the plugin data table into the conditional statement to obtain the test script for the friend query plugin.

2. The method according to claim 1, characterized in that, The requirements for the friend search plugin also include information synchronization and user permission requirements; the test script also includes: Based on the information synchronization requirements and user permission requirements, analyze the key points of testing the friend query plugin, and determine the information synchronization conditions and user permission conditions. Using the decision table method, conditional statements for the information synchronization condition and the user permission condition are generated respectively.

3. The method according to claim 2, characterized in that, The query interface requirements include adding a friend query interface, which includes a user name label, a user name input box, an organization name label, an organization name input box, and a query button. The information synchronization requirements include adding an information synchronization button to the friend query interface and automatically synchronizing friend information when the friend query plugin is enabled. With the friend search plugin enabled, users can click the information synchronization button to synchronize friend information. The user permission requirements include user permissions limited to the user's friend list.

4. The method according to claim 3, characterized in that, The step of generating the conditional statement for the query conditions using the equivalence class partitioning method includes: Using the equivalence class partitioning method, the input data type of the query condition is determined, and the condition statement of the query condition is obtained; The method of using decision tables to generate conditional statements for the information synchronization condition and the user permission condition includes: The on / off state of the friend query plugin and the click attribute of the information synchronization button are represented as conditional statements for the information synchronization conditions using the decision table method. Based on the current user ID, the conditional statement for the user permission conditions is generated using the decision table method.

5. The method according to claim 4, characterized in that, The conditional statement for the query is as follows: Determine whether the data in the user name input box and / or the organization name input box is a string type; if so, determine whether the click attribute of the query button is empty. If the click attribute of the query button is not empty, perform a search for the input content.

6. The method according to claim 4, characterized in that, The conditional statement for the information synchronization condition is: Determine whether the friend query plugin is enabled. If it is, synchronize the friend information. If not, determine whether the click attribute of the information synchronization button is empty. If the click attribute of the information synchronization button is not empty, the friend query plugin is enabled, and friend information is synchronized.

7. The method according to claim 4, characterized in that, The conditional statement for the user permission conditions is as follows: Construct a mapping relationship between the user IDs of all users and the friend information corresponding to the user IDs; Find and display the friend information that matches the current user ID in the mapping relationship.

8. The method according to claim 6, characterized in that, The step of inserting the plugin data table into the conditional statement includes: When the friend query plugin is enabled, friend information is synchronized to the plugin's data table. or, If the friend query plugin is off and the click attribute of the information synchronization button is not empty, synchronize friend information to the plugin data table.

9. The method according to claim 8, characterized in that, The test request also includes the communication requirements between the friend query plugin and the fund trading platform. Before synchronizing friend information to the plugin's data table, the conditional statements for the interaction conditions corresponding to the communication requirements include: Determine whether the communication between the friend query plugin and the fund trading platform is normal. If so, execute the synchronization of friend information from the fund trading platform to the plugin's data table.

10. The method according to claim 1, characterized in that, The test cases for generating the friend query plugin include: Target data that conforms to the initial framework of the plugin data table is filtered from the historical transaction data; wherein, the initial framework of the plugin data table includes user ID, user name, friend ID, friend name, name of the organization to which the user belongs, and name of the organization to which the friend belongs; Based on the test criteria, test data is selected from the target data, and boundary value analysis is used to determine the verification data corresponding to the test data. The test data and the test script are combined to obtain test cases for the friend query plugin.

11. The method according to claim 10, characterized in that, For the query conditions, determining the verification data corresponding to the test data includes: The test data includes multiple user names. The boundary value analysis method is used to perform precise matching of the multiple user names to determine the query results, which include the serial number, organization name, user name and user ID corresponding to the multiple user names, as verification data corresponding to the test data.

12. A testing method comprising a friend query plugin as described in any one of claims 1-11, characterized in that, include: Obtain the requirements analysis report and / or use case specification of the fund trading platform, and determine the functional testing points and process testing points of the fund trading platform; wherein, the fund trading platform includes a transaction management module, a confirmation management module, a message management module, a position management module, and a clearing and settlement management module for setting up the friend query plugin; Based on the functional testing criteria, functional test cases for the user data module, the transaction management module, the confirmation management module, the message management module, the position management module, and the clearing and settlement management module are written using equivalence class partitioning, boundary value analysis, or error guessing. Based on the process testing points, use decision tables, scenario methods, or error guessing methods to write small process test cases within each module and large process test cases simulating interactions between each module. The historical transaction data is divided into functional test data for each module, small process test data, and large process test data between the modules. The functional test cases and the process test cases are reviewed. If the review result is "passed", the functional test data, the small process test data, and the large process test data are substituted into the functional test cases, the small process test cases, and the large process test cases respectively to test the fund trading platform and determine whether the module test results of each module and the interaction test results between the modules meet the expected test results.

13. The method according to claim 12, characterized in that, The test cases for the small process of the transaction management module include: Log in to the aforementioned fund trading platform; Click the "Initiate Inquiry" button to request an inquiry approval. Redirecting to the approval form page, open the approval information corresponding to the inquiry approval request; Click the "Terminate Transaction" button; The expected test results of the aforementioned small-process test case include: Login successful; Initiation successful; Open successful; Transaction terminated for approval order.

14. The method according to claim 12, characterized in that, The large-scale test cases between the transaction management module and the message management module include: The confirmation management module sends a confirmation request message including a transaction identifier to the message management module; The message management module sends the confirmation request message to the registration system and receives the confirmation response message returned by the registration system; The message management module compares the confirmation request message and the confirmation response message, determines the matching result, and sends the matching result to the confirmation management module. If the confirmation request message and the confirmation response message match successfully, the confirmation management module will change the confirmation status of the transaction corresponding to the transaction identifier to confirmed.

15. A testing device for a friend search plugin, characterized in that, include: The acquisition module is used to acquire the test request of the friend query plugin; wherein, the test request includes the friend query plugin requirements and historical transaction data of the friend query plugin, and the friend query plugin requirements include query interface requirements; A module is developed to analyze the test points of the friend query plugin based on the requirements of the query interface, and to develop test scripts corresponding to the query conditions included in the test points. The generation module is used to select test data and verification data from the historical transaction data, combine the test data and the test script, and generate test cases for the friend query plugin. The testing module is used to respond to the test request, execute the test case, determine whether the execution result of the test case is verification data, and obtain the test result of the test request. The writing module is also used for: Construct the plugin data table for the friend query plugin; Using the equivalence class partitioning method, generate the conditional statement for the query conditions; Insert the plugin data table into the conditional statement to obtain the test script for the friend query plugin.

16. A testing apparatus comprising the friend query plugin as described in claim 15, characterized in that, include: The acquisition module is used to acquire the requirements analysis report and / or use case specification of the fund trading platform, and to determine the functional test points and process test points of the fund trading platform; wherein, the fund trading platform includes a transaction management module, a confirmation management module, a message management module, a position management module, and a clearing and settlement management module for setting up the friend query plugin; The module is designed to write functional test cases for the user data module, the transaction management module, the confirmation management module, the message management module, the position management module, and the clearing and settlement management module, respectively, based on the functional test points and using equivalence class partitioning, boundary value analysis, or error guessing. The module is also used to write small process test cases within each module and large process test cases simulating interactions between each module, based on the process test points and using decision tables, scenario methods, or error guessing methods. The data partitioning module is used to divide the historical transaction data into functional test data for each module, small process test data, and large process test data between the modules. The testing module is used to review the functional test cases and the process test cases. If the review result is "passed", the functional test data, the small process test data, and the large process test data are respectively substituted into the functional test cases, the small process test cases, and the large process test cases to test the fund trading platform and determine whether the module test results of each module and the interaction test results between the modules meet the expected test results.

17. An electronic device for testing a friend search plugin, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-14.

18. A computer-readable medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-14.

19. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-14.

Images