CN113297088B - Test method, test device, electronic equipment and storage medium - Google Patents
Test method, test device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN113297088B CN113297088B CN202110639754.1A CN202110639754A CN113297088B CN 113297088 B CN113297088 B CN 113297088B CN 202110639754 A CN202110639754 A CN 202110639754A CN 113297088 B CN113297088 B CN 113297088B
- Authority
- CN
- China
- Prior art keywords
- test
- branch
- test case
- item
- project
- 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.)
- Active
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 594
- 238000010998 test method Methods 0.000 title claims description 25
- 238000000034 method Methods 0.000 claims description 38
- 238000012217 deletion Methods 0.000 claims description 16
- 230000037430 deletion Effects 0.000 claims description 16
- 230000004044 response Effects 0.000 claims description 8
- 238000004590 computer program Methods 0.000 description 13
- 238000004891 communication Methods 0.000 description 11
- 238000010586 diagram Methods 0.000 description 9
- 239000000463 material Substances 0.000 description 7
- 238000012545 processing Methods 0.000 description 7
- 230000004048 modification Effects 0.000 description 6
- 238000012986 modification Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 230000001960 triggered effect Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000010411 postconditioning Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test 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 disclosure discloses a testing method, a testing device, electronic equipment and a storage medium, relates to the technical field of computers, and particularly relates to the testing field. The specific implementation scheme is as follows: responding to a local test task request, and acquiring a branch code and a test case corresponding to each item identifier in the local test task request, wherein each test case comprises a main test case; under the condition that the test cases further comprise branch test cases, the branch test cases are utilized to test the branch codes; and under the condition that the test cases do not comprise the branch test cases, testing the branch codes by using the main test cases.
Description
Technical Field
The present disclosure relates to the field of computer technology, and in particular, to the field of testing.
Background
With the continuous development of business, product version upgrades are more frequent. Product version upgrades are accompanied by project online. The code of the product version includes a backbone code and a branch code of each item.
In order to ensure that each product version can normally run, regression testing of the component codes by using test cases is required. Regression testing may refer to retesting modified code to confirm that the modified code did not introduce new errors or caused other code to produce errors.
Disclosure of Invention
The disclosure provides a testing method, a testing device, electronic equipment and a storage medium.
According to an aspect of the present disclosure, there is provided a test method including: responding to a local test task request, and acquiring a branch code and a test case corresponding to each item identifier in the local test task request, wherein each test case comprises a main test case; under the condition that the test case further comprises a branch test case, testing the branch codes by using the branch test case; and testing the branch code by using the trunk test case when the test case is determined not to include the branch test case.
According to another aspect of the present disclosure, there is provided a test apparatus comprising: the first acquisition module is used for responding to a local test task request and acquiring branch codes and test cases corresponding to each item identifier in the local test task request, wherein each test case comprises a main test case; the first test module is used for testing the branch codes by using the branch test cases under the condition that the test cases further comprise the branch test cases; and the second test module is used for testing the branch codes by using the trunk test case under the condition that the test case does not comprise the branch test case.
According to another aspect of the present disclosure, there is provided an electronic device including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executable by the at least one processor to enable the at least one processor to perform the method as described above.
According to another aspect of the present disclosure, there is provided a non-transitory computer-readable storage medium storing computer instructions for causing the computer to perform the method as described above.
According to another aspect of the present disclosure, there is provided a computer program product comprising a computer program which, when executed by a processor, implements a method as described above.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.
Drawings
The drawings are for a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:
FIG. 1 schematically illustrates an exemplary system architecture in which test methods and apparatus may be applied, according to embodiments of the present disclosure;
FIG. 2 schematically illustrates a flow chart of a test method according to an embodiment of the disclosure;
FIG. 3 schematically illustrates a schematic diagram of performing a local test task according to an embodiment of the disclosure;
FIG. 4 schematically illustrates a flow chart of testing a new backbone code according to an embodiment of the disclosure;
FIG. 5 schematically illustrates a schematic diagram of performing an online test task in accordance with an embodiment of the present disclosure;
FIG. 6 schematically illustrates a block diagram of a test apparatus according to an embodiment of the disclosure; and
fig. 7 shows a block diagram of an electronic device that may be suitable for use in a test method according to an embodiment of the disclosure.
Detailed Description
Exemplary embodiments of the present disclosure are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present disclosure to facilitate understanding, and should be considered as merely exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
The test cases for testing the backbone code may be test cases that have undergone complete functional testing and interface testing and are in a state of successful execution. However, since the branch code is obtained by modifying the trunk code, there is a possibility that the regression test is performed on the branch code by using the test cases for testing the trunk code, and the test cases may fail to be executed. The test case execution failure caused by the above-described case may be referred to as test case execution failure caused by incompatibility with the project. The test cases described in the embodiments of the present disclosure may refer to stock test cases.
To solve the problem of test case execution failure, the following two methods can be utilized.
In one mode, the test case is modified. That is, the test cases that have failed execution will be modified such that the modified test cases are compatible with the branch code, i.e., the modified test cases are compatible with the project.
And in the second mode, the test case is not modified. That is, it is determined that the test case fails to be executed, and after the branch code is online, the test case is modified, so that the modified test case is compatible with the branch code.
In the process of implementing the disclosed concept, it is found that if the first mode is utilized, since the modified test case is not compatible with other branch codes, in a period of time before the modification of the test case is completed and the branch codes are integrated into the main trunk code, if the modified test case is utilized to test other branch codes, the modified test case fails to be executed, which affects the test efficiency and the test stability. If the second mode is utilized, since the test case of the execution failure is not modified, it is difficult to ensure whether the function implemented by the modified code is normal, which affects the test quality.
In order to improve test efficiency, test stability and test quality, it is found that version distinction can be performed on test cases, test cases corresponding to branch codes are utilized to test the branch codes, and the test cases corresponding to the branch codes may include a main test case and not include a branch test case or may include a main test case and a branch test case.
Thus, embodiments of the present disclosure provide a test method, a test apparatus, a non-transitory computer readable storage medium storing computer instructions for an electronic device, and a computer program product. The test method comprises the following steps: responding to a local test task request, acquiring branch code test cases corresponding to each item identifier in the local test task request, wherein each test case comprises a main test case, testing the branch codes by using the branch test cases when the test cases are determined to further comprise the branch test cases, and testing the branch codes by using the main test cases when the test cases are determined to not comprise the branch test cases.
Fig. 1 schematically illustrates an exemplary system architecture 100 in which test methods and apparatus may be applied, according to embodiments of the present disclosure.
It should be noted that fig. 1 is only an example of a system architecture to which embodiments of the present disclosure may be applied to assist those skilled in the art in understanding the technical content of the present disclosure, but does not mean that embodiments of the present disclosure may not be used in other devices, systems, environments, or scenarios. For example, in another embodiment, an exemplary system architecture that may test methods and apparatuses may include a terminal device, but the terminal device may implement the test methods and apparatuses provided by the embodiments of the present disclosure without interacting with a server.
As shown in fig. 1, a system architecture 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used as a medium to provide communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired and/or wireless communication links, and the like.
The user may interact with the server 105 via the network 104 using the terminal devices 101, 102, 103 to receive or send messages or the like. Various communication client applications may be installed on the terminal devices 101, 102, 103, such as a knowledge reading class application, a web browser application, a search class application, an instant messaging tool, a mailbox client and/or social platform software, etc. (as examples only).
The terminal devices 101, 102, 103 may be a variety of electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server 105 may be a server providing various services, such as a background management server (by way of example only) providing support for content browsed by the user using the terminal devices 101, 102, 103. The background management server may analyze and process the received data such as the user request, and feed back the processing result (e.g., the web page, information, or data obtained or generated according to the user request) to the terminal device.
It should be noted that the test method provided by the embodiments of the present disclosure may be generally performed by the terminal device 101, 102, or 103. Accordingly, the test apparatus provided in the embodiments of the present disclosure may also be provided in the terminal device 101, 102, or 103.
Alternatively, the test methods provided by embodiments of the present disclosure may also be performed generally by the server 105. Accordingly, the testing apparatus provided by the embodiments of the present disclosure may be generally disposed in the server 105. The test method provided by the embodiments of the present disclosure may also be performed by a server or a server cluster that is different from the server 105 and is capable of communicating with the terminal devices 101, 102, 103 and/or the server 105. Accordingly, the test apparatus provided by the embodiments of the present disclosure may also be provided in a server or a server cluster that is different from the server 105 and is capable of communicating with the terminal devices 101, 102, 103 and/or the server 105.
For example, the server 105 responds to the local test task request, obtains the branch code and the test case corresponding to each item identifier in the local test task request, tests the branch code by using the branch test case when determining that the test case further includes the branch test case, and tests the branch code by using the trunk test case when determining that the test case does not include the branch test case. Or the branch code corresponding to the item identification is tested by a server or cluster of servers capable of communicating with the terminal devices 101, 102, 103 and/or server 105 using a branch test case or backbone test case.
It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Fig. 2 schematically illustrates a flow chart of a test method 200 according to an embodiment of the disclosure.
As shown in fig. 2, the method includes operations S210 to S230.
In operation S210, in response to the local test task request, a branch code and a test case corresponding to each item identifier in the local test task request are obtained, where each test case includes a main test case.
In operation S220, in case it is determined that the test cases further include a branch test case, the branch code is tested using the branch test case.
In operation S230, in case it is determined that the test cases do not include the branch test cases, the branch code is tested using the main test cases.
According to embodiments of the present disclosure, a local test task request may be used to characterize a task request that is tested against the branch code of an item. Item identification may be used to characterize an item. Each item has a corresponding one or more test cases. The code of each item may include a branch code of the item. The branch code of each item may be processed from the backbone code associated with the item, e.g., the branch code of each item may be modified from the backbone code associated with the item. For each item, the item's branch code, the backbone code associated with the item, and the test case may be associated with the item identification of the item, in other words, the item's branch code, the backbone code associated with the item, and the test case may be characterized by item target identifications. On this basis, the test cases of the project can be associated with the code of the project through project identification.
According to embodiments of the present disclosure, the test cases may include a main test case and not include a branch test case or may include a main test case and a branch test case. The test cases may be stored in the ITP (Integration Test Platform, integrated test platform). For each item, if the test cases of the item include a main test case and not a branch test case, the branch code of the item may be tested with the main test case. If the test cases of the project include a main test case and a branch test case, the branch code of the project may be tested with the branch test case. The branch test cases may be generated from a backbone test case and branch code corresponding to the item. If the test cases include a trunk test case and a branch test case, version switching can be performed in the ITP in the process of debugging the test cases, that is, switching to the trunk test case or the branch test case can be performed.
According to embodiments of the present disclosure, the local test task request may include a branch code and a test case corresponding to each item identification in one or more item identifications. The local test task request may be generated upon detecting that an item-submission task is triggered.
According to embodiments of the present disclosure, a local test task request may be obtained, and in response to the local test task request, a branch code and a test case corresponding to each of one or more project identifications may be obtained. The test cases may include a main test case. For the item characterized by each item identifier, if the test case corresponding to the item identifier is determined to further comprise a branch test case, the main test case is not compatible with the item, the branch test case is compatible with the item, and the branch code corresponding to the item identifier can be tested by using the branch test case. If the test case corresponding to the item identifier does not comprise the branch test case, the main test case can be indicated to be compatible with the item, and the branch code corresponding to the item identifier can be tested by using the main test case. The branch code is tested by utilizing a branch test case or a trunk test case to determine whether the branch code has a problem.
According to the embodiment of the disclosure, the branch codes corresponding to each item identifier can be tested by adopting the test method. Because the branch code of each project has a corresponding test case version, different projects can be mutually independent, and therefore, parallel testing of a plurality of projects can be realized. The method not only effectively ensures the local test task of each project, but also does not influence the automatic local test tasks of other projects.
According to an embodiment of the present disclosure, if a test case for testing a branch code is modified, the branch code needs to be tested by reusing the modified test case to determine whether the modification to the test case is correct and whether the branch code has a problem.
According to the embodiment of the disclosure, if each test case comprises a main test case and a branch test case in addition to the main test case, the branch test case corresponding to the item identifier is utilized to test the branch code, and if each test case comprises the main test case and does not comprise the branch test case, the main test case corresponding to the item identifier is utilized to test the branch code, and since the branch code of each item has a corresponding test case version, the compatibility of the item and the test case can be effectively ensured, thereby improving the test efficiency, the test stability and the test quality, and at least partially overcoming the technical problems of low test efficiency, test stability and test quality.
According to the embodiment of the disclosure, under the condition that the generation condition of the branch test cases is met, the branch test cases corresponding to the project identifications are generated according to the trunk test cases and the branch codes corresponding to the project identifications.
According to embodiments of the present disclosure, if it is determined that the main test case is not compatible with the project, it may be determined that the branch test case generation condition is satisfied. In this case, a branch test case corresponding to the item identification may be generated from the trunk test case corresponding to the item identification and the branch code.
According to an embodiment of the present disclosure, satisfying the branch test case generation condition may include: and testing the branch codes corresponding to the project identifications by using the main test cases corresponding to the project identifications, wherein the test result of testing the branch codes corresponding to the project identifications is test failure.
According to the embodiment of the disclosure, if a test result obtained by testing the branch code corresponding to the item identifier by using the main test case corresponding to the item identifier is a test failure, it can be stated that the main test case is not compatible with the item represented by the item identifier, thereby satisfying the generation condition of the branch test case.
According to an embodiment of the present disclosure, satisfying the branch test case generation condition may include: and under the condition that the branch codes corresponding to the project identifications are not tested by using the main test cases corresponding to the project identifications, determining that the main test cases are incompatible with the projects represented by the project identifications according to the interface documents corresponding to the project identifications.
According to embodiments of the present disclosure, the interface document may include interface parameters from which it may be determined whether the main test case is compatible with the project. For example, if the interface parameters are modified such that corresponding modifications to the backbone test case are required to make the modified backbone test case compatible with the project, it may be determined from the interface parameters that the backbone test case is not compatible with the project.
According to the embodiment of the disclosure, if the branch code corresponding to the item identifier is not tested by using the main test case corresponding to the item identifier, and the main test case is determined to be incompatible with the item according to the interface document corresponding to the item identifier, the main test case is not compatible with the item represented by the item identifier, so that the generation condition of the branch test case is satisfied.
According to an embodiment of the present disclosure, generating a branch test case corresponding to an item identification according to a backbone test case corresponding to the item identification and an item branch code may include the following operations.
And modifying the main test case corresponding to the item identifier according to the branch code corresponding to the item identifier to obtain the branch test case corresponding to the item identifier.
According to the embodiment of the disclosure, if the test result of testing the branch code corresponding to the item identifier by using the main test case corresponding to the item identifier is determined to be test failure, a new test case can be created, the main test case failing to be tested is copied into the new test case, and the main test case failing to be tested is modified according to the branch code corresponding to the item identifier, so that the branch test case corresponding to the item identifier is obtained.
According to the embodiment of the disclosure, if it is determined that the branch code corresponding to the item identifier is not tested by using the main test case corresponding to the item identifier and it is determined that the main test case is not compatible with the item represented by the item identifier according to the interface document corresponding to the item identifier, a new test case can be created, the main test case can be obtained according to the interface request address included in the interface document, the main test case is copied into the new test case, and the main test case is modified according to the branch code corresponding to the item identifier, so that the branch test case corresponding to the item identifier is obtained.
According to embodiments of the present disclosure, for each item, the test cases for testing the item are stored in the same collection, which may include a CI directory and a DEV directory. The CI catalog stores stock test cases, which may include trunk test cases and branch test cases described in embodiments of the present disclosure.
According to an embodiment of the present disclosure, each test case includes a precondition, a test case body, and a postconditioning, wherein the precondition includes at least one of: database operation statements, interface calls, and data upon which test cases depend. The post-condition comprises a statement for deleting a result obtained by executing the database operation statement and/or data generated by executing the interface call.
According to embodiments of the present disclosure, test cases may include a precondition (i.e., setup), a test case body (i.e., request), and a test post-condition (i.e., teardown). The preconditions of the test case may include at least one of database operation statements, interface calls, and data upon which the test case depends. The method has the advantages that partial parameters in the request body included in the test case body of the test case need to be written into the form of global variables, and the global variables characterize parameters which can be used by different test cases calling the same interface and can be used by different test cases of the interface, so that the condition that the parameters of the interface change and the test cases calling the interface need to be manually modified to adapt to the parameter change of the interface can be effectively avoided.
According to embodiments of the present disclosure, post-conditions of the test case may include statements for deleting results from executing database operation statements and/or executing data resulting from interface calls. The results of executing the operation statement and/or the data generated by executing the interface call may be referred to as materials required for testing. The post-condition of the test case can realize timely release of invalid resources, so that the influence on other tests is effectively prevented, for example, the quantity of materials in business logic is limited, and the invalid materials occupy limited quantity and name, so that the follow-up test case can fail to be executed due to the fact that the materials cannot be created. The method and the device realize timely release of invalid resources, prevent influence on other tests, for example, certain limit on the quantity of materials in general business logic, and the invalid materials occupy limited quantity and name, so that subsequent test cases fail to be executed due to the fact that the materials cannot be built during automatic execution.
According to an embodiment of the present disclosure, acquiring the branch code and the test case corresponding to each item identification may include the following operations.
A branch code corresponding to each item identification is obtained from a first directory corresponding to each item identification. And acquiring the test cases corresponding to each item identifier from the second catalogue corresponding to each item identifier.
According to embodiments of the present disclosure, the code of an item may be stored in a first directory, and the test cases of the item may be stored in a second directory, which may refer to CI directories in the set described above.
According to an embodiment of the present disclosure, the above-described test method may further include the following operations.
A local test task environment is deployed for executing local test tasks. Branch code corresponding to the project identification is then deployed in the local test task environment.
According to embodiments of the present disclosure, in order to implement a local test task, a local test task environment may be deployed. The XSTP service may be invoked to deploy a local test task environment for executing a local test task, and to deploy branch code corresponding to the item identification in the local test task environment.
The method illustrated in fig. 2 is further described below with reference to fig. 3 in conjunction with an exemplary embodiment.
Fig. 3 schematically illustrates a schematic diagram of performing a local test task 300 according to an embodiment of the disclosure.
As shown in fig. 3, when the local test task 301 is detected to be triggered, a branch code and a test case corresponding to each item identifier in the respective item identifiers, that is, a branch code 303 and a test case 305 corresponding to one item identifier, a branch code 304 and a test case 306 corresponding to another item identifier are acquired, the test case 305 includes a main test case 3050 and a branch test case 3051, and the test case 306 includes a main test case 3060. Test cases may be stored in a CI directory.
The XSTP service is invoked to deploy a local test task environment 302 for executing the local test task 301 and to deploy branch code of the respective project in the local test task environment 302, i.e. to deploy branch code 303 and branch code 304 in the local test task environment 302.
For the branch code 303, in a case where it is determined that the test case 305 for testing the branch code 303 includes a branch test case 3051, the branch code 303 is tested using the branch test case 3051. For the branch code 304, the branch code 304 is tested using the main test case 3060 in the event that it is determined that the test case 306 for testing the branch code 304 does not include a branch test case. After testing for branch code is completed, a test case execution report may also be generated.
The method shown in fig. 2 is further described below with reference to fig. 4-5, in conjunction with the exemplary embodiment.
Fig. 4 schematically illustrates a flow chart of testing 400 a new backbone code according to an embodiment of the disclosure.
As shown in FIG. 4, the method includes operations S440-S450.
In operation S440, in response to the online test task request, a new backbone code and a backbone test case corresponding to one or more item identifications in the online test task request are acquired.
In operation S450, a new backbone code is tested using the backbone test case, wherein the new backbone code is obtained by incorporating one or more branch codes into the original backbone code, and each of the one or more item identifications has a branch code.
According to embodiments of the present disclosure, an online test task request may be used to characterize a task request that is tested against a new backbone code. The online test task request may include a new backbone code and a backbone test case corresponding to one or more item identifications, i.e., there may be one or more items for which an online test task needs to be performed, and if the items for which an online test task needs to be performed include a plurality of items, the online test task request includes a new backbone code and a backbone test case corresponding to the plurality of item identifications. The plurality of item identifiers correspond to the same new backbone code and backbone test case. If the project needed to execute the online test task comprises one project, the online test task request comprises a new trunk code and a trunk test case corresponding to one project identifier.
According to embodiments of the present disclosure, an online test task request may be generated upon detecting that an item online task is triggered. The new backbone code corresponding to the one or more item identities may be obtained by incorporating one or more branch codes into the original backbone code, each of the one or more item identities having a branch code, i.e. the branch codes are in one-to-one correspondence with the item identities. There may be one or more items that need to perform the online test task. If the items needed to perform the online test task include multiple, multiple branch codes may be merged into the original backbone code to obtain a new backbone code. If the item needed to perform the online test task includes one, a branch code may be incorporated into the original backbone code to obtain a new backbone code.
According to embodiments of the present disclosure, a new backbone code corresponding to one or more item identities may be tested with a backbone test case corresponding to the one or more item identities to determine if there is a problem with the backbone test case and the new backbone code.
According to an embodiment of the present disclosure, the above-described test method may further include the following operations.
An online test task environment for executing an online test task is deployed. New backbone branch code corresponding to the one or more item identifications is then deployed in the online test task environment.
According to embodiments of the present disclosure, in order to implement the above-described test tasks, an online test task environment may be deployed. An XSTP service may be invoked to deploy an online test task environment for performing an online test task, and to deploy new backbone code corresponding to one or more item identifications in the online test task environment.
According to an embodiment of the present disclosure, the above-described test method may further include the following operations.
And acquiring project requirement information, wherein the project requirement information comprises project online time and project identification. Then, under the condition that the project represented by the project identifier meets the online test condition according to the project online time, obtaining a test case corresponding to the project identifier, wherein the test case comprises an original main test case. And finally, under the condition that the test case is determined to further comprise the branch test case, the branch test case is combined into the original main test case.
According to embodiments of the present disclosure, the project requirement information may include project online time and project identification of the project. Whether the project online test condition is met or not can be determined according to the project online time of the project, namely, whether the project online time of the project reaches the preset online time is determined, and if the project online time of the project reaches the preset online time, the test case corresponding to the project identifier can be obtained. It is determined whether the test cases corresponding to the item identification also include branch test cases. If it is determined that the test cases corresponding to the item identifiers also include branch test cases, the branch test cases may be incorporated into the original main test cases. In addition, the merging operation for the original main test case can be manually executed, for example, the merging operation for the original main test case can be executed in the ITP.
According to the embodiment of the disclosure, the above operation can be performed for each item meeting the online test condition of the item, that is, whether the test case corresponding to the item identifier further includes a branch test case is determined, and if it is determined that the test case corresponding to the item identifier further includes the branch test case, the branch test case can be incorporated into the original main test case.
According to embodiments of the present disclosure, the project requirement information may further include tester information corresponding to the project identification. If it is determined that the test cases corresponding to the item identifiers also include branch test cases, the branch test cases may be incorporated into the original main test cases. If it is determined that the merging conflict exists in the process of merging the branch test cases into the original main test case, the original main test case and the branch test case with the merging conflict can be sent to a tester corresponding to the tester information, so that the tester can process the merging conflict. And the original main test case and the branch test case which have the merging conflict can be sent to the testers corresponding to the tester information in a mail mode.
According to the embodiment of the disclosure, the test cases which are completed in a merging way can be marked, and the marked content can comprise at least one of test case identification, project online time and whether the test case is completed in a merging way or not.
According to the embodiment of the disclosure, in response to a test case deletion request, a branch test case corresponding to a branch test case identifier in the test case deletion request is deleted.
According to embodiments of the present disclosure, a test case delete request may be used to characterize a delete request for a branched test case of an item. The test deletion request may include a branch test case identification. The test case deletion request may be generated upon detecting that a test case deletion task is triggered.
According to the embodiment of the disclosure, a test case deletion request can be acquired, and the branch test case corresponding to the branch test case identifier is directly deleted in response to the test case deletion request. Alternatively, in response to the test case deletion request, it is determined whether the branch test case corresponding to the branch test case identification satisfies the test case deletion condition. If the branch test case corresponding to the branch test case identification is determined to meet the test case deletion condition, the branch test case corresponding to the branch test case identification may be deleted. Meeting the test case deletion condition may include the deletion time of the branch test case reaching a preset deletion time.
The method shown in FIG. 4 is further described with reference to FIG. 5 in conjunction with the exemplary embodiment
Fig. 5 schematically illustrates a schematic diagram of performing an online test task 500 according to an embodiment of the disclosure.
As shown in fig. 5, when the online test task 501 is detected to be triggered, a new trunk code 503 and test cases 504 corresponding to a plurality of item identifiers are acquired, the test cases 504 include a trunk test case 5040, and the trunk test case 5040 may be obtained by merging a plurality of branch test cases into the original trunk test case. Test cases may be stored in a CI directory.
The XSTP service is invoked to deploy an online test task environment 502 for executing an online test task 501 and to deploy new backbone code 503 in the online test task environment 502.
For the new backbone code 503, the new backbone code 503 is tested using the backbone test case 5040. After testing for the new backbone code is completed, a test case execution report may also be generated.
Fig. 6 schematically illustrates a block diagram of a testing apparatus 600 according to an embodiment of the disclosure.
As shown in fig. 6, the test apparatus 600 may include a first acquisition module 610, a first test module 620, and a second test module 630.
The first obtaining module 610 is configured to obtain, in response to a local test task request, a branch code and a test case corresponding to each item identifier in the local test task request, where each test case includes a main test case.
The first test module 620 is configured to test the branch code with the branch test case if it is determined that the test case further includes the branch test case.
And a second test module 630, configured to test the branch code by using the trunk test case if it is determined that the test case does not include the branch test case.
According to an embodiment of the present disclosure, the test apparatus 600 may further include a generating module.
The generating module is used for generating the branch test case corresponding to the project identifier according to the main test case corresponding to the project identifier and the branch code under the condition that the branch test case generating condition is met.
According to an embodiment of the present disclosure, satisfying the branch test case generation condition includes:
and testing the branch codes corresponding to the project identifications by using the main test cases corresponding to the project identifications, wherein the test result of testing the branch codes corresponding to the project identifications is test failure.
According to an embodiment of the present disclosure, satisfying the branch test case generation condition includes:
under the condition that the branch codes corresponding to the project identifications are not tested by utilizing the main automation test cases corresponding to the project identifications, the incompatibility of the main automation test cases and the projects represented by the project identifications is determined according to the interface documents corresponding to the project identifications.
According to an embodiment of the present disclosure, generating a branch test case corresponding to an item identification according to a backbone test case corresponding to the item identification and an item branch code may include the following operations.
And modifying the main test case corresponding to the item identifier according to the branch code corresponding to the item identifier to obtain the branch test case corresponding to the item identifier.
According to an embodiment of the present disclosure, each test case includes a precondition, a test case body, and a postconditioning, wherein the precondition includes at least one of: database operation sentences, interface calls and executes data on which test cases depend; the post-condition comprises a statement for deleting a result obtained by executing the database operation statement and/or data generated by executing the interface call.
According to an embodiment of the present disclosure, the first acquisition module may include a first acquisition unit and a second acquisition unit.
And the first acquisition unit is used for acquiring the branch code corresponding to each item identifier from the first catalogue corresponding to each item identifier.
And the second acquisition unit is used for acquiring the test cases corresponding to each item identifier from the second catalogue corresponding to each item identifier.
According to an embodiment of the present disclosure, the test apparatus 600 may further include a first deployment module and a second deployment module.
The first deployment module is used for deploying a local test task environment for executing a local test task.
The second deployment module is used for deploying branch codes corresponding to the project identifiers in the local test task environment.
According to an embodiment of the present disclosure, the test apparatus 600 may further include a second acquisition module and a third test module.
The second acquisition module is used for responding to the online test task request and acquiring a new trunk code and a trunk test case corresponding to one or more item identifiers in the online test task request.
And the third testing module is used for testing a new trunk code by utilizing the trunk test case, wherein the new trunk code is obtained by combining one or more branch codes into the original trunk code, and each item identifier in the one or more item identifiers is provided with one branch code.
According to an embodiment of the present disclosure, the test apparatus 600 may further include a third deployment module and a fourth deployment module.
And the third deployment module is used for deploying an online test task environment for executing the online test task.
And the fourth deployment module is used for deploying new trunk branch codes corresponding to one or more project identifiers in the online test task environment.
According to an embodiment of the present disclosure, the test apparatus 600 may further include a third acquiring module, a fourth acquiring module, and a merging module.
And the third acquisition module is used for acquiring project demand information, wherein the project demand information comprises project online time and project identification.
The fourth acquisition module is used for acquiring the test cases corresponding to the item identification under the condition that the item represented by the item identification meets the online test conditions according to the item online time, wherein the test cases comprise original main test cases.
And the merging module is used for merging the branch test cases into the original main test case under the condition that the test cases are determined to further comprise the branch test cases.
According to an embodiment of the present disclosure, the test apparatus 600 may further include a deletion module.
And the deleting module is used for responding to the test case deleting request and deleting the branch test cases corresponding to the branch test case identifications in the test case deleting request.
According to embodiments of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.
According to an embodiment of the present disclosure, an electronic device includes: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executable by the at least one processor to enable the at least one processor to perform the method as described above.
According to an embodiment of the present disclosure, a non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the method as described above.
According to an embodiment of the present disclosure, a computer program product comprising a computer program which, when executed by a processor, implements a method as described above.
Fig. 7 illustrates a block diagram of an electronic device 700 that may be suitable for use with the test method according to an embodiment of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the disclosure described and/or claimed herein.
As shown in fig. 7, the apparatus 700 includes a computing unit 701 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 702 or a computer program loaded from a storage unit 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the device 700 may also be stored. The computing unit 701, the ROM 702, and the RAM 703 are connected to each other through a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
Various components in device 700 are connected to I/O interface 705, including: an input unit 706 such as a keyboard, a mouse, etc.; an output unit 707 such as various types of displays, speakers, and the like; a storage unit 708 such as a magnetic disk, an optical disk, or the like; and a communication unit 709 such as a network card, modem, wireless communication transceiver, etc. The communication unit 709 allows the device 700 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.
The computing unit 701 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 701 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 701 performs the respective methods and processes described above, such as a test method. For example, in some embodiments, the test method may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage unit 708. In some embodiments, part or all of the computer program may be loaded and/or installed onto device 700 via ROM 702 and/or communication unit 709. When the computer program is loaded into RAM 703 and executed by computing unit 701, one or more steps of the test method described above may be performed. Alternatively, in other embodiments, the computing unit 701 may be configured to perform the test method by any other suitable means (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, 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), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the internet.
The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server may be a cloud server, a server of a distributed system, or a server incorporating a blockchain.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps recited in the present disclosure may be performed in parallel or sequentially or in a different order, provided that the desired results of the technical solutions of the present disclosure are achieved, and are not limited herein.
The above detailed description should not be taken as limiting the scope of the present disclosure. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present disclosure are intended to be included within the scope of the present disclosure.
Claims (15)
1. A method of testing, comprising:
responding to a local test task request, and acquiring a branch code and a test case corresponding to each item identifier in the local test task request, wherein each test case comprises a main test case;
under the condition that the test case further comprises a branch test case, testing the branch code by using the branch test case; and
Under the condition that the test case does not comprise the branch test case, testing the branch code by using the trunk test case;
under the condition that the generation condition of the branch test cases is met is determined, generating the branch test cases corresponding to the item identifications according to the trunk test cases and the branch codes corresponding to the item identifications;
the generating the branch test case corresponding to the project identifier according to the main test case corresponding to the project identifier and the project branch code comprises the following steps:
and modifying the main test case corresponding to the item identification according to the branch code corresponding to the item identification to obtain the branch test case corresponding to the item identification.
2. The method of claim 1, wherein the meeting a branch test case generation condition comprises:
and testing the branch codes corresponding to the item identifiers by using the main test cases corresponding to the item identifiers, wherein the test results of testing the branch codes corresponding to the item identifiers are test failures.
3. The method of claim 1, wherein the meeting a branch test case generation condition comprises:
and under the condition that the branch codes corresponding to the project identifications are not tested by utilizing the trunk test cases corresponding to the project identifications, determining that the trunk test cases are incompatible with the projects characterized by the project identifications according to the interface documents corresponding to the project identifications.
4. The method of any one of claims 1-3, wherein each of the test cases includes a pre-condition, a test case body, and a post-condition,
wherein the preconditions include at least one of: database operation sentences, interface calls and executes data on which the test case depends;
the post condition comprises a statement for deleting a result obtained by executing the database operation statement and/or data generated by executing an interface call.
5. The method of any one of claims 1-3, wherein the obtaining the branch code and the test case corresponding to each item identifier includes:
acquiring branch codes corresponding to each item identifier from a first catalogue corresponding to each item identifier; and
and acquiring test cases corresponding to each item identifier from a second catalogue corresponding to each item identifier.
6. The method of any one of claims 1-3, further comprising:
deploying a local test task environment for executing a local test task; and
and deploying branch codes corresponding to the project identifiers in the local test task environment.
7. The method of any one of claims 1-3, further comprising:
responding to an online test task request, and acquiring a new trunk code and a trunk test case corresponding to one or more item identifiers in the online test task request; and
and testing the new trunk code by using the trunk test case, wherein the new trunk code is obtained by combining one or more branch codes into the original trunk code, and each item identifier in the one or more item identifiers is provided with one branch code.
8. The method of claim 7, further comprising:
deploying an online test task environment for executing an online test task; and
and deploying new trunk branch codes corresponding to the one or more item identifiers in the online test task environment.
9. The method of claim 7, further comprising:
acquiring project demand information, wherein the project demand information comprises project online time and project identification;
under the condition that the project represented by the project identifier meets the online test condition according to the project online time, acquiring a test case corresponding to the project identifier, wherein the test case comprises an original main test case; and
And under the condition that the test cases further comprise branch test cases, the branch test cases are combined into the original main test cases.
10. The method of any one of claims 1-3, further comprising:
and deleting the branch test cases corresponding to the branch test case identifications in the test case deletion request in response to the test case deletion request.
11. A test apparatus comprising:
the first acquisition module is used for responding to a local test task request and acquiring branch codes and test cases corresponding to each item identifier in the local test task request, wherein each test case comprises a main test case;
the first test module is used for testing the branch codes by utilizing the branch test cases under the condition that the test cases further comprise the branch test cases; and
the second test module is used for testing the branch codes by using the main test case under the condition that the test case does not comprise the branch test case;
the generation module is used for generating the branch test case corresponding to the item identifier according to the main test case and the branch code corresponding to the item identifier under the condition that the generation condition of the branch test case is determined to be met;
The generating the branch test case corresponding to the project identifier according to the main test case corresponding to the project identifier and the project branch code comprises the following steps:
and modifying the main test case corresponding to the item identification according to the branch code corresponding to the item identification to obtain the branch test case corresponding to the item identification.
12. The apparatus of claim 11, wherein the meeting a branch test case generation condition comprises:
and testing the branch codes corresponding to the item identifiers by using the main test cases corresponding to the item identifiers, wherein the test results of testing the branch codes corresponding to the item identifiers are test failures.
13. The apparatus of claim 11, wherein the meeting a branch test case generation condition comprises:
and under the condition that the branch codes corresponding to the project identifications are not tested by utilizing the trunk automatic test cases corresponding to the project identifications, determining that the trunk test cases are incompatible with the projects represented by the project identifications according to the interface documents corresponding to the project identifications.
14. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
The memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-10.
15. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1-10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110639754.1A CN113297088B (en) | 2021-06-08 | 2021-06-08 | Test method, test device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110639754.1A CN113297088B (en) | 2021-06-08 | 2021-06-08 | Test method, test device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113297088A CN113297088A (en) | 2021-08-24 |
| CN113297088B true CN113297088B (en) | 2023-11-07 |
Family
ID=77327707
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110639754.1A Active CN113297088B (en) | 2021-06-08 | 2021-06-08 | Test method, test device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113297088B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108874656A (en) * | 2017-05-16 | 2018-11-23 | 北京京东尚科信息技术有限公司 | Code test method, device, readable storage medium storing program for executing and computer equipment |
| CN109388568A (en) * | 2018-09-29 | 2019-02-26 | 百度在线网络技术（北京）有限公司 | Code test method and device |
| CN109388561A (en) * | 2018-09-18 | 2019-02-26 | 深圳壹账通智能科技有限公司 | Interface testing case generation method, device, computer equipment and storage medium |
| CN109766269A (en) * | 2018-12-18 | 2019-05-17 | 微梦创科网络科技（中国）有限公司 | Continuous integrating automated testing method, device, equipment and medium |
| CN111177003A (en) * | 2019-12-30 | 2020-05-19 | 北京同邦卓益科技有限公司 | Test method, device, system, electronic equipment and storage medium |
| CN111708706A (en) * | 2020-06-19 | 2020-09-25 | 重庆赛宝工业技术研究院 | Industrial internet APP automatic test system and test method |
| CN111914262A (en) * | 2020-08-12 | 2020-11-10 | 中国工商银行股份有限公司 | Test method, device, system, electronic equipment and storage medium |
| CN112083948A (en) * | 2020-08-28 | 2020-12-15 | 广州九尾信息科技有限公司 | Automatic construction and deployment method and tool based on data configuration |
| CN112363921A (en) * | 2020-11-09 | 2021-02-12 | 中国平安人寿保险股份有限公司 | Code testing method and device, storage medium and computer equipment |
| CN112597046A (en) * | 2020-12-29 | 2021-04-02 | 上海商汤智能科技有限公司 | Test method, test device, computer equipment and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9710364B2 (en) * | 2015-09-04 | 2017-07-18 | Micron Technology Licensing, Llc | Method of detecting false test alarms using test step failure analysis |
-
2021
- 2021-06-08 CN CN202110639754.1A patent/CN113297088B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108874656A (en) * | 2017-05-16 | 2018-11-23 | 北京京东尚科信息技术有限公司 | Code test method, device, readable storage medium storing program for executing and computer equipment |
| CN109388561A (en) * | 2018-09-18 | 2019-02-26 | 深圳壹账通智能科技有限公司 | Interface testing case generation method, device, computer equipment and storage medium |
| CN109388568A (en) * | 2018-09-29 | 2019-02-26 | 百度在线网络技术（北京）有限公司 | Code test method and device |
| CN109766269A (en) * | 2018-12-18 | 2019-05-17 | 微梦创科网络科技（中国）有限公司 | Continuous integrating automated testing method, device, equipment and medium |
| CN111177003A (en) * | 2019-12-30 | 2020-05-19 | 北京同邦卓益科技有限公司 | Test method, device, system, electronic equipment and storage medium |
| CN111708706A (en) * | 2020-06-19 | 2020-09-25 | 重庆赛宝工业技术研究院 | Industrial internet APP automatic test system and test method |
| CN111914262A (en) * | 2020-08-12 | 2020-11-10 | 中国工商银行股份有限公司 | Test method, device, system, electronic equipment and storage medium |
| CN112083948A (en) * | 2020-08-28 | 2020-12-15 | 广州九尾信息科技有限公司 | Automatic construction and deployment method and tool based on data configuration |
| CN112363921A (en) * | 2020-11-09 | 2021-02-12 | 中国平安人寿保险股份有限公司 | Code testing method and device, storage medium and computer equipment |
| CN112597046A (en) * | 2020-12-29 | 2021-04-02 | 上海商汤智能科技有限公司 | Test method, test device, computer equipment and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 基于概念测试用例的快速需求测试过程框架;荣辉桂;徐小林;陈浩;;计算机系统应用(第08期);全文 * |
| 持续集成测试用例集优化综述研究;李英玲;王青;;软件学报(第10期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113297088A (en) | 2021-08-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102493449B1 (en) | Edge computing test methods, devices, electronic devices and computer-readable media | |
| CN107992409B (en) | Test case generation method and device, computer equipment and storage medium | |
| WO2019161619A1 (en) | Automatic interface test method and apparatus, and device and computer-readable storage medium | |
| CN111782519A (en) | Test method and device and electronic equipment | |
| CN110688305B (en) | Test environment synchronization method, device, medium and electronic equipment | |
| CN113760769A (en) | Test case processing method and device, electronic equipment and storage medium | |
| CN113138768B (en) | Application package generation method and device, electronic equipment and readable storage medium | |
| CN113282444A (en) | Visualization method and device for business process debugging | |
| CN113778849A (en) | Method, apparatus, device and storage medium for testing code | |
| CN113297088B (en) | Test method, test device, electronic equipment and storage medium | |
| CN111782520A (en) | Test method and device and electronic equipment | |
| CN111782518A (en) | Test method and device and electronic equipment | |
| CN111949536A (en) | JAVA application program testing method and system based on bytecode technology | |
| CN114510334A (en) | Class instance calling method and device, electronic equipment and automatic driving vehicle | |
| CN114721686A (en) | Configuration data updating method and device, electronic equipment and storage medium | |
| CN113434382A (en) | Database performance monitoring method and device, electronic equipment and computer readable medium | |
| CN113297081A (en) | Execution method and device of continuous integration assembly line | |
| CN113238901A (en) | Multi-device automatic testing method and device, storage medium and computer device | |
| CN112596750A (en) | Application testing method and device, electronic equipment and computer readable storage medium | |
| CN111209197A (en) | Application program continuous integration test method, system, equipment and storage medium | |
| CN111708545A (en) | Business process deployment method and device, electronic equipment and storage medium | |
| CN113032004A (en) | Method, apparatus and program product for managing development jobs in a development environment | |
| CN113535533B (en) | Method, apparatus, device and storage medium for testing code | |
| CN117435503A (en) | Test tool generation method, test device, test equipment and test medium | |
| CN116303019A (en) | Test tracing method, device, equipment and medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |