A method, apparatus, electronic device, and storage medium for generating test tasks

Abstract

The present invention discloses a method, apparatus, electronic device and storage medium for generating test tasks, and the present invention relates to the technical field of big data. The method includes: synchronizing information of each exchange interface in each upstream system and information of each integration interface in each downstream system from a data interface management platform based on a timed synchronization task; determining newly submitted exchange interfaces according to the information of each exchange interface, determining newly submitted integration interfaces according to the information of each integration interface, and writing the information of the newly submitted exchange interfaces and the information of the newly submitted integration interfaces into a local data table; based on a timed analysis task, determining downstream systems affected by the newly submitted exchange interfaces according to the information of the newly submitted exchange interfaces in the local data table and the information of each integration interface; generating test tasks for the newly submitted exchange interfaces for the determined downstream systems. The technical solution of the present invention can achieve the technical effects of reducing communication costs and enabling comprehensive test coverage.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of big data technology, and in particular, to a test task generation method, device, electronic device, and storage medium. Background Art

[0002] With the improvement of the informatization level of enterprises, more and more business systems are used within enterprises. Therefore, there are complex business connection relationships between systems, and the mutual dependence of data between systems also causes mutual influence between systems.

[0003] The upstream system can provide the data in the upstream system data table to the downstream system through the exchange interface. The downstream system receives the data of the upstream system through the integration interface and writes the data into the downstream system data table. The change of an exchange interface of an upstream system affects which downstream systems. Currently, the impact analysis is entirely done manually, and then the cooperation modifications and test situations made by the affected downstream systems for the change are collected offline. Due to the large number of systems and frequent interface changes, a large amount of human resources are required. And the offline communication cost is high, and there may be situations where notifications are not in place or feedback is not timely, resulting in incomplete test coverage and thus causing operation defects. Summary of the Invention

[0004] Embodiments of the present invention provide a test task generation method, device, equipment, and storage medium to solve the problems of requiring a large amount of human resources and incomplete test scope caused by manually analyzing the downstream systems affected by the change of the exchange interface and manually notifying the relevant personnel of the downstream systems to perform tests for the change in the prior art.

[0005] In a first aspect, embodiments of the present invention provide a test task generation method, which includes:

[0006] Based on a timed synchronization task, synchronize the information of each exchange interface in each upstream system and the information of each integration interface in each downstream system from the data interface management platform;

[0007] Determine the newly submitted exchange interfaces according to the information of each exchange interface, determine the newly submitted integration interfaces according to the information of each integration interface, and write the information of the newly submitted exchange interfaces and the information of the newly submitted integration interfaces into the local data table;

[0008] Based on a timed analysis task, determine the downstream systems affected by the newly submitted exchange interfaces according to the information of the newly submitted exchange interfaces in the local data table and the information of each integration interface;

[0009] Generate a test task for the newly submitted exchange interfaces for the determined downstream systems.

[0010] In a second aspect, embodiments of the present invention further provide a test task generation device, which includes:

[0011] An information synchronization module, configured to synchronize the information of each exchange interface in each upstream system and the information of each integration interface in each downstream system from the data interface management platform based on a timed synchronization task;

[0012] An information writing module, configured to determine newly submitted exchange interfaces according to the information of each exchange interface, determine newly submitted integration interfaces according to the information of each integration interface, and write the information of the newly submitted exchange interfaces and the information of the newly submitted integration interfaces into a local data table;

[0013] A system determination module, configured to determine the downstream systems affected by the newly submitted exchange interfaces based on a timed analysis task according to the information of the newly submitted exchange interfaces in the local data table and the information of each integration interface;

[0014] A task generation module, configured to generate a test task for the newly submitted exchange interfaces for the determined downstream systems.

[0015] Thirdly, an embodiment of the present invention further provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, the test task generation method as described in any one of the embodiments of the present invention is implemented.

[0016] Fourthly, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, the test task generation method as described in any one of the embodiments of the present invention is implemented.

[0017] Fifthly, an embodiment of the present invention further provides a computer program product, including a computer program. When the computer program is executed by a processor, the test task generation method as described in any one of the embodiments of the present invention is implemented.

[0018] In the embodiment of the present invention, based on a timed synchronization task, the information of each exchange interface in each upstream system and the information of each integration interface in each downstream system are automatically synchronized, and newly submitted exchange interfaces and integration interfaces are further determined. Then, the determined newly submitted exchange interfaces and integration interfaces are written into a local data table, and based on a timed analysis task, the downstream systems affected by the newly submitted exchange interfaces are automatically determined, so as to generate a test task for the newly submitted exchange interfaces for the determined downstream systems. Compared with the prior art in which the downstream systems affected by the changes in the exchange interfaces are manually analyzed and the relevant personnel of the downstream systems are manually notified to perform tests on the changes, this solution automatically analyzes the downstream systems affected by the changes in the exchange interfaces based on a timed task and automatically generates test tasks for the affected downstream systems, which can greatly save the human resources required and effectively solve problems such as incomplete test scope caused by manually notifying personnel to perform tests. Description of the Drawings

[0019] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for the embodiments will be briefly introduced below. It should be understood that the following accompanying drawings only show some embodiments of the present invention and should not be regarded as limiting the scope. For those of ordinary skill in the art, without creative efforts, other related accompanying drawings can also be obtained based on these drawings.

[0020] Figure 1 It is a flowchart of a test task generation method provided in the embodiments of the present invention;

[0021] Figure 2 It is a schematic diagram of the data models of an upstream system and a downstream system provided in the embodiments of the present invention;

[0022] Figure 3 It is another flowchart of a test task generation method provided in the embodiments of the present invention;

[0023] Figure 4 It is yet another flowchart of a test task generation method provided in the embodiments of the present invention;

[0024] Figure 5 It is a schematic structural diagram of a test task generation device provided in the embodiments of the present invention;

[0025] Figure 6 It is a schematic structural diagram of an electronic device provided in the embodiments of the present invention. Specific Embodiments

[0026] The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It can be understood that the specific embodiments described herein are only used to explain the present invention and not to limit the present invention. Additionally, it should be noted that for the sake of description, only the parts related to the present invention rather than all the structures are shown in the accompanying drawings.

[0027] It should be noted that: Similar reference numerals and letters represent similar items in the following accompanying drawings. Therefore, once an item is defined in one accompanying drawing, it does not need to be further defined and explained in subsequent accompanying drawings. At the same time, in the description of the present invention, terms such as "first", "second", etc. are only used for distinguishing descriptions and cannot be understood as indicating or implying relative importance.

[0028] In addition, in the embodiments of the present invention, words such as "optional" or "exemplary" are used to give examples, illustrations or explanations. Any embodiment or design solution described as "optional" or "exemplary" in the embodiments of the present invention should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "optional" or "exemplary" is intended to present relevant concepts in a specific manner. The acquisition, storage, use, processing, etc. of data in the technical solutions of this application all comply with the relevant regulations of national laws and regulations.

[0029] Figure 1 FIG. 4 is a flowchart of a test task generation method provided in an embodiment of the present invention. The embodiments of the present invention are applicable to the situation of test task generation. This method can be applied to a data line full-process test platform. This method can be executed by a test task generation device, and this device can be implemented in a software and / or hardware manner. In a specific embodiment, this device can be integrated in an electronic device. Refer to Figure 1 , the method of the embodiment of the present invention specifically includes the following steps:

[0030] S110. Based on the timed synchronization task, synchronize the information of each switching interface in each upstream system and the information of each integration interface in each downstream system from the data interface management platform.

[0031] Among them, the timed synchronization task refers to a task for periodically synchronizing interface information from the data interface management platform; the data interface management platform provides an Application Programming Interface (API) interface for querying all data switching interfaces or integration interfaces, and is a system for managing switching interfaces and integration interfaces; the upstream system refers to a system that produces data, also known as the source system; the downstream system refers to a system that uses data, also known as the target system; the switching interface refers to an interface provided by the upstream system for data; the integration interface refers to an interface for the downstream system to receive data; the information of each switching interface in the upstream system includes: the upstream system identifier to which it belongs and the registered upstream data table identifier; the information of each integration interface in the downstream system includes: the associated upstream system identifier, the associated upstream data table identifier, the downstream system identifier to which it belongs, and the registered downstream data table identifier.

[0032] Specifically, based on the timed synchronization task, determine the interface information to be synchronized, and synchronize the upstream system identifier to which each switching interface in each upstream system belongs and the registered upstream data table identifier, as well as the associated upstream system identifier, the associated upstream data table identifier, the downstream system identifier to which each integration interface in each downstream system belongs, and the registered downstream data table identifier from the data interface management platform.

[0033] Exemplarily, there can be at least one upstream system and at least one downstream system. Figure 2It is a schematic diagram of the data model of an upstream system and a downstream system provided in an embodiment of the present invention. As Figure 2 shown, there are an upstream system A, downstream systems B, C, and D. Among them, there are n switching interfaces in the upstream system A, namely switching interface 1, switching interface 2, switching interface 3, …, switching interface n; there are n integration interfaces in the downstream system B, namely integration interface B1, integration interface B2, integration interface B3, …, integration interface Bn; there are n integration interfaces in the downstream system C, namely integration interface C1, integration interface C2, integration interface C3, …, integration interface Cn; there are n integration interfaces in the downstream system D, namely integration interface D1, integration interface D2, integration interface D3, …, integration interface Dn. Among them, switching interface 1 of the upstream system A corresponds to integration interface B1 of the downstream system B, integration interface C1 of the downstream system C, and integration interface D1 of the downstream system D; switching interface 2 of the upstream system A corresponds to integration interface B2 of the downstream system B and integration interface C2 of the downstream system C; switching interface 3 of the upstream system A corresponds to integration interface C3 of the downstream system C and integration interface D2 of the downstream system D.

[0034] The switching interface provides data to the corresponding integration interface. Specifically, the switching interface reads data from the registered upstream data table of the affiliated upstream system according to its affiliated upstream system identifier and registered upstream data table identifier, and provides the read data to the corresponding integration interface; the integration interface receives data from the corresponding switching interface. Specifically, the integration interface receives the data read from the affiliated upstream data table from the switching interface of the affiliated upstream system according to its associated upstream system identifier and associated upstream data table identifier, and saves the received data to the registered downstream data table of the affiliated downstream system according to its affiliated downstream system identifier and registered downstream data table identifier. It can be seen that the affiliated upstream system identifier of the switching interface is the same as the associated upstream system identifier of the integration interface corresponding to this switching interface, and the registered upstream data table identifier of the switching interface is the same as the associated upstream data table identifier of the integration interface corresponding to this switching interface.

[0035] S120. Determine the newly submitted switching interface according to the information of each switching interface, determine the newly submitted integration interface according to the information of each integration interface, and write the information of the newly submitted switching interface and the information of the newly submitted integration interface into the local data table.

[0036] Among them, the newly submitted switching interface refers to the switching interface without information records in the local data table, and the newly submitted integration interface refers to the integration interface without information records in the local data table. The local data table is a data table used to store the information of each switching interface and each integration interface in the data line full-process test platform.

[0037] Specifically, for each synchronized switching interface, after determining the upstream system identifier and registered upstream data table identifier to which the switching interface belongs, further determine whether there are the same upstream system identifier and registered upstream data table identifier in the local data table. If so, determine that the switching interface is not a newly submitted switching interface; if not, determine that the switching interface is a newly submitted switching interface. For each synchronized integration interface, after determining the associated upstream system identifier, associated upstream data table identifier, downstream system identifier to which it belongs, and registered downstream data table identifier of the integration interface, further determine whether there are the same associated upstream system identifier, associated upstream data table identifier, downstream system identifier to which it belongs, and registered downstream data table identifier in the local data table. If so, determine that the integration interface is not a newly submitted integration interface; if not, determine that the integration interface is a newly submitted integration interface, and write the information of the newly submitted switching interface and the information of the newly submitted integration interface into the local data table.

[0038] Exemplarily, if there are switching interfaces 1, 2, and 3 in the local data table, and there are also integration interfaces 1 corresponding to switching interface 1, integration interface 2 corresponding to switching interface 2, and integration interface 3 corresponding to switching interface 3; among them, the information of switching interface 1 is the upstream system identifier 1 it belongs to and the registered upstream data table identifier 1, and the information of integration interface 1 is the associated upstream system identifier 1, the associated upstream data table identifier 1, the downstream system identifier 1 it belongs to, and the registered downstream data table identifier 1; the information of switching interface 2 is the upstream system identifier 2 it belongs to and the registered upstream data table identifier 2, and the information of integration interface 2 is the associated upstream system identifier 2, the associated upstream data table identifier 2, the downstream system identifier 2 it belongs to, and the registered downstream data table identifier 2; the information of switching interface 3 is the upstream system identifier 3 it belongs to and the registered upstream data table identifier 3, and the information of integration interface 3 is the associated upstream system identifier 3, the associated upstream data table identifier 3, the downstream system identifier 3 it belongs to, and the registered downstream data table identifier 3; the information of each switching interface synchronized based on the timed synchronization task is: the upstream system identifier 1 it belongs to and the registered upstream data table identifier 1 of switching interface 1, the upstream system identifier 2 it belongs to and the registered upstream data table identifier 2 of switching interface 2, the upstream system identifier 3 it belongs to and the registered upstream data table identifier 3 of switching interface 3, and the upstream system identifier 4 it belongs to and the registered upstream data table identifier 4 of switching interface 4, and the information of each synchronized integration interface is: the associated upstream system identifier 1, the associated upstream data table identifier 1, the downstream system identifier 1 it belongs to, and the registered downstream data table identifier 1 of integration interface 1, the associated upstream system identifier 2, the associated upstream data table identifier 2, the downstream system identifier 2 it belongs to, and the registered downstream data table identifier 2 of integration interface 2, the associated upstream system identifier 3, the associated upstream data table identifier 3, the downstream system identifier 3 it belongs to, and the registered downstream data table identifier 3 of integration interface 3, and the associated upstream system identifier 4, the associated upstream data table identifier 4, the downstream system identifier 4 it belongs to, and the registered downstream data table identifier 4 of integration interface 4. Accordingly, it is determined that the upstream system identifier 4 it belongs to and the registered upstream data table identifier 4 of switching interface 4, as well as the associated upstream system identifier 4, the associated upstream data table identifier 4, the downstream system identifier 4 it belongs to, and the registered downstream data table identifier 4 of integration interface 4 are not included in the local data table. Further, it is determined that switching interface 4 is a newly submitted switching interface, and it is determined that integration interface 4 is a newly submitted integration interface, and the upstream system identifier 4 it belongs to and the registered upstream data table identifier 4 of switching interface 4, as well as the associated upstream system identifier 4, the associated upstream data table identifier 4, the downstream system identifier 4 it belongs to, and the registered downstream data table identifier 4 of integration interface 4 are written into the local data table.

[0039] S130. Based on the timed analysis task, determine the downstream systems affected by the newly submitted switching interfaces according to the information of the newly submitted switching interfaces and the information of each integration interface in the local data table.

[0040] Among them, the timed analysis task is a task that analyzes the information of the switching interface and the integration interface in the system at regular intervals.

[0041] Specifically, based on the timed analysis task, after writing the information of the newly submitted switching interface and the information of each integration interface into the local data table, read the upstream system identifier and the registered upstream data table identifier of the newly submitted switching interface and the associated upstream system identifiers, associated upstream data table identifiers, downstream system identifiers, and registered downstream data table identifiers of each integration interface from the local data table, determine the change types of the newly submitted switching interfaces read, and filter out the newly submitted switching interfaces with the change type being a preset type. The preset type may include "new field added", etc. Screen out the switching interfaces with the change types of "algorithm change", "data supply method change", "structure change", and "offline", and match the upstream system identifier and the registered upstream data table identifier of the screened newly submitted switching interfaces with the associated upstream system identifiers and associated upstream data table identifiers of each integration interface respectively; determine the integration interface that matches successfully as the integration interface corresponding to the newly submitted switching interface, and determine the downstream system to which the integration interface corresponding to the newly submitted switching interface belongs. After de-duplicating the determined downstream systems, determine the remaining downstream systems as the first batch of downstream systems affected by the newly submitted switching interface, and generate test tasks for the newly submitted switching interface for each of the first batch of downstream systems.

[0042] The first batch of downstream systems are the downstream systems directly affected by the newly submitted switching interface. The second batch of downstream systems indirectly affected by the newly submitted switching interface can be further analyzed. Specifically, determine the integration interface corresponding to the newly submitted switching interface as the current interface; determine whether there is a target switching interface with the registered upstream data table identifier being the same as the registered downstream data table identifier of the current interface. If so, determine the target integration interface corresponding to the target switching interface as the new current interface, and return to execute the operation of determining whether there is a target switching interface with the registered upstream data table identifier being the same as the registered downstream data table identifier of the current interface; otherwise, determine the downstream systems to which the current interfaces belong as the second batch of downstream systems affected by the newly submitted switching interface.

[0043] S140. Generate test tasks for the newly submitted switching interface for the determined downstream systems.

[0044] Specifically, if a test task for any newly submitted switching interface is generated for any downstream system, the test-related personnel of the downstream system need to test the newly submitted switching interface.

[0045] Based on the above embodiments, optionally, after generating a test task for the newly submitted exchange interface for the determined downstream system, the test task generation method further includes: notifying the test task to the data line tester of the determined downstream system; receiving and storing the feedback information of the data line tester.

[0046] Among them, the ways of notifying the test task include email prompts, voice prompts, etc., which are not limited in this embodiment; the feedback information includes the information that the test task needs to be tested and the test result, or the information that the test task does not need to be tested and the reason for not needing to be tested.

[0047] Specifically, the test task is notified to the data line tester of the determined downstream system by email or voice prompt. After notifying the test task to the data line tester of the determined downstream system, the information that the test task needs to be tested and the test result, or the information that the test task does not need to be tested and the reason for not needing to be tested are received and stored. The advantage of this setting is that the test task is notified to the tester in a timely manner and the feedback information of the tester is received, ensuring that the tester can understand the progress and result of the test task in a timely manner during the test task and guaranteeing the efficiency of the test task.

[0048] Further, after receiving the email, the person in charge of the data line test of the downstream system logs in to the data line full-process test platform to view the task information. The person in charge of the data line test can view the list of system integration interfaces affected by the exchange interface and view the impact report; when clicking to view the impact report, the data line full-process test platform starts to analyze the data item asset table and analyzes the data report of the physical table used by the integrated interface; by analyzing the affected data report, the person in charge of the data line test of the downstream system gives feedback on whether each test task needs to be tested. If it needs to be tested, the test result needs to be feedback; if it does not need to be tested, the reason for not needing to be tested needs to be feedback.

[0049] Based on the above embodiments, optionally, after notifying the test task to the data line tester of the determined downstream system, the test task generation method further includes: displaying the relevant information of the test task through the user interface; when detecting a first preset trigger operation, displaying the interface list; when detecting a second preset trigger operation for the displayed integrated interface, displaying the relevant information of the target report, so that the data line tester can determine whether the test task needs to be tested according to the relevant information of the target report.

[0050] Among them, the user interface is used for the user to interact with the system and display the relevant information of the test task to the user; the first preset trigger operation refers to trigger operations such as clicking and swiping, which are not limited in this embodiment. The first preset trigger operation is used to trigger the user interface so that the user interface displays the interface list after receiving the first preset trigger operation.

[0051] Among them, the interface list contains information about the integration interfaces corresponding to the exchange interfaces newly submitted in the downstream system. The second preset trigger operation refers to trigger operations such as clicking and swiping, which are not limited in this embodiment. The second preset trigger operation is used to trigger the user interface so that the user interface displays the information of the target report after receiving the first preset trigger operation; the target report is a report that generates report data using the registered downstream data tables of the displayed integration interfaces; the display work content of the first preset trigger operation and the second preset trigger operation is different. Both the first preset trigger operation and the second preset trigger operation are one-key test functions.

[0052] Specifically, after notifying the data line tester of the downstream system determined of the test task, the relevant information of the test task is displayed through the user interface; when the first preset trigger operation is detected, the interface list is displayed; when the second preset trigger operation for the displayed integration interface is detected, the relevant information of the target report is displayed, so that the data line tester can determine whether the test task needs to be tested according to the report that generates report data using the registered downstream data tables of the displayed integration interfaces. The advantage of such a setting is that through different preset trigger operations, the user interface displays different information to the user. The tester can view the list of integration interfaces in the downstream system affected by the exchange interface, improving the accuracy of the interface display and enhancing the usage experience of the tester.

[0053] Based on the above embodiment, optionally, after displaying the relevant information of the target report, the test task generation method further includes: when the third preset trigger operation for the displayed target report is detected, starting the report data generation job of the target report and displaying the execution status of the report data generation job, so that the data line tester can determine the test result of the test task according to the execution status.

[0054] Among them, the third preset trigger operation refers to trigger operations such as clicking and swiping, which are not limited in this embodiment. The third preset trigger operation is used to start the report data generation job of the target report and display the execution status of the report data generation job; the execution status includes execution success and execution failure.

[0055] Specifically, after the relevant information of the target report is displayed, when a third preset trigger operation for the displayed target report is detected, a report data generation job for the target report is started, and the execution status of the report data generation job is displayed. Through the displayed execution status of the report data generation job, the data line tester can determine the test result of the test task according to the execution status. The advantage of this setting is that the execution status of the report data generation job, whether it is executed successfully or failed, can be promptly displayed to the tester, clarifying the execution status and determining the test result.

[0056] Based on the above embodiment, optionally, after receiving and storing the feedback information of the data line tester, the test task generation method further includes: sending the feedback information to the data interface management platform, so that the data interface management platform determines whether to perform a release operation on the newly submitted exchange interface according to the feedback information.

[0057] Specifically, after receiving and storing the feedback information of the data line tester, the feedback information such as the information that the test task needs to test and the test result, or the information that the test task does not need to test and the reason for not needing to test is sent to the data interface management platform, so that the data interface management platform determines whether the newly submitted exchange interface is usable or unusable according to the feedback information. Specifically, if all downstream systems feedback that the test result is successful or all feedback that the test task does not need to be tested, it is determined that the newly submitted exchange interface is usable; otherwise, it is determined that the newly submitted exchange interface is unusable. If it is determined that the newly submitted exchange interface is usable, a release operation is performed on the newly submitted exchange interface; if it is determined that the newly submitted exchange interface is unusable, a release operation is not performed on the newly submitted exchange interface. The advantage of this setting is that before releasing the newly submitted exchange interface, it is determined whether the newly submitted exchange interface is usable or unusable, and then a release operation is performed on the newly submitted exchange interface, improving the work efficiency of the tester.

[0058] Based on the above embodiment, optionally, when a selection operation of the online batch in the exchange interface impact analysis page is detected, a test situation summary table of the exchange interface of the selected online batch is displayed, and a notification operation is performed on the downstream systems that have not feedback the test situation.

[0059] Among them, the online batch specifically refers to the submission time; the summary table is used to feedback the specific situation of the test.

[0060] Specifically, when a selection operation on the online batch in the swap interface impact analysis page is detected, a summary table of the test conditions of the swap interfaces of the selected online batch is displayed, and a notification operation is performed on the downstream systems that have not provided feedback on the test conditions. The advantage of this setting is that the testers can be promptly notified of the downstream systems that have not provided feedback on the test conditions, enabling them to accurately understand the test situation.

[0061] Exemplarily, Table 1 is a summary table of a test situation. As shown in Table 1, when a selection operation on the online batch in the swap interface impact analysis page is detected, the summary table includes information such as the target interface name, whether testing is required, and verification test feedback.

[0062] Table 1

[0063] Submission Time Target Interface Name Whether Testing is Required Verification Test Feedback Remarks 20XX-03-06 T000_XXX Yes Tested 20XX-03-06 T000_XXX No Not Applicable 20XX-03-06 T000_XXX Yes Not Applicable 20XX-03-06 T000_XXX

[0064] In the embodiment of the present invention, based on the timed synchronization task, the information of each swap interface in each upstream system and the information of each integration interface in each downstream system are automatically synchronized. Further, the newly submitted swap interfaces and integration interfaces are determined, and then the determined newly submitted swap interfaces and integration interfaces are written into the local data table. Based on the timed analysis task, the downstream systems affected by the newly submitted swap interfaces are automatically determined, so as to generate test tasks for the newly submitted swap interfaces for the determined downstream systems. Compared with the prior art in which the downstream systems affected by the changes in the swap interfaces are manually analyzed and the relevant personnel of the downstream systems are manually notified to perform tests for the changes, this solution automatically analyzes the downstream systems affected by the changes in the swap interfaces based on the timed task and automatically generates test tasks for the affected downstream systems, which can greatly save the human resources required and effectively solve problems such as incomplete test scope caused by manually notifying personnel to perform tests.

[0065] Figure 3 Another flowchart of a test task generation method provided in the embodiment of the present invention. On the basis of the above embodiment, the newly submitted swap interfaces are determined according to the information of each swap interface, the newly submitted integration interfaces are determined according to the information of each integration interface, and the information of the newly submitted swap interfaces and the information of the newly submitted integration interfaces are written into the local data table; according to the information of the newly submitted swap interfaces in the local data table and the information of each integration interface, the downstream systems affected by the newly submitted swap interfaces are further optimized. The embodiment of the present invention is applicable to the test task generation situation. This method can be executed by a test task generation device, and the device can be implemented in software and / or hardware. In a specific embodiment, the device can be integrated in an electronic device. Refer to Figure 3 , the method of the embodiment of the present invention specifically includes the following steps:

[0066] S301. Synchronize the information of each switching interface in each upstream system and the information of each integration interface in each downstream system from the data interface management platform based on the timed synchronization task.

[0067] Specifically, based on the timed synchronization task, determine the interface information to be synchronized, and synchronize the upstream system identification and registered upstream data table identification of each switching interface in each upstream system, as well as the associated upstream system identification, associated upstream data table identification, downstream system identification, and registered downstream data table identification of each integration interface in each downstream system from the data interface management platform.

[0068] S302. Write the information of each switching interface and the information of each integration interface into a temporary table.

[0069] Among them, the temporary table is used to temporarily record and store the information of each switching interface and the information of each integration interface.

[0070] Specifically, after synchronizing the information of each switching interface in each upstream system and the information of each integration interface in each downstream system from the data interface management platform, temporarily record and store the information of each switching interface and the information of each integration interface in the temporary table.

[0071] S303. For each switching interface in the temporary table, determine whether the local data table contains a switching interface that is the same as the current switching interface according to the information of the current switching interface.

[0072] Among them, the information of each switching interface includes: upstream system identification and registered upstream data table identification.

[0073] Specifically, for each switching interface recorded and stored in the temporary table, compare the upstream system identification and registered upstream data table identification of the current switching interface with the upstream system identification and registered upstream data table identification of each switching interface in the local data table to determine whether the local data table contains a switching interface whose corresponding upstream system identification and registered upstream data table identification are the same as those of the current switching interface. If so, the local data table contains a switching interface that is the same as the current switching interface, determine that the current switching interface exists in the local data table and no addition is required, and execute S304; if not, the local data table does not contain a switching interface that is the same as the current switching interface, determine that the current switching interface is a newly submitted switching interface, write the information of the newly submitted switching interface into the local data table, and execute S305.

[0074] Exemplarily, if the switching interfaces in the temporary table include switching interface 1 and switching interface 2, the identified upstream system of switching interface 1 is the identified upstream system 1, the registered upstream data table identifier is the registered upstream data table identifier 1, the identified upstream system of switching interface 2 is the identified upstream system 2, and the registered upstream data table identifier is the registered upstream data table identifier 2; the local data table contains the identified upstream system 1 and the registered upstream data table identifier 1 corresponding to switching interface 1, and also contains the identified upstream system 2 and the registered upstream data table identifier 2 corresponding to switching interface 2. Therefore, it is determined that switching interface 1 and switching interface 2 exist in the local data table and no addition is required, and S304 is executed. If the switching interfaces in the temporary table further include switching interface 3, the identified upstream system of switching interface 3 is the identified upstream system 3, the registered upstream data table identifier is the registered upstream data table identifier 3, and the local data table does not contain the identified upstream system 3 and the registered upstream data table identifier 3 corresponding to switching interface 3. Therefore, switching interface 3 does not exist in the local data table, it is determined that switching interface 3 is a newly submitted switching interface, and the information of the newly submitted switching interface is written into the local data table, and S305 is executed.

[0075] S304. Determine that the current switching interface exists in the local data table and no addition is required.

[0076] S305. Determine that the current switching interface is a newly submitted switching interface, and write the information of the newly submitted switching interface into the local data table.

[0077] S306. For each integration interface in the temporary table, determine whether the local data table contains an integration interface identical to the current integration interface according to the information of the current integration interface.

[0078] Among them, the information of each integration interface includes the associated upstream system identifier, the associated upstream data table identifier, the identified downstream system identifier, and the registered downstream data table identifier.

[0079] Specifically, for each integration interface whose record is stored in the temporary table, compare the associated upstream system identifier, associated upstream data table identifier, affiliated downstream system identifier, and registered downstream data table identifier of the current integration interface with those of each integration interface in the local data table to determine whether the local data table contains an integration interface whose associated upstream system identifier, associated upstream data table identifier, affiliated downstream system identifier, and registered downstream data table identifier are the same as those of the current integration interface. If so, it is determined that the current integration interface exists in the local data table and no addition is required, then execute S307; if not, it is determined that the current integration interface is a newly submitted integration interface, and write the information of the newly submitted integration interface into the local data table, then execute S308.

[0080] Exemplarily, if the integration interfaces in the temporary table include Integration Interface 1 and Integration Interface 2, the associated upstream system identifier of Integration Interface 1 is Associated Upstream System Identifier 1, the associated upstream data table identifier is Associated Upstream Data Table Identifier 1, the affiliated downstream system identifier is Affiliated Downstream System Identifier 2, the associated upstream system identifier of Integration Interface 2 is Associated Upstream System Identifier 2, the associated upstream data table identifier is Associated Upstream Data Table Identifier 2, and the affiliated downstream system identifier is Affiliated Downstream System Identifier 2; the local data table contains the associated upstream system identifier 1, associated upstream data table identifier 1, affiliated downstream system identifier 1, and registered downstream data table identifier 1 corresponding to Integration Interface 1, and also contains the associated upstream system identifier 2, associated upstream data table identifier 2, affiliated downstream system identifier 2, and registered downstream data table identifier 2 corresponding to Integration Interface 2. Therefore, it is determined that Integration Interface 1 and Integration Interface 2 exist in the local data table and no addition is required, then execute S307. If the integration interfaces in the temporary table further include Integration Interface 3, the associated upstream system identifier of Integration Interface 3 is Associated Upstream System Identifier 3, the associated upstream data table identifier is Associated Upstream Data Table Identifier 3, the affiliated downstream system identifier is Affiliated Downstream System Identifier 3, and the local data table does not contain the associated upstream system identifier 3, associated upstream data table identifier 3, affiliated downstream system identifier 3, and registered downstream data table identifier 3 corresponding to Integration Interface 3. Therefore, Integration Interface 3 does not exist in the local data table. It is determined that Integration Interface 3 is a newly submitted integration interface, and write the information of the newly submitted integration interface into the local data table, then execute S308.

[0081] S307. Determine that the current integration interface exists in the local data table and no addition is required.

[0082] S308. Determine that the current integration interface is a newly submitted integration interface, and write the information of the newly submitted integration interface into the local data table.

[0083] Further, S303 - S305 and S306 - S308 can be executed synchronously without a sequence.

[0084] S309. Based on the timing analysis task, read the information of the newly submitted exchange interfaces and the information of each integration interface from the local data table.

[0085] Specifically, after writing the information of the newly submitted exchange interfaces into the local data table, based on the timing analysis task, read the information of the newly submitted exchange interfaces and the information of each integration interface from the local data table.

[0086] S310. Determine the change types of each newly submitted exchange interface read, and filter out the newly submitted exchange interfaces whose change types are the preset types.

[0087] Among them, the change types include algorithm change, data supply method change, structure change, offline, etc., which are not limited in this embodiment. The preset type is the change type of the exchange interface determined in advance.

[0088] Specifically, determine which change type the change type of each newly submitted exchange interface read is, and filter out the newly submitted exchange interfaces whose change types are the preset types.

[0089] Exemplarily, if the preset type is algorithm change, when the change type of the newly submitted exchange interface 1 read is data supply method change, it is determined that the change type of the newly submitted exchange interface 1 does not belong to the preset type, and thus does not need to be filtered; if the preset type is algorithm change, when the change type of the newly submitted exchange interface 1 read is algorithm change, it is determined that the change type of the newly submitted exchange interface 1 is the preset type, and thus the newly submitted exchange interface is filtered out.

[0090] S311. Match the upstream system identifier and the registered upstream data table identifier of the newly submitted exchange interface with the associated upstream system identifier and the associated upstream data table identifier of each integration interface respectively.

[0091] Specifically, match the upstream system identifier of the newly submitted exchange interface with the associated upstream system identifier of each integration interface, and match the registered upstream data table identifier of the newly submitted exchange interface with the associated upstream data table identifier of each integration interface.

[0092] S312. Determine the integration interface that matches successfully as the integration interface corresponding to the newly submitted exchange interface, and determine the downstream system to which the integration interface corresponding to the newly submitted exchange interface belongs as the downstream system affected by the newly submitted exchange interface.

[0093] Specifically, determine the successfully matched integration interface as the integration interface corresponding to the newly submitted exchange interface. If the integration interface has a downstream system, determine the downstream system to which the integration interface corresponding to the newly submitted exchange interface belongs as the downstream system affected by the newly submitted exchange interface.

[0094] S313. Generate a test task for the newly submitted exchange interface for the determined downstream system.

[0095] Specifically, after determining the downstream system affected by the newly submitted exchange interface, generate a test task for the newly submitted exchange interface for the determined downstream system.

[0096] In the embodiment of the present invention, the information of each exchange interface and the information of each integration interface are written into a temporary table. For each exchange interface in the temporary table, determine whether the local data table contains an exchange interface identical to the current exchange interface according to the information of the current exchange interface. Based on a timed analysis task, read the information of the newly submitted exchange interface and the information of each integration interface from the local data table. Determine the change type of each newly submitted exchange interface read, and filter out the newly submitted exchange interfaces whose change type is a preset type. Determine the successfully matched integration interface as the integration interface corresponding to the newly submitted exchange interface, and determine the downstream system to which the integration interface corresponding to the newly submitted exchange interface belongs as the downstream system affected by the newly submitted exchange interface, so as to generate a test task for the newly submitted exchange interface for the determined downstream system, achieving the technical effects of timely feedback and notification and comprehensive test scope, improving the test experience of testers and the efficiency of the test process.

[0097] Figure 4 This is another flowchart of a test task generation method provided in the embodiment of the present invention. Based on the above embodiment, the determination of the downstream system affected by the newly submitted exchange interface according to the information of the newly submitted exchange interface and the information of each integration interface in the local data table is further optimized. The embodiment of the present invention is applicable to the test task generation scenario. This method can be executed by a test task generation device, and the device can be implemented in software and / or hardware. In a specific embodiment, the device can be integrated in an electronic device. Refer to Figure 4 , the method of the embodiment of the present invention specifically includes the following steps:

[0098] S410. Based on a timed synchronization task, synchronize the information of each exchange interface in each upstream system and the information of each integration interface in each downstream system from the data interface management platform.

[0099] Specifically, based on the timing synchronization task, determine the interface information to be synchronized, and synchronize the upstream system identification and registered upstream data table identification of each exchange interface in each upstream system, as well as the associated upstream system identification, associated upstream data table identification, downstream system identification, and registered downstream data table identification of each integration interface in each downstream system, from the data interface management platform.

[0100] S420. Determine the newly submitted exchange interfaces based on the information of each exchange interface, determine the newly submitted integration interfaces based on the information of each integration interface, and write the information of the newly submitted exchange interfaces and the information of the newly submitted integration interfaces into the local data table.

[0101] S430. Based on the timing analysis task, read the information of the newly submitted exchange interfaces and the information of each integration interface from the local data table; match the upstream system identification and registered upstream data table identification of the newly submitted exchange interfaces with the associated upstream system identification and associated upstream data table identification of each integration interface respectively; determine the integration interfaces with successful matches as the integration interfaces corresponding to the newly submitted exchange interfaces, and determine the integration interfaces corresponding to the newly submitted exchange interfaces as the current interfaces.

[0102] S440. Determine whether there is a target exchange interface whose registered upstream data table identification is the same as the registered downstream data table identification of the current interface.

[0103] Specifically, in the local data table, determine whether there is a target exchange interface whose registered upstream data table identification is the same as the registered downstream data table identification of the current interface. If there is, execute S450; if not, execute S460.

[0104] S450. Determine the target integration interface corresponding to the target exchange interface as the new current interface.

[0105] Specifically, after determining that there is a target exchange interface whose registered upstream data table identification is the same as the registered downstream data table identification of the current interface, determine the target integration interface corresponding to the target exchange interface as the new current interface, and return to execute S440 to determine whether there is a target exchange interface whose registered upstream data table identification is the same as the registered downstream data table identification of the current interface.

[0106] S460. Determine the downstream systems to which each current interface belongs as the downstream systems affected by the newly submitted exchange interfaces.

[0107] Specifically, determine the downstream systems to which each current interface determined in this process belongs as the downstream systems affected by the newly submitted exchange interfaces.

[0108] For example, in S430, it is determined that the newly submitted switching interface 1 corresponds to the integration interface 1, and the integration interface 1 is taken as the current interface. It is determined that there is a target switching interface 2 in the local data table whose registered upstream data table identifier is the same as the registered downstream data table identifier of the current interface (integration interface 1), and the target switching interface 2 corresponds to the target integration interface 2. Then, the target integration interface 2 is determined as the new current interface. Further, it is determined that there is a target switching interface 3 in the local data table whose registered upstream data table identifier is the same as the registered downstream data table identifier of the current interface (target integration interface 2), and the target switching interface 3 corresponds to the target integration interface 3. Then, the target integration interface 3 is determined as the new current interface. It is determined that there is no target switching interface in the local data table whose registered upstream data table identifier is the same as the registered downstream data table identifier of the current interface (target integration interface 3). At this time, the downstream systems (including downstream system 1, downstream system 2, and downstream system 3) to which the determined current interfaces (including integration interface 1, target integration interface 2, and target integration interface 3) belong are determined as the downstream systems affected by the newly submitted switching interface 1.

[0109] S470. Generate a test task for the newly submitted switching interface for the determined downstream systems.

[0110] Specifically, after determining the downstream systems affected by the newly submitted switching interface, generate a test task for the newly submitted switching interface for each of the determined downstream systems respectively.

[0111] Continuing with the above example, generate a test task for the newly submitted switching interface 1 for downstream system 1, generate a test task for the newly submitted switching interface 1 for downstream system 2, and generate a test task for the newly submitted switching interface 1 for downstream system 3.

[0112] In the embodiment of the present invention, not only the downstream systems to which the integration interface corresponding to the newly submitted switching interface belongs, that is, the downstream systems directly affected by the newly submitted switching interface, are determined as the downstream systems affected by the newly submitted switching interface, but also the downstream systems indirectly affected by the newly submitted switching interface, that is, the downstream systems to which the target integration interface corresponding to the target switching interface whose registered upstream data table identifier is the same as the registered downstream data table identifier of the current interface belongs, are determined as the downstream systems affected by the newly submitted switching interface. Thus, the downstream systems affected by the newly submitted switching interface can be analyzed more comprehensively. Generating test tasks for the newly submitted switching interface for these downstream systems respectively can achieve the technical effect of more comprehensive test coverage.

[0113] Figure 5 It is a schematic structural diagram of a test task generation device provided in the embodiment of the present invention, as Figure 5As shown in the figure, the test task generation device includes an information synchronization module 510, an information writing module 520, a system determination module 530, and a task generation module 540. Among them,

[0114] The information synchronization module 510 is used to synchronize the information of each exchange interface in each upstream system and the information of each integration interface in each downstream system from the data interface management platform based on the timed synchronization task.

[0115] The information writing module 520 is used to determine the newly submitted exchange interfaces according to the information of each exchange interface, determine the newly submitted integration interfaces according to the information of each integration interface, and write the information of the newly submitted exchange interfaces and the information of the newly submitted integration interfaces into the local data table.

[0116] The system determination module 530 is used to determine the downstream systems affected by the newly submitted exchange interfaces based on the timed analysis task according to the information of the newly submitted exchange interfaces in the local data table and the information of each integration interface.

[0117] The task generation module 540 is used to generate test tasks for the newly submitted exchange interfaces for the determined downstream systems.

[0118] Optionally, the information writing module 520 is specifically used to: write the information of each exchange interface and the information of each integration interface into a temporary table; for each exchange interface in the temporary table, determine whether the local data table contains an exchange interface identical to the current exchange interface according to the information of the current exchange interface. If not, determine the current exchange interface as the newly submitted exchange interface and write the information of the newly submitted exchange interface into the local data table; for each integration interface in the temporary table, determine whether the local data table contains an integration interface identical to the current integration interface according to the information of the current integration interface. If not, determine the current integration interface as the newly submitted integration interface and write the information of the newly submitted integration interface into the local data table.

[0119] Optionally, the information of each exchange interface includes: the upstream system identifier to which it belongs and the registered upstream data table identifier; the information of each integration interface includes: the associated upstream system identifier, the associated upstream data table identifier, and the downstream system identifier to which it belongs.

[0120] Optionally, the system determination module 530 is specifically used to: read the information of the newly submitted exchange interfaces and the information of each integration interface from the local data table; match the upstream system identifier to which the newly submitted exchange interface belongs and the registered upstream data table identifier with the associated upstream system identifier and the associated upstream data table identifier of each integration interface respectively; determine the integration interface with a successful match as the integration interface corresponding to the newly submitted exchange interface, and determine the downstream system to which the integration interface corresponding to the newly submitted exchange interface belongs as the downstream system affected by the newly submitted exchange interface.

[0121] Optionally, the information of each integration interface further includes: a registered downstream data table identifier.

[0122] Optionally, the system determination module 530 is specifically configured to: determine the integration interface corresponding to the newly submitted exchange interface as the current interface; determine whether there is a target exchange interface whose registered upstream data table identifier is the same as the registered downstream data table identifier of the current interface. If so, determine the target integration interface corresponding to the target exchange interface as the new current interface, and return to perform the operation of determining whether there is a target exchange interface whose registered upstream data table identifier is the same as the registered downstream data table identifier of the current interface; otherwise, determine the downstream systems to which the current interfaces belong as the downstream systems affected by the newly submitted exchange interface.

[0123] Optionally, the system determination module 530 is further configured to: determine the change types of the newly submitted exchange interfaces read, and filter out the newly submitted exchange interfaces whose change types are preset types.

[0124] Optionally, the device further includes: an information receiving module, configured to notify the data line testers of the downstream systems determined of the test tasks; receive and store the feedback information of the data line testers; wherein the feedback information includes the information to be tested and the test results of the test tasks, or the information that the test tasks do not need to be tested and the reasons for not needing to be tested.

[0125] Optionally, the device further includes: an information display module, configured to display the relevant information of the test tasks through a user interface; display the interface list when detecting a first preset trigger operation; wherein the interface list contains the information of the integration interfaces corresponding to the newly submitted exchange interfaces in the downstream systems; display the relevant information of the target report when detecting a second preset trigger operation for the displayed integration interface, so that the data line testers can determine whether the test tasks need to be tested according to the relevant information of the target report; wherein the target report is a report that generates report data using the registered downstream data tables of the displayed integration interfaces.

[0126] Optionally, the device further includes: a test result determination module, configured to start the report data generation job of the target report and display the execution status of the report data generation job when detecting a third preset trigger operation for the displayed target report, so that the data line testers can determine the test results of the test tasks according to the execution status.

[0127] Optionally, the device further includes: a data sending module, configured to send the feedback information to the data interface management platform, so that the data interface management platform determines whether to perform a release operation on the newly submitted exchange interface according to the feedback information.

[0128] Optionally, the device further includes a test situation notification module, configured to display a summary table of the test situations of the switching interfaces of the selected online batch when detecting a selection operation on the online batch in the switching interface impact analysis page, and perform a notification operation on the downstream systems that have not provided feedback on the test situations.

[0129] The test task generation device provided by the embodiments of the present invention can execute the test task generation method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0130] Figure 6 It is a schematic structural diagram of an electronic device provided in the embodiments of the present invention. Figure 6 It shows a block diagram of an exemplary electronic device 12 suitable for implementing the embodiments of the present invention. Figure 6 The shown electronic device 12 is only an example and should not impose any limitation on the functions and usage scope of the embodiments of the present invention.

[0131] As Figure 6 shown, the electronic device 12 is presented in the form of a general-purpose computing device. The components of the electronic device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 connecting different system components (including the system memory 28 and the processing unit 16).

[0132] The bus 18 represents one or more of several types of bus architectures, including a memory bus or a memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the multiple bus architectures. For example, these architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a MicroChannel Architecture (MCA) bus, an Enhanced Industry Standard Architecture (ISA) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.

[0133] The electronic device 12 typically includes a variety of computer system-readable media. These media can be any available media accessible by the electronic device 12, including volatile and non-volatile media, removable and non-removable media.

[0134] System memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. The electronic device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 34 can be used for reading and writing on non-removable, non-volatile magnetic media ( Figure 6 not shown, commonly referred to as a "hard disk drive"). Although Figure 6 not shown in, a disk drive for reading and writing on removable non-volatile disks (such as "floppy disks") and an optical disk drive for reading and writing on removable non-volatile optical disks (such as compact disc read-only memory (CD-ROM) or other optical media) may be provided. In these cases, each drive may be connected to the bus 18 through one or more data media interfaces. The memory 28 may include at least one program product having a set (such as at least one) of program modules configured to perform the functions of the embodiments of the present invention.

[0135] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in the memory 28. Such program modules 42 include - but are not limited to - an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. The program modules 42 generally perform the functions and / or methods in the embodiments described in the present invention.

[0136] The electronic device 12 may also communicate with one or more external devices 14 (such as a keyboard, a pointing device, a display 24, etc.), and may also communicate with one or more devices that enable a user to interact with the electronic device 12, and / or communicate with any device that enables the electronic device 12 to communicate with one or more other computing devices (such as a network card, a modem, etc.). Such communication may be carried out through an input / output (I / O) interface 22. Additionally, in this embodiment of the electronic device 12, the display 24 does not exist as an independent entity but is embedded in the mirror. When the display surface of the display 24 is not being displayed, the display surface of the display 24 visually merges with the mirror surface. And, the electronic device 12 may also communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through a network adapter 20. As shown in the figure, the network adapter 20 communicates with other modules of the electronic device 12 through the bus 18. It should be understood that althoughFigure 6 which is not shown in the figure. Other hardware and / or software modules can be used in combination with the electronic device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0137] The processing unit 16 executes various functional applications and data processing by running the programs stored in the system memory 28. For example, it implements a test task generation method provided by an embodiment of the present invention: based on a timed synchronization task, synchronize the information of each switching interface in each upstream system and the information of each integration interface in each downstream system from the data interface management platform; determine the newly submitted switching interfaces according to the information of each switching interface, determine the newly submitted integration interfaces according to the information of each integration interface, and write the information of the newly submitted switching interfaces and the information of the newly submitted integration interfaces into the local data table; based on a timed analysis task, determine the downstream systems affected by the newly submitted switching interfaces according to the information of the newly submitted switching interfaces in the local data table and the information of each integration interface; generate test tasks for the newly submitted switching interfaces for the determined downstream systems.

[0138] An embodiment of the present invention also provides a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, it implements the following steps: based on a timing synchronization task, synchronize the information of each switching interface in each upstream system and the information of each integration interface in each downstream system from a data interface management platform; determine newly submitted switching interfaces according to the information of each switching interface, determine newly submitted integration interfaces according to the information of each integration interface, and write the information of the newly submitted switching interfaces and the information of the newly submitted integration interfaces into a local data table; based on a timing analysis task, determine the downstream systems affected by the newly submitted switching interfaces according to the information of the newly submitted switching interfaces in the local data table and the information of each integration interface; generate a test task for the newly submitted switching interfaces for the determined downstream systems. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples (a non-exhaustive list) of the computer-readable storage medium include: an electrical connection with one or more wires, a portable computer disk, a hard disk, RAM, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk CD-ROM, an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, the computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0139] The computer-readable signal medium can include a data signal propagated in a baseband or as part of a carrier wave, which carries the computer-readable program code. Such a propagated data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0140] The program code contained on the computer-readable medium can be transmitted by any suitable medium, including but not limited to wireless, wire, optical cable, and radio frequency (RF), etc., or any suitable combination of the above.

[0141] An embodiment of the present invention also provides a computer program product, including a computer program which, when executed by a processor, implements the test task generation method provided in any embodiment of the present application.

[0142] In the process of implementing the computer program product, computer program code for performing the operations of the present invention can be written in one or more programming languages or combinations thereof. The programming languages include object-oriented programming languages such as Java, Smalltalk, C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, executed as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network - including a local area network (LAN) or a wide area network (WAN) - or can be connected to an external computer (for example, by using an Internet service provider to connect through the Internet).

[0143] Note that the above is only a preferred embodiment of the present invention and the applied technical principles. Those skilled in the art will understand that the present invention is not limited to the specific embodiments here. Various obvious changes, re-adjustments, and substitutions can be made by those skilled in the art without departing from the protection scope of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments. Without departing from the concept of the present invention, more other equivalent embodiments can be included, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A method for generating test tasks, characterized in that, The method includes: Based on a timing synchronization task, synchronize the information of each exchange interface in each upstream system and the information of each integration interface in each downstream system from the data interface management platform; Determine the newly submitted exchange interfaces according to the information of each of the exchange interfaces, determine the newly submitted integration interfaces according to the information of each of the integration interfaces, and write the information of the newly submitted exchange interfaces and the information of the newly submitted integration interfaces into the local data table; Based on a timing analysis task, determine the downstream systems affected by the newly submitted exchange interfaces according to the information of the newly submitted exchange interfaces and the information of each integration interface in the local data table; Generate a test task for the newly submitted exchange interfaces for the determined downstream systems; Wherein, the information of each of the exchange interfaces includes: the upstream system identification to which it belongs and the registered upstream data table identification; the information of each of the integration interfaces includes: the associated upstream system identification, the associated upstream data table identification, and the downstream system identification to which it belongs; The determining the downstream systems affected by the newly submitted exchange interfaces according to the information of the newly submitted exchange interfaces and the information of each integration interface in the local data table includes: Read the information of the newly submitted exchange interfaces and the information of each integration interface from the local data table; Match the upstream system identification to which the newly submitted exchange interface belongs and the registered upstream data table identification with the associated upstream system identification and the associated upstream data table identification of each integration interface respectively; Determine the integration interfaces with successful matches as the integration interfaces corresponding to the newly submitted exchange interfaces, and determine the downstream systems to which the integration interfaces corresponding to the newly submitted exchange interfaces belong as the downstream systems affected by the newly submitted exchange interfaces.

2. The method according to claim 1, wherein The determining the newly submitted exchange interfaces according to the information of each of the exchange interfaces, determining the newly submitted integration interfaces according to the information of each of the integration interfaces, and writing the information of the newly submitted exchange interfaces and the information of the newly submitted integration interfaces into the local data table includes: Write the information of each of the exchange interfaces and the information of each of the integration interfaces into a temporary table; For each exchange interface in the temporary table, determine whether the local data table contains an exchange interface identical to the current exchange interface according to the information of the current exchange interface. If not, determine the current exchange interface as the newly submitted exchange interface, and write the information of the newly submitted exchange interface into the local data table; For each integration interface in the temporary table, determine whether the local data table contains an integration interface identical to the current integration interface according to the information of the current integration interface. If not, determine the current integration interface as the newly submitted integration interface, and write the information of the newly submitted integration interface into the local data table.

3. The method according to claim 1, wherein The information of each of the integration interfaces further includes: the registered downstream data table identification; The determining the downstream systems to which the integration interfaces corresponding to the newly submitted exchange interfaces belong as the downstream systems affected by the newly submitted exchange interfaces includes: Determine the integration interface corresponding to the newly submitted exchange interface as the current interface; Determine whether there is a target exchange interface whose registered upstream data table identifier is the same as the registered downstream data table identifier of the current interface. If so, determine the target integration interface corresponding to the target exchange interface as the new current interface, and return to perform the operation of determining whether there is a target exchange interface whose registered upstream data table identifier is the same as the registered downstream data table identifier of the current interface; otherwise, determine the downstream systems to which each current interface belongs as the downstream systems affected by the newly submitted exchange interface.

4. The method according to claim 1, wherein Before reading the information of the newly submitted exchange interface and the information of each integration interface from the local data table and before matching the upstream system identifier and the registered upstream data table identifier of the newly submitted exchange interface with the associated upstream system identifier and the associated upstream data table identifier of each integration interface respectively, the method further includes: Determine the change type of each of the newly submitted exchange interfaces read, and filter out the newly submitted exchange interfaces whose change type is a preset type.

5. The method according to claim 1, wherein After generating a test task for the newly submitted exchange interface for the determined downstream system, the method further includes: Notify the data line testers of the determined downstream system of the test task; Receive and store the feedback information of the data line testers; wherein the feedback information includes the information that the test task needs to test and the test result, or the information that the test task does not need to test and the reason for not needing to test.

6. The method according to claim 5, wherein After notifying the data line testers of the determined downstream system of the test task, the method further includes: Display the relevant information of the test task through the user interface; When detecting a first preset trigger operation, display the interface list; wherein the interface list contains the information of the integration interfaces corresponding to the newly submitted exchange interface in the downstream system; When detecting a second preset trigger operation for the displayed integration interface, display the relevant information of the target report, so that the data line testers can determine whether the test task needs to be tested according to the relevant information of the target report; wherein the target report is a report that generates report data using the registered downstream data table of the displayed integration interface.

7. The method according to claim 6, wherein After displaying the relevant information of the target report, the method further includes: When detecting a third preset trigger operation for the displayed target report, start the report data generation job of the target report, and display the execution status of the report data generation job, so that the data line testers can determine the test result of the test task according to the execution status.

8. The method according to claim 5, wherein After receiving and storing the feedback information of the data line testers, the method further includes: Send the feedback information to the data interface management platform, so that the data interface management platform can determine whether to perform a release operation on the newly submitted exchange interface according to the feedback information.

9. The method according to any one of claims 1-8, characterized in that, The method further includes: When a selection operation on the online batch in the swap interface impact analysis page is detected, a summary table of the test cases of the swap interfaces of the selected online batch is displayed, and a notification operation is performed on the downstream systems that have not reported the test cases.

10. A test task generation device, characterized in that, The device includes: An information synchronization module, configured to synchronize the information of each swap interface in each upstream system and the information of each integration interface in each downstream system from the data interface management platform based on a timed synchronization task; An information writing module, configured to determine newly submitted swap interfaces according to the information of each swap interface, determine newly submitted integration interfaces according to the information of each integration interface, and write the information of the newly submitted swap interfaces and the information of the newly submitted integration interfaces into a local data table; A system determination module, configured to determine the downstream systems affected by the newly submitted swap interfaces based on a timed analysis task according to the information of the newly submitted swap interfaces and the information of each integration interface in the local data table; A task generation module, configured to generate test tasks for the newly submitted swap interfaces for the determined downstream systems; Among them, the system determination module is specifically configured to: Read the information of the newly submitted swap interfaces and the information of each integration interface from the local data table; match the upstream system identifier and the registered upstream data table identifier of the newly submitted swap interface with the associated upstream system identifier and the associated upstream data table identifier of each integration interface respectively; determine the integration interfaces with successful matches as the integration interfaces corresponding to the newly submitted swap interfaces, and determine the downstream systems to which the integration interfaces corresponding to the newly submitted swap interfaces belong as the downstream systems affected by the newly submitted swap interfaces.

11. The device according to claim 10, characterized in that, The information writing module is specifically configured to: Write the information of each swap interface and the information of each integration interface into a temporary table; for each swap interface in the temporary table, determine whether the local data table contains a swap interface identical to the current swap interface according to the information of the current swap interface. If not, determine the current swap interface as a newly submitted swap interface, and write the information of the newly submitted swap interface into the local data table; for each integration interface in the temporary table, determine whether the local data table contains an integration interface identical to the current integration interface according to the information of the current integration interface. If not, determine the current integration interface as a newly submitted integration interface, and write the information of the newly submitted integration interface into the local data table.

12. The device according to claim 11, characterized in that, The system determination module is specifically configured to: Determine the integration interface corresponding to the newly submitted swap interface as the current interface; determine whether there is a target swap interface whose registered upstream data table identifier is the same as the registered downstream data table identifier of the current interface. If so, determine the target integration interface corresponding to the target swap interface as the new current interface, and return to execute the operation of determining whether there is a target swap interface whose registered upstream data table identifier is the same as the registered downstream data table identifier of the current interface; Otherwise, determine the downstream systems to which each current interface belongs as the downstream systems affected by the newly submitted swap interfaces.

13. An electronic device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor. It is characterized in that when the processor executes the computer program, it implements the test task generation method described in any one of claims 1 to 9.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the test task generation method described in any one of claims 1 to 9.

15. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the test task generation method described in any one of claims 1 to 9.

Images