Interface testing method, system and device and storage medium

Abstract

The invention relates to the technical field of intelligent equipment, and discloses a method, system and device for interface testing and a storage medium. The method comprises the steps of determining a current regression test case set corresponding to a current pretest event under the condition that the current pretest event is captured; determining a dynamic regression test plan according to a current test resource matched with the current test event, and controlling a corresponding test execution node to call a current regression test case set from a case platform according to the dynamic regression test plan and interface information managed by an application programming interface API management platform to perform a corresponding interface test; and generating a corresponding interface test report according to a current test result fed back by the test execution node. Therefore, multiple platforms are deeply fused, the test resources corresponding to the current test event are reasonably allocated, and the corresponding interface test is performed, so that the test resource allocation is more reasonable, the quality improvement strategy is more efficient, and the accuracy and efficiency of the interface test are further improved.

Description

Technical Field

[0001] The present application relates to the field of automated testing technology, for example, to methods, systems, devices, and storage media for interface testing. Background Art

[0002] With the rapid development of intelligent technology, more and more software and applications are being used in various devices. As software complexity increases and iteration accelerates, interface testing is crucial to ensuring the stability of various application systems and business systems.

[0003] Currently, during interface testing, test submissions often rely on manual coordination, resulting in delayed and often overlooked regression test plan development. This means the testing process lacks automated integration, making it difficult for regression test plans to immediately respond to test submissions. While some solutions that have introduced automated testing frameworks can perform regression testing regularly, they lack deep integration with the testing submission process and cannot be automatically triggered on demand. Furthermore, online inspections are independent of the defect management process, leading to a lengthy process between fault discovery and repair. Clearly, the automation, intelligence, and usability of interface testing still need to be improved.

[0004] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of this application, and therefore may include information that does not constitute prior art known to ordinary technicians in this field. Summary of the Invention

[0005] In order to provide a basic understanding of some aspects of the disclosed embodiments, a brief summary is given below. The summary is not an extensive review, nor is it intended to identify key / critical elements or delineate the scope of protection of these embodiments, but rather serves as a prelude to the detailed description that follows.

[0006] The embodiments of the present disclosure provide a method, system, device, and storage medium for interface testing to solve the technical problem of low interface testing efficiency.

[0007] In some embodiments, the method comprises:

[0008] When the current test event is captured, determine the current regression test case set corresponding to the current test event;

[0009] Determine the dynamic regression test plan based on the current test resources that match the current test event, and control the corresponding test execution node to call the current regression test case set from the use case platform according to the dynamic regression test plan and the interface information managed by the application programming interface (API) management platform to perform the corresponding interface test;

[0010] Generate the corresponding interface test report based on the current test results fed back by the test execution node.

[0011] In this way, the testing platform, use case platform, and API management platform are deeply integrated to make the allocation of testing resources more reasonable and the quality improvement strategy more efficient, further improving the accuracy and efficiency of interface testing.

[0012] In some embodiments, it further includes:

[0013] If the current test result includes test failure information, the test failure information is sent to the defect management platform, so that the defect management platform determines first repair task information that matches the test failure information;

[0014] A first test request event is captured after the corresponding repair is completed according to the first repair task information.

[0015] It can be seen that regression testing can be automatically triggered by raising the test, which can greatly shorten the test cycle and improve test efficiency.

[0016] In some embodiments, it further includes:

[0017] A second test request event is captured after the corresponding repair is completed according to the second repair task information, wherein the second repair task information is obtained after the defect management platform obtains the defect report obtained according to the inspection abnormal event.

[0018] In this way, online inspections and defect reporting are seamlessly connected, reducing accident response time and further enhancing the stability of the interface testing system.

[0019] In some embodiments, the defect management platform obtaining the second repair task information includes:

[0020] The defect management platform obtains the current defect report, which is obtained based on the current inspection abnormality event during the interface automated inspection process and the corresponding current defect template. The current defect template is determined by the event center platform after capturing the current inspection abnormality event.

[0021] The defect management platform determines the second current repair task information that matches the current defect report based on the attribution information corresponding to the current defect template and the stored developer skill information, and pushes the second current repair task information to be executed.

[0022] It can be seen that the process architecture of one-click reporting from the event center platform to the defect management platform corresponding to online inspection abnormal events, and the event classification and intelligent allocation algorithm accelerate the fault repair closed loop.

[0023] In some embodiments, it further includes:

[0024] When receiving the current test case, the use case platform performs format and semantic preprocessing on the current test case, determines the current storage location corresponding to the current test case in the layered architecture, and stores it accordingly;

[0025] When a review task for the current test case is initiated, the use case platform obtains online review information and obtains current quality information of the current test case based on the online review information.

[0026] In this way, the use case platform's automated architecture and use case life cycle management and review process optimization technology will improve use case quality and management efficiency.

[0027] In some embodiments, further comprising:

[0028] When receiving the current interface change information, the API management platform normalizes the current interface change information, stores the corresponding interface information, generates the corresponding interface change notification and sends it, so that one or more related platforms can update the corresponding interface information according to the interface change notification when receiving the interface change notification.

[0029] Of course, the API management platform's message-driven architecture, data consistency guarantee mechanism, and mapping update rules that synchronize with multiple platforms are the cornerstones of stable development and testing collaboration, and improve the stability of the interface testing system.

[0030] In some embodiments, further comprising:

[0031] Determine the current visual dashboard corresponding to the current user role information and current business scenario information;

[0032] Based on the test results corresponding to the test event, the log system data, and the test data corresponding to the defect management platform, corresponding visualization is presented through the current visualization dashboard.

[0033] In this way, test data collection and processing adopt visual data links, which further improves the intelligence of the interface test system and user experience.

[0034] In some embodiments, the system for interface testing includes: a testing platform, a use case platform, and an API management platform, wherein:

[0035] The testing platform is configured to determine the current regression test case set corresponding to the current testing event when the current testing event is captured; determine the dynamic regression test plan based on the current test resources matching the current testing event, and control the corresponding test execution node to call the current regression test case set from the use case platform according to the dynamic regression test plan and the interface information managed by the application programming interface API management platform to perform the corresponding interface test; generate the corresponding interface test report based on the current test results fed back by the test execution node.

[0036] In some embodiments, the device for interface testing includes a processor and a memory storing program instructions, and the processor is configured to perform the above-mentioned method for interface testing when executing the program instructions.

[0037] In some embodiments, the storage medium stores program instructions, and when the program instructions are run, the method for interface testing is executed.

[0038] The method, system, device, and storage medium for interface testing provided by the embodiments of the present disclosure can achieve the following technical effects:

[0039] Deeply integrate multiple platforms such as the testing platform, use case platform, and API management platform, reasonably allocate test resources corresponding to the current testing event, and conduct corresponding interface testing. In this way, test resource allocation is more reasonable, quality improvement strategies are more efficient, and the accuracy and efficiency of interface testing are further improved.

[0040] The above general description and the following description are exemplary and explanatory only and are not intended to limit the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] One or more embodiments are exemplarily described by corresponding drawings. These exemplary descriptions and drawings do not limit the embodiments. Elements with the same reference numerals in the drawings are shown as similar elements. The drawings do not constitute a scale limitation. In addition,

[0042] Figure 1 This is a schematic diagram of an architecture for an interface testing system provided by an embodiment of the present disclosure;

[0043] Figure 2 This is a flow chart of an interface testing method provided by an embodiment of the present disclosure;

[0044] Figure 3 This is a flow chart of an interface testing method provided by an embodiment of the present disclosure;

[0045] Figure 4 is a structural diagram of an interface testing device provided by an embodiment of the present disclosure;

[0046] Figure 5 is a structural diagram of an interface testing device provided by an embodiment of the present disclosure;

[0047] Figure 6 is a structural diagram of an interface testing device provided by an embodiment of the present disclosure;

[0048] Figure 7 is a structural diagram of an interface testing device provided by an embodiment of the present disclosure;

[0049] Figure 8 It is a structural diagram of an interface testing device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0050] In order to be able to understand the features and technical content of the embodiments of the present disclosure in more detail, the implementation of the embodiments of the present disclosure is described in detail below in conjunction with the accompanying drawings. The accompanying drawings are for reference only and are not used to limit the embodiments of the present disclosure. In the following technical description, for the sake of convenience of explanation, a full understanding of the disclosed embodiments is provided through multiple details. However, one or more embodiments can still be implemented without these details. In other cases, to simplify the drawings, well-known structures and devices can be simplified for display.

[0051] In the description and claims of the embodiments of the present disclosure, as well as in the accompanying drawings, the terms "first," "second," and the like are used to distinguish similar items and are not necessarily used to describe a particular order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate to describe the embodiments of the present disclosure herein. In addition, the terms "including," "having," and any variations thereof are intended to cover non-exclusive inclusions.

[0052] Unless otherwise stated, the term "plurality" means two or more.

[0053] In the embodiment of the present disclosure, the character " / " indicates that the preceding and following objects are in an "or" relationship. For example, A / B means: A or B.

[0054] The term "and / or" describes an association between objects, indicating that three relationships can exist. For example, A and / or B means: A or B, or A and B.

[0055] With the increasing complexity of software and the acceleration of iteration, interface testing is crucial to ensuring the stability of various application systems and business systems. In the disclosed embodiment, during the interface testing process corresponding to the software, multiple platforms such as the testing platform, use case platform, and application programming interface (API) management platform are deeply integrated, and regression testing is automatically triggered by testing, which greatly shortens the testing cycle and improves testing efficiency; online inspections and defect reporting are seamlessly connected to reduce accident response time and enhance system stability; use case platform reviews optimize use case quality and reduce the risk of test omissions; API management platform and multiple platforms are synchronized with one click to ensure data consistency and reduce collaborative error rates; visual presentation and analysis can assist in accurate decision-making, make test resource allocation more reasonable, and make quality improvement strategies more efficient, comprehensively promote software development from traditional discrete operations to a new stage of integrated intelligent collaboration, and significantly improve the market competitiveness of software products and the R&D benefits of enterprises.

[0056] Figure 1 This is a schematic diagram of a system architecture for interface testing provided by an embodiment of the present disclosure. Figure 1 As shown, the system for interface testing may include: a testing platform 100 , a use case platform 200 , and an API management platform 300 .

[0057] In the disclosed embodiments, the use case platform 200 is a unified use case management platform that integrates various automated use cases stored in a decentralized manner. Upon upload, test cases undergo format verification and pre-processing by a semantic analysis module to ensure compliance with platform specifications and business logic consistency. Test cases can be verified and processed based on industry standards and an internal enterprise test specification knowledge base.

[0058] Furthermore, the use case platform 200 organizes the use case library in a hierarchical structure, which facilitates retrieval, maintenance, and management. In some embodiments, the hierarchical structure may include: project-module-scenario dimensions.

