CN112241367B

CN112241367B - Data line testing method and device

Info

Publication number: CN112241367B
Application number: CN202011027111.3A
Authority: CN
Inventors: 薛潇; 杨有为; 夏晴; 王文娟; 林苇荞; 鲍明远; 于海; 刘庆文; 张同虎
Original assignee: CCB Finetech Co Ltd
Current assignee: CCB Finetech Co Ltd
Priority date: 2020-09-25
Filing date: 2020-09-25
Publication date: 2022-09-13
Anticipated expiration: 2040-09-25
Also published as: CN112241367A

Abstract

The invention discloses a data line testing method and a device, wherein the data line testing method comprises the following steps: analyzing downstream project group information corresponding to a report corresponding to the business demand based on the business demand, extracting data application demand and data integration demand based on the project group information, establishing a mapping relation between the data application demand and the data integration demand, and generating a test case corresponding to the report; the method comprises the steps of establishing a batch processing time point of test subject information and running approval supply number based on a test case, subscribing a data application requirement to be tested under the corresponding test subject information and running approval supply number to remind a supplier of a data integration requirement corresponding to the data application requirement to carry out supply approval, finishing supply approval confirmation based on supply reminding, loading data to a data warehouse, inquiring data reaching and data loading states, finishing the service requirement, and testing the test case based on the finished service requirement.

Description

Data line testing method and device

Technical Field

The invention relates to the technical field of computers, in particular to a large-scale data line testing method and device based on a transaction and data separation design background.

Background

In order to meet the requirements of business innovation and strategic transformation of banking business, a banking system starts the construction of a new generation of core system, a new generation of data line is used as one of the components of an IT architecture and is a general name of a system, a platform and an environment for supporting enterprise data management, management analysis and decision support, the overall construction target of the new generation of data line is to create values for operation, management and external supervision, change the current situations of lack, heavy, scattered, slow, frequent and poor management information and achieve the information application effects of 'full, province, credibility, quickness, easiness and goodness'.

Over the years of endeavor, data lines deliver a new generation of data application environments for my new generations, including: the application function of using data by a user is supported, and various data applications such as query, analysis, mining and the like are provided; an integration calculation area supporting data integration calculation is used for completing data integration of various systems such as new construction, reconstruction and reconstruction; and a public access area for users to access data is supported, and a unified data view is provided for service personnel to use the data.

In the new generation of data line construction process, the problems of numerous and complicated data receiving data of the data warehouse, low efficiency of the data exchange process, difficulty in testing and the like are also gradually generated along with the construction process of the new generation of data lines. The original test method mainly adopts the modes of data backup, migration conversion, report generation and two-way comparison. The process of production unloading, unified conversion and unified loading is required, the time consumption is huge, and uncertain factors in the process are extremely large. Usually, the report loaded by the test environment is a report two months ago. The processing requirements of the big data of the bank are difficult to meet in the aspects of business requirements and data timeliness. Data check cannot be performed quickly and accurately in the test process, and the production environment data problem is frequent.

Disclosure of Invention

In view of this, embodiments of the present invention provide a data line testing method and apparatus, which are based on a large-scale data line testing management tool under the background of transaction and data separation design, and solve the problems of slow data generation, poor data quality, more redundant data, poor test pertinence, no flow control, and the like, which are easily caused in the large-scale data testing process, mainly by establishing a corresponding relationship between an application requirement and a data interface, and by establishing a full link flow of data subscription, data generation, data provision, data processing, data checking, and application testing in a testing process. Through application requirement management, requirement subscription management, data checking management, supply loading management and other capabilities built in the management tool, a visual process is established at the key node, the data generation precision is improved, and the generation of the original data has pertinence and accuracy.

To achieve the above object, according to an aspect of an embodiment of the present invention, there is provided a data line testing method, including:

analyzing downstream project group information corresponding to a report corresponding to the business demand based on the business demand, extracting data application demand and data integration demand based on the project group information, establishing a mapping relation between the data application demand and the data integration demand, and generating a test case corresponding to the report;

establishing batch processing time points of test subject information and batch run supply number based on the test cases,

subscribing the data application requirement to be tested under the corresponding test subject information and the running approval supply number to remind the supplier of the data integration requirement corresponding to the data application requirement to carry out supply approval, finishing supply approval confirmation based on supply approval reminding,

loading data into a data warehouse, querying the data to reach a data loading state, completing the business requirements, and

and testing the test case based on the completed business requirement.

Optionally, the method further comprises receiving a business requirement, wherein the business requirement comprises a report to be verified.

