Regression test method and device of test case and electronic equipment
By establishing a correlation between the unique identifier of the end-to-end tracing log and the business ID in complex business processing systems, the target test cases are automatically queried and executed, solving the problem of unclear regression testing scope and achieving efficient and accurate regression testing.
Patent Information
- Application Number
- CN202510776135.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-06-11
- Publication Date
- 2025-10-17
AI Technical Summary
In existing technologies, the scope of regression testing for complex business processing systems cannot be accurately determined, resulting in inaccurate selection of regression test cases, low efficiency, and slow speed due to reliance on manual selection, which cannot efficiently cover the affected interfaces and business processes.
By monitoring software interface changes and establishing a relationship between the unique identifier (UniqueID) and business ID in the end-to-end tracking log, target test cases can be automatically queried and executed, achieving efficient end-to-end regression testing.
It improves the efficiency and accuracy of regression testing, reduces the time for manual selection of use cases, ensures accurate coverage of the impact range, and improves the efficiency of integration testing.
Smart Images
Figure CN120803910A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present disclosure belongs to the technical field of testing, and particularly relates to a regression testing method, device and electronic equipment for test cases. BACKGROUND
[0002] A complex business processing system often contains multiple different software systems, each of which is responsible for processing respective business logic, and the software systems have close business data interaction with each other. Business data flows among the software systems according to processing logic order, and finally completes various complex businesses. End-to-end regression testing of such a complex business processing system is challenging, mainly because the regression range cannot be accurately confirmed, resulting in a large regression range and too many test cases, thus leading to low regression efficiency.
[0003] For example, a complex business processing system includes front-end software A, back-end business processing software B, C, D, E,..., and Z. All the software has relatively complete and mature automated test cases. When software D undergoes some important interface restructuring, it may affect upstream and downstream software, and each software of the entire system needs to be regressed. However, there is currently no efficient method to accurately locate which interfaces or businesses of which software are affected by the changed interfaces of software D, and it is even more difficult to directly correspond to the corresponding test cases. Therefore, the current regression test case selection is based on the experience of test personnel to select regression test cases. This has the following problems: first, manual selection is slow; second, the selected test cases cannot ensure accurate coverage of the affected interfaces and businesses; and third, there are too many test cases, and the execution takes a long time. The above problems all affect the efficiency of integration testing.
[0004] It is understood that there is currently such a problem in the industry, and there is no good method to accurately locate the interfaces and businesses associated with each other among multiple systems and the corresponding test cases, and then to perform targeted end-to-end integration testing.
[0005] Therefore, how to provide a regression testing method that can greatly improve the efficiency and accuracy of regression testing is a technical problem to be solved. SUMMARY
[0006] Therefore, how to provide a regression testing method that can greatly improve the efficiency and accuracy of regression testing is a technical problem to be solved.
[0007] In a first aspect, an embodiment of the present application provides a regression testing method for test cases, the method comprising: If it is monitored that the target interface of the downstream target software of the current software is changed, a first query request is sent to the test case management platform, and the first query request carries the software name of the downstream target software and the interface name of the target interface; Based on the software name of the downstream target software and the interface name of the target interface, a second query request is sent to the end-to-end monitoring processing center through the test case management platform to query the target service ID associated with the software name of the downstream target software and the interface name of the target interface based on the second query request; The target service ID is sent to the test case management platform to query the associated target test case from the database of the test case management platform based on the target service ID; For the change of the target interface, regression testing is performed based on the target test case, and a regression test result is obtained.
[0008] Optionally, the method further comprises: For each service of each test case, an HTTP request generated for each service is obtained, and a full-link tracking log unique mark generated for the HTTP request is obtained; The full-link tracking log unique mark is sequentially transmitted from the current software to the downstream software to be called by the current service in order until the current software successfully receives the return of all downstream software.
[0009] Optionally, before the target service ID associated with the software name of the downstream target software and the interface name of the target interface is queried based on the second query request, the method further comprises: In response to the instruction of the target software executing the current case, the current service calls a plurality of downstream software of the target software, listens through the end-to-end monitoring processing center, obtains the HTTP request information corresponding to the target software, and the HTTP request information corresponding to the plurality of downstream software called in turn; A plurality of key information is obtained by sequentially extracting from the HTTP request information corresponding to the target software and the HTTP request information corresponding to the plurality of downstream software called in turn; By the full-link tracking log unique mark generated for each HTTP request, the logs of all software in the current service calling process are concatenated to obtain a calling link.
[0010] Optionally, the plurality of key information comprises: the full-link tracking log unique mark generated for each HTTP request, the service ID, the current participating software name, and the actually called interface name.
[0011] Optionally, after the call link is obtained, the method further comprises: all software names, all interface names and business IDs associated with the call link are obtained; for any one of the all software, a corresponding association relationship is established between the software name, the corresponding interface name and the business ID; each of the all software is traversed to obtain the corresponding association relationship; the association relationship corresponding to the software is stored in the database.
[0012] Optionally, the method further comprises: if the target software receives the test case management platform Jenkins issued test task to execute the test case, when the target software receives the test case management platform Jenkins issued test task to execute the test case, and after starting to listen to the execution of the target software, all HTTP request information during the execution of the test case is collected through the test execution information processing module; all HTTP request information is extracted to obtain the corresponding full link tracking log unique mark; the full link tracking log unique mark is extracted to obtain the current business ID; the current execution case ID is obtained from the test case management platform Jenkins; an association relationship is established between the current execution case ID and the business ID; the current execution case ID, the business ID and the association relationship are stored in the corresponding database.
[0013] Optionally, after the association relationship between the current execution case ID and the business ID is established, the method further comprises: the association relationship is synchronized to the test case management platform; the corresponding business ID is obtained based on the association relationship; the business ID is written back to the label field of the corresponding test case.
[0014] In a second aspect, an embodiment of the present application provides a regression test system for test cases, and the device comprises: a first sending module, configured to send a first query request to a test case management platform if it is monitored that a target interface of a downstream target software of a current software has changed, wherein the first query request carries a software name of the downstream target software and an interface name of the target interface; The second sending module is configured to send a second query request to the end-to-end monitoring processing center through the test case management platform based on the software name of the downstream target software and the interface name of the target interface, so as to query a target service ID associated with the software name of the downstream target software and the interface name of the target interface based on the second query request; The third sending module is configured to send the target service ID to the test case management platform, so as to query an associated target test case from a database of the test case management platform based on the target service ID. The test module is configured to perform regression testing based on the target test case for the change of the target interface, and obtain a regression testing result.
[0015] In a third aspect, a computer readable storage medium is provided, which stores a computer program. When the computer program is executed in a computer, the computer performs the method of the first aspect.
[0016] In a fourth aspect, an electronic device is provided, which includes a memory and a processor. The memory stores executable code, and the processor executes the executable code to implement the method of the first aspect.
[0017] In the embodiments of the present application, if it is monitored that the target interface of the downstream target software of the current software is changed, a first query request is sent to the test case management platform, and the first query request carries the software name of the downstream target software and the interface name of the target interface. Based on the software name of the downstream target software and the interface name of the target interface, a second query request is sent to the end-to-end monitoring processing center through the test case management platform, so as to query a target service ID associated with the software name of the downstream target software and the interface name of the target interface based on the second query request. The target service ID is sent to the test case management platform, so as to query an associated target test case from a database of the test case management platform based on the target service ID. For the change of the target interface, regression testing is performed based on the target test case, and a regression testing result is obtained. The regression testing method provided in the embodiments of the present application can quickly query the target test case associated with the changed software and interface when the interface of the software is changed, and perform regression testing based on the target test case. Therefore, the efficiency and accuracy of the regression testing can be greatly improved. BRIEF DESCRIPTION OF DRAWINGS
[0018] The exemplary embodiments of the present application can be more fully understood with reference to the following description when taken in connection with the accompanying drawings, in which:
[0019] Figure 1 This is a flow chart for implementing a reverse lookup test case using the changed software name and interface name using the business ID in the unique tag UniqueID in the full-link tracking log containing the business ID. Figure 2 A schematic diagram for establishing and maintaining the relationship data between test cases and business ID items (taking software A as an example); Figure 3 A flowchart of a regression testing method for a test case provided according to an exemplary embodiment of the present invention; Figure 4 1 is a schematic structural diagram of a regression testing apparatus 400 for a test case according to an exemplary embodiment of the present invention. DETAILED DESCRIPTION
[0020] Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments described herein. Rather, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.
[0021] It should be noted that, unless otherwise specified, the technical or scientific terms used in the present invention should have the common meanings understood by those skilled in the art to which the present invention belongs.
[0022] In addition, the terms "first" and "second" are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, apparatus, product, or device comprising a series of steps or elements is not limited to the listed steps or elements, but may optionally include steps or elements not listed, or may optionally include other steps or elements inherent to the process, method, product, or device.
[0023] Embodiments of the present invention provide a regression testing method and apparatus for a test case, a computer-readable medium, and an electronic device, which are described below with reference to the accompanying drawings.
[0024] like Figure 1 As shown, this is a framework diagram corresponding to the regression testing method for implementing test cases in the present invention.
[0025] like Figure 1 As shown, when each software executes a test case, the test execution information processing module collects the full-link tracking log unique identifier UniqueID generated in the business log of the software being executed into its own database.
[0026] In addition, the test execution information processing module associates the UniqueID, business ID and the test case ID being executed generated when the software executes the test case, and stores them in the database. The business ID is also written back to the label field of the test case.
[0027] As shown in Figure 1 , software A executes a test case, and sending 5 requests to the downstream software is required to complete all test case steps, each request being a business, and each business generates an HTTP request. When the request is generated, software A generates a full-link tracking log unique mark UniqueID for the request. This UniqueID has a design specification, and all software in the system generates the UniqueID of its own business according to the unified specification. During the processing of each business, the UniqueID is transmitted to the downstream software that needs to be called through the HTTP request header in sequence until software A successfully receives the return of the downstream software, and the business is completed. This unique UniqueID runs through the entire calling link.
[0028] In a specific application scenario, if a test test case needs to handle 5 businesses, then the test case will generate 5 such UniqueIDs.
[0029] As shown in Figure 1 , during the execution of the test case by software A, the first business calls three downstream software, which are software B, software C and software D. During the processing of this business by the four different software, the end-to-end monitoring processing center listens and collects the HTTP request information of software A and the called software, and extracts the UniqueID, business ID, current participating software name and actual interface name called from the information. The extracted UniqueID, business ID, current participating software name and actual interface name are all stored in the database. The UniqueID is linked with the logs of all software called for the business handling. The end-to-end monitoring processing center combs to form a complete calling link: software A->software B->software C->software D. In addition, the software name, interface name and business ID involved are associated and stored in the database.
[0030] As shown in Figure 1As shown in the figure, assuming that the interface d of the downstream software D of the software A has a large change and needs to be regression tested, a query request can be sent to the test case management platform directly using the software D name and the interface d name, the test case management platform uses the software D name and the interface d name to request the query of the target business ID associated therewith from the end-to-end monitoring processing center and returns the target business ID to the test case management platform, finally, the target test case associated therewith is queried from the database of the test case management platform using the target business ID, so as to perform the regression test for the change, and the purposes of automation, high efficiency and range determination can be achieved.
[0031] As shown in the figure, Figure 2 As shown in the figure, the Jenkins of the test case management platform sends a test task to the software A to execute the test case, and starts to listen to the execution of the software A at the same time, the test execution information processing module is responsible for collecting all HTTP request information in real time when the test case is executed, and extracts the UniqueID in the request header. Further, the current business ID is extracted from the UniqueID; at the same time, the test case ID of the current execution is obtained from the Jenkins of the test case management platform, the test case ID and the business ID are associated and exist in the database. The association relationship between the business ID and the test case ID is synchronized to the test case management platform, and the business ID is written back to the label field of the test case. The test task can be executed regularly, and each execution will update the associated business ID relationship of all test cases. If a change occurs, the business ID in the test case label field will also be updated, so that the purpose of automatic maintenance is achieved.
[0032] Please refer to Figure 3 , which shows a flowchart of a regression test method of a test case provided by some embodiments of the application, as shown in Figure 3 The regression test method of the test case can include the following steps: Step S301: If it is monitored that a target interface of a downstream target software of a current software has changed, a first query request is sent to a test case management platform, and the software name of the downstream target software and the interface name of the target interface are carried in the first query request.
[0033] Step S302: Based on the software name of the downstream target software and the interface name of the target interface, a second query request is sent to an end-to-end monitoring processing center through the test case management platform, so as to query a target business ID associated with the software name of the downstream target software and the interface name of the target interface based on the second query request.
[0034] Step S303: The target business ID is sent to the test case management platform, so as to query an associated target test case from a database of the test case management platform based on the target business ID.
[0035] Step S304: Regression testing is performed based on the target test case for the change of the target interface, and a regression testing result is obtained.
[0036] It should be noted that the regression testing described above is end-to-end integrated regression testing.
[0037] Since each test case can establish an association relationship between the business ID and the software name and interface name of the associated software involved in the business of the test case, when some interfaces of a certain software are changed and end-to-end integrated regression testing is required, the software name and interface name of the changed software can be used to query the associated business ID, and then the business ID can be used to query the test case of the associated software, and the test case can be used to accurately and efficiently perform regression testing within a more accurate impact range.
[0038] In an example, the regression testing method of the test case provided by the embodiment of the application can further include the following steps: For each business of each test case, an HTTP request generated for each business is obtained, and a full-link tracking log unique mark generated for the HTTP request is obtained; The full-link tracking log unique mark is sequentially transmitted from the current software to the downstream software to be called by the current business, until the current software successfully receives the return of all downstream software.
[0039] In an example, before querying the target business ID associated with the software name of the downstream target software and the interface name of the target interface based on the second query request, the regression testing method of the test case provided by the embodiment of the application can further include the following steps: In response to the instruction of the target software to execute the current case, the current business calls a plurality of downstream software of the target software, listens to the end-to-end monitoring processing center, obtains the HTTP request information corresponding to the target software, and the HTTP request information corresponding to the plurality of downstream software called in sequence; The plurality of key information is obtained by sequentially extracting from the HTTP request information corresponding to the target software and the HTTP request information corresponding to the plurality of downstream software called in sequence; The logs of all software of the current business calling process are concatenated by the full-link tracking log unique mark generated for each HTTP request, and a calling link is obtained.
[0040] It should be noted that the full-link tracking log unique mark UniqueID is throughout the full-business calling link from the current software to other downstream software.
[0041] In an example, the plurality of key information includes: a full link tracking log unique mark generated for each HTTP request, a business ID, a current participating software name, and an actual called interface name.
[0042] In an example, after obtaining the call link, the regression test method of the test case provided by the embodiment of the application can further include the following steps: obtaining all software names, all interface names and business IDs associated with the call link; establishing a corresponding association relationship between the software name, the corresponding interface name and the business ID of any one of the software; traversing each of the software to obtain the corresponding association relationship; storing the association relationship corresponding to the software in the database.
[0043] In an example, the regression test method of the test case provided by the embodiment of the application can further include the following steps: if the target software receives the test case executed by the test task issued by the Jenkins of the test case management platform, after the target software receives the test case executed by the test task issued by the Jenkins of the test case management platform, and the execution of the target software is started, all HTTP request information during the execution of the test case is collected by the test execution information processing module; extracting all HTTP request information to obtain the corresponding full link tracking log unique mark; extracting the full link tracking log unique mark to obtain the current business ID; obtaining the case ID currently executed from the Jenkins of the test case management platform; establishing an association relationship between the case ID currently executed and the business ID; storing the case ID currently executed, the business ID and the association relationship in the corresponding database.
[0044] In an example, after establishing the association relationship between the case ID currently executed and the business ID, the regression test method of the test case provided by the embodiment of the application can further include the following steps: synchronizing the association relationship to the test case management platform; obtaining the corresponding business ID based on the association relationship; rewriting the business ID to the label field of the corresponding test case.
[0045] The regression test method provided by the embodiments of the present application can quickly query the target test case associated with the changed software and interface when the interface of the software is changed, and perform regression test based on the target test case, so that the efficiency and accuracy of the regression test can be greatly improved. Further, the regression test method provided by the embodiments of the present application effectively solves the problem that the end-to-end regression test of numerous software in a complex business processing system has low efficiency due to the difficulty in defining the influence range. The regression test method provided by the embodiments of the present application uses the business ID to establish the association between all test cases and all software names and interfaces, when the interface of the software is changed, the test case associated with the interface can be quickly and automatically searched out through the software name and interface name, instead of relying on the experience of the test personnel to manually select the business-related test case from hundreds of thousands of test cases, the speed is greatly improved, the confirmation of the influence range is also more accurate and has basis, the number of test cases searched out is also much smaller than the number of test cases manually selected, and the efficiency and accuracy of the regression test are greatly improved. In addition, the regression test method provided by the embodiments of the present application has the universality of similar scenarios and different software systems, as long as the systems have similar attributes, the regression test method can be used to solve the problem of low end-to-end regression efficiency.
[0046] In the above embodiments, a regression test method of test cases is provided, and the present application also provides a regression test device of test cases. The regression test device of test cases provided by the embodiments of the present application can implement the regression test method of test cases, and the regression test device of test cases can be implemented by software, hardware or a combination of software and hardware. For example, the regression test device of test cases can include integrated or separate functional modules or units to perform the corresponding steps in the above methods.
[0047] Please refer to Figure 4 which shows a schematic diagram of a regression test device of test cases provided by some embodiments of the present application. Since the device embodiments are basically similar to the method embodiments, the description is relatively simple, and the related parts can be referred to the part of the method embodiments. The device embodiments described below are only schematic.
[0048] As Figure 4 shown, the regression test device of test cases 400 can include: A first sending module 401 is configured to send a first query request to a test case management platform if it is monitored that a target interface of a downstream target software of a current software is changed, and the first query request carries a software name of the downstream target software and an interface name of the target interface. A second sending module 402 is configured to send a second query request to the end-to-end monitoring processing center through the test case management platform based on the software name of the downstream target software and the interface name of the target interface, so as to query the target service ID associated with the software name of the downstream target software and the interface name of the target interface based on the second query request; The third sending module 403 is used to send the target service ID to the test case management platform, so as to query the associated target test case from the database of the test case management platform based on the target service ID; The testing module 404 is used to perform regression testing on the target interface changes based on the target test cases to obtain regression testing results.
[0049] In some implementations of the embodiments of the present invention, the regression testing apparatus 400 for the test case may further include: The first acquisition module (in Figure 4 (not shown) for each transaction in each test case, obtaining the HTTP request generated for each transaction, and obtaining the unique tag of the full-link tracking log generated for the HTTP request; Transport module (in Figure 4 (not shown) is used to sequentially transmit the unique mark of the full-link tracking log from the current software to the downstream software to be called by the current business until the current software successfully receives the feedback from all downstream software.
[0050] In some implementations of the embodiments of the present invention, the regression testing apparatus 400 for the test case may further include: Call link determination module (in Figure 4 (not shown) for, before querying the target service ID associated with the software name of the downstream target software and the interface name of the target interface based on the second query request, responding to the target software's instruction to execute the current use case, the current service calls multiple downstream software of the target software, and listening through the end-to-end monitoring processing center to obtain HTTP request information corresponding to the target software and HTTP request information corresponding in sequence to the multiple downstream software called; Extracting multiple key information from the HTTP request information corresponding to the target software and the HTTP request information corresponding to the multiple downstream software being called; By generating a unique tag for the full-link tracking log for each HTTP request, the logs of all software in the current business call process are connected in series to obtain the call link.
[0051] In some implementations of the embodiments of the present invention, multiple key information include: a unique tag of the full-link tracking log generated for each HTTP request, a business ID, the name of the current participating software, and the name of the interface actually called.
[0052] In some implementations of the embodiments of the present invention, the regression testing apparatus 400 for the test case may further include: The first association relationship determination module (in Figure 4 (not shown) for obtaining, after obtaining the call link, all software names, all interface names, and service IDs associated with the call link; For any software among all software, establish a corresponding association between its software name, corresponding interface name and business ID; Traverse each software in all software and obtain the corresponding association relationship; The first storage module (in Figure 4 (not shown) for storing the association relationships corresponding to the software in a database.
[0053] In some implementations of the embodiments of the present invention, the regression testing apparatus 400 for the test case may further include: The second association relationship determination module (in Figure 4 ), used to: If the target software receives a test task issued by Jenkins of the test case management platform to execute the test case, after the target software receives a test task issued by Jenkins of the test case management platform to execute the test case and starts monitoring the execution status of the target software, all HTTP request information during the execution of the test case is collected through the test execution information processing module; Extract all HTTP request information and obtain the corresponding unique tag of the full-link tracking log; Extract the unique tag of the full-link tracking log to obtain the current business ID; Get the currently executed test case ID from Jenkins on the test case management platform; Establish an association between the currently executed use case ID and the business ID; The second storage module (in Figure 4 ), which is used to store the currently executed use case ID, business ID and association relationship in the corresponding database.
[0054] In some implementations of the embodiments of the present invention, the regression testing apparatus 400 for the test case may further include: Synchronous module (in Figure 4The association relationship is synchronized to the test case management platform after the association relationship between the currently executed use case ID and the service ID is established. The second obtaining module (not shown in the figures) is configured to obtain the corresponding service ID based on the association relationship. Figure 4 The second obtaining module (not shown in the figures) is configured to obtain the corresponding service ID based on the association relationship. The write-back module (not shown in the figures) is configured to write back the service ID to the label field of the corresponding test case. Figure 4 The write-back module (not shown in the figures) is configured to write back the service ID to the label field of the corresponding test case.
[0055] In some embodiments of the present application, the regression testing device 400 of the test case provided by the present application has the same beneficial effects as the regression testing method of the test case provided by the aforementioned embodiments of the present application.
[0056] According to another aspect, embodiments also provide a computer readable storage medium having stored thereon a computer program that, when executed in a computer, cause the computer to perform the method described above. Figure 3 According to another aspect, embodiments also provide a computer readable storage medium having stored thereon a computer program that, when executed in a computer, cause the computer to perform the method described above.
[0057] According to another aspect, embodiments also provide an electronic device comprising a memory and a processor, the memory having stored thereon executable code that, when executed by the processor, implements the method described above. Figure 3 According to another aspect, embodiments also provide an electronic device comprising a memory and a processor, the memory having stored thereon executable code that, when executed by the processor, implements the method described above.
[0058] Those skilled in the art should be aware that the functions described in the above one or more examples can be implemented in hardware, software, firmware or any combination thereof. When implemented in software, the functions can be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium. The above detailed description of the specific implementation of the present application further explains the purpose, technical solutions and beneficial effects of the present application. It should be understood that the above detailed description is only a specific implementation of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made on the basis of the technical solutions of the present application should be included in the protection scope of the present application.
Claims
1. A regression testing method for a test case, characterized in that: The method comprises: If a target interface of a downstream target software of the current software is detected to have changed, a first query request is sent to the test case management platform, where the first query request carries the software name of the downstream target software and the interface name of the target interface; Based on the software name of the downstream target software and the interface name of the target interface, sending a second query request to the end-to-end monitoring processing center through the test case management platform to query the target service ID associated with the software name of the downstream target software and the interface name of the target interface based on the second query request; Sending the target service ID to the test case management platform to query the associated target test case from the database of the test case management platform based on the target service ID; For the changes to the target interface, regression testing is performed based on the target test case to obtain regression test results.
2. The regression testing method according to claim 1, wherein: The method further comprises: For each transaction in each test case, obtain the HTTP request generated for each transaction and the unique tag of the full-link tracking log generated for the HTTP request; The unique mark of the full-link tracking log is transmitted sequentially from the current software to the downstream software to be called by the current business until the current software successfully receives feedback from all downstream software.
3. The regression testing method according to claim 2, wherein: Before querying the target service ID associated with the software name of the downstream target software and the interface name of the target interface based on the second query request, the method further includes: In response to the target software's instruction to execute the current use case, the current business calls multiple downstream software of the target software, and listens through the end-to-end monitoring processing center to obtain HTTP request information corresponding to the target software and HTTP request information corresponding to the multiple downstream software called in sequence; Extracting from the HTTP request information corresponding to the target software and the HTTP request information corresponding to the multiple called downstream software in sequence to obtain multiple key information; By generating a unique tag for the full-link tracking log for each HTTP request, the logs of all software in the current business call process are connected in series to obtain the call link.
4. The regression testing method according to claim 3, wherein: The multiple key information include: a unique tag of the full-link tracking log generated for each HTTP request, a business ID, the name of the current participating software, and the name of the interface actually called.
5. The regression testing method according to claim 3, wherein: After obtaining the call link, the method further includes: Obtain all software names, all interface names, and service IDs associated with the call link; For any software among all software, establish a corresponding association between its software name, corresponding interface name and business ID; Traverse each software in all software and obtain the corresponding association relationship; The association relationships corresponding to the software are all stored in a database.
6. The regression testing method according to claim 1, wherein: The method further comprises: If the target software receives a test task issued by Jenkins of the test case management platform to execute the test case, after the target software receives a test task issued by Jenkins of the test case management platform to execute the test case and starts monitoring the execution status of the target software, all HTTP request information during the execution of the test case is collected through the test execution information processing module; Extract all HTTP request information and obtain the corresponding unique tag of the full-link tracking log; Extract the unique tag of the full-link tracking log to obtain the current business ID; Get the currently executed test case ID from Jenkins on the test case management platform; Establish an association between the currently executed use case ID and the business ID; The currently executed use case ID, the business ID and the association relationship are stored in the corresponding database.
7. The regression testing method according to claim 6, characterized in that: After establishing an association relationship between the currently executed use case ID and the service ID, the method further includes: Synchronize the association relationship to the test case management platform; Obtaining a corresponding business ID based on the association relationship; Write the service ID back to the tag field of the corresponding test case.
8. A regression testing system for test cases, characterized in that: The system comprises: A first sending module is configured to send a first query request to the test case management platform if a target interface of a downstream target software of the current software is detected to have changed, wherein the first query request carries the software name of the downstream target software and the interface name of the target interface; a second sending module, configured to send a second query request to the end-to-end monitoring processing center through the test case management platform based on the software name of the downstream target software and the interface name of the target interface, so as to query a target service ID associated with the software name of the downstream target software and the interface name of the target interface based on the second query request; A third sending module is used to send the target service ID to the test case management platform, so as to query the associated target test case from the database of the test case management platform based on the target service ID; The test module is used to perform regression testing on the target interface based on the target test case and obtain regression test results.
9. A computer-readable storage medium, characterized in that A computer program is stored thereon, which, when executed in a computer, causes the computer to execute the method according to any one of claims 1 to 7.
10. An electronic device, characterized in that: The method comprises a memory and a processor, wherein the memory stores executable code, and when the processor executes the executable code, the method according to any one of claims 1 to 7 is implemented.