CN111290941A - Method and device for testing multiple interfaces, computing equipment and medium - Google Patents

Method and device for testing multiple interfaces, computing equipment and medium Download PDF

Info

Publication number
CN111290941A
CN111290941A CN201811505029.XA CN201811505029A CN111290941A CN 111290941 A CN111290941 A CN 111290941A CN 201811505029 A CN201811505029 A CN 201811505029A CN 111290941 A CN111290941 A CN 111290941A
Authority
CN
China
Prior art keywords
test
interface
result
interfaces
module
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN201811505029.XA
Other languages
Chinese (zh)
Inventor
张婷婷
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Jingdong Century Trading Co Ltd
Beijing Jingdong Shangke Information Technology Co Ltd
Original Assignee
Beijing Jingdong Century Trading Co Ltd
Beijing Jingdong Shangke Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Jingdong Century Trading Co Ltd, Beijing Jingdong Shangke Information Technology Co Ltd filed Critical Beijing Jingdong Century Trading Co Ltd
Priority to CN201811505029.XA priority Critical patent/CN111290941A/en
Publication of CN111290941A publication Critical patent/CN111290941A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3688Test management for test execution, e.g. scheduling of test suites

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The present disclosure provides a method, an apparatus, a computer device and a medium for testing a plurality of interfaces, the method comprising: configuring interface parameters of the plurality of interfaces to obtain an interface structure, so that the plurality of interfaces meet a calling sequence in an application scene, wherein the interface structure comprises an input parameter and an output parameter, and the output parameter comprises an interface structure output parameter or an interface structure output parameter and at least one interface output parameter; assigning the test data of at least one test case to the input parameters of the interface structure to obtain the output parameter values of the interface structure as test results; and acquiring a case test result according to the test result and the expected result.

Description

Method and device for testing multiple interfaces, computing equipment and medium
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for testing multiple interfaces, a computing device, and a medium.
Background
The interface test is mainly used for detecting interaction points between external systems and between internal subsystems, and the test is mainly used for checking data exchange, transmission, control and management processes, mutual logic dependency relations between systems and the like. With the continuous increase of the complexity of the system, the cost of the traditional test method is increased sharply, the test efficiency is reduced greatly, and the interface test can provide a solution under the condition.
In the prior art, a single interface is mainly tested, for example, tests on different conditions of the single interface are realized by using Postman, JMeter or other automation frameworks (Django). In addition, there is a Mock test to test some objects that are not easily conceived.
However, for the situations that a plurality of interfaces are requested simultaneously, methods between the interfaces are called internally, intermediate results need to be thrown, and the like, the creation of each test case, application scene, and the like needs to check the stored results once, so that the workload is very large, and the repeated work is frequent.
Disclosure of Invention
In view of this, the present disclosure provides a method, an apparatus, a computing device, and a medium for testing multiple interfaces, which can solve the problem that when multiple interfaces are simultaneously requested and intermediate results need to be thrown, each test case or application scenario is not easily created.
One aspect of the present disclosure provides a method for testing a plurality of interfaces, including: firstly, configuring interface parameters of a plurality of interfaces to obtain an interface structure, enabling the plurality of interfaces to meet a calling sequence in an application scene, wherein the interface structure comprises an input parameter and an output parameter, the output parameter comprises an interface structure output parameter or an interface structure output parameter and at least one interface output parameter, then assigning test data of at least one test case to the input parameter of the interface structure, obtaining a parameter value of the interface structure as a test result, and obtaining a case test result according to the test result and an expected result.
According to an embodiment of the present disclosure, the configuring the interface parameters of the plurality of interfaces to obtain an interface structure may include: firstly, determining a plurality of interfaces and the calling sequence of the plurality of interfaces according to the calling sequence and the application scene of each interface in a code, and then configuring interface parameters of the plurality of interfaces so that the plurality of interfaces meet the calling sequence, wherein the interface parameters comprise any one or more of the following: the method comprises the steps of protocol type, interface address, interface method name, interface input parameter and interface output parameter, and in addition, the mapping relation between the interface address and the IP address of the test server is required to be configured according to the test environment. Thus, an interface structure satisfying a certain application scenario can be obtained.
According to an embodiment of the present disclosure, the interface method name includes any one or more of: an information request, a header request, a processing request, a deletion request, a local modification request, a transfer request, or a method return request.
According to an embodiment of the present disclosure, the method may further include an operation of changing the corresponding interface parameter when the calling order is changed; and/or when the test environment is changed, changing the mapping relation between the corresponding interface address and the IP address of the test server. Therefore, maintenance can be simply and timely carried out when the calling sequence of certain interfaces in the application scene is changed, and timely change is conveniently carried out when the testing environment, such as a testing host, is changed.
According to an embodiment of the present disclosure, assigning the test data of the at least one test case to the entry parameters of the interface structure may include, for example, first obtaining the test case, where the test case includes a test variable and corresponding test data, then storing the test variable and the corresponding test data in a readable and writable file, and then setting a data value path of the entry parameters corresponding to the test data. Therefore, the value of the parameter of the test case can be quickly and accurately modified, and the test case does not need to be regenerated when the value of the parameter of the test case is changed.
According to an embodiment of the present disclosure, the test result is stored in a database, the method may further include the following operation, first, presetting a database field name and a field value, where the database field name and the field value may be used as an identifier of a result that needs to be focused on, and accordingly, obtaining a case test result according to the test result and the expected result may include: and comparing the test result and the expected result corresponding to the field name and the field value of the database, and if the test result and the expected result are different, acquiring the difference and a log corresponding to the difference. Therefore, important results can be focused on, and logs can be timely thrown out when the important results are abnormal so as to analyze reasons.
According to the embodiment of the disclosure, the method may further include the following operation that after the interface structure is obtained, an assembly is added, so that the expected result and the test result may be imported through the assembly and displayed, and the visualization of the test result is realized, which is helpful for improving the detection efficiency of a tester.
According to an embodiment of the present disclosure, the method may further include performing a regression test on the partial test cases through the test case switch when there is a difference between the test result of the partial test cases and the expected result. Because the interface structure that this disclosure provided can run a plurality of test cases simultaneously, when some test cases appear unusually, can only test unusual test case through the simple quick realization of test case switch, improve the convenient degree of test.
Another aspect of the present disclosure provides a testing apparatus for multiple interfaces, including an interface configuration module, a testing module, and a result obtaining module, where the interface configuration module is configured to configure interface parameters of the multiple interfaces to obtain an interface structure, so that the multiple interfaces satisfy a calling order in an application scenario, the interface structure includes an entry parameter and an exit parameter, the exit parameter includes an interface structure exit parameter or an interface structure exit parameter and at least one interface exit parameter, the testing module is configured to assign test data of at least one test case to the entry parameter of the interface structure, obtain a value of the exit parameter of the interface structure as a testing result, and the result obtaining module is configured to obtain a case testing result according to the testing result and an expected result.
According to an embodiment of the present disclosure, the interface configuration module may include a calling order obtaining unit, a first configuration unit, and a second configuration unit, where the calling order obtaining unit is configured to determine a plurality of interfaces and calling orders of the plurality of interfaces according to a calling order and an application scenario of each interface in a code, the first configuration unit is configured to configure interface parameters of the plurality of interfaces so that the plurality of interfaces satisfy the calling order, and the interface parameters include any one or more of: the second configuration unit is used for configuring the mapping relation between the interface address and the IP address of the test server according to the test environment.
According to an embodiment of the present disclosure, the interface method name may include any one or more of: an information request, a header request, a processing request, a deletion request, a local modification request, a transfer request, or a method return request.
According to an embodiment of the present disclosure, the apparatus may further include: the device comprises a first changing module and a second changing module, wherein the first changing module is used for changing corresponding interface parameters when the calling sequence is changed, and the second changing module is used for changing the mapping relation between the IP address and the host name of the corresponding test host when the testing environment is changed.
According to an embodiment of the present disclosure, the test module may include a test case obtaining unit, a storage unit, and a first setting unit. The test case obtaining unit is used for obtaining a test case, the test case comprises test variables and corresponding test data, the storage unit is used for storing the test variables and the corresponding test data in a readable and writable file, and the first setting unit is used for setting a data value path of an input parameter corresponding to the test data.
According to an embodiment of the disclosure, the result obtaining module may be specifically configured to compare the test result with the expected result to obtain a case test result.
According to an embodiment of the present disclosure, the storage unit may be further configured to store the test result in a database, and accordingly, the apparatus may further include a setting module, where the setting module is configured to preset a database field name and a field value. Correspondingly, the result obtaining module may include a comparing unit and a log obtaining unit, wherein the comparing unit is configured to compare a test result and an expected result corresponding to the field name and the field value of the database, and the log obtaining unit is configured to obtain a difference and a log corresponding to the difference if the test result and the expected result are different.
According to an embodiment of the present disclosure, the apparatus may further include a component adding module and a displaying module, wherein the component adding module is configured to add a component after obtaining the interface structure, and the displaying module is configured to import the expected result and the test result through the component and display the expected result and the test result. Optionally, the component adding module includes a second setting unit and an importing unit, where the second setting unit is configured to set a data dereferencing path of a database field name and a field value corresponding to the test result, and the importing unit is configured to import the expected result and the test result through the component.
According to the embodiment of the disclosure, the apparatus may further include a case switch module, where the case switch module is configured to implement a regression test on the partial test cases through the test case switch when a difference exists between a test result of the partial test cases and an expected result.
Another aspect of the disclosure provides a computing device that may include one or more processors, and storage for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, implement the method as described above.
Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions for implementing the method as described above when executed.
Another aspect of the disclosure provides a computer program comprising computer executable instructions for implementing the method as described above when executed.
According to the embodiment of the disclosure, the problem that in the prior art, when different testers test the same application scene, test cases need to be repeatedly created or test scenes need to be created can be at least partially solved, and the intermediate result can be thrown out so that the testers can assist in positioning the defect reasons according to the logs corresponding to the intermediate result, which is beneficial to improving the defect of black box testing.
According to the embodiment of the disclosure, the calling sequence of the configuration interface is consistent with the code implementation, and the accuracy of the test result can be improved. This is because there may not be only one system or subsystem that can implement a certain function, but these systems or subsystems are not completely the same, and the corresponding interfaces are configured according to the calling order of the interfaces in the code, so that it can be at least partially avoided that the called interfaces are inconsistent with the interfaces in the code, which results in an exception that cannot be detected, or that the test result is abnormal.
According to the embodiment of the disclosure, the corresponding relation between the field names and the field values is realized after data is imported, so that the focus result can be conveniently focused, and the testing efficiency is improved.
Drawings
The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments of the present disclosure with reference to the accompanying drawings, in which:
FIG. 1A schematically illustrates a schematic view of an olive model of a test field according to an embodiment of the disclosure;
FIG. 1B schematically illustrates an application scenario of a method, apparatus, computing device and medium for testing multiple interfaces according to an embodiment of the present disclosure;
FIG. 1C schematically illustrates a diagram of a plurality of interface calls, according to an embodiment of the disclosure;
FIG. 2A schematically illustrates a flow chart of a method of testing a plurality of interfaces according to an embodiment of the present disclosure;
FIG. 2B schematically illustrates an interface parameter configuration diagram according to an embodiment of the disclosure;
FIG. 2C schematically illustrates a flow chart of a method of testing a plurality of interfaces according to another embodiment of the present disclosure;
FIG. 2D schematically illustrates a flow chart of a method of testing a plurality of interfaces according to another embodiment of the present disclosure;
FIG. 3A schematically illustrates a block diagram of a test setup for multiple interfaces according to an embodiment of the present disclosure;
FIG. 3B schematically illustrates a block diagram of a test setup for multiple interfaces according to another embodiment of the present disclosure;
FIG. 3C schematically illustrates a block diagram of a test setup for multiple interfaces according to another embodiment of the present disclosure;
FIG. 4 schematically illustrates a block diagram of a computer system suitable for implementing a testing method for multiple interfaces according to an embodiment of the disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.
Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase "a or B" should be understood to include the possibility of "a" or "B", or "a and B".
The embodiment of the disclosure provides a method and a device for testing a plurality of interfaces, computing equipment and a medium. The method comprises an interface structure configuration process and a test process. In the interface structure configuration process, interface parameters of the plurality of interfaces are configured to obtain an interface structure, so that the plurality of interfaces meet a calling sequence in an application scene, wherein the interface structure comprises an input parameter and an output parameter, and the output parameter comprises an interface structure output parameter or an interface structure output parameter and at least one interface output parameter. After the configuration of the interface structure is completed, a test process is started, test data of at least one test case is assigned to input parameters of the interface structure, output parameters of the interface structure are obtained and used as test results, and then case test results are obtained according to the test results and expected results.
Fig. 1A schematically illustrates a schematic view of an olive model in the field of testing according to an embodiment of the present disclosure. As shown in fig. 1A, the conventional test mainly includes a User Interface (UI) test, an Application Programming Interface (API) test, and a Unit (Unit) test, where the Application Programming Interface test is hereinafter referred to as an Interface test. Generally, the lower level of testing, such as unit testing, is more stable, efficient and less costly, but the more investment that is relatively needed, the higher the requirements for technical expertise. Considering the above problems comprehensively, the olive model is proposed, and after comparing the interface test with the UI test and the unit test, the highest return on investment of the interface test is finally determined.
Fig. 1B schematically illustrates an application scenario of a method, an apparatus, a computing device, and a medium for testing multiple interfaces according to an embodiment of the present disclosure. An exemplary system architecture 100 is shown in fig. 1B. It should be noted that fig. 1B is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.
As shown in fig. 1B, the system architecture 100 according to this embodiment may include one or more servers 101, and a network 102 connecting the plurality of servers 101. Network 102 serves as a medium for providing communication links between servers 101. Network 102 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The server 101 may be a variety of electronic devices having a display screen and supporting a test system, including but not limited to laptop portable computers, desktop computers, server clusters, and the like. In particular, the server 101 may be an electronic device providing a test service, for example, for detecting interaction points between external systems and between subsystems within the systems.
It should be noted that the testing method for multiple interfaces provided by the embodiment of the present disclosure may be generally performed by the server 101, for example, only one server 101 is used for testing, and of course, if conditions allow, multiple servers 101 may also be used for testing, for example, different systems are installed on different servers 101 to be closer to the real application environment. Accordingly, the testing device for multiple interfaces provided by the embodiments of the present disclosure may be generally disposed in the server 101. The testing method for multiple interfaces provided by the embodiment of the present disclosure may also be executed by a server or a server cluster that is different from the server 101 and is capable of communicating with the server 101. Accordingly, the testing devices of the plurality of interfaces provided by the embodiment of the present disclosure may also be disposed in a server or a server cluster different from the server 101 and capable of communicating with the server 101.
It should be understood that the number of servers and networks in FIG. 1B is merely illustrative. There may be any number of servers and networks, as desired for implementation.
FIG. 1C schematically shows a schematic diagram of a plurality of interface calls according to an embodiment of the disclosure.
As shown in FIG. 1C, the directional arrows represent call relationships, and each interface may call or be called by multiple interfaces. For example, entering detailed information of a commodity in a background, creating the commodity which can be displayed in the foreground, editing various categories, setting various function buttons, triggering the foreground and other application scenes, a plurality of interfaces are simultaneously requested, methods between the interfaces are internally called, and intermediate results are processed to realize that final data is stored in a Redis database, a JIM database or other databases.
In the prior art, Postman, a Jmeter or other automation frameworks (Django) can only realize the verification test of the returned results of different conditions and different use scenes of a single interface and cannot realize the verification of the final results of the contract calls of a plurality of interfaces. In addition, manual creation, modification, deletion, and inspection of data results, including database lookup field insertion (insert), update (update), etc., are time-consuming tasks, and it is necessary to ensure complete case coverage, clear idea of testing process, and no omission of inspection of final field values. If the test passes through once, only the test energy of different cases is used once, and if the test does not pass, the test energy needs to be paid for many times.
Fig. 2A schematically illustrates a flow chart of a method of testing a plurality of interfaces according to an embodiment of the present disclosure.
As shown in fig. 2A, the method includes operations S201 to S203.
In operation S201, interface parameters of the plurality of interfaces are configured to obtain an interface structure, so that the plurality of interfaces satisfy a call sequence in an application scenario, where the interface structure includes an entry parameter and an exit parameter, and the exit parameter includes an interface structure exit parameter or an interface structure exit parameter and at least one interface exit parameter.
In this embodiment, the interface structure may be configured according to an interface calling sequence (including internal method call), and the configuration of the interface structure may be specifically implemented by configuring interface parameters, where the interface parameters may include: configuration protocol type, interface address, interface method name, etc.
Specifically, the protocol types may include, but are not limited to: an HTTP interface protocol type, a jeff interface protocol type, or a webservice interface protocol type, etc. The specific configuration methods of different interface protocol types are different, but are not the key point of the present disclosure, and here, only the HTTP interface protocol type is schematically illustrated, for example, an interface address, an interface method name, an interface parameter, and the like are encapsulated in an HTTP request, and the HTTP request is sent to the interface address to find the HTTP interface to be called, so that, during testing, for example, the value of the interface parameter is assigned to the interface parameter of the HTTP interface to be called to perform testing.
Fig. 2B schematically illustrates an interface parameter configuration diagram according to an embodiment of the disclosure.
As shown in fig. 2B, the test interface may include a server IP address, a port number, connection status information, an interface method name, and the like. First, an HTTP request may be selected, and then interface parameters may be configured in an interface parameter configuration interface, such as by get (get).
In one embodiment, the configuring the interface parameters of the plurality of interfaces to obtain the interface structure may include: firstly, determining a plurality of interfaces and the calling sequence of the plurality of interfaces according to the calling sequence and the application scene of each interface in the code, and then configuring interface parameters of the plurality of interfaces so that the plurality of interfaces meet the calling sequence, wherein the interface parameters may include any one or more of the following: protocol type, interface address, interface method name, interface entry and exit, etc. Furthermore, if the test is performed on the test server, the test server needs to be configured, for example, according to the mapping relationship between the interface address and the IP address of the test server. The calling sequence in the interface structure is determined according to the calling sequence of each interface in the code, so that the configuration of the calling sequence of the interfaces can be consistent with the realization of the code, and the following problems can be avoided: if a certain function can be realized by a plurality of interfaces respectively, but when a certain difference exists between the interfaces actually, the interface selected randomly in the testing stage does not show a problem during testing, but the interface actually required to be used may have an abnormal condition during use.
In a particular embodiment, the interface method name includes any one or more of: information request (get), header request (head), process request (post), delete request (delete), local modification request (patch), transfer request (put), or method return request (option), etc.
Through the operation, the interface structure can be solidified, the interface calling program does not need to be rewritten to call the interfaces in the corresponding test scene, namely, multiple use case executions, multiple coverage tests, regression tests and the like can be completed only by one-time configuration, and the test time is effectively saved. In addition, the output parameter can comprise an interface structure output parameter and at least one interface output parameter, and the interface output parameter can throw out an intermediate result, so that the problem that only the black box test can be realized in the existing functional test is effectively solved.
It should be noted that, performing maintenance on the interface structure in the later period may include the following operations: and when the calling sequence is changed, changing the corresponding interface parameters. Or when the test environment is changed, changing the mapping relation between the corresponding interface address and the IP address of the test server (host). For example, when the calling order of the interfaces changes, the interface parameters of the changed interfaces can be reconfigured. When the test server is changed, only the host of the changed test server needs to be configured.
Then, in operation S202, the test data of at least one test case is assigned to the input parameter of the interface structure, and the value of the output parameter of the interface structure is obtained as the test result.
In this embodiment, the interface testing process may include: firstly, the value of the test case is assigned to the corresponding interface input parameter, so that the value of each interface output parameter can be obtained.
Taking the error-free throwing call as an example, the method may include the following operations:
Set_default_headers()
Initialize()
Prepare()
HTTP method ()
On_finish()
Taking the call with error throwing as an example, the method may include the following operations:
Set_default_headers()
Initialize()
Prepare()
HTTP method ()
Set_default_headers()
Write_error()
On_finish()
When the call is thrown by mistake, the log of the interface can be obtained for analysis when the value of the parameter output by the interface is incorrect.
In addition, in order to facilitate changing the test data and inputting the test data, assigning the test data of at least one test case to the entry parameter of the interface structure includes the following operations: firstly, a test case is obtained, the test case comprises a test variable and corresponding test data, then the test variable and the corresponding test data are stored in a readable and writable file, and then a data value taking path of a parameter corresponding to the test data is set, so that the test data can be automatically read.
Specifically, the test cases may be designed first, then the test data used by each test case is recorded into an Excel or txt document, the expected result data is recorded into another document, then the parameter value $isconfigured, and the data source value path is set.
In operation S203, a case test result is obtained according to the test result and the expected result.
In this embodiment, the comparison process may be performed with the prior art, for example, manually, or automatically by a computer. In addition, in order to further improve the testing efficiency, only the result needing attention can be compared.
The interface test provided by the embodiment can realize any one or more of the following tests: the system comprises a service function test (comprising a normal scene and an abnormal scene), an editing analysis test (such as a service rule boundary analysis and an input/output parameter boundary analysis), a parameter combination test, an abnormal condition test (such as repeated submission, a concurrent test, a transaction test, a distributed test, an environment abnormality, a large quantity test and the like), a performance test (such as response time, throughput, a concurrent number, server resource utilization rate and the like) and a safety test (such as whether sensitive information is encrypted or not).
Fig. 2C schematically illustrates a flow chart of a method of testing a plurality of interfaces according to another embodiment of the present disclosure.
In this embodiment, the test result is stored in a database, as shown in fig. 2C, the method may further include operation S204.
In operation S204, a database field name and a field value are preset. The database field name and field value correspond to a result that requires attention.
Correspondingly, the obtaining of the case test result according to the test result and the expected result may include: firstly, comparing a test result and an expected result corresponding to the field name and the field value of the database, and if the test result and the expected result have differences, acquiring the differences and a log corresponding to the differences.
In addition, in order to further facilitate the examination of the result which needs to be paid attention to by the tester, the test result visualization can be carried out. Specifically, after obtaining the interface structure, a component may be added, and the expected result and the test result may be imported and displayed by the component.
Specifically, the importing, by the component, the test result includes: firstly, the field names and the field values of the database are imported through the components, and then, data dereferencing paths of test results corresponding to the field names and the field values of the database are set.
In one embodiment, in the stage of adding components, first, the components are added, the result to be concerned is imported (corresponding to the specific database field name and field value), then the data file corresponding to the expected result is imported and visually displayed for the tester to check, and then the actual result field data path is configured. In the test phase, testing is performed when the interface structure, test cases, and expected results are all ready. In the testing process, a plurality of test cases can be executed in parallel, a case testing result compared with an expected result is obtained, and if the case testing result or an intermediate result (a value of interface output parameters) is inconsistent with the expected result, a log can be attached to the case testing result or the intermediate result so that a tester can conveniently analyze and locate problems according to the log. It should be noted that the visual comparison result may provide multiple schemes for the tester to select a visual scheme suitable for the tester, for example, the visual comparison is simply performed by using only the values referred to by the interface structure, or the visual comparison is performed by using the intermediate result (at least one value referred to by the interface) focused on, or the visual comparison is performed by using the result (including the intermediate result and the value referred to by the interface structure) focused on, although other feasible visual result comparison schemes may also exist, which are not limited herein.
Fig. 2D schematically illustrates a flow chart of a method of testing a plurality of interfaces according to another embodiment of the present disclosure.
As shown in fig. 2D, the method may further include operation S205.
In operation S205, when the test result of the partial test case is different from the expected result, performing a regression test on the partial test case through the test case switch is implemented.
Because the interface structure provided by the disclosure can realize the parallel execution of a plurality of test cases, when one or more test cases are abnormal, the common method is to stop the test process of all the test cases, start to search for the abnormal test cases, and further analyze the abnormal test cases so as to find the abnormal interface. In this embodiment, the output parameter of the interface structure may include an interface structure output parameter and at least one interface output parameter, so that the intermediate result may be compared at any time, and a result that needs to be paid attention to is preset, so that a tester may easily and conveniently find an abnormal test result and a corresponding test case.
FIG. 3A schematically illustrates a block diagram of a test setup for multiple interfaces according to an embodiment of the present disclosure.
Correspondingly, the present disclosure also provides a testing device for multiple interfaces. As shown in fig. 3A, the testing apparatus 300 may include an interface configuration module 310, a testing module 320, and a result obtaining module 330. The interface configuration module 310, the test module 320, and the result obtaining module 330 may perform a test method of a plurality of interfaces as shown in fig. 2A to 2B.
The interface configuration module 310 is configured to configure interface parameters of the plurality of interfaces to obtain an interface structure, so that the plurality of interfaces satisfy a call sequence in an application scenario, where the interface structure includes an entry parameter and an exit parameter, and the exit parameter includes an interface structure exit parameter or an interface structure exit parameter and at least one interface exit parameter.
The test module 320 is configured to assign test data of at least one test case to the input parameters of the interface structure, and obtain output parameters of the interface structure as a test result.
The result obtaining module 330 is configured to obtain a case test result according to the test result and the expected result.
In one embodiment, the interface configuration module 310 may include a call order obtaining unit, a first configuration unit, and a second configuration unit.
The calling sequence acquiring unit is used for determining a plurality of interfaces and the calling sequences of the interfaces according to the calling sequence and the application scene of each interface in the code.
The first configuration unit is configured to configure interface parameters of the plurality of interfaces so that the plurality of interfaces satisfy the call order, where the interface parameters include any one or more of: protocol type, interface address, interface method name, interface entry and interface exit.
The second configuration unit is used for configuring the mapping relation between the interface address and the IP address of the test server according to the test environment.
In one embodiment, the interface method name includes any one or more of: an information request, a header request, a processing request, a deletion request, a local modification request, a transfer request, or a method return request.
In another embodiment, to facilitate maintenance of the test devices of the plurality of interfaces, the device may further include a first alteration module 340 and/or a second alteration module 350.
The first changing module 340 is configured to change the corresponding interface parameter when the calling sequence is changed.
The second changing module 350 is configured to change the mapping relationship between the IP address and the host name of the corresponding test host when the test environment is changed.
In another embodiment, the test module 320 may include a test case obtaining unit, a storage unit, and a first setting unit.
The test case obtaining unit is used for obtaining a test case, and the test case comprises test variables and corresponding test data.
The storage unit is used for storing the test variables and the corresponding test data in a readable and writable file.
The first setting unit is used for setting a data value taking path of the input parameter corresponding to the test data.
Correspondingly, the result obtaining module 330 is specifically configured to compare the test result with the expected result to obtain a case test result.
FIG. 3B schematically illustrates a block diagram of a test setup for multiple interfaces according to another embodiment of the present disclosure.
As shown in fig. 3B, in this embodiment, the testing apparatus 300 for multiple interfaces may further include a setting module 360, and the testing apparatus 300 for multiple interfaces may implement the method shown in fig. 2C. Correspondingly, the storage unit is also used for storing the test result in a database.
The setting module 360 is configured to preset a database field name and a field value.
Correspondingly, the result obtaining module 330 may include a comparing unit and a log obtaining unit.
The comparison unit is used for comparing the test result and the expected result corresponding to the field name and the field value of the database.
The log obtaining unit is used for obtaining the difference and the log corresponding to the difference if the test result is different from the expected result.
To facilitate the tester to view the test results, need to focus on the results, etc., the visualization component may be packaged. Specifically, the testing device 300 for multiple interfaces may further include a component adding module 370 and a presentation module 380.
Wherein the component adding module 370 is used for adding components after obtaining the interface structure.
The display module 380 is configured to import the expected result and the test result through the component, and display the expected result and the test result.
Preferably, the component adding module 370 may include a second setting unit and an importing unit. The second setting unit is used for setting a data dereferencing path of a database field name and a field value corresponding to the test result. The importing unit is used for importing the expected result and the test result through the component.
FIG. 3C schematically illustrates a block diagram of a test setup for multiple interfaces according to another embodiment of the present disclosure.
As shown in fig. 3C, the testing apparatus 300 for multiple interfaces may further include a use case switch module 390, and the testing apparatus 300 for multiple interfaces may implement the method shown in fig. 2D. The case switch module 390 is configured to implement a regression test on a part of test cases through the test case switch when a difference exists between a test result of the part of test cases and an expected result. As described above, the output parameter of the interface structure may include at least one interface output parameter, so that an intermediate result can be obtained in time and displayed for reading, and in addition, a result to be paid attention to is preset, so that a tester can easily and conveniently find an abnormal test result and a corresponding test case.
Any number of modules, sub-modules, units, sub-units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in any other reasonable manner of hardware or firmware by integrating or packaging a circuit, or in any one of or a suitable combination of software, hardware, and firmware implementations. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the disclosure may be at least partially implemented as a computer program module, which when executed may perform the corresponding functions.
For example, any plurality of the interface configuration module 310, the test module 320, the result obtaining module 330, the first changing module 340, the second changing module 350, the setting module 360, the component adding module 370, the showing module 380, and the use case switch module 390 may be combined into one module to be implemented, or any one of the modules may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the interface configuration module 310, the test module 320, the result obtaining module 330, the first altering module 340, the second altering module 350, the setting module 360, the component adding module 370, the presentation module 380, and the use case switch module 390 may be at least partially implemented as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or implemented by any one of three implementations of software, hardware, and firmware, or by a suitable combination of any of them. Alternatively, at least one of the interface configuration module 310, the test module 320, the result obtaining module 330, the first altering module 340, the second altering module 350, the setting module 360, the component adding module 370, the exposing module 380, and the use case switch module 390 may be at least partially implemented as a computer program module that, when executed, may perform a corresponding function.
FIG. 4 schematically illustrates a block diagram of a computer system suitable for implementing the above-described method according to an embodiment of the present disclosure. The computer system illustrated in FIG. 4 is only one example and should not impose any limitations on the scope of use or functionality of embodiments of the disclosure.
As shown in fig. 4, a computer system 400 according to an embodiment of the present disclosure includes a processor 401 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)402 or a program loaded from a storage section 408 into a Random Access Memory (RAM) 403. Processor 401 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 401 may also include onboard memory for caching purposes. Processor 401 may include a single processing unit or multiple processing units for performing the different actions of the method flows in accordance with embodiments of the present disclosure.
In the RAM 403, various programs and data necessary for the operation of the system 400 are stored. The processor 401, ROM 402 and RAM 403 are connected to each other by a bus 404. The processor 401 performs various operations of the method flows according to the embodiments of the present disclosure by executing programs in the ROM 402 and/or the RAM 403. Note that the programs may also be stored in one or more memories other than the ROM 402 and RAM 403. The processor 401 may also perform various operations of the method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.
According to an embodiment of the present disclosure, system 400 may also include an input/output (I/O) interface 405, input/output (I/O) interface 405 also connected to bus 404. The system 400 may also include one or more of the following components connected to the I/O interface 405: an input section 406 including a keyboard, a mouse, and the like; an output section 407 including a display device such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 408 including a hard disk and the like; and a communication section 409 including a network interface card such as a LAN card, a modem, or the like. The communication section 409 performs communication processing via a network such as the internet. A driver 510 is also connected to the I/O interface 405 as necessary. A removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 510 as necessary, so that a computer program read out therefrom is mounted into the storage section 408 as necessary.
According to embodiments of the present disclosure, method flows according to embodiments of the present disclosure may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 409, and/or installed from the removable medium 511. The computer program, when executed by the processor 401, performs the above-described functions defined in the system of the embodiments of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.
The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.
According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. Examples may include, but are not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
For example, according to embodiments of the present disclosure, a computer-readable storage medium may include ROM 402 and/or RAM 403 and/or one or more memories other than ROM 402 and RAM 403 described above.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.
The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims (20)

1. A method of testing a plurality of interfaces, comprising:
configuring interface parameters of the plurality of interfaces to obtain an interface structure, so that the plurality of interfaces meet a calling sequence in an application scene, wherein the interface structure comprises an input parameter and an output parameter, and the output parameter comprises an interface structure output parameter or an interface structure output parameter and at least one interface output parameter;
assigning the test data of at least one test case to the input parameters of the interface structure to obtain the output parameter values of the interface structure as test results; and
and obtaining a case test result according to the test result and the expected result.
2. The method of claim 1, wherein the configuring interface parameters of the plurality of interfaces results in an interface structure comprising:
determining a plurality of interfaces and the calling sequence of the plurality of interfaces according to the calling sequence of each interface in the code and the application scene;
configuring interface parameters of the plurality of interfaces so that the plurality of interfaces satisfy the calling order, wherein the interface parameters comprise any one or more of the following: protocol type, interface address, interface method name, interface entry and exit; and
and configuring the mapping relation between the interface address and the IP address of the test server according to the test environment.
3. The method of claim 2, wherein the interface method name comprises any one or more of: an information request, a header request, a processing request, a deletion request, a local modification request, a transfer request, or a method return request.
4. The method of claim 2, further comprising:
when the calling sequence is changed, changing the corresponding interface parameters; and/or
And when the test environment is changed, changing the mapping relation between the corresponding interface address and the IP address of the test server.
5. The method of claim 1, wherein assigning test data of at least one test case to an entry of the interface fabric comprises:
acquiring a test case, wherein the test case comprises a test variable and corresponding test data;
storing the test variables and the corresponding test data in a readable and writable file; and
and setting a data value taking path of the input parameter corresponding to the test data.
6. The method of claim 1, the test results being stored in a database, the method further comprising:
presetting a database field name and a field value;
the obtaining of the case test result according to the test result and the expected result comprises:
comparing the test result and the expected result corresponding to the field name and the field value of the database;
and if the test result is different from the expected result, acquiring the difference and a log corresponding to the difference.
7. The method of claim 6, further comprising:
after obtaining the interface structure, adding components; and
and importing the expected result and the test result through the component, and displaying.
8. The method of claim 7, wherein importing, by the component, the test results comprises:
importing, by the component, the database field name and field value; and
and setting a data dereferencing path of the test result corresponding to the field name and the field value of the database.
9. The method of claim 1, further comprising:
and when the test result of the part of the test cases is different from the expected result, the regression test of the part of the test cases is realized through the test case switch.
10. A test apparatus for multiple interfaces, comprising:
the interface configuration module is used for configuring interface parameters of the plurality of interfaces to obtain an interface structure so that the plurality of interfaces meet a calling sequence in an application scene, wherein the interface structure comprises an input parameter and an output parameter, and the output parameter comprises an interface structure output parameter or an interface structure output parameter and at least one interface output parameter;
the test module is used for assigning the test data of at least one test case to the input parameter of the interface structure to obtain the output parameter value of the interface structure as a test result; and
and the result acquisition module is used for acquiring a case test result according to the test result and the expected result.
11. The apparatus of claim 10, wherein the interface configuration module comprises:
the calling sequence acquiring unit is used for determining a plurality of interfaces and the calling sequences of the interfaces according to the calling sequence and the application scene of each interface in the code;
a first configuration unit, configured to configure interface parameters of the plurality of interfaces so that the plurality of interfaces satisfy the call order, where the interface parameters include any one or more of: protocol type, interface address, interface method name, interface entry and exit; and
and the second configuration unit is used for configuring the mapping relation between the interface address and the IP address of the test server according to the test environment.
12. The apparatus of claim 11, wherein the interface method name comprises any one or more of: an information request, a header request, a processing request, a deletion request, a local modification request, a transfer request, or a method return request.
13. The apparatus of claim 11, further comprising:
the first changing module is used for changing the corresponding interface parameters when the calling sequence is changed; and/or
And the second changing module is used for changing the mapping relation between the IP address and the host name of the corresponding test host when the test environment is changed.
14. The apparatus of claim 10, wherein the test module comprises:
the test case acquisition unit is used for acquiring a test case, and the test case comprises test variables and corresponding test data;
the storage unit is used for storing the test variables and the corresponding test data in a readable and writable file; and
and the first setting unit is used for setting a data value taking path of the input parameter corresponding to the test data.
15. The apparatus of claim 10, wherein the result obtaining module is specifically configured to compare the test result with the expected result to obtain a case test result.
16. The apparatus of claim 15, wherein the storage unit is further configured to store the test results in a database, the apparatus further comprising:
the setting module is used for presetting a database field name and a field value;
the result acquisition module comprises:
the comparison unit is used for comparing the test result and the expected result corresponding to the field name and the field value of the database; and
a log obtaining unit for obtaining, if there is a difference between the test result and the expected result,
and acquiring the difference and a log corresponding to the difference.
17. The apparatus of claim 16, further comprising:
the component adding module is used for adding components after the interface structure is obtained;
the display module is used for importing the expected result and the test result through the component and displaying the expected result and the test result;
the component addition module comprises:
the second setting unit is used for setting a data dereferencing path of the database field name and the field value corresponding to the test result; and
an importing unit for importing the expected result and the test result through the component.
18. The apparatus of claim 10, further comprising:
and the case switch module is used for realizing regression testing on the part of the test cases through the test case switch when the test results of the part of the test cases are different from the expected results.
19. A computing device, comprising:
one or more processors;
a storage device for storing one or more programs,
wherein the one or more programs, when executed by the one or more processors, implement the method of any of claims 1-9.
20. A computer readable medium having stored thereon executable instructions which, when executed by a processor, implement a method according to any one of claims 1 to 9.
CN201811505029.XA 2018-12-10 2018-12-10 Method and device for testing multiple interfaces, computing equipment and medium Pending CN111290941A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201811505029.XA CN111290941A (en) 2018-12-10 2018-12-10 Method and device for testing multiple interfaces, computing equipment and medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811505029.XA CN111290941A (en) 2018-12-10 2018-12-10 Method and device for testing multiple interfaces, computing equipment and medium