Optionally, the data application requirements include: inquiring application requirements; newly adding and importing application requirements; application requirement modification, and application requirement deletion.

Optionally, the data application requirements are screened out by screening attribute information of the system to which the data application requirements belong, the cause group to which the data application requirements belong, the system number and the like.

Optionally, the data application requirements include at least one of a number, a name, a corresponding service function, a frequency, a format, an aging, a type, an inquiry deadline, a belonging mechanism, an implementation mode, whether to initialize a report, a proposing department, a proposing person, a target system english name, a production time, a corresponding post, and a corresponding menu.

Optionally, the data integration requirements include corresponding upstream project data exchange interfaces.

Optionally, the data integration requirement includes establishing a mapping relationship between a "report" and an "interface" according to the data integration requirement.

To achieve the above object, according to still another aspect of embodiments of the present invention, there is provided a data line testing apparatus.

The device for testing the data line is characterized by comprising the following components:

the demand service module analyzes downstream project group information corresponding to a report corresponding to the business demand based on the business demand, extracts data application demand and data integration demand based on the project group information, establishes a mapping relation between the data application demand and the data integration demand, and generates a test case corresponding to the report;

a batch processing service module which establishes batch processing time points of test subject information and batch run supply number based on the test cases,

a subscription and approval module which subscribes the data application requirement to be tested under the corresponding test subject information and the running approval supply number to remind the supplier of the data integration requirement corresponding to the data application requirement to carry out supply approval, and finishes supply approval confirmation based on supply reminding,

a status query module that loads data to a data warehouse, queries data to reach a data loading status, fulfills the business requirements, and

and the batch processing service module tests the test case based on the completed business requirement.

To achieve the above object, according to still another aspect of the embodiments of the present invention, there is provided an electronic device for data line testing.

An electronic device for data line testing according to an embodiment of the present invention includes: one or more processors; a storage device for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement a method for data line testing of an embodiment of the present invention.

To achieve the above object, according to still another aspect of embodiments of the present invention, there is provided a computer-readable storage medium.

A computer-readable storage medium of an embodiment of the present invention has stored thereon a computer program that, when executed by a processor, implements a method of data line testing of an embodiment of the present invention.

One embodiment of the above invention has the following advantages or benefits: through application requirement management, requirement subscription management, data checking management, supply loading management and other capabilities built in the management tool, a visual process is established at the key node, the data generation precision is improved, and the generation of the original data has pertinence and accuracy.

Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.

Drawings

The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:

FIG. 1 is a schematic diagram illustrating the main steps of a data line testing method according to an embodiment of the present invention;

FIG. 2 is a schematic diagram illustrating a data flow process of a data line testing method according to an embodiment of the present invention;

3A-3E are schematic diagrams of the functionality of various posts of data line testing according to embodiments of the present invention;

FIGS. 4A-4Q are block diagrams of components of a test system and corresponding modules that perform their functions according to embodiments of the present invention;

FIG. 5 is a schematic diagram of the main modules of a data line testing apparatus according to an embodiment of the present invention;

FIG. 6 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;

fig. 7 is a schematic block diagram of a computer system suitable for use in implementing a terminal device or server according to an embodiment of the present invention.

Detailed Description

Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

It should be noted that the embodiments of the present invention and the technical features of the embodiments may be combined with each other without conflict.

First, the technical terms of the present disclosure are as follows:

data line: based on the background of separating transaction and data of banks, a complete set of data is generated, transmitted to a data warehouse, processed to a data consumption component and generated into a report or index flow.

Data integration: the data with different sources, formats and characteristic properties are logically or physically organically concentrated and loaded in a unified way, and subsequent operations such as processing, analysis and the like are carried out.

Supply number: the upstream component provides data to the data warehouse in a batch processing mode, a unloading mode, an extracting mode and the like, or the data warehouse provides data to the downstream component after completing data processing through various processing modes.

An upstream component: a component system that generates source data. Typically a transaction-like component system.

A downstream component: the component system that needs data is typically a management analysis type component system.

Data migration: and (3) performing backup, migration and conversion of production data, processing the original system into data which can be adapted to the new system according to the processing logic of the new system, and loading the data into the new system.

Fig. 1 is a schematic diagram illustrating main steps of a data line testing method according to an embodiment of the present invention.

As shown in fig. 1, a data line testing method according to an embodiment of the present invention mainly includes the following steps:

step S101: analyzing downstream project group information corresponding to a report corresponding to the business demand based on the business demand, extracting data application demand and data integration demand based on the project group information, establishing a mapping relation between the data application demand and the data integration demand, and generating a test case corresponding to the report.

Step S102: and establishing batch processing time points of the test subject information and the batch running supply number based on the test cases.

Step S103: and subscribing the data application requirements to be tested under the corresponding test subject information and the running approval supply number so as to remind the supplier of the data integration requirements corresponding to the data application requirements to carry out supply number approval, and finishing supply number approval confirmation based on supply number reminding.

Step S104: and loading the data into a data warehouse, and inquiring whether the data reaches a data loading state to complete the service requirement.

Step S105: and testing the test case based on the completed business requirement.

The data line test system is described in detail below in conjunction with fig. 2-4N.

The data line testing system (also called as a management tool or a platform) comprises service modules such as demand service, batch processing service, subscription and approval service, state query service, warehouse synchronous data service, index statistical service, platform management and the like.

The upstream and downstream components and the data line test management personnel of each service group can perform the functions of requirement maintenance, data subscription, data examination and approval, supply state inquiry, various data line index statistics, test case downloading and the like on the data line test system. The test system covers various work contents of the current data line test implementation management service.

Referring first to FIG. 2, a process by which data is ultimately streamed downstream from production to streaming to the data warehouse pursuant to a data exchange interface is described. According to the current working situation of a data line separating bank transaction and data, each upstream component (such as a logic subsystem A, a logic subsystem B and a logic subsystem C in the figure 2) transmits the data to a data warehouse by issuing a data exchange interface. And the data warehouse processes, cleans, converts and enters a corresponding access area or a forwarding interface according to the received data. The data information is passed to a downstream utilization element (e.g., logic subsystem D) in various ways.

The workflow contents of the data line test system are described below according to different user roles.

Referring to FIG. 3A, there is depicted downstream duties that are the primary users of the data line test system. The target object is a downstream array component responsible person in the data line test system. The downstream application data post can perform application demand management of data, integrated demand query, demand mapping association of application demand and data integration, batch running plan, open batch application, synchronous data click-through and demand subscription, synchronous supply detail, warehouse supply detail, upstream supply detail, demand loading detail and other related functions through the data line test system.

Referring to FIG. 3B, there is depicted an upstream duty post, which is the primary user of the data line test system. The target object is an upstream supply component person in charge in the data line test system. The upstream use and use of the multi-job data can be realized through a test system of a data line, and related functions such as a run approval plan, synchronous warehouse approval, theme demand approval, batch demand approval, upstream supply detail, synchronous warehouse detail and the like can be realized.

Referring to fig. 3C, a warehouse supply post is depicted, which is the primary user of the data line testing system. The target object is an upstream supply component responsible person in the data line test. The post personnel can use related functions such as a run approval plan, synchronous warehouse approval, theme demand approval, batch demand approval, upstream supply number detail, synchronous warehouse detail and the like through a test system of a data line.

Referring to FIG. 3D, a utility group management post is depicted, which is the maintenance manager of the test system for the data line. The target object is a test and quality control contact person of each business group in the data line test. The post personnel can assist the project group contact persons to carry out various operations of upstream supply and downstream use of the work group through the test system of the data line. Meanwhile, latitude index information such as demand loading statistics, topic subscription statistics, batch subscription statistics, topic examination and approval statistics, batch examination and approval statistics, upstream supply statistics, warehouse supply statistics and the like can be consulted. User permission posts can be added to the contacts of the event group project group in the platform management module.

Referring to fig. 3E, a test center management post is depicted, which is the final manager of the test system for the data line. The target object is a contact person of a data line service team of a measurement and control center in data line testing. The post personnel can assist each role post to complete the use of all functions of the test system of the data line through the test system of the data line. Meanwhile, management operations such as test subject maintenance, batch running plan maintenance, subscription level, synchronous level maintenance, batch application auditing and the like can be performed on a test system of the data line.

Fig. 4A is a structural diagram of the data line test system of the present invention. The functions of the respective blocks of the data line test system are described in detail below based on fig. 4A.

Demand service module

The demand service is a core module of the data line test system and provides functions of adding, modifying and deleting data application demands, inquiring data integration demands, mapping and associating the data application demands with the data integration demands and the like.

The demand service module further comprises the following features:

1. application requirements management, the application requirements management further comprising: inquiring application requirements; newly adding and importing application requirements; application requirement modification and application requirement deletion.

1.1. Application demand query

Referring to fig. 4B, by screening attribute information of each item, such as the system to which the system belongs, the cause group to which the system belongs, the system number, and the like, the corresponding data application requirement can be screened out, and the related information can be referred. Meanwhile, a universal demand download function is provided.

1.2. Application demand adding and importing

Referring to fig. 4C, the data line testing system provides two modes of page addition and file import to add data application requirements. Meanwhile, a data application requirement import template can be downloaded in the page. The newly added data application requirement template is basically consistent with the data application requirement list submitted in the ITM. The application needs to fill in data, such as number, name, corresponding service function, frequency, format, timeliness, type, query deadline, affiliated mechanism, implementation mode, whether to initialize report forms, proposing department, proposing person, target system English name, production time, corresponding post and corresponding menu.

1.3. Application demand modification

Referring to FIG. 4D, the data line testing system provides data application requirement modification functionality. The modify function only supports editing on a page. All fields of the data application requirements may be modified in the page.

1.4. Application demand deletion

The data line test system provides a data application requirement deleting function. The deleted data application demand state is changed to "invalid". The deleted data application requirements may also be subsequently restored.

2. Integrated demand query

2.1. Data integration demand query

Referring to fig. 4E, the data line test system synchronizes the latest data integration requirements in real time from the ITM. As can be seen from fig. 4E, it provides the latest data integration requirement query service. The downstream system can be screened according to the integration requirement, and the screening can also be carried out according to other columns in the page. Meanwhile, a universal demand download function is provided.

2.2. Requirement mapping association

Data application requirements are associated with data integration requirements

The data transmission method aims to improve the data supply efficiency and ensure the data transmission coverage of the data lines. The data line testing system introduces a requirement mapping correlation operation. Downstream users can establish the mapping relation between the report and the interface according to the requirements. And establishing a mapping relation. The data subscription operation can be more conveniently carried out.

Referring to fig. 4F, the user may first click on 1 or more data application requirements, and the currently associated data integration requirements are automatically listed in the data integration requirements list below.

At this time, a new button may be clicked to add new association.

Referring to fig. 4G, in the new page, all data integration requirements proposed by the system are listed. The user can select 1 or more data integration requirements according to the needs. Upon selection, the associated button is clicked. The association is completed.

Batch processing service module

The batch service module provides an overall view of the data and data components. The project group can check the host batch processing arrangement and the supply arrangement in the module, and put forward and check the non-host batch processing requirement.

The functions of the module mainly include:

1. run batch plan view:

1.1. the batch plan view includes:

1.1.1. monthly run lot plan lookup

After clicking the batch running plan menu, the system automatically displays a calendar page, wherein the page comprises information of a host, open batch running business days, natural days, batch running time and the like of each environmental plan in the month;

1.1.2. detailed review of daily batches

Clicking a certain date in the calendar, popping up a query box, and displaying the detail condition of the current day batch. The method comprises the steps of testing subject, batch type, testing environment, batch state, business day, natural day, batch running plan information and the like of a corresponding batch;

1.1.3. detailed review of daily batches

Clicking a certain date in the calendar, popping up a query box, and displaying the detail condition of the current day batch. Including test subject, batch type, test environment, batch status, business day, natural day, run and batch plan information, etc. of the corresponding batch.

2. Open batch application

2.1. Batch application for new addition

The platform inherits the batch running plan of all the hosts and simultaneously adds the application function of the open platform batch. The downstream personnel using the plurality of posts can open a batch application menu again to newly add, review and propose a batch processing application.

When a new batch processing application is added, one or more batch processing time requirements may be filled in. And drawing up the batch components needing to be supplied. Meanwhile, the specific batch application should be filled in the test requirement profile column.

The personnel at the management post of the measurement and control center can carry out combination and adjustment according to the proposed batch processing requirements. Filling in the approval opinions. And increasing the batches. After the batch is added, the downstream users can perform operations such as demand subscription and the like.

2.2. Batch application modification

After the application is made, the user can modify the application before the user passes the audit and when the audit is not passed.

2.3. Batch application deletion

After the application is made, the user can pass the audit of the user on the management post. The application may be deleted.

2.4. Batch application review

The personnel at the management post of the measurement and control center can check the batch processing application provided by the user. During auditing, analysis should be performed according to applications proposed by downstream use numbers, and similar applications should be merged. The batch plan is rearranged. Feedback in the approval opinion.

3. Test topic maintenance

3.1. Test subject addition, modification, deletion

The test subject is maintained as the management function of the management post user of the measurement and control center. The test subject can be subjected to the operation of adding, deleting and modifying.

