Test management method, system and device, storage medium and program product

By receiving non-standard test data and converting it into standard formats, and combining with preset workflow initiating approval processes, the problem of integrating test management tools for large financial IT enterprises is solved, and the closed-loop and efficiency improvement of test management is achieved.

CN118897801APending Publication Date: 2024-11-05CCB FINTECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410968371.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-18
Publication Date
2024-11-05

AI Technical Summary

Technical Problem

Due to the closed function of existing separate test management tools, they cannot support the overall test management of large financial IT enterprises, especially when the project scale and R&D process are different, resulting in complex and cumbersome testing management.

Method used

Provide a test management method and system, by receiving non-standard test data, generating custom configuration conversion files, converting data into standard formats, and launching enterprise approval process or next test process according to preset workflows, connecting different Test tools and enterprise management systems to form closed-loop management.

Benefits of technology

It realizes seamless integration of different testing tools and enterprise management systems, improves the efficiency and standardization of test management, supports the diversified testing needs of large financial IT enterprises, and forms an overall closed-loop management of the test process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118897801A_ABST
    Figure CN118897801A_ABST
Patent Text Reader

Abstract

The invention provides a test management method, system and device, a storage medium and a program product. Relates to the technical field of big data. The method comprises the following steps: receiving non-standard test data uploaded by a test tool system, wherein the non-standard test data comprises table data; extracting data content from the table data; generating a one-time imported custom configuration conversion file according to the global public parameters; converting the data content into a target file in a target format according to the custom configuration conversion file; and initiating an enterprise approval process or a next test process according to a preset workflow and the target file. Through the method, different test tool systems and enterprise approval management systems can be connected in series, when non-standard test data is received, the non-standard test data can be converted into data in a standard format, and development of existing real test management work is supported.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of big data technology, and in particular to a test management method, system, device, storage medium and program product. Background Art

[0002] In large financial IT enterprises, test management is complex and tedious, and the scale of projects varies by several orders of magnitude. IT test management in large financial enterprises has always been a challenging task.

[0003] At present, some commercial or open source project management or test management software can provide complete full-process support for the test management of a single project or a small enterprise. However, this kind of individual management tool is always based on a certain process development theory, such as project management and test management based on agile development or standard waterfall process.

[0004] Due to the independence of individual management tools, their own functions are closed and cannot support the overall test management of large financial IT companies. Summary of the invention

[0005] The present application provides a test management method, system, device, storage medium and program product to solve the problem that the separate test management tools in the prior art cannot support the overall test management of large financial IT enterprises due to the closed nature of their own functions.

[0006] In a first aspect, the present application provides a test management method, the method comprising:

[0007] Receiving non-standard test data uploaded by the test tool system, wherein the non-standard test data includes table data;

[0008] Extracting data content from the table data;

[0009] Generate a one-time imported custom configuration conversion file according to the global public parameters pre-stored in the test data management open platform, wherein the global public parameters include reusable field mapping relationships and error handling rules, and the custom configuration conversion file includes a mapping relationship between fields in the data content and standard fields of the test data management open platform;

[0010] Converting the data content into a target file in a target format according to the custom configuration conversion file;

[0011] Initiate the enterprise approval process or the next step of the testing process according to the preset workflow and the target file.

[0012] In one possible design, the method further includes:

[0013] Identify whether there is missing data in the table data;

[0014] If there is any missing data, the missing data in the table data is supplemented according to the preset rules.

[0015] In a possible design, the filling in missing data in the table data according to a preset rule includes:

[0016] Identify the data types of missing data, including critical data and non-critical data;

[0017] If the data type of the missing data is identified as key data, then the missing data in the table data is completed according to a preset rule or algorithm;

[0018] If the data type of the missing data is identified as non-critical data, the missing data in the table data is filled with default values.

[0019] In a possible design, initiating an enterprise approval process or a next step of a testing process according to a preset workflow and the target file includes:

[0020] When a preset specific event is triggered, the global docking interface of the test data management open platform obtains project data from the database, wherein the project data includes a target file carrying a project identifier and standard test data carrying a project identifier uploaded by the test tool system;

[0021] Update the current workflow status according to the project data;

[0022] According to the updated workflow status and preset rules, an approval process is automatically initiated and sent to the enterprise-level management system for approval.

[0023] In one possible design, the method further includes:

[0024] Receiving the approval result returned by the enterprise-level management system;

[0025] If the approval result indicates that a supplementary test or a modified test is to be performed, the approval result is sent to the test tool system indicated by the approval result;

[0026] If the approval result indicates to perform the next test, the current state of the workflow is updated, and a trigger test instruction is sent to the test tool system corresponding to the next test in the workflow.

[0027] In one possible design, the method further includes:

[0028] Obtaining a data source of defect testing in a database, wherein the data source includes a defect tracking system data source, a test management system data source, and a version control system data source;

[0029] Extracting defect data from each data source, the defect data including defect reports, test reports, and version information;

[0030] Convert the defect status in each defect data into a unified format;

[0031] Defect data converted to a unified format is grouped and summarized according to predefined hierarchies using aggregation functions.

[0032] In one possible design, the method further includes:

[0033] Receive a software code of a functional test environment and an identifier of the functional test environment to which the software code belongs, submitted by a user;

[0034] Numbering the software code, and storing the software code in a code library according to the functional test environment identifier, wherein the code library stores codes of multiple functional test environments;

[0035] Receiving a triggered rollback task initiated by a user in a test tool system, wherein the rollback task includes a serial number of a software code to be rolled back;

[0036] The software code is determined according to the serial number of the rolled-back software code, and the software code is redeployed to a functional test environment to which the software code belongs, where the functional test environment to which the software code belongs is deployed in an independent container.

[0037] In a second aspect, the present application provides a test management device, the device comprising:

[0038] A receiving module, used for receiving non-standard test data uploaded by the test tool system, wherein the non-standard test data includes table data;

[0039] An extraction module, used for extracting data content from the table data;

[0040] A generation module, used to generate a one-time imported custom configuration conversion file according to the pre-stored global public parameters of the test data management open platform, wherein the global public parameters include reusable field mapping relationships and error handling rules, and the custom configuration conversion file includes a mapping relationship between fields in the data content and standard fields of the test data management open platform;

[0041] A conversion module, used to convert the data content into a target file in a target format according to the custom configuration conversion file;

[0042] The process control module is used to initiate the enterprise approval process or the next test process according to the preset workflow and the target file.

[0043] In a third aspect, the present application provides a test management system, including: a test data management open platform, a test tool system, and a conversion tool;

[0044] The test data management open platform includes an input interface and a global process docking interface;

[0045] The input interface includes a predefined standard data input interface and a non-standard test data input interface;

[0046] The standard data input interface is connected to the test tool system, and the standard data input interface is used to receive test data of the standard test tool for performing standard functional test and standard non-functional test;

[0047] The non-standard test data input interface is connected to the conversion tool, and the non-standard test data input interface is used to receive the converted target file sent by the conversion tool;

[0048] The conversion tool is used to convert the non-standard test content into a target file in a target format;

[0049] The global process docking interface is used to dock the test tool system with the enterprise-level management system in the test data management open platform. The test tool system includes a test case management tool, a continuous integration tool, and a defect tracking tool. The enterprise-level management system is a system used to perform project management, quality management, and version control functions. Each test tool system requires a global process docking interface to dock with the enterprise-level management system. The configuration of each global process docking interface needs to be set according to the interface type, data format, and trigger conditions of the connected test tool system.

[0050] In a fourth aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor;

[0051] The memory stores computer-executable instructions;

[0052] The processor executes the computer-executable instructions stored in the memory to implement the method as described in any one of the first aspects.

[0053] In a fifth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the method as described in any one of the first aspects.

[0054] In a sixth aspect, the present application provides a computer program product, comprising a computer program, which, when executed by a processor, is a method as described in any one of the first aspects.

[0055] The present application provides a test management method, system, device, storage medium and program product, the method comprising: receiving non-standard test data uploaded by a test tool system, the non-standard test data including tabular data; extracting data content from the tabular data; generating a one-time imported custom configuration conversion file according to the global public parameters pre-stored by the test data management open platform, the global public parameters including reusable field mapping relationships and error handling rules, the custom configuration conversion file including the mapping relationship between the fields in the data content and the standard fields of the test data management open platform; converting the data content into a target file in a target format according to the custom configuration conversion file. The test data management open platform initiates the enterprise approval process or the next test process according to the preset workflow and target file. Through this method, different test tool systems and enterprise approval management systems can be connected in series, and standard data and non-standard test data uploaded by the test tool are received. When non-standard test data is received, it is converted into data in a standard format, forming a closed-loop management of the entire test process. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0057] Figure 1 A schematic diagram of the architecture of the test management system provided for this application;

[0058] Figure 2 A flowchart of the first embodiment of the test management method provided by this application;

[0059] Figure 3 A flowchart of the second embodiment of the test management method provided by this application;

[0060] Figure 4 A flowchart of the third embodiment of the test management method provided by this application;

[0061] Figure 5 A flowchart of a fourth embodiment of the test management method provided by this application;

[0062] Figure 6 A flowchart of a fifth embodiment of the test management method provided in this application;

[0063] Figure 7 A schematic diagram of the structure of the test management device embodiment 1 provided by the present application;

[0064] Figure 8 A schematic diagram of the structure of the electronic device provided in this application.

[0065] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0066] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0067] In the technical solution of this application, the collection, storage, use, processing, transmission, provision and disclosure of information such as financial data or user data involved shall comply with the provisions of relevant laws and regulations and shall not violate public order and good morals.

[0068] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0069] With the development of science and technology, testing technology has developed rapidly in the IT field. At present, some commercial or open source project management or test management software can provide complete full-process support for the test management of a single project or a small enterprise, such as ZenTao, JIRA and other test management software.

[0070] However, this kind of management tool based on independent construction ideas always carries out project management and test management based on a certain process R&D theory, such as agile development or standard waterfall process, etc. It is a self-contained system, resulting in closed system functions and unable to support the diverse overall test management needs of large financial IT companies.

[0071] Due to the different enterprise scales and project management forms, the R&D process of the project is divided into steady-state projects based on standard development processes and agile R&D projects with the goal of rapid iteration. With the differences in business complexity and importance, the number of people in different project teams may range from a few to hundreds. From the perspective of scale, the complexity of its testing process varies greatly. At the same time, due to the importance of the financial field, in addition to basic functional correctness, it also has extremely high requirements for multiple non-functional characteristic indicators of production applications. Therefore, it is necessary to design a diversified and developed test management system to support its overall test management work. The test management system can connect various test links and enterprise management in series to form a closed-loop management of the test process within the enterprise.

[0072] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0073] Figure 1 The schematic diagram of the test management system provided for this application is as follows: Figure 1 As shown, the test management system includes:

[0074] Test data management open platform, test tool system, conversion tool;

[0075] Among them, the test data management open platform aims to uniformly manage and process test data, and provide standardized interfaces and processes so that different test tools can be seamlessly integrated and work together. The test tool system includes tools for various tests, which are generally divided into functional tests and non-functional tests. Functional tests include manual tests, interface tests, unit tests and other test types. Non-functional tests include security tests, performance tests and other types. The test tool system provides the tools required for the above tests.

[0076] The test data management open platform includes input interface, output interface, and global process docking interface;

[0077] The input interface includes a predefined standard data input interface and a non-standard test data input interface;

[0078] In this solution, "standard data" and "non-standard test data" are mainly determined based on the pre-defined data management and processing methods, as well as the degree of standardization of the tools and methods used. Data in structured data formats such as XML, JSON, and YAML are defined as standard data. Non-standard test data refers to data that is managed and processed using informal or customized tools and methods during the test process. The data usually exists in unstructured or semi-structured forms, such as Excel tables, text files, etc. The data format is not unified and lacks a strict verification mechanism, which is prone to format inconsistency or data loss. For example, Excel in non-standard test data is a general-purpose spreadsheet tool that does not have functions specifically designed for Excel test management, such as test case management, defect tracking, test report generation, etc. During the testing process, some projects will adopt business test management based on Excel circulation, and some managed and written test cases are also circulated through Excel tables.

[0079] The standard data input interface is connected to the test tool system, and the standard data input interface is used to receive standard data for the standard test tool to perform standard functional testing and standard non-functional testing.

[0080] The conversion tool is used to convert the test content (such as a table) of non-standard test data into test data in a standard format.

[0081] In one implementation, the conversion tool may be a tool provided in the test data management open platform, and is located in the same physical device as the test data management open platform.

[0082] The non-standard test data input interface is connected to the conversion tool, and the non-standard test data input interface is used to receive the converted standard data sent by the conversion tool;

[0083] The global process docking interface is used to connect the test tool system with the enterprise management system in the test data management open platform. The test tool system includes test case management tools, continuous integration tools, and defect tracking tools. The enterprise management system is a system used for project management, quality management, and version control functions. Each test tool system needs a global process docking interface to connect with the enterprise management system. The configuration of each global process docking interface needs to be set according to the interface type, data format, and trigger conditions of the connected test tool system. For example, after a test tool completes a test, it needs to submit the results and trigger subsequent approvals or further test steps. The process docking in the middle is achieved through the global process docking interface.

[0084] The test data management open platform provides a data input interface for each specific test tool, which allows each specific test tool to upload data to the open platform. All test tools need to format and upload data according to a global parameter definition. The format and type of data are unified at the global level. The global process docking interface is used to connect the tool-level process with the enterprise-level process on the development platform, thereby forming a closed-loop management test process to ensure that the entire process from test tools to enterprise-level management is controllable.

[0085] The test tool system includes the following categories:

[0086] General functional test management tools: manage the general functional test process, covering all aspects from test planning to execution, defect tracking and report generation. Get test parameters from the test parameter library defined by the enterprise; create, edit, execute and manage test cases; record, track and manage defects found during the test process; you can use existing open source or commercial software, or develop your own tools that meet enterprise standards.

[0087] Interface test management tool: Provides automated interface testing in the form of enterprise standard interfaces based on configured test cases; supports automated execution of defined interface test cases; compares actual return results with expected results to verify results; records detailed logs for each test, troubleshooting and analysis.

[0088] Standard non-functional test management tools: perform non-functional tests such as security testing and performance testing, including vulnerability scanning, virus scanning, and manual security vulnerability detection; support performance testers to perform stress testing, load testing, and capacity testing; integrate existing security testing and performance testing tools.

[0089] The test data management open platform also includes an aggregation module, which is used to aggregate platform data according to multiple levels such as projects, test stages, applications, etc., such as unit testing, system integration testing, user acceptance testing, version verification testing, etc.

[0090] The test data management open platform also includes an output module, which provides a unified test view based on the platform standard data to the enterprise comprehensive project management system. The test view includes: global parameter view; project-level test plan, progress, case, defect statistics view; necessary detailed view. Through the output module, the full-process test products such as test reports are output to a wider range of project process management platforms.

[0091] The test data management open platform also includes a test management configuration module, which is used to define global parameters, processes and business meanings; at the specific level, it is used to configure test types, test phases, project types, test tools, test team management, test standard processes, test environment management, etc.; it is also used to configure forms containing structured online data, such as test plans, test plans, test execution, test reports, test evaluations, etc.

[0092] For the complete open source test management tools on the market, their data can be read through their free API interfaces and database access, and by establishing standard data conversion tools, the data of the open source test management tools can be converted to the open platform target format based on the custom data conversion configuration file to realize data reporting. Similarly, the conversion tool can receive standard process events issued by the open platform, and convert the standard process instructions into corresponding platform instructions based on the configuration file and the interface definition of the target test tool. Or it can be executed in the opposite direction, capturing the process events of the target test management tool, triggering the conversion and reporting to the test data management open platform.

[0093] The test management system provided in this embodiment is based on the data management open platform, and combines standard basic models, standard basic processes, separate docking forms at the business level and the technical level, standardized default processes and data management tools, and extensible third-party tool conversion forms to build an overall solution for large-scale financial IT test management. This solution strongly supports the development of existing real test management work.

[0094] The following is an introduction to a specific test management method applied to a test management system using a specific embodiment.

[0095] Figure 2 A flow chart of the test management method embodiment 1 provided in this application, such as Figure 2 As shown, the following steps are included:

[0096] S101. Receive non-standard test data uploaded by a test tool system, where the non-standard test data includes table data.

[0097] In this step, the conversion tool needs to provide an interface that is only used to receive non-standard test data from other tools in the test tool system connected through an API. The interface can communicate through a network protocol (such as HTTP) and use a suitable data format (such as CSV or Excel) to transmit non-standard test data, such as tabular data.

[0098] S102: extracting data content from the table data.

[0099] The conversion tool can use data processing libraries (such as data analysis libraries in Python) to parse the tabular data and extract the required data content from it. For example, if the tabular data is stored in Excel in CSV format, you can use the data analysis library Pandas in Python to read the CSV file and then extract the required fields and data based on the column name or index.

[0100] S103. Generate a one-time imported custom configuration conversion file according to the global public parameters pre-stored in the test data management open platform. The global public parameters include reusable field mapping relationships and error handling rules. The custom configuration conversion file includes mapping relationships between fields in the data content and standard fields of the test data management open platform.

[0101] In this step, the conversion tool obtains pre-stored global public parameters from the test data management open platform. The parameters may include field mapping relationships (for example, mapping column names in a table to field names defined by the platform), error handling rules (for example, how to handle data type mismatches or missing data), etc. Users can set global public parameters in the test data management open platform.

[0102] Convert global public parameters from a platform-specific format (such as JSON or XML) to a data structure that can be processed internally by the conversion tool, such as a dictionary or object in Python. Using the parsed global public parameters, the conversion tool generates a custom configuration conversion file based on predefined rules and logic. The format of a custom configuration conversion file can be a JSON file containing mapping rules and conversion logic, or a configuration file in a specific format containing various processing rules and mapping definitions. For example, for a table data, specify that each column is mapped to a data field defined by the platform. The generated custom configuration conversion files are stored in the configuration directory of the conversion tool so that subsequent data conversion tasks can read and use these configurations.

[0103] S104: Convert the data content into a target file in a target format according to the custom configuration conversion file.

[0104] In this step, the conversion tool creates a new XML document or JSON object, performs corresponding conversion operations on the data content according to the parsed custom configuration conversion file, and fills the data content into the corresponding fields and nodes.

[0105] Using custom configuration conversion files can improve the flexibility, maintainability, and accuracy of the data conversion process. Different data sources (such as databases, Excel tables, CSV files, text files, etc.) may have different structures and field names. Custom configuration conversion files can map data to the target format based on the mapping relationship between each format field and the standard field defined by the global public parameters without modifying the code of the conversion tool. When business requirements may change. For example, some fields may require specific processing or conversion rules, and this flexibility can be easily achieved through custom configuration files. If the mapping relationship is defined directly in the code, the code needs to be modified and redeployed every time the data structure or mapping rules change. With custom configuration files, you only need to update the configuration file without changing the code, which reduces maintenance costs.

[0106] The conversion tool sends the target file to the test data management open platform for storage.

[0107] S105: Initiate the enterprise approval process or the next test process according to the preset workflow and target file.

[0108] In this step, after receiving the target file, the test data management open platform determines the next process according to the preset workflow. If the next process is the approval process, the approval process is initiated to the enterprise-level approval management system; if the next process is to continue other tests, the instruction to trigger the next test is sent to the test tool system required for the next test.

[0109] This embodiment provides a test management method, in which a conversion tool receives non-standard test data uploaded by a test tool system, and the non-standard test data includes table data; extracts data content from the table data; generates a one-time imported custom configuration conversion file according to the global public parameters of the test data management open platform, and the global public parameters include reusable field mapping relationships and error handling rules, and the custom configuration conversion file includes a mapping relationship between fields in the data content and standard fields of the test data management open platform; converts the data content into a target file in a target format according to the custom configuration conversion file; and sends the target file to the test data management open platform for storage. The test data management open platform initiates the enterprise approval process or the next test process according to the preset workflow and target file. Through this method, different test tool systems and enterprise approval management systems can be connected in series to receive standard data and non-standard test data uploaded by the test tool. When non-standard test data is received, it is converted into data in a standard format through the conversion tool, forming a closed-loop management of the entire test process.

[0110] In the first embodiment of the above method, when converting the table data, the data in the table may be incomplete, which will cause the converted data format to be incomplete, affecting subsequent analysis. The following is an example of a test management method for incomplete table data.

[0111] Figure 3 A flow chart of the second embodiment of the test management method provided in this application, such as Figure 3 As shown, the following steps are included:

[0112] S201. The conversion tool identifies whether there is any missing data in the table data.

[0113] Identifying whether there is missing data in table data often requires combining multiple methods.

[0114] Checks if a cell in a table has an empty value.

[0115] Check whether the key fields in the table (such as the name of the first row in the table) are the same as the preset ones.

[0116] Check the length of string fields; strings that are too short may indicate missing or incomplete data.

[0117] S202: If there is any missing data, fill in the missing data in the table data according to preset rules.

[0118] In one implementation, the user is reminded to supplement the missing data. Specifically, a simple web interface is pre-developed using a web framework, allowing the user to manually supplement the missing data on the interface, and when missing data is identified, the user is reminded to manually supplement the data through a pop-up web interface.

[0119] In another implementation, missing data is automatically supplemented. The data type of the missing data is identified, and the data type includes key data and non-key data. Among them, data fields that are considered key data are pre-defined, such as ID, date, amount, etc., and other data that are not key data are considered non-key data. The data in tables for different test purposes are different, so the key data fields corresponding to each type of table data are pre-stored. When data is missing, compare whether the data in the key data field is missing. If the data type of the missing data is identified as key data, the missing data in the table data is supplemented according to preset rules or algorithms; if the data type of the missing data is identified as non-key data, the missing data in the table data is supplemented with default values.

[0120] For example, assume there is an Excel file as shown in Table 1 below:

[0121] User ID describe Person in charge state 001 Login Functionality Zhang San Under development 002 Registration Function Li Si Completed

[0122] Check the key fields in the table and find that two key data are missing, such as "Priority" and "Estimated Completion Time".

[0123] In the preset rules, all "completed" tasks have a default priority of low, and all "under development" tasks have a default priority of high.

[0124] For the estimated completion time, you can obtain the average completion time of similar tasks in historical data to estimate the estimated completion time. If there are no similar tasks in historical data, you can use default values ​​to complete the filling, such as setting the priority to "Medium" and the estimated completion time to the current date plus 7 days.

[0125] The automatically filled table is shown in Table 2 below.

[0126]

[0127] In the above example, if the person in charge is a non-key field, and a certain user does not fill in the person in charge field, the person in charge field is non-key data, and the data is filled in by filling in the default person in charge ID.

[0128] This embodiment provides a test management method, in which a conversion tool extracts data content from table data and determines whether the data is missing. When the data is missing, data filling can be implemented to prevent errors in subsequent data analysis and use.

[0129] The global process docking interface has certain management capabilities, but its main responsibilities are coordination and triggering. The following are some of its key management functions:

[0130] Status checking and monitoring: Monitor the execution status of each test tool to ensure that all necessary test steps have been completed.

[0131] Process control: Determine whether to proceed to the next process step based on predefined rules and conditions.

[0132] Trigger subsequent processes: After confirming that all preceding steps are completed, the subsequent approval or processing process is automatically triggered.

[0133] The following is an introduction to the role of the global process docking interface in test management using an embodiment.

[0134] Figure 4 The flowchart of the third embodiment of the test management method provided by this application is as follows: Figure 4 As shown, the following steps are included:

[0135] S301. When a preset specific event is triggered, the global docking interface of the test data management open platform obtains project data from the database. The project data includes a target file carrying a project identifier and standard test data carrying a project identifier uploaded by a test tool system.

[0136] When a preset specific event is triggered (for example, a test request is submitted, a test phase is completed, or the time for regular polling is reached), the global docking interface obtains relevant project data from the database. The project data may include the target file stored after conversion by the conversion tool, and may also include standard test data with project identification uploaded by the test tool system, such as test cases, test results, etc.

[0137] S302: Update the current workflow status according to the project data.

[0138] Based on the project data obtained from the database, the system needs to update the current workflow status. The workflow status reflects the current testing phase or activity of the project. Updating the workflow status helps ensure that the tracking of the project is up to date and provides a basis for the next step.

[0139] S303: Automatically initiate an approval process based on the updated workflow status and preset rules, and send the approval process to the enterprise-level management system.

[0140] Based on the updated workflow status and preset rules (such as approval required after a specific test phase is completed), the global process docking interface automatically initiates an approval process and sends it to the enterprise management system. This approval process usually contains the project data that needs to be approved, current status information, etc.

[0141] S304: Receive the approval result returned by the enterprise-level management system.

[0142] After processing the approval request, the enterprise management system will return the approval result, which may indicate approval, rejection, or the need for additional information.

[0143] S305. If the approval result indicates that a supplementary test or a modified test is to be performed, the approval result is sent to the test tool system indicated by the approval result.

[0144] In this step, if the approval result indicates that additional testing or modified testing is required, the global process docking interface will send the approval result to the corresponding test tool system. After receiving the instruction, the test tool system will perform the necessary additional testing or modified testing based on the approval result.

[0145] S306: If the approval result indicates to conduct the next test, the current state of the workflow is updated, and a trigger test instruction is sent to the test tool system corresponding to the next test in the workflow.

[0146] If the approval result indicates that the next test can be carried out, the global process docking interface will update the current status of the workflow to reflect that it has passed the approval and entered the next stage. Subsequently, the global process docking interface will trigger the test instruction and send it to the test tool system corresponding to the next test in the workflow. The test instruction notifies the test tool system to start executing the next stage of the test task.

[0147] Through this embodiment, the test data system can efficiently manage and coordinate the test process, from data acquisition, workflow status update, approval process initiation and result processing, to triggering the next test instruction, each step ensures the standardization and smoothness of the test work. This not only improves the automation level of the test process, but also ensures the coordination and cooperation between different systems.

[0148] In addition, when multiple tests (such as functional tests and non-functional tests) are involved, and tests are performed in different orders, the global process docking interface needs to have a certain degree of flexibility and intelligence to handle these complex workflows.

[0149] The following is a detailed explanation of the role and processing strategy of the global process docking interface through two examples.

[0150] Example 1: A project needs to wait for all tests to be completed and the test results to pass before it can be approved.

[0151] The global process docking interface regularly or continuously monitors the submission status of various test data of ongoing projects in the database.

[0152] If it is detected that one or more test data are incomplete, the global process docking interface should generate a notification to inform the relevant personnel or system which data has not been submitted and the latest submission deadline.

[0153] The interface can set a certain waiting time and retry mechanism to recheck the submission status of the data within the set time interval.

[0154] When it is detected that all test data of a project is in the submitted state, the process approval process is triggered.

[0155] Example 2: There are sequential requirements for testing, and each test must be approved before the next test can proceed.

[0156] The global process docking interface predefines the entire testing and approval workflow, including each step of the test, approval nodes and their dependencies. This definition can be achieved through pre-configured configuration files, workflow engines or rule engines.

[0157] After each test step is completed, the global process docking interface will trigger the corresponding approval process. After each test or approval step is completed, the interface should update the current status of the entire workflow.

[0158] Wait for the approval result, and decide whether to proceed to the next step of testing or return for correction or supplementary testing based on the approval result.

[0159] In a complex workflow, different branch processing may occur depending on the approval results or test results. Therefore, the global process docking interface needs to have conditional judgment capabilities to trigger different subsequent steps based on different test situations.

[0160] For example,

[0161] Start functional testing, the input interface receives data and stores it.

[0162] The global process docking interface detects that the functional test data is completed and triggers the approval process.

[0163] If approved, update the status and notify relevant personnel.

[0164] The test tool system is triggered to perform non-functional testing according to the workflow, and the input interface receives and stores non-functional test data. If the non-functional test data is a table or text, it needs to be further converted into a standard format through a conversion tool.

[0165] The global process docking interface detects that all test data in the database is completed, triggering the final approval process.

[0166] Once approved, the process is completed, the system updates the status and closes the workflow.

[0167] The test management system can also aggregate the data managed within the system to output the aggregated data.

[0168] Figure 5 A flow chart of the fourth embodiment of the test management method provided in this application, such as Figure 5 As shown, the following steps are included:

[0169] S401. The test data management open platform obtains the data source of the defect test in the database, where the data source includes the defect tracking system data source, the test management system data source, and the version control system data source.

[0170] The database is classified according to the data of different testing tools. The test data management open platform obtains data sources from the database locations of different defect tracking systems, test management systems, and version control systems.

[0171] S402: Extract defect data from each data source, where the defect data includes defect reports, test reports and version information.

[0172] S403: Convert the defect status in each defect data into a unified format.

[0173] Many system integration test tools are open source test tools. Therefore, the defect status defined in different test tools is different. It is necessary to define a unified defect status standard, such as "new", "assigned", "processing", "resolved", "closed", etc. For the defect status in each data source, write adapters or conversion functions to map the status in different data sources to the defined unified format.

[0174] S404: using an aggregation function, grouping and summarizing the defect data converted into a unified format according to a predefined hierarchy.

[0175] In this step, the predefined hierarchical structure is used to group the data, such as project, version, defect status, etc., and each level is aggregated and calculated to generate corresponding statistical reports or indicators. Aggregation functions used in the grouping and aggregation process can be functions such as SUM, COUNT, AVERAGE, etc.

[0176] After the above data aggregation steps, reports and charts of multiple dimensions can be generated, including:

[0177] In the project dimension: the total number of defects in different projects and the distribution of defects in each stage.

[0178] In the testing phase dimension: defects in unit testing, system integration testing, user acceptance testing, and version verification testing.

[0179] In the version dimension: the defect fix status of each version released.