[0059] The API management platform 300 builds a central repository of interface definitions, gathering metadata for all software platform interfaces, including interface names, request parameter formats, response data structures, access permissions, call frequency limits, and other information. Once a development team submits an interface design or changes an interface, it is standardized and entered into the central repository by the API management platform 300. Simultaneously, a change notification is generated and pushed to multiple associated platforms, such as the testing platform 100 and the use case platform 200.

[0060] In this way, after the use case platform 200 organizes the use case library in a hierarchical architecture and the API management platform 300 builds the interface definition central library and enters the corresponding interface information, the corresponding interface test can be performed. That is, the testing platform 100 is configured to determine the current regression test case set corresponding to the current test event when the current test event is captured; determine the dynamic regression test plan based on the current test resources matching the current test event, and control the corresponding test execution node to call the current regression test case set from the use case platform 200 according to the dynamic regression test plan and the interface information managed by the application programming interface API management platform 300 to perform the corresponding interface test; and generate the corresponding interface test report based on the current test results fed back by the test execution node.

[0061] It can be seen that the testing platform, use case platform, and API management platform are integrated. The testing platform can brake the dynamic regression test plan according to the corresponding test resources, and call the current regression test case set from the use case platform 200 according to the dynamic regression test plan and the interface information managed by the API management platform 300 to perform corresponding interface testing.

[0062] Figure 2 This is a flow chart of an interface testing method provided by an embodiment of the present disclosure, such as Figure 2 As shown, the interface testing process includes:

[0063] Step 201: When a current test event is captured, a current regression test case set corresponding to the current test event is determined.

[0064] The testing platform analyzes the current testing event to obtain the corresponding current testing information, including module versions, a list of changed interfaces, and testing environment parameters. It then compares this information with historical test data based on pre-set rules, intelligently filtering associated regression test cases to determine the corresponding current regression test case set. For example, the platform can use interface change impact analysis algorithms, version difference backtracking models, and other methods to determine the corresponding current regression test case set.

[0065] Step 202: Determine the dynamic regression test plan based on the current test resources that match the current test event, and control the corresponding test execution node to call the current regression test case set from the use case platform according to the dynamic regression test plan and the interface information managed by the application programming interface API management platform to perform corresponding interface testing.

[0066] Based on the test information obtained after parsing the current test event, the testing platform determines the current test resources that match the current test event, including associated use cases, execution threads, and available test skill profiles. It then generates a dynamic regression test plan based on the current test resources. In some embodiments, dynamic regression test plans may be generated based not only on the current test resources but also on a stored priority policy. The priority policy may be set based on business urgency and change risk assessment.

[0067] A dynamic regression test plan has been developed, and the testing platform can accurately assign test tasks to test execution nodes. This allows the corresponding test execution node to call the current regression test case set from the use case platform according to the dynamic regression test plan and the interface information managed by the API management platform to perform the corresponding interface testing. Specifically, this may include: the test execution node calls the corresponding current regression test case set from the use case platform according to the dynamic regression test plan, and drives the interface testing tool to simulate requests based on the interface information managed by the API management platform to verify interface functions and performance. Among them, performance includes monitoring indicators such as response time, throughput, and concurrent processing capabilities.

[0068] Step 203: Generate a corresponding interface test report based on the current test result fed back by the test execution node.

[0069] During the interface testing process, the testing platform can obtain the test results fed back by the test execution node in real time, that is, obtain the corresponding current test results, and then obtain the corresponding interface test report based on the current test results. Alternatively, in some embodiments, the current test results can be sent to the result summary and analysis module, which then analyzes and integrates the current test results and the saved test results related to the interface to obtain the corresponding interface test report.

[0070] It can be seen that in this embodiment, multiple platforms such as the testing platform, use case platform, and API management platform are deeply integrated, the test resources corresponding to the current testing event are reasonably allocated, and the corresponding interface tests are performed. In this way, the test resource allocation is more reasonable and the quality improvement strategy is more efficient, further improving the accuracy and efficiency of the interface test.

[0071] The current test event captured by the testing platform can be initiated by a tester or automatically by the interface testing system. In some embodiments, a test event can be triggered by a tester, for example, when developing a new interface or updating an interface. The tester can trigger a test event, which is then captured by the testing platform, effectively obtaining the current test event.

[0072] In the embodiment of the present disclosure, the system for interface testing can be an automated testing system. Therefore, the testing platform can also capture the first testing event after the previous test failure is repaired by the defect management platform, or can also capture the second testing event after the abnormal event is detected during inspection and repaired by the defect management platform. Figure 1 As shown, the system for interface testing may further include: a defect management platform 400 and an event center platform 500 .

[0073] When the current test result obtained by the testing platform 100 after testing the interface includes a test failure, the testing platform 100 may send the test failure information to the defect management platform 400. The defect management platform 400 can then analyze the test failure information, determine the defect category, and obtain corresponding first remediation task information. Based on the defect category, developer skill matrix, and other factors, the platform intelligently assigns the remediation task to the responsible R&D team and simultaneously sends notifications to the team members' work terminals, for example, via email or instant messaging. In this way, when the developer submits the solution after the remediation, the corresponding interface information in the API management platform 300 is updated, which in turn triggers the initiation of the corresponding test event, allowing the testing platform to capture the corresponding first test event. Specifically, in some embodiments, when the current test result includes a test failure, the test failure information is sent to the defect management platform, allowing the defect management platform to determine the first remediation task information that matches the test failure information and capture the first test event after the corresponding remediation is completed according to the first remediation task information.

[0074] Therefore, in some embodiments, the test submission platform 100 is configured to send the test failure information to the defect management platform when the current test result includes the test failure information, and capture the first test submission event after the corresponding repair is completed according to the first repair task information.

[0075] The defect management platform 400 is configured to determine first repair task information matching the test failure information, and push the first current repair task information to be executed.

[0076] The system used for interface testing can also initiate online automated inspection tasks, which can regularly inspect business interfaces. The inspection frequency can be intelligently adjusted based on business peak and trough periods. In this way, after capturing abnormal events, such as interface response timeouts, return data errors, abnormal status codes, etc., they can be pushed to the event center platform 500 in real time. The event center platform 500 uses the abnormality type and predefined rule engine to determine the severity and impact scope, associates the corresponding defect template, and generates the corresponding defect report. The defect template includes: defect description, reproduction steps, expected result template, etc., and the abnormality types include: network layer, application layer, business logic layer, etc.

[0077] Then, according to the operating instructions of the monitoring personnel, the event center platform 500 pushes the current defect report carrying the abnormal data information corresponding to the current abnormal event to the defect management platform 400. In this way, the defect management platform 400 can analyze the current defect report, determine the defect category, obtain the corresponding second repair task information, and intelligently assign the repair task to the responsible R&D team based on module affiliation, developer skill matrix, etc., and push notifications to the team members' work terminals at the same time, for example, reminding the corresponding R&D team members through email or instant messaging tools. In this way, after the R&D personnel submit the solution after the repair, the corresponding interface information in the API management platform 300 can be updated, and then the corresponding test event can be triggered to start, so that the test platform can capture the corresponding second test event. That is, in some embodiments, the second test event after the corresponding repair is completed according to the second repair task information is captured, wherein the second repair task information is obtained after the defect management platform obtains the defect report obtained based on the inspection abnormal event. The defect management platform obtains the second repair task information, including: the defect management platform obtains the current defect report, wherein the current defect report is obtained based on the current inspection abnormality event in the interface automation inspection process, and the corresponding current defect template, and the current defect template is determined by the event center platform after capturing the current inspection abnormality event; the defect management platform determines the second current repair task information that matches the current defect report based on the attribution information corresponding to the current defect template and the saved developer skill information, and pushes it so that the second current repair task information is executed.

[0078] Therefore, in some embodiments, the testing platform 100 is configured to capture a second testing event after the corresponding repair is completed according to the second repair task information.

[0079] The event center platform 500 is configured to, when capturing a current inspection abnormality event during the interface automated inspection process, determine a current defect template corresponding to the current inspection abnormality event and push the corresponding current defect report to the defect management platform 400 .

[0080] The defect management platform 400 is configured to obtain the current defect report, determine the second current repair task information that matches the current defect report based on the attribution information corresponding to the current defect template and the saved developer skill information, and push the second current repair task information to be executed.

[0081] Thus, after capturing the first or second test event, the testing platform 100 can integrate with the use case platform 200 and the API management platform 300 as described above to perform corresponding interface testing. This completes closed-loop management through regression verification by testers, ensuring timely and effective defect resolution and improving system reliability and stability. Regression verification involves performing regression testing based on a set of test cases associated with the defect fix. Furthermore, by automatically triggering regression testing through testing, the testing cycle is significantly shortened and test efficiency is improved by over 20%. Seamless integration of online inspections and defect reporting reduces incident response time and enhances system stability, reducing incident response time by 30%.

[0082] In the interface testing system, the use case platform serves as a unified use case management platform, integrating various automated use cases stored in separate locations. Therefore, when a test case needs to be received and saved, it undergoes format verification and pre-processing using the semantic analysis module before being stored in a corresponding hierarchical architecture for easy retrieval, maintenance, and management. Furthermore, the use case platform also facilitates the review of managed test cases. For example, after the use case platform initiates a review task for a current test case, experts conduct online reviews based on criteria such as use case coverage, effectiveness, execution efficiency, and maintainability assessment details, marking issues and providing comments and suggestions. These comments are then aggregated and fed back to the use case platform, thereby obtaining online review information. Based on this online review information, the use case platform then obtains the corresponding review results, including pass rate and defect severity distribution. Based on the review results, it can determine whether the current test case passes, requires optimization and modification, or requires re-review, thereby ensuring test case quality and improving testing accuracy and efficiency.

[0083] In some embodiments, the method for interface testing also includes: when receiving the current test case, the use case platform performs format and semantic preprocessing on the current test case, determines the current storage location corresponding to the current test case in the hierarchical architecture, and performs corresponding storage; when initiating a review task for the current test case, the use case platform obtains online review information, and obtains current quality information of the current test case based on the online review information.

[0084] Correspondingly, in the system for interface testing, the use case platform 200 is configured to, upon receiving the current test case, perform format and semantic preprocessing on the current test case, determine the current storage location corresponding to the current test case in the hierarchical architecture, and perform corresponding storage; and, upon initiating a review task for the current test case, obtain online review information, and obtain current quality information of the current test case based on the online review information.

[0085] It can be seen that the use case platform can manage the entire life cycle of test cases, manage and review and optimize the quality of test cases, improve the quality and management efficiency of test cases, and reduce the risk of test omissions.

[0086] In the system for interface testing, the API management platform 300 builds an interface definition central library and manages the relevant information of the entered interfaces. In this way, once the interface definition central library changes, the API management platform 300 can synchronize with other related platforms with one click. That is, in some embodiments, the method for interface testing also includes: when receiving the current interface change information, the API management platform normalizes the current interface change information, stores the corresponding interface information, generates a corresponding interface change notification, and sends it, so that one or more related platforms, when receiving the interface change notification, update the corresponding interface information according to the interface change notification.