When the test theme is newly added, the information of the theme name, state, plan start, end time, examination and approval management and control party, subscription management and control party and the like should be filled.

3.2. Subscription level maintenance

3.2.1. Topic catalog maintenance

The subscription level maintenance is a module for maintaining the theme by the user of the monitoring center management post, and can establish a directory for the test theme. At the same time, the directory may be renamed and deleted.

3.2.2. Test lot maintenance

The module can also perform test batch addition and modification. Click the new and modified buttons. The information of the corresponding batch can be newly added/modified in the platform.

Meanwhile, the administrator should associate all the batches corresponding to the topics into corresponding directories according to the directories.

Third, subscription and approval module

The subscription approval module is the foundation of the test system of the data line. The users of the downstream use management post, the business group management post and the measurement and control center management post can subscribe the application requirements. The users of the upstream supply posts, the business group management posts and the measurement and control center management posts can carry out the examination and approval by subject and the examination and approval by batch of the subscription interface.

In particular, the inventor introduces a per-subject approval function in the test system of the data line, which can reduce the complexity and frequency of approval of the upstream system. After the examination and approval according to the theme, the follow-up different batches with the same test theme do not need to be repeatedly examined and approved. For individual unavailable interfaces. The users for several posts can easily screen out the interfaces in the batch approval. And carrying out operation of modifying the approval result.

The subscription approval module comprises the following functions:

1. demand subscription

1.1 subscribed information query

Referring to fig. 4H, in the requirement subscription function, the user should first select information such as a name of a downstream system that the user needs to subscribe to, a test topic where a subscribed batch is located, and a batch that the user needs to subscribe to. Upon selection, the system will list all data application requirements that have been currently subscribed to. After the data application requirements are selected, the data integration requirements which are subscribed currently are displayed.

1.2 subscription of addition, modification and deletion requirements

Referring to fig. 4H, click the "add" button of the data application requirement list, and may enter an add requirement subscription interface. The platform provides three subscription modes: subscribe on demand, subscribe on custom template, subscribe in batch, see fig. 4I. Wherein:

subscription on demand: the data exchange interface is subscribed according to the mapping relation between the data application requirement and the data exchange interface maintained by the user. This list lists all the data application requirements of the corresponding system. And after selection, finishing all the mapped interface subscriptions.

Subscribing according to batches: the user can copy the application requirements and the interface subscription results according to the contents subscribed in a certain batch under a certain test topic in history.

Subscribing according to a custom template: the user can make copy subscription according to a certain set of report/interface stored in history. The custom template can be stored according to the conditions of a certain batch of subscriptions, and can also be modified and established in a custom template maintenance page.

And after the application requirement addition is completed, displaying a subscribed data integration requirement list in the page. The data integration requirements can be increased or decreased on a manifest basis, see FIG. 4J.

1.3 saving custom templates

After the data application requirements and the data integration requirements of the batch of subscriptions are maintained, a user can click a [ save template ] button to input a template name and establish a data application requirement group to be saved as a self-defined template so as to facilitate the follow-up subscription and use.

When the template name is input, a new template name can be selected to be input, or the original old template can be covered.

2. Custom template maintenance

2.1. Custom template query

The data line testing system supports the operation of customizing the subscription template. The user can combine one or a group of data application requirements and specific data integration requirements into a custom template so as to be used when the subscription is required. After subscribing according to the custom template, modification of data application requirements and data integration requirements can be carried out on the basis of the template, and the template is continuously maintained.

2.2 adding, modifying and deleting custom templates

The page usage of the user-defined template for adding, modifying and deleting is basically the same as the operation of the subscription requirement. The user can subscribe in three modes. Meanwhile, the data application requirements and the data integration requirements can be subjected to the operations of adding and deleting. The template may also be renamed.

3. Subject approval

3.1. Batch approval

Referring to fig. 4K, the upstream provisioning component may filter the topic catalog to view the interface subscribed by the downstream component, and click the [ batch approval ] button for approval.

If the upstream approval is passed, the approval state can be modified to be 'source system pass', the contact person for supply number is selected, the approval opinions are filled, the date for supply number is planned, or the date for supply number reference and the date for supply number deviation are selected. If the switch is turned off, only the subject interface is approved, and if the subject interface needs to be approved, the interface needs to enter a 'batch approval' menu for approval according to the batch.