[0180] Aggregate reports are created through data visualization tools (such as Tableau, Power BI) or programming languages ​​(such as Python's Matplotlib, Seaborn).

[0181] Through the method provided in this embodiment, the test data management open platform can efficiently acquire, integrate and process defect test data from different data sources, ensure the consistency and availability of data, and provide a reliable basis for subsequent analysis and reporting.

[0182] The test management configuration module in the test data management open platform manages and configures the test environment. Test environment management is a key component in the software development and testing process.

[0183] Environmental management includes the configuration of hardware, operating system, network configuration, database, application server, middleware, etc., ensuring that these configurations are consistent with the production environment or specific test requirements; managing the use of the test environment by different teams or projects to avoid conflicts and waste of resources; ensuring that the software version in the test environment is consistent with the test requirements, and managing switching and rollback between different versions.

[0184] Assume that an enterprise has five functional test environments (functional test environments 1 to 5) and several non-functional test environments (such as performance test environment, security test environment, etc.).

[0185] For example:

[0186] Functional test environment 1: used for testing login and user authentication modules.

[0187] Functional test environment 2: used for testing the shopping cart and checkout modules.

[0188] Functional test environment 3: used for testing the order management module.

[0189] Functional test environment 4: used for testing the inventory management module.

[0190] Functional testing environment 5: used for testing payment and accounting modules.

[0191] Environment configuration and setup: Each functional test environment needs to be configured with the code, database, and dependencies of the corresponding module to ensure that it is consistent with the production environment or test requirements.

[0192] Environment allocation and use: Through the test management configuration module, you can reasonably arrange the use of each functional test environment by different test teams to avoid conflicts. For example, when Team A is testing the login module on Functional Test Environment 1, Team B can test the shopping cart module on Functional Test Environment 2.

[0193] Non-functional test environment management includes: specifically used for performance testing, simulating high-load, high-concurrency scenarios, and testing the performance of the system under extreme conditions; used for security testing, checking whether the system has vulnerabilities and verifying the effectiveness of security patches.

[0194] The performance test environment needs to be configured with special performance test tools and set parameters to simulate a large number of user accesses. The security test environment needs to install various security test tools to perform vulnerability scanning and penetration testing. The performance test environment needs to monitor the use of resources such as CPU, memory, and network bandwidth in real time to ensure the accuracy of the test. The security test environment needs to regularly update security test tools and vulnerability libraries to maintain the effectiveness of the test.

[0195] The following is an introduction to test environment management using an embodiment.

[0196] Figure 6 A flowchart of the fifth embodiment of the test management method provided in this application is shown in FIG. Figure 6 As shown, the following steps are included:

[0197] S501. The test data management open platform receives software code of a functional test environment and an identifier of the functional test environment to which the software code belongs, submitted by a user.

[0198] In this step, the test data management open platform receives the software code of the functional test environment submitted by the user and the functional test environment identifier to which the code belongs through the input interface.

[0199] S502: Number the software codes, and store the software codes in a code library according to the functional test environment identifier, wherein the code library stores codes of multiple functional test environments.

[0200] The test data management open platform will number the received software code. Each software code will be assigned a unique number to identify the code. The test data management open platform will then associate the software code with the functional test environment identifier to which it belongs and store it in the code library. The code library will store the codes of multiple functional test environments so that they can be found and used when needed.

[0201] S503: receiving a trigger rollback task initiated by a user in the test tool system, where the rollback task includes the serial number of the software code to be rolled back.

[0202] The test data management open platform will receive the triggered rollback task initiated by the user in the test tool system. The rollback task includes the number of the software code that needs to be rolled back. The user can initiate the rollback task through the interface or API provided by the test tool system and specify the number of the software code that needs to be rolled back.

[0203] S504: Determine the software code according to the serial number of the rolled-back software code, and redeploy the software code to the functional test environment to which the software code belongs. The functional test environment to which the software code belongs is deployed in an independent container.

[0204] The test data management open platform will determine the software code that needs to be rolled back according to the number of the rolled back software code, and then the test data management open platform will redeploy the software code to the functional test environment to which it belongs.

[0205] These functional test environments are usually deployed in independent containers to ensure isolation and independence from each other. By redeploying the software code, you can implement a rollback operation and restore the functional test environment to its previous state.

[0206] In one implementation, each test team has its own virtual machine instance, each running its own operating system and software configuration. The virtual machines are completely isolated from each other and can be started, stopped, and restarted independently.

[0207] In one implementation, using container technology such as Docker, you can create independent containers for the test team. Multiple containers share the same operating system kernel but are isolated from each other.

[0208] The following is an example of test code rollback.

[0209] The development team completed the development of new features for the user login module, submitted the code to the test data management open platform repository, and created a new tag v1.1.

[0210] The test data management open platform triggers the build process and generates a new version of the login module.

[0211] The new version of the login module is automatically deployed to functional test environment A.

[0212] The testing team conducted tests on functional testing environment A and found that the new version v1.1 had a defect and needed to be rolled back to the previous stable version v1.0.

[0213] The testing team decided to roll back to version v1.0. The tag confirmed that v1.0 was the last stable version.

[0214] Trigger the rollback task in the test tool and specify to roll back to v1.0.

[0215] The test data management open platform pulls the v1.0 version of the code, rebuilds it, and deploys it to functional test environment A.

[0216] Through software code management and rollback mechanisms, enterprises can achieve efficient version control, independent environment isolation and resource control, while automated operations improve work efficiency and traceability.

[0217] Figure 7 This is a schematic diagram of the structure of the test management device embodiment 1 provided in this application, such as Figure 7As shown, the test management device 40 includes:

[0218] A receiving module 401 is used to receive non-standard test data uploaded by a test tool system, wherein the non-standard test data includes table data;

[0219] An extraction module 402, used to extract data content from the table data;

[0220] A generation module 403, used to generate a one-time imported custom configuration conversion file according to the pre-stored global public parameters of the test data management open platform, wherein the global public parameters include reusable field mapping relationships and error handling rules, and the custom configuration conversion file includes a mapping relationship between the fields in the data content and the standard fields of the test data management open platform;

[0221] A conversion module 404, configured to convert the data content into a target file in a target format according to the custom configuration conversion file;

[0222] The process control module 405 is used to initiate the enterprise approval process or the next test process according to the preset workflow and the target file.

[0223] The test management device provided in this embodiment is used to execute the method of the test data management open platform side in the above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be described in detail here.

[0224] Figure 8 This is a schematic diagram of the structure of the electronic device provided in this application. Figure 8 As shown, the electronic device 50 may include: at least one processor 501 and a memory 502. Optionally, the device 50 further includes a communication component 503. The processor 501, the memory 502 and the communication component 503 are connected via a bus 504.

[0225] In a specific implementation process, at least one processor 501 executes the computer-executable instructions stored in the memory 502, so that at least one processor 501 executes the above method.

[0226] The specific implementation process of the processor 501 can be found in the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

[0227] In the above embodiments, it should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the invention may be directly implemented as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0228] The memory may include a high-speed memory (Random Access Memory, RAM), and may also include a non-volatile memory (Non-volatile Memory, NVM), such as at least one disk memory.

[0229] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.

[0230] The present application also provides a computer program product, including a computer program, which implements the above method when executed by a processor.

[0231] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the above method is implemented.

[0232] The above-mentioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special-purpose computer.

[0233] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (Application Specific Integrated Circuits, referred to as: ASIC). Of course, the processor and the readable storage medium can also exist in the device as discrete components.

[0234] The division of units is only a logical function division, and there may be other divisions in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

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

[0236] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

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

[0238] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0239] Finally, it should be noted that those skilled in the art will readily conceive of other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses or adaptations of the present invention, which follow the general principles of the present invention and include common knowledge or customary technical means in the art not disclosed by the present invention, are not limited to the precise structure described above and shown in the drawings, and may be modified and changed in various ways without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A test management method, characterized in that: The method comprises: Receiving non-standard test data uploaded by the test tool system, wherein the non-standard test data includes table data; Extracting data content from the table data; Generate a one-time imported custom configuration conversion file according to the global public parameters pre-stored in the test data management open platform, wherein the global public parameters include reusable field mapping relationships and error handling rules, and the custom configuration conversion file includes a mapping relationship between fields in the data content and standard fields of the test data management open platform; Converting the data content into a target file in a target format according to the custom configuration conversion file; Initiate the enterprise approval process or the next step of the testing process according to the preset workflow and the target file.

2. The method according to claim 1, characterized in that The method further comprises: Identify whether there is missing data in the table data; If there is any missing data, the missing data in the table data is supplemented according to the preset rules.

3. The method according to claim 1, characterized in that The method of filling in missing data in the table data according to a preset rule includes: Identify the data types of missing data, including critical data and non-critical data; If the data type of the missing data is identified as key data, then the missing data in the table data is completed according to a preset rule or algorithm; If the data type of the missing data is identified as non-critical data, the missing data in the table data is filled with default values.

4. The method according to any one of claims 1 to 3, characterized in that: The initiation of the enterprise approval process or the next step of the testing process according to the preset workflow and the target file includes: When a preset specific event is triggered, the global docking interface of the test data management open platform obtains project data from the database, wherein the project data includes a target file carrying a project identifier and standard test data carrying a project identifier uploaded by the test tool system; Update the current workflow status according to the project data; According to the updated workflow status and preset rules, an approval process is automatically initiated and sent to the enterprise-level management system for approval.

5. The method according to claim 4, characterized in that The method further comprises: Receiving the approval result returned by the enterprise-level management system; If the approval result indicates that a supplementary test or a modified test is to be performed, the approval result is sent to the test tool system indicated by the approval result; If the approval result indicates to perform the next test, the current state of the workflow is updated, and a trigger test instruction is sent to the test tool system corresponding to the next test in the workflow.

6. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: Obtaining a data source of defect testing in a database, wherein the data source includes a defect tracking system data source, a test management system data source, and a version control system data source; Extracting defect data from each data source, the defect data including defect reports, test reports, and version information; Convert the defect status in each defect data into a unified format; Defect data converted to a unified format is grouped and summarized according to predefined hierarchies using aggregation functions.

7. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: Receive a software code of a functional test environment and an identifier of the functional test environment to which the software code belongs, submitted by a user; Numbering the software code, and storing the software code in a code library according to the functional test environment identifier, wherein the code library stores codes of multiple functional test environments; Receiving a triggered rollback task initiated by a user in a test tool system, wherein the rollback task includes a serial number of a software code to be rolled back; The software code is determined according to the serial number of the rolled-back software code, and the software code is redeployed to a functional test environment to which the software code belongs, where the functional test environment to which the software code belongs is deployed in an independent container.

8. A test management device, characterized in that: The device comprises: A receiving module, used for receiving non-standard test data uploaded by the test tool system, wherein the non-standard test data includes table data; An extraction module, used for extracting data content from the table data; A generation module, used to generate a one-time imported custom configuration conversion file according to the pre-stored global public parameters of the test data management open platform, wherein the global public parameters include reusable field mapping relationships and error handling rules, and the custom configuration conversion file includes a mapping relationship between fields in the data content and standard fields of the test data management open platform; A conversion module, used to convert the data content into a target file in a target format according to the custom configuration conversion file; The process control module is used to initiate the enterprise approval process or the next test process according to the preset workflow and the target file.

9. A test management system, characterized in that: include: Test data management open platform, test tool system, conversion tool; The test data management open platform includes an input interface and a global process docking interface; The input interface includes a predefined standard data input interface and a non-standard test data input interface; The standard data input interface is connected to the test tool system, and the standard data input interface is used to receive test data of the standard test tool for performing standard functional test and standard non-functional test; The non-standard test data input interface is connected to the conversion tool, and the non-standard test data input interface is used to receive the converted target file sent by the conversion tool; The conversion tool is used to convert the non-standard test content into a target file in a target format; The global process docking interface is used to dock the test tool system with the enterprise-level management system in the test data management open platform. The test tool system includes a test case management tool, a continuous integration tool, and a defect tracking tool. The enterprise-level management system is a system used to perform project management, quality management, and version control functions. Each test tool system requires a global process docking interface to dock with the enterprise-level management system. The configuration of each global process docking interface needs to be set according to the interface type, data format, and trigger conditions of the connected test tool system.

10. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 7.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 7 when executed by a processor.

12. A computer program product, characterized in that The method comprises a computer program which, when executed by a processor, performs the method according to any one of claims 1 to 7.