[0087] The one-click synchronization process may include: the use case platform 200 subscribes to the interface definition central library change notification, that is, after the API management platform sends a change notification, the use case platform 200 can receive the update, and then, according to the mapping rules such as the interface unique identifier association and parameter mapping relationship table, it can automatically compare and update the interface call configuration and parameter verification logic in the use case platform 200; while other modules, such as the interface document system in the API management platform 300, also synchronously refresh the interface document content to ensure the consistency and timeliness of interface information in each link. It can be seen that the one-click synchronization mechanism uses message queues and data consistency verification to ensure accurate and efficient data synchronization, reduce the risk of testing and development collaboration caused by interface definition changes, and improve software integration stability.

[0088] Correspondingly, in the system used for interface testing, when the current interface change information is received, the API management platform 300 is configured to normalize the current interface change information, store the corresponding interface information, and generate the corresponding interface change notification and send it, so that one or more related platforms can update the corresponding interface information according to the interface change notification when receiving the interface change notification.

[0089] The use case platform 200 is configured to automatically compare and update the interface call configuration and parameter verification logic in the use case platform 200 according to the mapping rules after obtaining the interface change notification through subscription.

[0090] It can be seen that the synchronization mechanism, change notification mechanism, use case and document synchronization update logic of the API management platform can ensure data consistency and reduce the collaboration error rate. In some embodiments, the collaboration error rate can be reduced by more than 5%.

[0091] In step 203, in some embodiments, the current test results may be sent to a result summary and analysis module, which then analyzes and integrates the current test results and the stored test results related to the interface to generate a corresponding interface test report. The result summary and analysis module may integrate the collected data and perform visualization and analysis.

[0092] Test data collected from multiple sources such as testing platforms, log systems, and defect management platforms, for example, covers interface function test results, performance indicators, defect data, use case execution count statistics, etc., and undergoes data cleaning, such as removing redundancy and erroneous data, and then undergoes normalization, format unification, and other conversion processes. Finally, it is aggregated by classifying and summarizing test rounds and interface modules, and stored in the corresponding data warehouse of the result summary and analysis module.

[0093] During visualization and analysis, customizable dashboards can be created based on user role information and business scenarios. These dashboards include dynamic charts displaying interface coverage, pass rate trends, and defect stacking by module and time. User role information can include: developers focusing on code-level test metrics, testers focusing on use case execution and defect distribution, and project managers focusing on overall quality trends and resource utilization efficiency. This visualization and analysis empowers R&D teams with precise insights into testing progress, enabling efficient decision-making and optimization strategies, and improving R&D and testing collaboration and quality control.

[0094] Therefore, in some embodiments, the method for interface testing also includes: determining the current visual dashboard corresponding to the current user role information and the current business scenario information; and performing corresponding visual presentation through the current visual dashboard based on the test results corresponding to the test event, the log system data, and the test data corresponding to the defect management platform.

[0095] Correspondingly, in the system used for interface testing, the testing platform 100 is also configured to determine the current visual dashboard corresponding to the current user role information and the current business scenario information; and perform corresponding visual presentation through the current visual dashboard based on the test results corresponding to the testing event, the log system data, and the test data corresponding to the defect management platform.

[0096] It can be seen that visual presentation and analysis can help to make accurate decisions, make R&D resource allocation more reasonable, and make quality improvement strategies more efficient. It can comprehensively promote software development from traditional discrete operations to a new stage of integrated intelligent collaboration, and significantly improve the market competitiveness of software products and the R&D efficiency of enterprises.

[0097] The following operation procedures are grouped into specific embodiments to illustrate the interface testing process provided by the embodiments of the present invention.

[0098] In one embodiment of the present disclosure, Figure 1 As shown, the interface testing system may include: a testing platform, a use case platform, an API management platform, a defect management platform, and an event center platform. As mentioned above, in this embodiment, the API management platform builds an interface definition central library, and the testing platform may also include a result summary and analysis module.

[0099] Figure 3 FIG. 1 is a schematic diagram of a signaling interaction for interface testing provided by an embodiment of the present disclosure. Figure 3 As shown, the interface testing process includes:

[0100] Step 301: During the interface automated inspection process, the event center platform captures the current inspection abnormality event.

[0101] Inspection abnormal events include: interface response timeout, return data error, abnormal status code, etc.

[0102] Step 302: The event center platform determines the severity and impact scope of the current inspection abnormal event based on the abnormality type and the predefined rule engine, and associates it with the corresponding defect template to determine it as the current defect template.

[0103] Step 303: The event center platform obtains a current defect report based on the current inspection abnormal event and the corresponding current defect template.

[0104] Step 304: Upon receiving the user's test request instruction, the event center platform sends the current defect report to the defect management platform.

[0105] Step 305: The defect management platform determines the second current repair task information that matches the current defect report based on the attribution information corresponding to the current defect template and the stored developer skill information, and pushes the second current repair task information to be executed.

[0106] It can be seen that the integration of online inspection and defect reporting reduces accident response time and enhances system stability.

[0107] Step 306: The test request platform captures the second test request event after the corresponding repair is completed according to the second repair task information, and determines it as the current test request event.

[0108] By automatically triggering regression testing through test submission, the test cycle can be greatly shortened and test efficiency can be improved.

[0109] Step 307: The testing platform determines the current regression test case set corresponding to the current testing event.

[0110] Step 308: The testing platform determines the dynamic regression test plan based on the current test resources that match the current test event, and controls the corresponding test execution node to call the current regression test case set from the use case platform according to the dynamic regression test plan and the interface information managed by the application programming interface API management platform to perform the corresponding interface test.

[0111] Step 309: The test platform obtains the current test result fed back by the test execution node and sends it to the result summary and analysis module for storage.

[0112] Step 310: The result summary and analysis module in the testing platform determines the current visualization dashboard corresponding to the current user role information and the current business scenario information.

[0113] Step 311: The result summary and analysis module in the test platform performs corresponding visualization through the current visualization dashboard based on the saved test results, log system data, and test data corresponding to the defect management platform.

[0114] Deep integration across multiple platforms, including the testing platform, use case platform, and API management platform, allows for the rational allocation of testing resources corresponding to current testing events and the execution of corresponding interface tests. This results in more rational allocation of testing resources and more efficient quality improvement strategies, further improving the accuracy and efficiency of interface testing. Furthermore, visualization and analysis facilitate accurate decision-making, making R&D resource allocation more rational and quality improvement strategies more efficient. This comprehensively propels software R&D from traditional discrete operations to a new stage of integrated intelligent collaboration, significantly enhancing the market competitiveness of software products and the efficiency of enterprise R&D.

[0115] Step 312: When the current test case is received, the use case platform performs format and semantic preprocessing on the current test case, determines the current storage location corresponding to the current test case in the layered architecture, and performs corresponding storage.

[0116] The use case platform organizes test cases in a layered architecture for easy retrieval, maintenance, and management.

[0117] Step 313: When initiating a review task for the current test case, the use case platform obtains online review information and obtains current quality information of the current test case based on the online review information.

[0118] After the use case platform initiates a review task, experts conduct online reviews based on the review criteria, identify issues, and provide comments and suggestions. These comments are then aggregated and fed back to the platform. The platform then obtains the online review information and uses it to determine the current quality of the test case, including whether it passes, requires optimization, revisions, or requires re-review. This ensures the quality of the test case and improves testing accuracy and efficiency.

[0119] Step 314: After receiving the current interface change information, the API management platform normalizes the current interface change information, stores the corresponding interface information, and generates and sends the corresponding interface change notification.

[0120] The interface document system in the API management platform can synchronously refresh the interface document content.

[0121] Step 315: When the use case platform obtains the interface change notification through subscription, it automatically compares and updates the interface call configuration and parameter verification logic in the test case according to the mapping rules.

[0122] It can be seen that in this embodiment, multiple platforms such as the testing platform, use case platform, API management platform, defect management platform and event center platform are deeply integrated, and regression testing is automatically triggered by testing, which greatly shortens the test cycle and improves test efficiency; online inspections and defect reporting are seamlessly connected, reducing accident response time and enhancing system stability; use case platform review optimizes use case quality and reduces the risk of test omissions; API management platform and multiple platforms are synchronized with one click to ensure data consistency and reduce collaborative error rate; visual presentation and analysis can assist in accurate decision-making, make test resource allocation more reasonable, and make quality improvement strategies more efficient, comprehensively promote software development from traditional discrete operations to a new stage of integrated intelligent collaboration, and significantly improve the market competitiveness of software products and the R&D efficiency of enterprises.

[0123] According to the above-mentioned process for interface testing, an apparatus for interface testing can be constructed.

[0124] Figure 4 This is a schematic diagram of the structure of an interface testing device provided by an embodiment of the present disclosure. Figure 4 As shown, the device can be applied to a testing platform, and includes: a use case determination module 410, a testing module 420, and a result summary and analysis module 430.

[0125] The use case determination module 410 is configured to determine the current regression test case set corresponding to the current test event when the current test event is captured;

[0126] The test module 420 is configured to determine a dynamic regression test plan based on the current test resources that match the current test event, and control the corresponding test execution node to call the current regression test case set from the use case platform according to the dynamic regression test plan and the interface information managed by the application programming interface (API) management platform to perform the corresponding interface test;

[0127] The result summary and analysis module 430 is configured to generate a corresponding interface test report according to the current test result fed back by the test execution node.

[0128] In some embodiments, further comprising:

[0129] The first capture module is configured to send the test failure information to the defect management platform when the current test result includes the test failure information, so that the defect management platform determines the first repair task information that matches the test failure information; and capture the first test event after the corresponding repair is completed according to the first repair task information.

[0130] In some embodiments, further comprising:

[0131] The second capture module is configured to capture a second test event after the corresponding repair is completed according to the second repair task information, wherein the second repair task information is obtained after the defect management platform obtains the defect report obtained according to the inspection abnormal event.

[0132] In some embodiments, the result summary and analysis module 430 is specifically configured to determine the current visualization dashboard corresponding to the current user role information and the current business scenario information; and perform corresponding visualization presentation through the current visualization dashboard based on the test results corresponding to the test event, the log system data, and the test data corresponding to the defect management platform.

[0133] It can be seen that in this embodiment, the device for interface testing can determine the current regression test case set corresponding to the current test event, and after formulating a dynamic regression test plan, it can call the current regression test case set from the use case platform by controlling the corresponding test execution node according to the dynamic regression test plan and the interface information managed by the application programming interface API management platform to perform the corresponding interface test. It can also perform visual analysis and presentation based on the current test results fed back by the test execution node. In this way, the test resource allocation can be more reasonable and the quality improvement strategy can be more efficient, further improving the accuracy and efficiency of the interface test. In addition, visual presentation and analysis can help to make accurate decisions, make the test resource allocation more reasonable, and make the quality improvement strategy more efficient, and comprehensively promote software development from traditional discrete operations to a new stage of integrated intelligent collaboration, significantly improving the market competitiveness of software products and the R&D benefits of enterprises.

[0134] Figure 5 This is a schematic diagram of the structure of an interface testing device provided by an embodiment of the present disclosure. Figure 5 As shown, the device can be applied to a defect management platform, and includes: a report acquisition module 510 and a confirmation push module 520.

[0135] The report acquisition module 510 is configured to obtain the current defect report, wherein the current defect report is obtained based on the current inspection abnormality event in the interface automated inspection process and the corresponding current defect template. The current defect template is determined by the event center platform after capturing the current inspection abnormality event.

[0136] The determination push module 520 is configured to determine the second current repair task information matching the current defect report according to the attribution information corresponding to the current defect template and the stored developer skill information, and push the second current repair task information so that it is executed.

[0137] It can be seen that in this embodiment, the interface testing device can complete the closed-loop management verified by the testers' regression, ensuring that defects are handled in a timely and effective manner, improving the reliability and stability of the system, and seamlessly connecting online inspections with defect reporting, reducing the accident response time and enhancing system stability.

[0138] Figure 6 This is a schematic diagram of the structure of an interface testing device provided by an embodiment of the present disclosure. Figure 6 As shown, the device can be applied to a use case platform, including: a pre-processing module 610 and an online review module 620.

[0139] The preprocessing module 610 is configured to, upon receiving a current test case, perform format and semantic preprocessing on the current test case, determine a current storage location corresponding to the current test case in the hierarchical architecture, and store the location accordingly;

[0140] The online review module 620 is configured to obtain online review information when initiating a review task for the current test case, and obtain current quality information of the current test case based on the online review information.

[0141] In some embodiments, it further includes:

[0142] The update module is configured to automatically compare and update the stored interface call configuration and parameter verification logic according to the mapping rules after obtaining the interface change notification through subscription.

[0143] It can be seen that in this embodiment, the interface testing device performs full life cycle management on test cases, manages and reviews test case quality, improves case quality and management efficiency, and reduces the risk of test omissions.

[0144] Figure 7 This is a schematic diagram of the structure of an interface testing device provided by an embodiment of the present disclosure. Figure 7 As shown, the device can be applied to an API management platform, including: a specification storage module 710 and a change notification module 720.

[0145] The standard storage module 710 is configured to, upon receiving the current interface change information, perform standardization processing on the current interface change information and then store the corresponding interface information.

[0146] The change notification module 720 is configured to generate and send a corresponding interface change notification, so that one or more related platforms update corresponding interface information according to the interface change notification when receiving the interface change notification.

[0147] It can be seen that the synchronization mechanism, change notification mechanism, use case and document synchronization update logic used for interface testing devices can ensure data consistency and reduce the collaboration error rate.

[0148] Combine Figure 8 , an embodiment of the present disclosure provides an apparatus 800 for interface testing, comprising:

[0149] Processor 1000 and memory 1001 may also include a communication interface 1002 and a bus 1003. Processor 1000, communication interface 1002, and memory 1001 may communicate with each other via bus 1003. Communication interface 1002 may be used for information transmission. Processor 1000 may invoke logic instructions in memory 1001 to execute the interface testing method of the above embodiment.

[0150] In addition, the logic instructions in the memory 1001 can be implemented in the form of software functional units and can be stored in a computer-readable storage medium when sold or used as an independent product.

[0151] Memory 1001, as a computer-readable storage medium, can be used to store software programs and computer-executable programs, such as program instructions / modules corresponding to the methods in the embodiments of the present disclosure. Processor 1000 executes the program instructions / modules stored in memory 1001 to perform functional applications and data processing, thereby implementing the method for interface testing in the above-mentioned method embodiments.

[0152] The memory 1001 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and at least one application required for a function; the data storage area may store data created according to the use of the terminal device, etc. In addition, the memory 1001 may include a high-speed random access memory and a non-volatile memory. For example: the memory 1001 may be Figure 1 The external memory in can be Flash.

[0153] An embodiment of the present disclosure provides an interface testing device, comprising: a processor and a memory storing program instructions, wherein the processor is configured to execute an interface testing method when executing the program instructions.

[0154] An embodiment of the present disclosure provides a storage medium storing program instructions, which, when run, execute the above-mentioned method for interface testing.

[0155] An embodiment of the present disclosure provides a computer program product, which includes a computer program stored on a storage medium. The computer program includes program instructions. When the program instructions are executed by a computer, the computer executes the above-mentioned interface testing method.

[0156] The aforementioned storage medium may be a transient computer-readable storage medium or a non-transitory computer-readable storage medium.

[0157] The technical solution of the embodiments of the present disclosure may be embodied in the form of a software product, which is stored in a storage medium and includes one or more instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in the embodiments of the present disclosure. The aforementioned storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program code, or a transient storage medium.

[0158] The above description and accompanying drawings sufficiently illustrate the embodiments of the present disclosure to enable those skilled in the art to practice them. Other embodiments may include structural, logical, electrical, process, and other changes. The embodiments represent only possible variations. Unless expressly required, individual components and functions are optional, and the order of operations may vary. Portions and features of some embodiments may be included in or substituted for portions and features of other embodiments. The scope of the embodiments of the present disclosure includes the entire scope of the claims and all available equivalents thereof. When used in this application, although the terms "first," "second," etc. may be used in this application to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element can be called a second element, and similarly, a second element can be called a first element, without changing the meaning of the description, as long as all occurrences of "first element" are consistently renamed and all occurrences of "second element" are consistently renamed. The first element and the second element are both elements, but they may not be the same element. Furthermore, the terms used in this application are only used to describe the embodiments and are not intended to limit the claims. As used in the description of the embodiments and claims, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to include the plural forms as well. Similarly, the term "and / or" as used in this application refers to any and all possible combinations of one or more of the associated listings. In addition, when used in this application, the term "comprise" and its variations "comprises" and / or comprising refer to the presence of stated features, wholes, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or groups of these. Without further limitation, an element defined by the phrase "comprising a..." does not exclude the presence of other identical elements in the process, method or apparatus comprising the element. In this article, each embodiment may focus on the differences from other embodiments, and the same and similar parts between the embodiments can be referred to each other. For the methods, products, etc. disclosed in the embodiments, if they correspond to the method part disclosed in the embodiments, then the relevant parts can be referred to the description of the method part.

[0159] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software may depend on the specific application and design constraints of the technical solution. The technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of the present disclosure. The technicians will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0160] In the embodiments disclosed herein, the disclosed methods and products (including but not limited to devices, equipment, etc.) can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units can be merely a logical functional division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between each other shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, and can be electrical, mechanical or other forms. 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 they may be distributed on multiple network units. Some or all of the units may be selected to implement this embodiment according to actual needs. In addition, the functional units in the embodiments of the present disclosure may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0161] The flowcharts and block diagrams in the accompanying drawings show the possible implementation architectures, functions and operations of the systems, methods and computer program products according to the embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment or part of the code, and the module, program segment or part of the code contains one or more executable instructions for implementing the specified logical functions. In some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, or they can sometimes be executed in the opposite order, which can depend on the functions involved. In the descriptions corresponding to the flowcharts and block diagrams in the accompanying drawings, the operations or steps corresponding to different boxes can also occur in an order different from that disclosed in the description, and sometimes there is no specific order between different operations or steps. For example, two consecutive operations or steps can actually be executed substantially in parallel, or they can sometimes be executed in the opposite order, which can depend on the functions involved. Each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented by a dedicated hardware-based system that performs the specified function or action, or may be implemented by a combination of dedicated hardware and computer instructions.

Claims

1. A method for interface testing, characterized in that: include: When the current test event is captured, determine the current regression test case set corresponding to the current test event; Determine the dynamic regression test plan based on the current test resources that match the current test event, and control the corresponding test execution node to call the current regression test case set from the use case platform according to the dynamic regression test plan and the interface information managed by the application programming interface (API) management platform to perform the corresponding interface test; Generate the corresponding interface test report based on the current test results fed back by the test execution node.

2. The method according to claim 1, characterized in that Also includes: If the current test result includes test failure information, the test failure information is sent to the defect management platform, so that the defect management platform determines first repair task information that matches the test failure information; A first test request event is captured after the corresponding repair is completed according to the first repair task information.

3. The method according to claim 1, characterized in that Also includes: A second test request event is captured after the corresponding repair is completed according to the second repair task information, wherein the second repair task information is obtained after the defect management platform obtains the defect report obtained according to the inspection abnormal event.

4. The method according to claim 3, characterized in that The defect management platform acquiring the second repair task information includes: The defect management platform obtains the current defect report, which is obtained based on the current inspection abnormality event during the interface automated inspection process and the corresponding current defect template. The current defect template is determined by the event center platform after capturing the current inspection abnormality event. The defect management platform determines the second current repair task information that matches the current defect report based on the attribution information corresponding to the current defect template and the stored developer skill information, and pushes the second current repair task information to be executed.

5. The method according to any one of claims 1 to 4, characterized in that Also includes: When receiving the current test case, the use case platform performs format and semantic preprocessing on the current test case, determines the current storage location corresponding to the current test case in the layered architecture, and stores it accordingly; When a review task for the current test case is initiated, the use case platform obtains online review information and obtains current quality information of the current test case based on the online review information.

6. The method according to claim 5, characterized in that Also includes: When receiving the current interface change information, the API management platform normalizes the current interface change information, stores the corresponding interface information, generates the corresponding interface change notification and sends it, so that one or more related platforms can update the corresponding interface information according to the interface change notification when receiving the interface change notification.

7. The method according to claim 5, characterized in that Also includes: Determine the current visual dashboard corresponding to the current user role information and current business scenario information; Based on the test results corresponding to the test event, the log system data, and the test data corresponding to the defect management platform, corresponding visualization is presented through the current visualization dashboard.

8. A system for interface testing, characterized in that: include: Testing platform, use case platform, and API management platform, among which, The testing platform is configured to determine the current regression test case set corresponding to the current testing event when the current testing event is captured; determine the dynamic regression test plan based on the current test resources matching the current testing event, and control the corresponding test execution node to call the current regression test case set from the use case platform according to the dynamic regression test plan and the interface information managed by the application programming interface API management platform to perform the corresponding interface test; generate the corresponding interface test report based on the current test results fed back by the test execution node.

9. A device for interface testing, comprising a processor and a memory storing program instructions, characterized in that: The processor is configured to perform the method for interface testing according to any one of claims 1 to 7 when executing the program instructions.

10. A storage medium storing program instructions, characterized in that: When the program instructions are executed, the method for interface testing as described in any one of claims 1 to 7 is executed.

Images