If the upstream approval fails, the approval status can be modified to [ source system reject ], and the rejection opinion is filled in, and all the lots under the topic directory are rejected. If the switch is turned off, the subject directory interface is only rejected, and if the interface needs to be approved, the interface needs to enter a 'batch approval' menu for approval according to the batch. The warehouse will not be supplied with the interface rejected by the source system.

Referring to fig. 4L, after the [ batch approval ] switch is turned on by default, that is, after the theme is approved, all the batches under the theme are automatically approved in the same state, and if the [ batch approval ] switch is turned off, only the theme interface is approved, and the batch interface is not approved, and the [ batch approval ] menu is required to be entered for approval according to the batch. If some interfaces of a certain batch need to be different from the states of other batches, the interfaces of the certain batch need to be individually entered into a [ batch approval ] menu to modify the states of the interfaces of the certain batch.

Further, the functions further include: and the functions of checking operation logs, inquiring original requirements, examining and approving details, downloading and the like are realized.

4. Batch approval

4.1. Batch approval

Referring to fig. 4M and 4N, the upstream provisioning component may filter topic directories and batches to see the interface of the downstream subscription, click the [ approve ] button approve interface.

If the upstream approval passes, the approval state can be modified to be the source system pass, a plan supply date is selected, or a supply date standard and a supply date deviation are selected, a supply contact person is filled in the approval opinion.

If the upstream approval fails, the approval state can be modified to be [ source system refusal ], and the supplied number contact person is selected to fill in refusal opinions. The warehouse will not be supplied with the interface rejected by the source system.

Further, the functions include: and the functions of checking operation logs, inquiring original requirements, examining and approving details, downloading and the like are realized.

State query module

The state query module provides query functions of information such as the number supply progress and the state and maintenance functions of application requirement loading conditions for the upstream number supply assembly, the downstream number utilization assembly and an administrator. The project group and the administrator can check the upstream component interface, the supply condition of the warehouse interface and the application requirement loading condition under the subject catalog batch in the module.

The functions of the module mainly include: the upstream supply detail (which comprises supply detail inquiry, supply real-time state inquiry, statistical information inquiry, supply state modification and the like); warehouse supply detail (which comprises supply detail inquiry and statistical information inquiry); demand load details (which include: demand load case maintenance), and the like.

Index statistical module

The index statistical module provides a multidimensional statistical view for the management post of the public institution and the management post of the measurement and control center. The administrator can check the statistics of demand loading, topic catalog approval, batch approval, upstream supply and warehouse supply in the module respectively.

Wherein, in statistics of 1) subject directory approval, 2) batch approval, 3) upstream supply, and 4) warehouse supply and demand loading, an administrator can screen the subject directory to check statistics of the upstream component approval condition, and can also download excel forms to check.

Platform management module

The platform management module provides management functions of the management post of the measurement and control center for platform system user maintenance, user authority maintenance, system maintenance, operation log viewing, mail log viewing, page access maintenance, test environment information maintenance and the like. In the functions, a measurement and control center administrator can add, modify and delete platform users and can download excel forms for viewing.

An example of a platform-based implementation using a platform to complete a full link is described below:

taking an example of a business test newly added in overseas banks, the specific use flow is as follows:

1. overseas users propose service requirement applications and a list of reports needing to be verified;

2. the monitoring center management post personnel analyze the downstream project group information corresponding to the report;

3. the downstream project group arranges data application requirements and data integration requirements (comprising corresponding upstream project data exchange interfaces). The method comprises the following modules of application requirement management, integrated requirement query, requirement mapping association and the like of a platform. Adding, importing and updating data application requirements and establishing a mapping relation between the application requirements and the integration requirements.

According to application requirements, a user directly imports the data into the platform in an attachment uploading or page new creation mode. The data integration requirement is directly acquired from the ITM platform of the existing bank through a data interface and is displayed on the platform. The platform designs functions that establish a mapping relationship between application requirements and integration requirements. Before subscribing application requirements, a user needs to use the function to complete the establishment of the mapping relation.

Referring to fig. 4O, taking an astener branch as an example, after the branch applies for testing environment testing due to service or new function requirement, the environment team of the testing environment will arrange a host batch processing plan. The corresponding test subject and the batch arrangement of the host are registered in the platform. The downstream application data item group can complete application requirement import and mapping relation establishment work of corresponding data application requirements (reports) through the platform. And completing data subscription under the corresponding topic and batch.

Referring to FIGS. 4P-4Q, the Suspen currency tests are illustrated. 1 data application requirement (associated mapping 17 data integration requirements) needs to be tested, which relates to 1 project group, and 3 batches are arranged in one test subject.

Meanwhile, overseas users and downstream project groups can complete compiling of test cases through a case automatic generation function. The automatic generation of cases is a sub-function in the application requirements management module. The block diagram is labeled "case download". The current functions are according to the application requirement name, the use frequency, the processing time, the inquiry post, the menu and the subscribed topic and the batch time in the application requirement. A set of test cases generated in accordance with a standard format for the test cases. Usually, one application requirement generates two test cases, one is a report format verification case, and the other is a data correctness verification case.

4. The measurement and control center management post is arranged according to the whole batch processing, and the whole batch processing is determined according to the whole batch processing plan of the whole row of test environments. The test environment team will issue a next-month host batch arrangement view at the end of each month according to the load of the hosts and the condition of the service test requirement.

Taking 8 months of 2020 as an example, the institute Asia/hong Kong division arranges a PL4 environment for a batch process each week during a 8-month test. After each batch, the relevant host and other open platform upstream project groups complete data transmission as required, and the warehouse completes data loading as required. The downstream project group receives the data and processes the application requirements. The batch processing requirement is provided by business personnel to a test environment team according to the test requirement at present. And is not directly related to the application requirements themselves. Through the functions of test subject maintenance, batch running planning, hierarchical maintenance and the like, batch processing time points of test subject information and batch running supply are established for the platform.

The downstream project group can also apply for newly adding and modifying batch processing requirements through an 'open batch application' function;

5. and the downstream project group subscribes the application requirements to be tested under the corresponding theme and batch by using a platform requirement subscription function. The system can remind an integrated demand supplier (upstream project group) corresponding to the demand to carry out supply examination and approval according to the subscribed application demand.

The upstream project group completes the approval confirmation of the supply number by using the functions of 'theme requirement approval' or 'batch requirement approval' and the like.

6. And completing the batch running according to the corresponding natural date in the test environment. The platform interfaces with the data warehouse for data arrival and data loading. The information such as the current batch, the upstream supply condition of the current theme, the warehouse loading condition, the application requirement processing completion condition and the like can be inquired through each inquiry function in the state inquiry module and the index statistical module.

7. The overseas user can acquire the query date, the time point and the completion condition of the application requirement by querying the information in the 6 th point. And testing the application requirements.

8. Overseas users complete the test using the test cases generated in article 3. And (5) providing a test report.

Fig. 5 is a schematic diagram of main blocks of a data line testing apparatus according to an embodiment of the present invention.

As shown in fig. 5, a data line testing apparatus 500 according to an embodiment of the present invention includes: a demand service module 501, a batch processing service module 502, a subscription and approval module 503 and a state query module 504; wherein the content of the first and second substances,

the requirement service module 501 is configured to analyze downstream project group information corresponding to a report corresponding to a business requirement based on the business requirement, extract a data application requirement and a data integration requirement based on the project group information, establish a mapping relationship between the data application requirement and the data integration requirement, and generate a test case corresponding to the report;

the batch processing service module 502 establishes batch processing time points of test subject information and batch running supply number based on the test cases;

the subscription and approval module 503 subscribes the data application requirement to be tested under the corresponding test subject information and the running approval supply number to remind the supplier of the data integration requirement corresponding to the data application requirement to carry out supply number approval, and completes supply number approval confirmation based on supply number reminding;

the status query module 504 loads data into a data warehouse, queries data to reach a data loading status, fulfills the business requirements, and

In an embodiment of the present invention, the requirement service module 501 receives a business requirement, where the business requirement includes a report to be verified.

In an embodiment of the present invention, the data application requirements in the requirements service module 501 include: inquiring application requirements; newly adding and importing application requirements; and modifying the application requirements and deleting the application requirements.

In an embodiment of the present invention, the data application requirement of the requirement service module 501 is obtained by screening attribute information of the system, the cause group, and the system number to which the data application requirement belongs.

In an embodiment of the present invention, the data application requirements include at least one of a number, a name, a corresponding service function, a frequency, a format, an aging, a type, a query deadline, an affiliated entity, an implementation mode, whether to initialize a report, a proposing department, a proposing person, a target system english name, a commissioning time, a corresponding post, and a corresponding menu.

According to the data line testing device provided by the embodiment of the invention, the data line testing device has the module functions of data application demand management, batch processing arrangement service, supply demand release, approval, supply state tracking, report loading tracking, test implementation support, case automatic generation and the like. According to data analysis statistics, after the data line testing device is used, the data subscription efficiency is improved by 450%, the approval efficiency is improved by 672%, and the supply efficiency is integrally improved by 126%.

Fig. 6 shows an exemplary system architecture 600 of a data line testing method or a large-scale data line testing apparatus to which embodiments of the present invention can be applied.

As shown in fig. 6, the system architecture 600 may include

terminal devices

601, 602, 603, a network 604, and a server 605. The network 604 serves to provide a medium for communication links between the

terminal devices

601, 602, 603 and the server 605. Network 604 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.

A user may use the

terminal devices

601, 602, 603 to interact with the server 605 via the network 604 to receive or send messages or the like. Various communication client applications, such as an internet banking application, a web browser application, a search application, an instant messaging tool, a mailbox client, social platform software, and the like, may be installed on the

terminal devices

601, 602, and 603.

The

terminal devices

601, 602, 603 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 605 may be a server that provides various services, such as a background management server that supports an online banking management-type website browsed by a user using the

terminal devices

601, 602, and 603. The background management server may analyze and perform other processing on the received data such as the product information query request, and feed back a processing result (e.g., target push information and product information) to the terminal device.

It should be noted that the data line testing method provided by the embodiment of the present invention is generally executed by the server 605, and accordingly, the account management apparatus is generally disposed in the server 605.

It should be understood that the number of terminal devices, networks, and servers in fig. 6 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Referring now to FIG. 7, shown is a block diagram of a computer system 700 suitable for use with a terminal device implementing embodiments of the present invention. The terminal device shown in fig. 7 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.

As shown in fig. 7, the computer system 700 includes a Central Processing Unit (CPU)701, which can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data necessary for the operation of the system 700 are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.

The following components are connected to the I/O interface 705: an input portion 706 including a keyboard, a mouse, and the like; an output section 707 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 708 including a hard disk and the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. A drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read out therefrom is mounted into the storage section 708 as necessary.

In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer-readable medium, the computer program comprising program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 709, and/or installed from the removable medium 711. The computer program performs the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 701.

It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures 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 the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor includes a first account creation module, a second account creation module, and a management module. The names of these modules do not in some cases form a limitation on the module itself, and for example, a management module may also be described as a "module that manages the first account and the second account".

As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise: acquiring a first account opening request, wherein the first account opening request indicates information of a first user; according to the first account opening request, a first account corresponding to the first user is established; acquiring a second account opening request, wherein the second account opening request indicates information of a second user; when the first user is determined to be associated with the second user according to the information of the second user and the information of the first user, creating a second account corresponding to the second account opening request, and constructing an association relationship between the second account and the first account; and managing the first account and the second account according to the association relationship.

According to the technical scheme of the embodiment of the invention, a first account corresponding to a first user is firstly created according to an account opening request of the first user, after a second account opening request of a second user is obtained, if the second user is determined to be associated with the first user, a second account corresponding to the second user is automatically created, the association relationship between the first account and the second account is established, and then the first account and the second account are managed according to the association relationship. Therefore, the account is established on line according to the information of the user without the need of the user to go to the off-line counter to open the account, so that the account establishing efficiency is improved, and the user experience is improved. And moreover, the associated accounts are managed in a unified manner, so that the management of multiple accounts is facilitated, and the account management efficiency is improved.

The above-described embodiments should not be construed as limiting the scope of the invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A data line testing method is characterized by comprising the following steps:

loading data into a data warehouse, and querying the data to reach a data loading state, fulfilling the business requirements, an

And testing the test case based on the completed business requirement.

2. The method of claim 1, further comprising:

and receiving a business requirement, wherein the business requirement comprises a report needing to be verified.

3. The method of claim 1, wherein the data application requirements comprise:

inquiring application requirements;

newly adding and importing application requirements;

application requirement modification, and

and deleting the application requirements.

4. The method of claim 1,

the data application requirements are screened out corresponding data application requirements by screening various attribute information such as the affiliated system, the affiliated business group, the system number and the like.

5. The method of claim 1,

the data application requirements comprise at least one of a number, a name, a corresponding service function, frequency, a format, timeliness, a type, a query deadline, a belonging mechanism, an implementation mode, whether to initialize a report, a proposing department, a proposing person, a target system English name, a production time, a corresponding post and a corresponding menu.

6. The method of claim 1,

the data integration requirements include corresponding upstream project data exchange interfaces.

7. The method of claim 1,

the data integration requirement comprises the step of establishing a mapping relation between a report and an interface according to the data integration requirement.

8. A data line testing device, comprising:

9. A data line test electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.

10. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-7.