Publications (1)

Publication Number Publication Date
CN111290941A true CN111290941A (en) 2020-06-16

Family

ID=71020730

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811505029.XA Pending CN111290941A (en) 2018-12-10 2018-12-10 Method and device for testing multiple interfaces, computing equipment and medium

Country Status (1)

Country Link
CN (1) CN111290941A (en)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111897722A (en) * 2020-07-15 2020-11-06 重庆紫光华山智安科技有限公司 Automatic test case processing method and device, server and storage medium
CN112486806A (en) * 2020-11-18 2021-03-12 中信银行股份有限公司 Test case execution method and device, electronic equipment and readable storage medium
CN112559352A (en) * 2020-12-16 2021-03-26 平安银行股份有限公司 Interface test method, device, equipment and storage medium
CN113094264A (en) * 2021-03-31 2021-07-09 北京深思数盾科技股份有限公司 Interface testing method and device
CN113342689A (en) * 2021-07-01 2021-09-03 中诚信征信有限公司 Automatic testing method and device for interface, electronic equipment and storage medium
CN113392004A (en) * 2021-06-15 2021-09-14 中国工商银行股份有限公司 Interface verification method, device, equipment, medium and program product
CN113535565A (en) * 2021-07-19 2021-10-22 工银科技有限公司 Interface use case generation method, device, equipment, medium and program product
CN114238065A (en) * 2020-09-09 2022-03-25 马上消费金融股份有限公司 Test processing method, device, equipment and readable storage medium

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111897722A (en) * 2020-07-15 2020-11-06 重庆紫光华山智安科技有限公司 Automatic test case processing method and device, server and storage medium
CN114238065A (en) * 2020-09-09 2022-03-25 马上消费金融股份有限公司 Test processing method, device, equipment and readable storage medium
CN112486806A (en) * 2020-11-18 2021-03-12 中信银行股份有限公司 Test case execution method and device, electronic equipment and readable storage medium
CN112559352A (en) * 2020-12-16 2021-03-26 平安银行股份有限公司 Interface test method, device, equipment and storage medium
CN113094264A (en) * 2021-03-31 2021-07-09 北京深思数盾科技股份有限公司 Interface testing method and device
CN113094264B (en) * 2021-03-31 2022-02-18 北京深思数盾科技股份有限公司 Interface testing method and device
CN113392004A (en) * 2021-06-15 2021-09-14 中国工商银行股份有限公司 Interface verification method, device, equipment, medium and program product
CN113342689A (en) * 2021-07-01 2021-09-03 中诚信征信有限公司 Automatic testing method and device for interface, electronic equipment and storage medium
CN113535565A (en) * 2021-07-19 2021-10-22 工银科技有限公司 Interface use case generation method, device, equipment, medium and program product
CN113535565B (en) * 2021-07-19 2022-10-04 工银科技有限公司 Interface use case generation method, device, equipment and medium

