Financial institution system testing method and device and storage medium

Abstract

The invention discloses a financial institution system testing method and device and a storage medium. The method comprises the following steps: determining a to-be-tested target financial institution system and determining financial service test requirements; according to the financial service test requirement, performing point burying processing on the source code of the target financial institution system to obtain a processed source code; determining a target test case according to burying point information in the processed source code; the target financial institution system with the burying point information is tested through the target test case, a test result is obtained, and the test result is used for representing whether the target financial institution system has risks or not. According to the invention, the method solves a problem that the testing accuracy of the financial institution system is low because the comprehensive testing of the financial institution system can only be carried out in the related technology.

Description

Technical Field

[0001] The present application relates to the field of financial technology, and more specifically, to a test, device and storage medium for a financial institution system. Background Art

[0002] In the financial industry, as business continues to expand and become more complex, the scale and complexity of financial institutions' systems are also increasing. Traditionally, the testing of these systems has mostly adopted a comprehensive, full-function coverage strategy, that is, during the testing phase, all functional modules, all business processes, and all data processing logic of the system are fully verified as much as possible.

[0003] However, this all-round testing strategy requires the testing team to have an in-depth understanding and mastery of every detail of the financial institution's system. Testers often need to spend a lot of time learning and understanding complex business processes, and this high reliance on business knowledge means an extension of the testing cycle and excessive consumption of human resources. Secondly, all-round testing often requires a large amount of test data when executing, especially for systems involving a large amount of transaction records and customer information. This not only increases the workload of data preparation, but may also lead to excessive resource consumption in the test environment, thereby affecting the test efficiency. More importantly, it is difficult for all-round testing to cover all possible abnormal situations and boundary conditions within a limited time. Therefore, the accuracy of the test results may be limited, and the stability and security of the system under extreme circumstances cannot be guaranteed.

[0004] Currently, no effective solution has been proposed to address the problem that related technologies can only conduct all-round testing on financial institution systems, resulting in relatively low accuracy in testing financial institution systems. Summary of the invention

[0005] The main purpose of this application is to provide a test, device and storage medium for a financial institution system to solve the problem that the related technology can only perform a comprehensive test on the financial institution system, resulting in a relatively low accuracy of the test on the financial institution system.

[0006] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a testing method for a financial institution system is provided. The method includes: determining a target financial institution system to be tested and determining financial service testing requirements; performing point tracking processing on the source code of the target financial institution system according to the financial service testing requirements to obtain processed source code; determining a target test case according to the point tracking information in the processed source code; testing the target financial institution system with the point tracking information through the target test case to obtain a test result, wherein the test result is used to characterize whether the target financial institution system has risks.

[0007] Furthermore, the target financial institution system with the burying point information is tested through the target test case, and the test results obtained include: running the target test case in the host system in the target financial institution system with the burying point information to obtain a first running result; running the target test case in the lower host system in the target financial institution system with the burying point information to obtain a second running result; and obtaining the test result based on the first running result and the second running result.

[0008] Furthermore, according to the financial business testing requirements, the source code of the target financial institution system is processed by embedding points, and the processed source code includes: according to the financial business testing requirements, a first keyword is determined, wherein the first keyword is used to indicate the location of embedding points in the source code of the target financial institution system; according to the first keyword, the source code of the target financial institution system is processed by embedding points to obtain the processed source code.

[0009] Furthermore, determining the first keyword based on the financial business testing requirements includes: determining the financial business functions that need to be tested based on the financial business testing requirements; determining the target code in the source code for implementing the financial business functions based on the financial business functions; and determining the first keyword based on the target code.

[0010] Furthermore, determining the target test case based on the tracking information in the processed source code includes: determining the test coverage based on the tracking information; and determining the target test case based on the test coverage.

[0011] Furthermore, after obtaining the test results based on the first operating result and the second operating result, the method also includes: determining a first test coverage of the target test case based on the first operating result; determining a second test coverage of the target test case based on the second operating result; updating the target test case based on the first test coverage and the second test coverage, and testing the target financial institution system again based on the updated target test case.

[0012] Furthermore, determining the target test case based on the tracking information in the processed source code includes: determining a second keyword based on the full-branch testing requirement for the source code, wherein the second keyword is used to indicate the location of the tracking in the source code of the target financial institution system; adjusting the tracking information in the processed source code based on the second keyword to obtain adjusted source code; and determining the target test case based on the tracking information in the adjusted source code.

[0013] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a testing device for a financial institution system is provided. The device includes: a first determination unit, used to determine the target financial institution system to be tested and determine the financial service test requirements; a first processing unit, used to perform point-embedding processing on the source code of the target financial institution system according to the financial service test requirements to obtain the processed source code; a second determination unit, used to determine the target test case according to the point-embedding information in the processed source code; a testing unit, used to test the target financial institution system with the point-embedding information through the target test case to obtain the test result, wherein the test result is used to characterize whether the target financial institution system has risk.

[0014] Furthermore, the test unit includes: a first running module, used to run the target test case in the host system of the target financial institution system with the burial point information, and obtain a first running result; a second running module, used to run the target test case in the lower host system of the target financial institution system with the burial point information, and obtain a second running result; a test result module, used to obtain the test result based on the first running result and the second running result.

[0015] Furthermore, the first processing unit includes: a first determination module, used to determine a first keyword based on financial business testing requirements, wherein the first keyword is used to indicate the location of a target financial institution system's source code for embedding; a first processing module, used to embed the source code of the target financial institution system based on the first keyword to obtain processed source code.

[0016] Furthermore, the first determination module includes: a first determination sub-module, used to determine the financial business functions that need to be tested according to the financial business testing requirements; a second determination sub-module, used to determine the target code in the source code for implementing the financial business functions based on the financial business functions; and a third determination sub-module, used to determine the first keyword based on the target code.

[0017] Furthermore, the second determination unit includes: a fourth determination submodule, used to determine the test coverage according to the tracking point information; and a fifth determination submodule, used to determine the target test case according to the test coverage.

[0018] Furthermore, the device also includes: a third determination unit, used to determine a first test coverage of the target test case based on the first operation result; a fourth determination unit, used to determine a second test coverage of the target test case based on the second operation result; a second processing unit, used to update the target test case based on the first test coverage and the second test coverage, and test the target financial institution system again based on the updated target test case.

[0019] Furthermore, the second determination unit includes: a sixth determination sub-module, used to determine the second keyword based on the full-branch testing requirement of the source code, wherein the second keyword is used to indicate the location of the embedding in the source code of the target financial institution system; an adjustment sub-module, used to adjust the embedding information in the processed source code based on the second keyword to obtain the adjusted source code; and a seventh determination sub-module, used to determine the target test case based on the embedding information in the adjusted source code.

[0020] In an embodiment of the present application, by determining the target financial institution system to be tested and determining the financial business test requirements; according to the financial business test requirements, the source code of the target financial institution system is processed with tracking points to obtain the processed source code; according to the tracking point information in the processed source code, the target test case is determined; the target financial institution system with the tracking point information is tested through the target test case to obtain the test result, wherein the test result is used to characterize whether the target financial institution system has risks, which solves the problem that only the financial institution system can be tested in an all-round way in the related technology, resulting in relatively low accuracy of the financial institution system test. In the present application, according to the specific financial business test requirements, the source code is accurately tracked, the target test case is designed according to the tracking point information, and the financial institution system is tested using the target test case, which can more accurately evaluate the performance of the system in a specific business scenario, effectively identify potential risk points and functional defects, and thus achieve the technical effect of improving the accuracy of the test. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The drawings constituting a part of the present application are used to provide a further understanding of the present application. The illustrative embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0022] Figure 1 A hardware structure block diagram of a computer terminal for implementing a testing method for a financial institution system is shown;

[0023] Figure 2 is a flow chart of a testing method for a financial institution system provided according to an embodiment of the present application;

[0024] Figure 3 It is a flow chart of a method for testing a financial institution system with embedded point information provided in accordance with an embodiment of the present application;

[0025] Figure 4 is a flowchart of a method for determining a first keyword provided in an embodiment of the present application;

[0026] Figure 5 is a schematic diagram of a testing device for a financial institution system provided according to an embodiment of the present application;

[0027] Figure 6 It is a structural block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0028] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

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

[0030] It should be noted that the collected information involved in this application (including but not limited to the source code of the target financial institution system, the processed source code, the financial business test requirements, the target test cases, etc.) is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data are in compliance with relevant laws, regulations and standards, necessary confidentiality measures are taken, and public order and good customs are not violated, and corresponding operation entrances are provided for users to choose to authorize or refuse. For example, an interface is set up between this system and relevant users or institutions to provide users with corresponding operation entrances for users to choose to agree or refuse the automated decision results; if the user chooses to refuse, the expert decision process will be entered.

[0031] Example 1

[0032] According to an embodiment of the present application, a method embodiment for testing a financial institution system is also provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0033] The method embodiment provided in the first embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 FIG. 1 shows a hardware structure block diagram of a computer terminal (or mobile device) for implementing a testing method for a financial institution system. Figure 1 As shown, the computer terminal 10 (or mobile device) may include one or more (102a, 102b, ..., 102n are used to illustrate) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0034] It should be noted that the one or more processors 102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10 (or mobile device). As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0035] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the test method of the financial institution system in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the test method of the financial institution system described above is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0036] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0037] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 (or mobile device).

[0038] Under the above operating environment, this application provides Figure 2 The testing method for the financial institution system shown. Figure 2 It is a flowchart of the testing method of the financial institution system according to Example 1 of the present application.

[0039] Step S201, determining the target financial institution system to be tested and determining the financial service testing requirements.

[0040] Optionally, determine the target financial institution that the current financial institution needs to test, and then analyze and determine the financial business scenarios and logical function points that need to be verified (i.e., the above-mentioned financial business test requirements) based on business requirement documents, system design documents, and user feedback. For example, financial business test requirements may include account management, transaction processing, customer information maintenance, report generation, exception handling, and security mechanisms. It should be noted that the above-mentioned target financial institution system includes the host system and the part of the financial institution information system that has been or is about to be migrated from the large host system to the platform system (lower host system).

[0041] Step S202, based on the financial business testing requirements, the source code of the target financial institution system is processed to obtain the processed source code.

[0042] Optionally, according to the financial business testing requirements, in the corresponding business scenarios, the source code of the target financial institution system is selected to determine the key code paths and data processing points. After locating the key code paths and data processing points, intelligent recognition technology can be used to identify keywords or code structures. After identifying the dynamically defined keywords or code structures, text matching is performed, and then the embedded point information is inserted at the corresponding position. The embedded point information can be a log record, a variable status checkpoint, or a specific test identifier, etc. Through the above embedded point operation, the source code with embedded point information added is obtained, that is, the processed source code.

[0043] For example, the testing requirements may be to verify the accuracy of exchange rate calculations, ensure that all compliance checks are performed in accordance with regulations, check the integrity of transaction records, and ensure that the process of fund transfers is completely consistent with the existing host system. Based on the above testing requirements, log points are embedded at key logic points such as exchange rate calculations, compliance checks, and transaction records. For example, when the exchange rate calculation function is called, the input amount and source currency, target currency, and calculated exchange rate value are recorded by embedding log points; when performing compliance checks, the type of check (such as sanctions list checks) and the results of the check are recorded; in the processing part of the transaction record, the time, amount, remitter information, and beneficiary information of the transaction are recorded.

[0044] Step S203, determining the target test case according to the embedded point information in the processed source code.

[0045] Optionally, analyze the tracking information in the processed source code, identify the possible branch structure, conditional judgment and data processing logic in the system, and design target test cases to simulate real business scenarios and data flows, including transaction processing under normal circumstances, system response under abnormal circumstances, data consistency verification, etc., to ensure that the test cases can trigger the key paths and data processing points recorded in the tracking information. Test case design should take into account the complexity of business processes and the diversity of data to ensure that the functions and performance of the system can be fully verified.

[0046] For example, the target test case corresponding to the step S202 case includes the exchange rate calculation function test case "Case ID: C001; Test conditions: Input amount: 10000A, source currency: A, target currency: B; Expected result: Calculation result: 65000B, exchange rate value: 6.50 (A / B))".

[0047] Step S204, testing the target financial institution system with the embedded point information through the target test case to obtain the test result, wherein the test result is used to characterize whether the target financial institution system has risks.

[0048] Optionally, by executing the target test case on the host system and the downstream host system of the target financial institution respectively, a first running result and a second running result are obtained, and by comparing the two running results, the consistency of data processing and business logic is checked to verify the functional correctness and data integrity of the system.

[0049] For example, the target test case is run in the downstream host system with tracking information to obtain the first running result A, such as performing a normal deposit operation in the account deposit function, and the tracking records the time consumption of the operation, the change in the account balance and other information. The target test case is run in the host system to obtain the second running result B, such as executing the same test case on the host system in the account deposit function and collecting the same type of data. Based on the first running result A and the second running result B, the test results are compared and analyzed to compare whether the changes in the account balances in the two systems are consistent, whether the time consumption of the operation is reasonable, and whether there are any abnormal behaviors or data inconsistencies. Assuming that the time consumption of the deposit operation in the downstream host system is significantly greater than that in the host system, or the calculation results of the account balance are inconsistent, this may indicate performance problems or data processing errors, and there are potential risks in the system.

[0050] In an embodiment of the present application, by determining the target financial institution system to be tested and determining the financial business test requirements; according to the financial business test requirements, the source code of the target financial institution system is processed with tracking points to obtain the processed source code; according to the tracking point information in the processed source code, the target test case is determined; the target financial institution system with the tracking point information is tested through the target test case to obtain the test result, wherein the test result is used to characterize whether the target financial institution system has risks, which solves the problem that only the financial institution system can be tested in an all-round way in the related technology, resulting in relatively low accuracy of the financial institution system test. In the present application, according to the specific financial business test requirements, the source code is accurately tracked, the target test case is designed according to the tracking point information, and the financial institution system is tested using the target test case, which can more accurately evaluate the performance of the system in a specific business scenario, effectively identify potential risk points and functional defects, and thus achieve the technical effect of improving the accuracy of the test.

[0051] In an optional embodiment, if Figure 3 As shown in the figure, the target financial institution system with embedded point information is tested through the target test case, and the test results include:

[0052] Step S301, run the target test case in the host system of the target financial institution system with the embedded point information to obtain the first running result.

[0053] Optionally, deploy the target financial institution system with the tracking point information in the test environment of the host system, and then execute the target test case in the system for testing. The system will collect key data and status information during the runtime based on the tracking point location, and this information will be recorded as the first running result.

[0054] For example, taking an international remittance case as the basis, the design target test case is "Test case ID: TC004; Test purpose: to verify the consistency and accuracy of the exchange rate calculation, compliance check and transaction record generation functions from to in the international remittance process; Test conditions: the remittance amount is 10,000, the remittance time is 2023-10-01 14:00:00, the remitter is "Li Hua", and the payee is "John Doe"".

[0055] Execute the TC004 test case to perform international remittance operations in the host system. Assuming that the exchange rate at that time is 6.50, 10,000 should be converted to 65,000. After the host system executes the transaction, the following first operation result can be obtained: "Exchange rate calculation result: 65,000; Compliance check result: Transaction passed, no sanctions list check was triggered; Transaction record: 2023-10-01 14:00:00, remitter "Li Hua", recipient "John Doe", amount 10,000, exchange rate 6.50, final amount 65,000, status successful".

[0056] Step S302, running the target test case in the lower host system of the target financial institution system with the buried point information to obtain a second running result.

[0057] Optionally, as in step S301, the target financial institution system with the embedded point information is deployed in the test environment of the host system, and the same target test case is executed for testing. When the system is running, the key data and status of the running time are recorded as the second running result.

[0058] For example, execute the TC004 test case in the host system to perform the same international remittance operation. The host system should perform the same exchange rate calculation, compliance check and transaction record generation logic to obtain the following second operation result: "Exchange rate calculation result: 65000 (or should be consistent with the calculation result of the host system); Compliance check result: Transaction passed, no sanctions list check was triggered; Transaction record: 2023-10-01 14:00:00, remitter "Li Hua", recipient "John Doe", amount 10000, exchange rate 6.50, final amount 65000, status successful".

[0059] Step S303, obtaining a test result according to the first operation result and the second operation result.

[0060] Optionally, after executing the target test cases in the host system and the down-host system and collecting the running results in steps S301 and S302, the tester or the automated testing tool needs to compare and analyze the two sets of running results. The main comparison points include but are not limited to: consistency of data processing, correctness of function implementation, similarity of exception handling mechanisms, comparison of performance indicators (such as response time, processing speed), etc. If the first running result and the second running result are completely consistent with the above-mentioned comparison points, or are within an acceptable range of differences, the test results indicate that the system maintains the original functions and performance after migration, and there is no obvious risk. On the contrary, if the difference is found to be beyond expectations, or there is a lack of function or data processing error, the test results will point out where these risks are, and further debugging and optimization are required.

[0061] For example, by comparing the first running result in step S301 and the second running result in step S302, it is found that the two are completely consistent. The test results show that when the host system processes international remittance transactions, its functions and logic are consistent with the host system, and no differences or potential risk points are found. This verifies that the functions of the host project can be successfully implemented, which can ensure that the key financial business logic remains accurate after the business migration.

[0062] Through the above technical solution, the same test cases are executed in the host system and the downstream host system and the results are compared to verify the success and security of the downstream host project. This can not only effectively detect the logical differences in the code migration process, but also evaluate the ability of the downstream host system to handle actual financial business, reducing the potential business risks caused by code migration.

[0063] In an optional embodiment, according to the financial business test requirements, the source code of the target financial institution system is subjected to point tracking processing, and the processed source code includes:

[0064] The first step is to determine the first keyword based on the financial business testing requirements, wherein the first keyword is used to indicate the location of the source code of the target financial institution system.

[0065] Optionally, the test target function is clarified according to the test requirements, and the business process is analyzed. For example, code dependency analysis tools are used to understand the dependencies between functions, methods or classes; static code analysis tools are used to detect the call graph in the code, identify the key functions, methods, classes, etc. in the source code, identify the key nodes of the data flow, that is, the points where data enters the system, is processed and leaves the system, and determine the first keyword. For example, the first keyword may include the start and end of the transaction processing function, the conditional statement for transaction amount verification (such as if (amount>0)), a specific variable assignment statement, an exception handling code segment (such as a try-catch statement), etc.

[0066] Taking the international remittance business test as an example, it is assumed that the test requirements include verifying whether the exchange rate calculation in the international remittance process is accurate, and whether the compliance check (including the sanction list check, etc.) is performed as expected. Therefore, it is determined that the first keyword includes the exchange rate calculation function: "calculateExchangeRate" and the compliance check function: "performComplianceCheck".

[0067] In the second step, the source code of the target financial institution system is processed according to the first keyword to obtain the processed source code.

[0068] Optionally, after determining the first keyword that needs to be tracked, the tracking code can be inserted at the location indicated by these keywords in the source code through an automated tool. The insertion of the tracking code can be automatically generated by writing or using an existing code analysis and insertion tool that can identify the first keyword and automatically insert the tracking logic. For example, the tool can automatically add a line of logging statements after identifying "if(..." to record the status of the conditional judgment. It can also be done manually, by the tester or developer inserting the tracking logic at the appropriate location in the source code according to the test requirements and the instructions of the first keyword. These tracking codes may include functions such as logging, performance timing, and exception capture, so that the key behaviors and data processing of the system can be captured when the test case is executed. For example, in the source code of the transfer function, tracking marks may be added before and after the transfer amount verification logic to record the input and output data of the verification logic.

[0069] Through the above technical solution, the test requirements are clarified and the corresponding keywords are determined, and the tracking information can be accurately added to the source code, providing a basis for subsequent comparative testing. It can not only reduce the dependence on the business knowledge of testers, but also ensure the depth and breadth of the test, thereby achieving the technical effect of improving test efficiency and accuracy.

[0070] In an optional embodiment, if Figure 4 As shown, according to the financial business testing requirements, the first keyword is determined to include:

[0071] Step S401, determining the financial business functions that need to be tested according to the financial business test requirements.

[0072] Optional, financial business testing requirements refer to specific business functions and scenarios that need to be verified in the target financial institution system in the host project based on business processes, functional requirements and compliance requirements. These requirements are usually described in detail in business requirements documents and system design documents, and can also be recorded in user manuals, operation guides and other documents so that testers can fully understand the business logic and usage scenarios of the system. Therefore, by analyzing business requirements documents, system design documents, user manuals and other materials, the business functions and corresponding operation processes to be tested can be identified.

[0073] Step S402: determining the target code in the source code for implementing the financial business function according to the financial business function.

[0074] Optionally, obtain the complete source code library of the target software system. The code files of the development environment can be downloaded or accessed through the version control system. Conduct code review on the entire source code library, understand its business logic and data processing process, find code segments related to the previously determined financial business functions, and use code analysis tools and keyword search functions to quickly locate the code area that implements specific business functions. For example, use regular expressions to search for function names and parameters related to "account transfer" or "loan application". By reading and understanding the code, identify the key algorithms, data structures, and function calls that implement business functions, and record the location, function name, input and output parameters, and other important information of the target code for subsequent code tracking and test design. It should be noted that the above-mentioned target code refers to the code segment in the source code that directly implements specific financial business functions, including but not limited to algorithm implementation, data processing logic, external service calls, and result verification.

[0075] For example, for the exchange rate calculation function of international remittances, the target code can be located at the code segment that executes the exchange rate API call, exchange rate conversion calculation and result verification. The code segment for the exchange rate API call, for example, calls the function of the external exchange rate service; the algorithm code for executing the exchange rate conversion calculation, such as the formula for calculating the amount of foreign currency to be exchanged for local currency; the code logic for result verification, such as checking whether the converted amount is within a reasonable range.

[0076] Step S403, determining the first keyword according to the target code.

[0077] Optionally, according to the target code determined in the second step, you can use tools or methods such as static code analysis, dynamic code analysis, dependency analysis, regular expressions and text search, source code annotations, business process diagrams and architecture design documents to identify the key functions, methods or classes responsible for implementing financial business functions. Assuming that you need to test the transaction record update function, you need to track the updateRecord() method in the TransactionRecord class and any conditional statements involving transaction status judgment, such as if (transactionStatus == SUCCESS), where the method name or class name can be directly used as a keyword, for example, the updateRecord method name can be directly used as the first keyword; if it is a conditional statement, the first keyword can be defined in combination with a regular expression.

[0078] Through the above technical solution, key code locations in business scenarios are targeted and tracking is performed to ensure the accuracy of tracking, thereby achieving the technical effect of improving test efficiency and quality.

[0079] In an optional embodiment, determining the target test case according to the tracking information in the processed source code includes:

[0080] The first step is to determine the test coverage based on the tracking point information.

[0081] Optionally, collect and review all the tracking information that has been set, and use code analysis tools to identify all code paths related to the test business. For example, the transfer business may include the normal transfer process, branch processing logic under abnormal conditions, and code segments that interact with external systems. Based on the above code path analysis, formulate detailed test coverage to ensure that the functional points and exception handling logic corresponding to each tracking information are included in the test plan.

[0082] Assume that the transfer business function is being tested. In addition to tracking the code logic branches corresponding to the normal transfer process, tracking is also performed on the logic branches under abnormal conditions such as the transfer amount is less than 0, the account balance is insufficient, and the recipient's account does not exist. The test coverage should cover the code path of the normal transfer process and the code path for handling the above abnormal conditions.

[0083] The second step is to determine the target test cases based on the test coverage.

[0084] Optionally, based on the test coverage determined in the first step, design target test cases that can trigger all buried point information. For example, the test cases for the transfer business function in the first step case should include normal transfer process test cases and abnormal condition test cases. Among them, normal business process test cases can be generated according to the system model (such as state diagrams, flow charts, etc.); for branch processing logic codes under abnormal conditions, fuzzy testing can be used to generate test cases containing irregular or boundary data to ensure that every important scenario and logic point is fully verified. In addition, you can also manually design a part of the core or complex test cases, and then use automation tools to generate a large number of basic test cases to cover various boundary conditions and input combinations.

[0085] For example, for the abnormal condition handling in the first step, the abnormal condition test cases can be designed as follows:

[0086] When the transfer amount is less than 0, the designed test case TC001 can be to transfer -500 from account A (balance 3000) to account B. The expected result should be that the transaction is rejected and the tracking information "transferLessThanZero" is recorded.

[0087] When the account balance is insufficient, the test case TC002 can be designed to transfer 100 from account C (balance 99) to account D. The expected result should be that the transaction is rejected, the account balance remains unchanged, and the buried information "insufficientBalance" is recorded.

[0088] When the recipient account does not exist, the designed test case TC003 can be to transfer 500 from account E (balance 10,000) to a non-existent account F. The expected result should be that the transaction is rejected and the embedding information "recipientAccountNotFound" is recorded.

[0089] Through the above technical solution, through the analysis and utilization of the buried point information, the formulation and optimization of test cases are guided to achieve higher test efficiency and test quality, thereby achieving the technical effect of improving the accuracy of the test.

[0090] In an optional embodiment, after obtaining the test result according to the first operation result and the second operation result, the method further includes:

[0091] The first step is to determine the first test coverage of the target test case according to the first running result.

[0092] Optionally, a code coverage analysis tool can be used to analyze the first run result, identify the number of code lines triggered by the test case and the number of code lines not triggered, so as to determine the first test coverage of the target test case, that is, the proportion of the number of executed code lines to the total number of code lines. For example, if there are 1,000 lines of code in total and the first run result triggers 800 lines, the first test coverage is 80%.

[0093] The second step is to determine the second test coverage of the target test case based on the second running result.

[0094] Optionally, the same code coverage analysis tool as in the first step may be used to analyze the second running result to determine the second test coverage of the target test case.

[0095] The third step is to update the target test cases based on the first test coverage and the second test coverage, and test the target financial institution system again based on the updated target test cases.

[0096] Optionally, based on the analysis results of the first test coverage and the second test coverage, the code areas where the execution of the test cases in the host system and the host system are significantly different are identified, which may include branches that are frequently triggered in the host system but not covered in the host system, or logic points that are specially processed in the host system but not fully tested in the host system. After that, new test cases are designed or existing test cases are adjusted to supplement the business functions of the scenarios with incomplete coverage or large differences found in the above analysis. For example, if the test coverage of the large transfer approval process is found to be low in the host system, new test cases are designed to specifically test this process to ensure that all possible abnormal conditions and business scenarios are covered. After obtaining the new test cases, the target financial institution system is tested again using the updated target test case set, new test results are collected, and changes in test coverage are analyzed to ensure that all key business logic and data processing paths are fully verified.

[0097] Through the above technical solution, areas with insufficient testing can be specifically identified and test cases can be updated in a timely manner, which can achieve dynamic optimization of target test cases and continuous testing of target financial institution systems, thereby improving the accuracy of testing.

[0098] In an optional embodiment, determining the target test case according to the tracking information in the processed source code includes:

[0099] The first step is to determine the second keyword based on the full-branch testing requirements for the source code, wherein the second keyword is used to indicate the location of the source code of the target financial institution system to be buried.

[0100] Optionally, a syntax analyzer or regular expression can be used to scan the source code to identify all second keywords, including conditional statements and loop body boundaries. Based on the identified second keyword positions, all possible branch points in the code are determined, and a point-burying rule is defined for each branch point, such as inserting a specific color-burying code before each "{" symbol to record the execution of the branch.

[0101] For example, if the following situation is identified as an uncovered branch, for example, the account balance is exactly equal to the transfer amount, in which case the transfer should be successful, but the balance is zero. In the source code of the transfer function of the target financial institution system, multiple conditional statements are identified, and one of the key conditional statements is used to determine whether the account balance is sufficient for the transfer operation, such as "if (accountBalance> = transferAmount) {", then this conditional statement is used as the second keyword.

[0102] In the second step, according to the second keyword, the tracking point information in the processed source code is adjusted to obtain the adjusted source code.

[0103] Optionally, the source code is modified at the identified keyword position to add the relevant code for the coloring embedding. An optional modification method is to write an adjustment script to automatically insert the coloring embedding code at the position indicated by the second keyword in the source code, such as recording logs, setting marker variables, etc., to track the execution of branches. After the adjustment script is written, the adjustment script can be directly run to obtain the adjusted source code.

[0104] For example, according to the case in the second step, the tracking point is set at "if (accountBalance> = transferAmount) {", and the tracking point code obtained may be "if (accountBalance> = transferAmount) {" execute the transfer operation; testLogger.log ("TransferInitiated", transferAmount, accountBalance);}" Among them, "testLogger.log" is a custom color tracking point function used to record the test log of transfer initialization. The parameter "TransferInitiated" is the identifier of the tracking point information, and transferAmount and accountBalance are the specific values ​​of the transfer amount and account balance respectively.

[0105] The third step is to determine the target test cases based on the tracking information in the adjusted source code.

[0106] Optionally, collect and review all the set tracking information. You can use tools such as static code analysis to identify all code paths related to the test business and determine the test coverage. Design target test cases based on the test coverage. For example, you can generate normal process test cases based on the system model (such as state diagrams, flow charts). For branch processing logic code under abnormal conditions, you can use fuzz testing to generate abnormal condition test cases including irregular or boundary data to ensure that every important scenario and logic point is fully verified. In addition, you can manually design a part of the core or complex test cases, and then use automation tools to generate a large number of basic test cases to cover various boundary conditions and input combinations.

[0107] For example, the target test case designed for the technical branch not covered in the case in the first step can be "Test case ID: TC003, account balance: 1000, transfer amount: 1000, expected result: transfer successful, account balance is zero".

[0108] Through the above technical solution, full branch test coverage of the target financial institution system source code is ensured, thereby achieving the technical effect of improving the comprehensiveness and accuracy of the test.

[0109] In the embodiment of the present application, the target financial institution system to be tested and the financial business test requirements are determined; according to the financial business test requirements, the source code of the target financial institution system is processed with tracking points to obtain the processed source code; according to the tracking point information in the processed source code, the target test case is determined; the target financial institution system with the tracking point information is tested with the target test case to obtain the test result, wherein the test result is used to characterize whether the target financial institution system has risks, which solves the problem that only the financial institution system can be tested in an all-round way in the related technology, resulting in relatively low accuracy of the financial institution system test. According to the specific financial business test requirements, the source code is accurately tracked and the target test case is designed, and the system is tested using the target test case, which can more accurately evaluate the performance of the system in a specific business scenario, effectively identify potential risk points and functional defects, and thus achieve the technical effect of improving the accuracy of the test.

[0110] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0111] Example 2

[0112] The present application also provides a testing device for a financial institution system. It should be noted that the testing device for a financial institution system in the present application can be used to execute the testing method for a financial institution system provided in the present application. The following is an introduction to the testing device for a financial institution system provided in the present application.

[0113] According to an embodiment of the present application, a device for implementing the above-mentioned financial institution system testing method is also provided, such as Figure 5 As shown, the device includes: a first determining unit 501, a first processing unit 502, a second determining unit 503, and a testing unit 504.

[0114] Specifically, the first determination unit 501 is used to determine the target financial institution system to be tested and to determine the financial business test requirements; the first processing unit 502 is used to perform tracking processing on the source code of the target financial institution system according to the financial business test requirements to obtain the processed source code; the second determination unit 503 is used to determine the target test case based on the tracking information in the processed source code; the testing unit 504 is used to test the target financial institution system with the tracking information through the target test case to obtain the test result, wherein the test result is used to characterize whether the target financial institution system has risks.

[0115] The test device for the financial institution system provided in the embodiment of the present application is used to determine the target financial institution system to be tested and determine the financial business test requirements through the first determination unit 501; the first processing unit 502 is used to perform point tracking processing on the source code of the target financial institution system according to the financial business test requirements to obtain the processed source code; the second determination unit 503 is used to determine the target test case according to the point tracking information in the processed source code; the test unit 504 is used to test the target financial institution system with point tracking information through the target test case to obtain the test result, wherein the test result is used to characterize whether the target financial institution system has risk, which solves the problem that only the financial institution system can be tested in all aspects in the related technology, resulting in relatively low accuracy of the financial institution system test. According to the specific financial business test requirements, the source code is accurately tracked and the target test case is designed, and the system is tested using the target test case, which can more accurately evaluate the performance of the system in a specific business scenario, effectively identify potential risk points and functional defects, thereby achieving the technical effect of improving the accuracy of the test.

[0116] Optionally, the testing unit 504 includes: a first running module, used to run the target test case in the host system of the target financial institution system with the burial point information, and obtain a first running result; a second running module, used to run the target test case in the lower host system of the target financial institution system with the burial point information, and obtain a second running result; a test result module, used to obtain the test result based on the first running result and the second running result.

[0117] Optionally, the first processing unit 501 includes: a first determination module, used to determine a first keyword based on financial business testing requirements, wherein the first keyword is used to indicate the location of the source code of the target financial institution system; a first processing module, used to perform point embedding processing on the source code of the target financial institution system based on the first keyword to obtain processed source code.

[0118] Optionally, the first determination module includes: a first determination sub-module, used to determine the financial business functions that need to be tested according to the financial business testing requirements; a second determination sub-module, used to determine the target code in the source code for implementing the financial business functions based on the financial business functions; and a third determination sub-module, used to determine the first keyword based on the target code.

[0119] Optionally, the second determination unit 502 includes: a fourth determination submodule, used to determine the test coverage according to the test point information; and a fifth determination submodule, used to determine the target test case according to the test coverage.

[0120] Optionally, the device also includes: a third determination unit, used to determine a first test coverage of the target test case based on the first operating result; a fourth determination unit, used to determine a second test coverage of the target test case based on the second operating result; a second processing unit, used to update the target test case based on the first test coverage and the second test coverage, and test the target financial institution system again based on the updated target test case.

[0121] Optionally, the second determination unit 502 includes: a sixth determination sub-module, used to determine the second keyword based on the full-branch testing requirement of the source code, wherein the second keyword is used to indicate the location of the source code of the target financial institution system; an adjustment sub-module, used to adjust the tracking information in the processed source code based on the second keyword to obtain the adjusted source code; a seventh determination sub-module, used to determine the target test case based on the tracking information in the adjusted source code.

[0122] It should be noted that the first determination unit 501, the first processing unit 502, the second determination unit 503, and the testing unit 504 correspond to steps S201 to S204 in Example 1, and the four units and the corresponding steps implement the same examples and application scenarios, but are not limited to the contents disclosed in the above-mentioned Example 1. It should be noted that the above-mentioned modules or units may be hardware components or software components stored in a memory (e.g., memory 104) and processed by one or more processors (e.g., processors 102a, 102b, ..., 102n), and the above-mentioned modules may also be part of the device and may be run in the computer terminal 10 provided in Example 1.

[0123] Example 3

[0124] An embodiment of the present application may provide an electronic device, Figure 6 is a structural block diagram of an electronic device according to an embodiment of the present application. Figure 6 As shown, the electronic device may include: one or more ( Figure 6 (only one is shown) processor 602, memory 604, storage controller, and peripheral interface, wherein the peripheral interface is connected to the radio frequency module, audio module and display.

[0125] Among them, the memory can be used to store software programs and modules, such as program instructions / modules corresponding to the methods and devices in the embodiments of the present application, and the processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, realizing the above-mentioned method. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0126] The processor can call the information and application programs stored in the memory through the transmission device to perform the following steps: determine the target financial institution system to be tested and determine the financial business test requirements; based on the financial business test requirements, perform point embedding processing on the source code of the target financial institution system to obtain the processed source code; based on the point embedding information in the processed source code, determine the target test case; test the target financial institution system with the point embedding information through the target test case to obtain the test result, wherein the test result is used to characterize whether the target financial institution system has risks.

[0127] The processor can call the information and application programs stored in the memory through the transmission device to perform the following steps: test the target financial institution system with the buried point information through the target test case, and obtain the test results including: running the target test case in the host system in the target financial institution system with the buried point information to obtain the first running result; running the target test case in the lower host system in the target financial institution system with the buried point information to obtain the second running result; and obtaining the test result based on the first running result and the second running result.

[0128] The processor can call the information and application programs stored in the memory through the transmission device to execute the following steps: based on the financial business testing requirements, the source code of the target financial institution system is subjected to point embedding processing to obtain the processed source code, including: based on the financial business testing requirements, determining a first keyword, wherein the first keyword is used to indicate the location of the source code of the target financial institution system for point embedding; based on the first keyword, the source code of the target financial institution system is subjected to point embedding processing to obtain the processed source code.

[0129] The processor can call the information and application programs stored in the memory through the transmission device to perform the following steps: determining the first keyword based on the financial business test requirements includes: determining the financial business functions that need to be tested based on the financial business test requirements; determining the target code in the source code for implementing the financial business functions based on the financial business functions; and determining the first keyword based on the target code.

[0130] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: determine the target test case based on the embedded point information in the processed source code, including: determine the test coverage based on the embedded point information; determine the target test case based on the test coverage.

[0131] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: after obtaining the test results based on the first operation result and the second operation result, the method also includes: determining the first test coverage of the target test case based on the first operation result; determining the second test coverage of the target test case based on the second operation result; updating the target test case based on the first test coverage and the second test coverage, and testing the target financial institution system again based on the updated target test case.

[0132] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: determining the target test case based on the embedded point information in the processed source code, including: determining the second keyword based on the full-branch test requirement of the source code, wherein the second keyword is used to indicate the location of the embedded point in the source code of the target financial institution system; adjusting the embedded point information in the processed source code based on the second keyword to obtain the adjusted source code; determining the target test case based on the embedded point information in the adjusted source code.

[0133] By adopting the embodiment of the present application, a solution for testing the financial institution system is provided. By determining the target financial institution system to be tested and determining the financial business test requirements; according to the financial business test requirements, the source code of the target financial institution system is processed with tracking points to obtain the processed source code; according to the tracking point information in the processed source code, the target test case is determined; the target financial institution system with the tracking point information is tested with the target test case to obtain the test result, wherein the test result is used to characterize whether the target financial institution system has risks, which solves the problem that only the financial institution system can be tested in an all-round way in the related technology, resulting in relatively low accuracy of the financial institution system test. According to the specific financial business test requirements, the source code is accurately tracked and the target test case is designed, and the system is tested using the target test case, which can more accurately evaluate the performance of the system in a specific business scenario, effectively identify potential risk points and functional defects, and thus achieve the technical effect of improving the accuracy of the test.

[0134] It can be understood by those skilled in the art that Figure 6 The structure shown is for illustration only, and the electronic device may also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a PDA, a mobile Internet device (Mobile Internet Devices, MID), a PAD, or other terminal devices. Figure 6 The structure of the electronic device is not limited. Figure 6 More or fewer components (such as network interfaces, display devices, etc.) shown in, or having Figure 6 Different configurations are shown.

[0135] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0136] Example 4

[0137] The embodiment of the present application further provides a storage medium. Optionally, in this embodiment, the storage medium can be used to store the program code executed by the test method of the financial institution system provided in the first embodiment.

[0138] Optionally, in this embodiment, the above storage medium may be located in any computer terminal in a computer terminal group in a computer network, or in any mobile terminal in a mobile terminal group.

[0139] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing the program steps of the testing method for a financial institution system.

[0140] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0141] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

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

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

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

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

[0146] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for testing a financial institution system, characterized in that: include: Determine the target financial institution system to be tested and determine the financial business testing requirements; According to the financial business test requirements, the source code of the target financial institution system is processed to obtain the processed source code; Determine a target test case based on the tracking information in the processed source code; The target financial institution system with embedded point information is tested through the target test case to obtain a test result, wherein the test result is used to characterize whether the target financial institution system has risks.

2. The method according to claim 1, characterized in that The target financial institution system with embedded point information is tested through the target test case, and the test results obtained include: Run the target test case in the host system of the target financial institution system with the embedded point information to obtain a first running result; Run the target test case in the lower host system of the target financial institution system with the embedded point information to obtain a second running result; The test result is obtained according to the first operation result and the second operation result.

3. The method according to claim 1, characterized in that According to the financial business test requirements, the source code of the target financial institution system is processed, and the processed source code includes: Determine a first keyword according to the financial business test requirement, wherein the first keyword is used to indicate a location for embedding a test point in the source code of the target financial institution system; The source code of the target financial institution system is processed according to the first keyword to obtain processed source code.

4. The method according to claim 3, characterized in that According to the financial business test requirements, the first keyword is determined to include: Determine the financial business functions that need to be tested according to the financial business test requirements; According to the financial business function, determining the target code in the source code for realizing the financial business function; The first keyword is determined according to the target code.

5. The method according to claim 1, characterized in that Determining the target test case based on the tracking information in the processed source code includes: Determine the test coverage based on the tracking point information; The target test case is determined according to the test coverage.

6. The method according to claim 2, characterized in that After obtaining the test result according to the first operation result and the second operation result, the method further includes: Determining a first test coverage of the target test case according to the first running result; Determining a second test coverage of the target test case according to the second running result; The target test case is updated based on the first test coverage and the second test coverage, and the target financial institution system is tested again based on the updated target test case.

7. The method according to claim 1, characterized in that Determining the target test case based on the tracking information in the processed source code includes: Determine a second keyword according to a full-branch test requirement for the source code, wherein the second keyword is used to indicate a location for embedding a test point in the source code of the target financial institution system; According to the second keyword, adjusting the tracking point information in the processed source code to obtain an adjusted source code; The target test case is determined according to the tracking point information in the adjusted source code.

8. A testing device for a financial institution system, characterized in that: include: A first determination unit, used to determine a target financial institution system to be tested and to determine financial service test requirements; A first processing unit is used to perform point tracking processing on the source code of the target financial institution system according to the financial business test requirements to obtain processed source code; A second determination unit is used to determine a target test case according to the embedded point information in the processed source code; The testing unit is used to test the target financial institution system with the embedded point information through the target test case to obtain the test result, wherein the test result is used to characterize whether the target financial institution system has risks.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored executable program, wherein when the executable program is executed, the device where the computer-readable storage medium is located is controlled to execute the testing method for the financial institution system according to any one of claims 1 to 7.

10. An electronic device, characterized in that: include: A memory storing an executable program; A processor is used to run the program, wherein the program, when running, executes the testing method of the financial institution system as claimed in any one of claims 1 to 7.

11. A computer program product comprising computer instructions, characterized in that: When the computer instructions are executed by a processor, the steps of the testing method of a financial institution system as claimed in any one of claims 1 to 7 are implemented.

Images