Similar Documents

Publication Publication Date Title
CN109302522B (en) Test method, test device, computer system, and computer medium
CN111290941A (en) Method and device for testing multiple interfaces, computing equipment and medium
US9910941B2 (en) Test case generation
US10360141B2 (en) Automated application test system
US10956311B2 (en) White box code concurrency testing for transaction processing
US11294803B2 (en) Identifying incorrect variable values in software testing and development environments
US10552304B2 (en) Using test workload run facts and problem discovery data as input for business analytics to determine test effectiveness
CN111831573A (en) Method, device, computer system and medium for determining code branch coverage condition
US11232020B2 (en) Fault detection using breakpoint value-based fingerprints of failing regression test cases
US20200104246A1 (en) Continuous automation with test suite engine
CN113014445B (en) Operation and maintenance method, device and platform for server and electronic equipment
US11663113B2 (en) Real time fault localization using combinatorial test design techniques and test case priority selection
CA2811617C (en) Commit sensitive tests
US9513948B2 (en) Automated virtual machine provisioning based on defect state
US10725895B2 (en) Measuring and improving test coverage
US10346293B2 (en) Testing pre and post system call exits
JP6771413B2 (en) Software verification device and software verification program
US11294804B2 (en) Test case failure with root cause isolation
CN111930629A (en) Page testing method and device, electronic equipment and storage medium
Chaudhary Latest software testing tools and techniques: A review
US20210406158A1 (en) Systems and methods for automated device testing
US20210303766A1 (en) Pre-silicon chip model of extracted workload inner loop instruction traces
US11036624B2 (en) Self healing software utilizing regression test fingerprints
CN113392002A (en) Test system construction method, device, equipment and storage medium
US11645142B1 (en) Use sequential set index for root cause location and problem verification

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination