CN115061916A - Method for automatically generating interface test case and related equipment thereof - Google Patents
Method for automatically generating interface test case and related equipment thereof Download PDFInfo
- Publication number
- CN115061916A CN115061916A CN202210707047.6A CN202210707047A CN115061916A CN 115061916 A CN115061916 A CN 115061916A CN 202210707047 A CN202210707047 A CN 202210707047A CN 115061916 A CN115061916 A CN 115061916A
- Authority
- CN
- China
- Prior art keywords
- test
- interface
- test interface
- test case
- assertion
- 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.)
- Granted
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 533
- 238000000034 method Methods 0.000 title claims abstract description 87
- 238000004422 calculation algorithm Methods 0.000 claims abstract description 11
- 238000012545 processing Methods 0.000 claims description 14
- 238000013507 mapping Methods 0.000 claims description 10
- 238000000605 extraction Methods 0.000 claims description 2
- 230000010354 integration Effects 0.000 claims 1
- 238000012423 maintenance Methods 0.000 abstract description 2
- 238000012216 screening Methods 0.000 abstract description 2
- 238000005516 engineering process Methods 0.000 description 11
- 238000013473 artificial intelligence Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 238000013461 design Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 2
- 230000006835 compression Effects 0.000 description 2
- 238000007906 compression Methods 0.000 description 2
- 125000004122 cyclic group Chemical group 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000003058 natural language processing Methods 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 206010024796 Logorrhoea Diseases 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 210000001520 comb Anatomy 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000013135 deep learning Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 239000011159 matrix material Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000003062 neural network model Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
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
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 embodiment of the application belongs to the field of operation and maintenance test, is applied to the field of test case automation, and relates to a method for automatically generating an interface test case, which comprises the steps of obtaining a test interface address, assertion data and input parameter data, obtaining a multi-set direct product of the input parameter data based on a Cartesian product combination algorithm, constructing the test case, judging whether the test case obtained before multiplexing can be carried out or not, if multiplexing can be carried out, multiplexing after updating, repeatedly executing, obtaining the test case of the whole test script, generating a full-coverage test case through Cartesian product combination, screening out the reusable test case through test case multiplexing judgment, directly updating and multiplexing, ensuring that the test quality does not depend on the experience and the demand quality of a tester, greatly reducing the threshold of interface automation, ensuring that a novice tester does not need to know business logic, and only needs to lead in the test case in advance, the automated testing of the service can be completed.
Description
Technical Field
The present application relates to the field of operation and maintenance testing and automatic generation of test cases, and in particular, to a method for automatically generating interface test cases and related devices.
Background
A large number of interfaces in a software system need to be tested, and at present, a tester conventionally combs the functions and logic of the interfaces according to a requirement document, inputs interface automation cases according to a test case design method and personal experience, and modifies a large number of cases again after the interfaces are changed.
In the prior art, when interface test case design is carried out, the requirement document quality and the capability of testers are often relied on, but the case quality cannot be guaranteed, business familiarity and case design need to be carried out on each interface, a large amount of manpower and time are consumed, most cases need to be combed and changed again after the interfaces are changed, and the reusability is too low.
Disclosure of Invention
The embodiment of the application aims to provide a method, a device, computer equipment and a storage medium for automatically generating an interface test case, so that a tester can automatically generate the test case without being familiar with business logic, and the test case can be multiplexed and selected.
In order to solve the above technical problem, an embodiment of the present application provides a method for automatically generating an interface test case, which adopts the following technical scheme:
a method for automatically generating interface test cases comprises the following steps:
step S1, based on a preset configuration file, obtaining a current test interface address and entry data corresponding to the current test interface, and setting a first distinguishing name for the interface address, wherein the configuration file comprises: the address of each test interface in the test script, and the mapping relation between each test interface and the list where the input parameter data is located;
step S2, based on the preset assertion form, identifying whether the current test interface uses assertion, if yes, obtaining corresponding assertion data, and setting a second distinguishing name for the assertion data;
step S3, acquiring a multi-set direct product of the parameter data based on a Cartesian product combination algorithm;
step S4, based on the preset judgment mode, judging whether the current test interface can reuse the test case obtained by the previous test interface;
step S5, if the multiplexing is available, the test case corresponding to the previous test interface is updated, and the updated test case is used as the test case of the current test interface;
step S6, if the multiplexing can not be carried out, the first distinguished name, the second distinguished name, the assertion data and the multi-set direct product are used as test data, and a test case corresponding to the current test interface is constructed;
and S7, repeatedly executing the steps S1 to S6, obtaining the test cases corresponding to each test interface, recording the test cases one by one, and taking the final recording result as the test case of the whole test script.
Further, the step of identifying whether the current test interface uses the assertion based on the preset assertion form specifically includes:
the assertions used in the test script are integrated into a preset assertion form as elements in advance;
taking the code content in the test script as a query source, and taking each element in a preset assertion form as a query field, and querying in the query source;
when the assertion is queried, it is confirmed that the assertion is used by the current test interface.
Further, the step of determining whether the current test interface can reuse the test case acquired by the previous test interface based on the preset determination mode specifically includes:
judging whether a code block in a service method corresponding to a current test interface is the same as a code block in a service method corresponding to a previous test interface or not based on a preset first judgment condition;
judging whether the parameter entering format of the current test interface is the same as the parameter entering format of the previous test interface or not based on a preset second judgment condition;
if the judgment results of the first judgment condition and the second judgment condition are the same, the current test interface can reuse the test case obtained by the previous test interface;
and if any judgment result of the first judgment condition and the second judgment condition is different, the current test interface can not reuse the test case acquired by the previous test interface.
Further, the step of determining whether the code block in the service method corresponding to the current test interface is the same as the code block in the service method corresponding to the previous test interface based on the preset first determination condition specifically includes:
if the assertion is not used in the current test interface and the test interface which obtains the test case before, or the assertion is used in the current test interface and the test interface which obtains the test case before, and the assertion data is the same, obtaining a code block in a service method corresponding to the current test interface as a first code block, and obtaining a code block in a service method corresponding to the previous test interface as a second code block;
dividing codes in the first code block and the second code block into a non-variable code part and a variable code part, wherein the variable code part refers to a variable name, a method name and a self-defining method name of a callback, which are self-defined by a programmer, and the non-variable code part refers to code which is self-defined by the programmer;
extracting features of non-variable code parts in the first code block and the second code block based on preset English BERT to obtain a first feature and a second feature;
comparing the extracted first characteristic with the extracted second characteristic, and judging whether the comparison results are the same;
if the comparison result is the same, confirming that the code block in the service method corresponding to the current test interface is the same as the code block in the service method corresponding to the previous test interface;
and if the comparison result is different, determining that the code block in the service method corresponding to the current test interface is different from the code block in the service method corresponding to the previous test interface.
Further, the step of extracting features of the non-variable code portions in the first code block and the second code block based on the preset english BERT specifically includes:
inputting each English word in a non-variable code part in the first code block and the second code block into a preset English BERT;
respectively acquiring a position vector and a word vector of each English word in a non-variable code part in the first code block and the second code block;
taking the position vector and the word vector of each English word in the non-variable code part in the first code block as code features corresponding to the first code block, and recording the code features as first features;
and taking the position vector and the word vector of each English word in the non-variable code part in the second code block as the code features corresponding to the second code block, and recording the code features as second features.
Further, the step of determining whether the reference format of the current test interface is the same as the reference format of the previous test interface based on a preset second determination condition specifically includes:
respectively acquiring the input parameter data types and the input parameter quantities of the current test interface and the previous test interface;
judging whether the input parameter data types and the input parameter quantities of the current test interface and the previous test interface are the same;
if the input parameter data types and the input parameter quantities of the current test interface and the previous test interface are the same, confirming that the input format of the current test interface is the same as that of the previous test interface;
and if any of the input parameter data types and the input parameter numbers of the two interfaces are different, confirming that the input format of the current test interface is different from the input format of the previous test interface.
Further, the step of updating the test case corresponding to the previous test interface and taking the updated test case as the test case of the current test interface specifically includes:
replacing the first distinguished name corresponding to the current test interface with the name of the test case of the previous test interface;
and taking the test case of the replaced previous test interface as the test case of the current test interface.
Further, the step of constructing a test case corresponding to the current test interface by using the first distinguished name, the second distinguished name, the assertion data, and the multi-set direct product as test data specifically includes:
taking a direct product corresponding to the current test interface as set data, taking a first distinguishing name corresponding to the set data as a set name, and constructing a configuration data set;
if the current test interface does not use the assertion, the configuration data set is directly set as a test case corresponding to the current test interface;
if the current test interface uses the assertion, the assertion data is used as a key value, a corresponding second distinguishing name is used as a key name key, a key-value type key value pair is constructed, the key-value type key value pair is used as a set element and is added into the configuration data set, and then the configuration data set is set as a test case corresponding to the current test interface.
In order to solve the above technical problem, an embodiment of the present application further provides an apparatus for automatically generating an interface test case, which adopts the following technical scheme:
an automated generate interface test case apparatus, comprising:
the interface address processing module is used for acquiring a current test interface address and entry data corresponding to the current test interface based on a preset configuration file, and setting a first distinguishing name for the interface address, wherein the configuration file comprises: the address of each test interface in the test script, and the mapping relation between each test interface and the list where the input parameter data is located;
the assertion data processing module is used for identifying whether the current test interface uses assertion or not based on a preset assertion form, acquiring corresponding assertion data if the assertion is used, and setting a second distinguishing name for the assertion data;
the Cartesian product combination module is used for acquiring a multi-set direct product of the input parameter data based on a Cartesian product combination algorithm;
the multiplexing pre-judgment module is used for judging whether the current test interface can multiplex the test cases acquired by the previous test interface or not based on a preset judgment mode;
the first test case generation module is used for updating the test case corresponding to the previous test interface if the test case can be reused, and taking the updated test case as the test case of the current test interface;
the second test case generation module is used for taking the first distinguished name, the second distinguished name, the assertion data and the multi-set direct product as test data and constructing a test case corresponding to the current test interface if the multiplexing cannot be performed;
and the cyclic execution module is used for repeatedly executing the steps S1 to S6, obtaining the test cases corresponding to each test interface, recording the test cases one by one, and taking the final recording result as the test case of the whole test script.
Compared with the prior art, the embodiment of the application mainly has the following beneficial effects:
the method for automatically generating the interface test case comprises the steps of identifying whether the current test interface uses assertion or not by obtaining the address of the current test interface, obtaining assertion data, obtaining reference data of the current test interface, obtaining a multi-set direct product of the reference data based on a Cartesian product combination algorithm, constructing a test case corresponding to the current test interface, judging whether the current test interface can reuse the test case obtained by the previous test interface or not before constructing the test case corresponding to the current test interface based on a preset judgment mode, if the current test interface can be reused, updating the test case corresponding to the previous test interface, updating the updated test case, namely the test case of the current test interface, repeatedly executing the test case, obtaining the test case respectively corresponding to each test interface as the test case of the whole test script, and generating the full-coverage test case through Cartesian product combination, and the reusable test cases are screened out through the test case reuse judgment, the reuse is directly updated, the test quality does not depend on the experience and the required quality of a tester, the threshold of interface automation is greatly reduced, and a novice tester does not need to know the business logic, and can complete the automatic test of the business only by leading in the test cases in advance.
Drawings
In order to more clearly illustrate the solution of the present application, the drawings needed for describing the embodiments of the present application will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and that other drawings can be obtained by those skilled in the art without inventive effort.
FIG. 1 is an exemplary system architecture diagram to which the present application may be applied;
FIG. 2 is a flow diagram of one embodiment of a method for automatically generating interface test cases in accordance with the present application;
FIG. 3 is a flowchart of one embodiment of step S4 shown in FIG. 2;
FIG. 4 is a flowchart of one embodiment of step S401 shown in FIG. 3;
FIG. 5 is a flowchart of one embodiment of step S4013 shown in FIG. 4;
FIG. 6 is a flowchart of one embodiment of step S402 shown in FIG. 3;
FIG. 7 is a block diagram illustrating one embodiment of an apparatus for automatically generating interface test cases in accordance with the present application;
FIG. 8 is a schematic diagram of the structure of one embodiment of 703 shown in FIG. 7;
FIG. 9 is a block diagram of one embodiment of a computer device according to the present application.
Detailed Description
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "including" and "having," and any variations thereof, in the description and claims of this application and the description of the above figures are intended to cover non-exclusive inclusions. The terms "first," "second," and the like in the description and claims of this application or in the above-described drawings are used for distinguishing between different objects and not for describing a particular order.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.
As shown in fig. 1, the system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
A user may use terminal devices 101, 102, 103 to interact with a server 105 over a network 104 to receive or send messages or the like. The terminal devices 101, 102, 103 may have various communication client applications installed thereon, such as a web browser application, a shopping application, a search application, an instant messaging tool, a mailbox client, social platform software, and the like.
The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III, mpeg compression standard Audio Layer 3), MP4 players (Moving Picture Experts Group Audio Layer iv, mpeg compression standard Audio Layer 4), laptop portable computers, desktop computers, and the like.
The server 105 may be a server providing various services, such as a background server providing support for pages displayed on the terminal devices 101, 102, 103.
It should be noted that, the method for automatically generating an interface test case provided in the embodiment of the present application is generally executed by a server/terminal device, and accordingly, an apparatus for automatically generating an interface test case is generally disposed in the server/terminal device.
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.
With continued reference to FIG. 2, a flowchart of one embodiment of a method for automatically generating interface test cases is shown, in accordance with the present application. The method for automatically generating the interface test case comprises the following steps:
step S1, based on a preset configuration file, obtaining a current test interface address and entry parameter data corresponding to the current test interface, and setting a first distinguishing name for the interface address, where the configuration file includes: and (4) mapping relations among the addresses of all the test interfaces, all the test interfaces and the list where the input parameters of the test interfaces are located in the test script.
In this embodiment, the current test interface address includes: the protocol part, the domain name part and the parameter part can also comprise a port part, a virtual directory part, a file name part and an anchor part, when in specific setting, the interface address is directly used as a variable value, a first distinguished name is set as a variable name, and the configuration file comprises: and testing each test interface address in the script.
In this embodiment, the configuration file includes a mapping relationship between each test interface and a form in which the input parameter data of each test interface is located, so as to obtain the input parameter data of each test interface through the mapping relationship.
Step S2, based on the preset assertion form, identifying whether the current test interface uses assertion, if yes, obtaining corresponding assertion data, and setting a second distinguishing name for the assertion data.
In this embodiment, the step of identifying whether the current test interface uses the assertion based on the preset assertion form specifically includes: the method comprises the steps that an assertion used in a test script is integrated into a preset assertion form as an element in advance; taking the code content in the test script as a query source, and taking each element in a preset assertion form as a query field, and querying in the query source; when the assertion is queried, it is confirmed that the assertion is used by the current test interface.
In this embodiment, correspondingly, when it is determined that the assertion is used in the current test interface, the first distinguished name corresponding to the current test interface may be obtained, two sets are constructed, and the first distinguished name corresponding to the test interface using the assertion and the first distinguished name corresponding to the test interface not using the assertion are respectively stored.
In this embodiment, a first distinguishing name corresponding to a current test interface is obtained, two sets are constructed, and the first distinguishing name corresponding to a test interface using assertion and the first distinguishing name corresponding to a test interface not using assertion are respectively stored.
Taking assertion "Status code is 200" as an example, that is, if the assertion response Status code is 200, taking assertion "Status code is 200" as a query field, querying in the code content in the test script, and if "Status code is 200" is queried, acquiring the first difference name of the test interface corresponding to the assertion.
In this embodiment, if an assertion is used, corresponding assertion data is obtained, and a second distinguished name is set for the assertion data, because the assertion data corresponding to the assertion is often a section of judgment statement, in order to facilitate automated test case generation and later automated testing, the second distinguished name is set for the assertion, the second distinguished name is used as a variable name, and specific assertion data is used as a variable value.
And step S3, acquiring a multi-set direct product of the parameter data based on a Cartesian product combination algorithm.
In this embodiment, it is assumed that the number of parameter entries of the current test interface is 3, which are an account, a password, and a verification code, where the account is stored in the first form, the retrievable data is "{ twilight, small flower }", the password is stored in the second form, the retrievable data is "{ 111, 222 }", the verification code is stored in the third form, the retrievable data is "{ aaa, bbb }", the configuration file includes a mapping relationship between each test interface and a form in which the parameter entry data of each test interface is located, and the parameter entry data of each test interface is obtained through the mapping relationship.
In this embodiment, a multiple-set direct product between the account number, the password and the authentication code is directly obtained based on a cartesian product combination algorithm, in which each input parameter used is taken as a 1 × n matrix, i.e., a set of 1 row and n columns, and then, one element is obtained from each set to perform multiplication, so as to obtain possible results of all the multiplication products, i.e., the results of the cartesian product combination algorithm, taking the account number, the password and the authentication code as an example, the first set is { smallness, floret }, the second set is {111, 222}, and the third set is { aaa, bbb }, i.e., the results of "{ (smallness, 111, aaa), (smallness, 111, bbb), (smallness, 222, aaa), (smallness, 111, aaa), (111, bbb), (smallness, 222, aaa), (smallness, 222, bbb) } ", aiming at realizing full coverage of the reference combination of the test interface and effectively improving the test coverage rate and quality.
And step S4, judging whether the current test interface can reuse the test cases acquired by the previous test interface based on a preset judgment mode.
With continuing reference to fig. 3, a flowchart of an embodiment of step S4 depicted in fig. 2 is shown, which specifically includes:
step S401, based on a preset first judgment condition, judging whether a code block in a service method corresponding to a current test interface is the same as a code block in a service method corresponding to a previous test interface.
With continuing reference to fig. 4, a flowchart of an embodiment of step S401 shown in fig. 3 is shown, which specifically includes:
step S4011, if there are no assertions used by the current test interface and the test interface which has previously acquired the test case, or both assertions are used and the assertion data are the same, acquiring a code block in a service method corresponding to the current test interface as a first code block, and acquiring a code block in a service method corresponding to the previous test interface as a second code block;
step S4012, dividing the codes in the first code block and the second code block into a non-variable code portion and a variable code portion, where the variable code portion refers to a programmer-defined variable name, a method name, and a callback-defined method name, and the non-variable code portion refers to a non-programmer-defined code;
step S4013, extracting features of non-variable code parts in the first code block and the second code block based on preset English BERT to obtain a first feature and a second feature;
step S4014, comparing the extracted first characteristic and the extracted second characteristic, and judging whether the comparison results are the same;
step S4015, if the comparison result is the same, confirming that the code block in the service method corresponding to the current test interface is the same as the code block in the service method corresponding to the previous test interface;
step S4016, if the comparison result is different, it is determined that the code block in the service method corresponding to the current test interface is different from the code block in the service method corresponding to the previous test interface.
Before generating a test case for a current test interface, searching a previous test interface which does not use assertion or uses assertion and has the same assertion data, further acquiring non-variable code parts of service codes in the current test interface and the previous test interface, if the characteristics of the two are the same through English BERT analysis, defaulting that the service codes of the two are equivalent, preliminarily judging that the test case of the previous test interface can be reused, avoiding that a tester blindly generates the test case after receiving a test task to cause verbosity of the test case, and simultaneously, carrying out the equivalent judgment of the service codes through the comparison mode without requiring the tester to be familiar with the service contents of the test interface before writing the test case, and carrying out the manual operation by a new tester.
With continuing reference to fig. 5, a flowchart of an embodiment of step S4013 in fig. 4 is shown, which specifically includes:
step S40131, inputting each english word in the non-variable code portion in the first code block and the second code block into a preset english BERT;
step S40132, respectively obtaining a position vector and a word vector of each english word in the non-variable code portion in the first code block and the second code block;
step S40133, taking the position vector and word vector of each English word in the non-variable code part in the first code block as the code features corresponding to the first code block, and recording as the first features;
step S40134, taking the position vector and the word vector of each english word in the non-variable code portion in the second code block as the code features corresponding to the second code block, and marking them as the second features.
The position vector and the word vector of each English word in the non-variable code part are directly obtained through the English BERT, the position vector and the word vector are directly used as code features, when the position vector and the word vector are compared, each English word in the non-variable code part in the first code block and the second code block is directly compared one by one, a neural network model is not required to be introduced again for feature value calculation, the mode is simple, and the feature comparison effect can be achieved.
Step S402, based on the preset second judgment condition, judging whether the parameter format of the current test interface is the same as the parameter format of the previous test interface.
With continuing reference to fig. 6, a flowchart of an embodiment of step S402 shown in fig. 3 is shown, which specifically includes:
step S4021, respectively acquiring the input parameter data types and the input parameter quantities of the current test interface and the previous test interface;
step S4022, judging whether the data types and the quantity of the input parameters of the current test interface and the previous test interface are the same;
step S4023, if the input parameter data types and the input parameter numbers of the two are the same, confirming that the input format of the current test interface is the same as the input format of the previous test interface;
step S4024, if the input parameter data type and the input parameter quantity of the two are different, determining that the input format of the current test interface is different from the input format of the previous test interface.
By judging the input parameter data types and the input parameter quantities of the current test interface and the previous test interface, if the input parameter quantities are the same, the method ensures that the format of the Cartesian direct product result of the test case in the previous test interface is the same as the Cartesian direct product result of the parameter input data of the current test interface, avoids the condition that the test case is unavailable due to different parameter input quantities, meanwhile, the judgment of the type of the input parameter data is to distinguish the type of the input parameter data which can not be converted by the compiler, for data of int, char and String types, the compiler can convert itself, however, if the data type of the input parameter of the current test interface is Boolean judgment type and the data type of the input parameter of the previous test interface is numerical type, the automatic conversion cannot be carried out, therefore, and judging whether the input parameter data types confirm whether the two interfaces can be subjected to test case multiplexing or not.
Step S403, if the determination results of the first determination condition and the second determination condition are the same, the current test interface may reuse the test case obtained by the previous test interface.
Step S404, if any judgment result of the first judgment condition and the second judgment condition is different, the current test interface can not reuse the test case acquired by the previous test interface.
Before the current test interface generates the test case, the multiplexing prepositive judgment is firstly carried out to judge whether the test case generated by the previous test interface can be multiplexed or not, so that the problem that the test case is long due to the fact that the test case is constructed blindly after test tasks are increased is avoided, in addition, in the test process, if the test case of the previous test interface can be directly multiplexed, the time consumption for creating the test case can be relatively reduced, and the common test case library can be constructed for codes of the same business logic after more and more test interfaces are provided.
And step S5, if the multiplexing is available, updating the test case corresponding to the previous test interface, and taking the updated test case as the test case of the current test interface.
In this embodiment, the step of updating the test case corresponding to the previous test interface and taking the updated test case as the test case of the current test interface specifically includes: replacing the first distinguished name corresponding to the current test interface with the name of the test case of the previous test interface; and taking the test case of the replaced previous test interface as the test case of the current test interface.
Directly replacing a first distinguishing name corresponding to the current test interface with the name of a test case of the previous test interface, wherein the first distinguishing name corresponds to the interface address of the current test interface, so that the interface address is replaced indirectly, only the first distinguishing name is replaced, and when the test is called, the interface address corresponding to the current test interface is determined through the first distinguishing name to carry out the test.
And step S6, if the multiplexing is impossible, the first distinguished name, the second distinguished name, the assertion data and the multi-set direct product are used as test data to construct a test case corresponding to the current test interface.
In this embodiment, the step of constructing the test case corresponding to the current test interface by using the first distinguished name, the second distinguished name, the assertion data, and the multi-set direct product as test data specifically includes:
taking a direct product corresponding to the current test interface as set data, taking a first distinguishing name corresponding to the set data as a set name, and constructing a configuration data set;
if the current test interface does not use the assertion, the configuration data set is directly set as a test case corresponding to the current test interface;
if the current test interface uses the assertion, the assertion data is used as a key value, a corresponding second distinguishing name is used as a key name key, a key-value type key value pair is constructed, the key-value type key value pair is used as a set element and is added into the configuration data set, and then the configuration data set is set as a test case corresponding to the current test interface.
Assuming that the direct product corresponding to the current test interface is "{ (mingming, 111, aaa), (mingming, 111, bbb), (mingming, 222, aaa), (mingming, 222, bbb), (floret, 111, aaa), (floret, 111, bbb), (floret, 222, aaa), (floret, 222, bbb) } and the first region alias is" URL _1 ", the configuration data set is constructed by using" URL _1 "as the direct product set name in the test case and the direct product as the set data.
If the current test interface does not use assertion, the configuration data set is directly used as a test case of the current test interface, and the test case can acquire the access data and the test interface address according to the first distinguished name.
If the current test interface uses assertion, the assertion data is "Status code is 200", the second distinguished name is "Status _ 1", the assertion data "Status code is 200" is used as a key value, the corresponding second distinguished name "Status _ 1" is used as a key name, a key-value type key value pair, namely [ "Status _ 1": Status code is 200 "], is used as a set element and is added into the configuration data set, and then the configuration data set is set as the test case corresponding to the current test interface, that is, a new configuration data set is generated: "{ (Xiaoming, 111, aaa), (Xiaoming, 111, bbb), (Xiaoming, 222, aaa), (Xiaoming, 222, bbb), (Xiaohua, 111, aaa), (Xiaohua, 111, bbb), (Xiaohua, 222, aaa), (Xiaohua, 222, bbb), [" Status _1 ": Status code is 200" ] } ", and the new configuration data set is used as a test case of the current test interface.
And S7, repeatedly executing the steps S1 to S6, obtaining the test cases corresponding to each test interface, recording the test cases one by one, and taking the final recording result as the test case of the whole test script.
In addition, in this embodiment, after the test interface is newly added or updated, step S1 to step S6 are also executed to generate test cases, so that a large number of test cases with duplicate business logic can be prevented from being generated.
The embodiment of the application can acquire and process related data based on an artificial intelligence technology. Among them, Artificial Intelligence (AI) is a theory, method, technique and application system that simulates, extends and expands human Intelligence using a digital computer or a machine controlled by a digital computer, senses the environment, acquires knowledge and uses the knowledge to obtain the best result.
The artificial intelligence infrastructure generally includes technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technologies, operation/interaction systems, mechatronics, and the like. The artificial intelligence software technology mainly comprises a computer vision technology, a robot technology, a biological recognition technology, a voice processing technology, a natural language processing technology, machine learning/deep learning and the like.
Specifically, in the embodiment of the present application, the steps of the method for automatically generating an interface test case may be integrated into a dedicated artificial intelligence chip.
In addition, in the embodiment of the application, the first feature and the second feature are obtained based on preset English BERT, and the method belongs to a natural language processing technology in an artificial intelligence basic technology.
The automatic generation of the interface test case can be further ensured by utilizing an artificial intelligence technology.
The method comprises the steps of obtaining a test interface address, assertion data and input parameter data, obtaining a multi-set direct product of the input parameter data based on a Cartesian product combination algorithm, constructing a test case, judging whether the test case obtained before multiplexing can be used, multiplexing after updating if multiplexing can be carried out, repeatedly executing, obtaining the test case of the whole test script, generating a full-coverage test case through Cartesian product combination, screening out reusable test cases through test case multiplexing judgment, directly updating and multiplexing, enabling the test quality to be independent of experience and demand quality of a tester, greatly reducing the threshold of interface automation, enabling a novice tester to finish automatic test of services only by leading in the test case in advance without knowing service logic.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware associated with computer readable instructions, which can be stored in a computer readable storage medium, and when executed, the processes of the embodiments of the methods described above can be included. The storage medium may be a non-volatile storage medium such as a magnetic disk, an optical disk, a Read-Only Memory (ROM), or a Random Access Memory (RAM).
It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least a portion of the steps in the flow chart of the figure may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
With further reference to fig. 7, as an implementation of the method shown in fig. 2, the present application provides an embodiment of an apparatus for automatically generating interface test cases, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 2, and the apparatus may be specifically applied to various electronic devices.
As shown in fig. 7, the device 700 for automatically generating an interface test case according to this embodiment includes: the device comprises an interface address processing module 701, an assertion data processing module 702, a Cartesian product combination module 703, a multiplexing pre-judgment module 704, a first test case generation module 705 and a cyclic execution module 707. Wherein:
an interface address processing module 701, configured to obtain, based on a preset configuration file, a current test interface address and entry data corresponding to the current test interface, and set a first difference name for the interface address, where the configuration file includes: the address of each test interface in the test script, and the mapping relation between each test interface and the list where the input parameter data is located;
the assertion data processing module 702 is configured to identify whether the current test interface uses assertion based on a preset assertion form, and if yes, obtain corresponding assertion data thereof, and set a second difference name for the assertion data;
a cartesian product combining module 703, configured to obtain a multi-set direct product of the input parameter data based on a cartesian product combining algorithm;
the multiplexing pre-judgment module 704 is configured to judge whether the current test interface can multiplex the test case obtained by the previous test interface based on a preset judgment mode;
the test case first generation module 705 is configured to update the test case corresponding to the previous test interface if multiplexing is possible, and use the updated test case as the test case of the current test interface;
a second test case generation module 706, configured to use the first distinguished name, the second distinguished name, the assertion data, and the multi-set direct product as test data to construct a test case corresponding to the current test interface if multiplexing is not possible;
and the circular execution module 707 is configured to obtain the test cases corresponding to each test interface in a circular execution manner, record the test cases one by one, and use a final record result as the test case of the whole test script.
According to the device for automatically generating the interface test case, relevant data required by generating the interface test case is acquired through the interface address processing module 701, the assertion data processing module 702 and the cartesian product combining module 703, different modules are respectively used for acquiring different configuration data, and the coupling degree between the configuration data is reduced; meanwhile, the multiplexing prepositive judgment module 704 is adopted to judge whether the test case generated by the test interface before the current test interface can be multiplexed or not in advance before the test case is generated, so that the problem that the test case content is long due to blind generation of the interface test case is avoided, and the workload of a tester is reduced to a certain extent; the reusable test cases are screened out through test case reuse judgment, reuse is directly updated, test quality does not depend on experience and required quality of testers, the threshold of interface automation is greatly reduced, and novice testers do not need to know business logic and only need to introduce the test cases in advance to finish automatic test of business.
Referring to fig. 8, which is a schematic structural diagram of an embodiment of the multiplexing pre-judgment module, the multiplexing pre-judgment module 704 includes a first judgment sub-module 7041, a second judgment sub-module 7042, and a third judgment sub-module 7043,
the first determining sub-module 7041 is configured to determine, based on a preset first determining condition, whether a code block in a service method corresponding to a current test interface is the same as a code block in a service method corresponding to a previous test interface, and specifically, the first determining sub-module 7041 includes:
a code block obtaining unit, configured to obtain, if neither an assertion nor assertion is used by a current test interface or a test interface that has previously obtained a test case, or both assertions and assertion data are the same, a code block in a service method corresponding to the current test interface as a first code block and a code block in a service method corresponding to the previous test interface as a second code block;
a code block classifying unit, configured to divide the codes in the first code block and the second code block into a non-variable code portion and a variable code portion, where the variable code portion refers to a programmer-defined variable name, a method name, and a callback-defined custom method name, and the non-variable code portion refers to a non-programmer-defined code;
the characteristic extraction unit is used for extracting the characteristics of the non-variable code parts in the first code block and the second code block based on preset English BERT to obtain a first characteristic and a second characteristic;
the characteristic comparison unit is used for comparing the extracted first characteristic with the extracted second characteristic and judging whether the comparison results are the same or not; if the comparison result is the same, confirming that the code block in the service method corresponding to the current test interface is the same as the code block in the service method corresponding to the previous test interface; and if the comparison result is different, determining that the code block in the service method corresponding to the current test interface is different from the code block in the service method corresponding to the previous test interface.
The second determining sub-module 7042 is configured to determine, based on a preset second determining condition, whether the parameter entry format of the current test interface is the same as the parameter entry format of the previous test interface, and specifically, the second determining sub-module 7042 includes:
the device comprises an access type and quantity acquisition unit, a parameter acquisition unit and a parameter acquisition unit, wherein the access type and quantity acquisition unit is used for respectively acquiring the access parameter data types and the access parameter quantities of a current test interface and a previous test interface;
the parameter input type and quantity comparison unit is used for judging whether the parameter input data types and the parameter input quantities of the current test interface and the previous test interface are the same or not; if the input parameter data types and the input parameter quantities of the current test interface and the previous test interface are the same, confirming that the input format of the current test interface is the same as that of the previous test interface; and if any of the input parameter data types and the input parameter numbers of the two interfaces are different, confirming that the input format of the current test interface is different from the input format of the previous test interface.
A third judging sub-module 7043, configured to, if the judgment results of the first judging condition and the second judging condition are the same, reuse the test case obtained by the previous test interface by the current test interface, and otherwise, not reuse the test case obtained by the previous test interface by the current test interface.
In order to solve the technical problem, an embodiment of the present application further provides a computer device. Referring to fig. 9, fig. 9 is a block diagram of a basic structure of a computer device according to the present embodiment.
The computer device 9 comprises a memory 91, a processor 92, a network interface 93 communicatively connected to each other via a system bus. It is noted that only a computer device 9 having components 91-93 is shown, but it is understood that not all of the shown components are required to be implemented, and that more or fewer components may be implemented instead. As will be understood by those skilled in the art, the computer device herein is a device capable of automatically performing numerical calculation and/or information processing according to preset or stored instructions, and the hardware thereof includes but is not limited to a microprocessor, an Application Specific Integrated Circuit (ASIC), a Programmable Gate Array (FPGA), a Digital Signal Processor (DSP), an embedded device, and the like.
The computer device can be a desktop computer, a notebook, a palm computer, a cloud server and other computing devices. The computer equipment can carry out man-machine interaction with a user in a keyboard mode, a mouse mode, a remote controller mode, a touch panel mode or a voice control equipment mode.
The memory 91 includes at least one type of readable storage medium including a flash memory, a hard disk, a multimedia card, a card type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, etc. In some embodiments, the storage 91 may be an internal storage unit of the computer device 9, such as a hard disk or a memory of the computer device 9. In other embodiments, the memory 91 may also be an external storage device of the computer device 9, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, provided on the computer device 9. Of course, the memory 91 may also comprise both an internal memory unit and an external memory device of the computer device 9. In this embodiment, the memory 91 is generally used for storing an operating system installed in the computer device 9 and various application software, such as computer readable instructions of a method for automatically generating interface test cases. Further, the memory 91 may also be used to temporarily store various types of data that have been output or are to be output.
The processor 92 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments. The processor 92 is typically used to control the overall operation of the computer device 9. In this embodiment, the processor 92 is configured to execute the computer readable instructions or process data stored in the memory 91, for example, execute the computer readable instructions of the method for automatically generating interface test cases.
The network interface 93 may comprise a wireless network interface or a wired network interface, and the network interface 93 is generally used for establishing communication connection between the computer device 9 and other electronic devices.
Through the description of the foregoing embodiments, it is clear to those skilled in the art that the method of the foregoing embodiments may be implemented by software plus a necessary general hardware platform, and certainly may also be implemented by hardware, but in many cases, the former is a better implementation. Based on such understanding, the technical solutions of the present application or portions thereof that contribute to the prior art may be embodied in the form of a software product, where the computer software product is stored in a storage medium (such as a ROM/RAM, a magnetic disk, and an optical disk), and includes several instructions for enabling a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.
It is to be understood that the above-described embodiments are merely illustrative of some, but not restrictive, of the broad invention, and that the appended drawings illustrate preferred embodiments of the invention and do not limit the scope of the invention. This application is capable of embodiments in many different forms and is provided for the purpose of enabling a thorough understanding of the disclosure of the application. Although the present application has been described in detail with reference to the foregoing embodiments, it will be apparent to one skilled in the art that the present application may be practiced without modification or with equivalents of some of the features described in the foregoing embodiments. All equivalent structures made by using the contents of the specification and the drawings of the present application are directly or indirectly applied to other related technical fields and are within the protection scope of the present application.
Claims (11)
1. A method for automatically generating an interface test case is characterized by comprising the following steps:
step S1, based on a preset configuration file, obtaining a current test interface address and entry parameter data corresponding to the current test interface, and setting a first distinguishing name for the interface address, where the configuration file includes: the address of each test interface in the test script, and the mapping relation between each test interface and the list where the input parameter data is located;
step S2, based on the preset assertion form, identifying whether the current test interface uses assertion, if yes, obtaining corresponding assertion data, and setting a second distinguishing name for the assertion data;
step S3, acquiring a multi-set direct product of the parameter data based on a Cartesian product combination algorithm;
step S4, based on the preset judgment mode, judging whether the current test interface can reuse the test case obtained by the previous test interface;
step S5, if the multiplexing is available, the test case corresponding to the previous test interface is updated, and the updated test case is used as the test case of the current test interface;
step S6, if the multiplexing can not be carried out, the first distinguished name, the second distinguished name, the assertion data and the multi-set direct product are used as test data, and a test case corresponding to the current test interface is constructed;
and S7, repeatedly executing the steps S1 to S6, obtaining the test cases corresponding to each test interface, recording the test cases one by one, and taking the final recording result as the test case of the whole test script.
2. The method for automatically generating an interface test case according to claim 1, wherein the step of identifying whether the current test interface uses the assertion based on the preset assertion form specifically comprises:
the assertions used in the test script are integrated into a preset assertion form as elements in advance;
taking the code content in the test script as a query source, and taking each element in a preset assertion form as a query field, and querying in the query source;
when the assertion is queried, it is confirmed that the assertion is used by the current test interface.
3. The method according to claim 1, wherein the step of determining whether the current test interface can reuse the test case obtained by the previous test interface based on a preset determination mode specifically comprises:
judging whether a code block in a service method corresponding to a current test interface is the same as a code block in a service method corresponding to a previous test interface or not based on a preset first judgment condition;
judging whether the parameter entering format of the current test interface is the same as the parameter entering format of the previous test interface or not based on a preset second judgment condition;
if the judgment results of the first judgment condition and the second judgment condition are the same, the current test interface can reuse the test case obtained by the previous test interface;
and if any judgment result of the first judgment condition and the second judgment condition is different, the current test interface can not reuse the test case acquired by the previous test interface.
4. The method for automatically generating an interface test case according to claim 3, wherein the step of determining whether the code block in the service method corresponding to the current test interface is the same as the code block in the service method corresponding to the previous test interface based on a preset first determination condition specifically includes:
if the assertion is not used in the current test interface and the test interface which obtains the test case before, or the assertion is used in the current test interface and the test interface which obtains the test case before, and the assertion data is the same, obtaining a code block in a service method corresponding to the current test interface as a first code block, and obtaining a code block in a service method corresponding to the previous test interface as a second code block;
dividing codes in the first code block and the second code block into a non-variable code part and a variable code part, wherein the variable code part refers to a variable name, a method name and a self-defining method name of a callback, which are self-defined by a programmer, and the non-variable code part refers to code which is self-defined by the programmer;
performing feature extraction on non-variable code parts in the first code block and the second code block based on preset English BERT to obtain a first feature and a second feature;
comparing the extracted first characteristic with the extracted second characteristic, and judging whether the comparison results are the same;
if the comparison result is the same, confirming that the code block in the service method corresponding to the current test interface is the same as the code block in the service method corresponding to the previous test interface;
and if the comparison result is different, determining that the code block in the service method corresponding to the current test interface is different from the code block in the service method corresponding to the previous test interface.
5. The method for automatically generating interface test cases according to claim 4, wherein the step of extracting features of the non-variable code portions in the first code block and the second code block based on the preset English BERT specifically includes:
inputting each English word in a non-variable code part in the first code block and the second code block into a preset English BERT;
respectively acquiring a position vector and a word vector of each English word in a non-variable code part in the first code block and the second code block;
taking the position vector and the word vector of each English word in the non-variable code part in the first code block as the code characteristics corresponding to the first code block, and recording as first characteristics;
and taking the position vector and the word vector of each English word in the non-variable code part in the second code block as the code features corresponding to the second code block, and recording the code features as second features.
6. The method for automatically generating an interface test case according to claim 3, wherein the step of determining whether the reference format of the current test interface is the same as the reference format of the previous test interface based on a preset second determination condition specifically includes:
respectively acquiring the input parameter data types and the input parameter quantities of the current test interface and the previous test interface;
judging whether the input parameter data types and the input parameter quantities of the current test interface and the previous test interface are the same;
if the input parameter data types and the input parameter quantities of the current test interface and the previous test interface are the same, confirming that the input format of the current test interface is the same as that of the previous test interface;
and if any of the input parameter data types and the input parameter numbers of the two interfaces are different, confirming that the input format of the current test interface is different from the input format of the previous test interface.
7. The method according to claim 1, wherein the step of updating the test case corresponding to the previous test interface and taking the updated test case as the test case of the current test interface specifically includes:
replacing the first distinguished name corresponding to the current test interface with the name of the test case of the previous test interface;
and taking the test case of the replaced previous test interface as the test case of the current test interface.
8. The method according to claim 1, wherein the step of constructing the test case corresponding to the current test interface by using the first distinguished name, the second distinguished name, the assertion data, and the multi-set direct product as test data specifically includes:
taking a direct product corresponding to the current test interface as set data, taking a first distinguishing name corresponding to the set data as a set name, and constructing a configuration data set;
if the current test interface does not use the assertion, the configuration data set is directly set as a test case corresponding to the current test interface;
if the current test interface uses the assertion, the assertion data is used as a key value, a corresponding second distinguishing name is used as a key name key, a key-value type key value pair is constructed, the key-value type key value pair is used as a set element and is added into the configuration data set, and then the configuration data set is set as a test case corresponding to the current test interface.
9. An automated interface generation test case apparatus, comprising:
the interface processing module is used for acquiring a current test interface address and the access data corresponding to the current test interface based on a preset configuration file, and setting a first distinguishing name for the interface address, wherein the configuration file comprises: the address of each test interface in the test script, and the mapping relation between each test interface and the list where the input parameter data is located;
the assertion data processing module is used for identifying whether the current test interface uses assertion or not based on a preset assertion form, acquiring corresponding assertion data if the assertion is used, and setting a second distinguishing name for the assertion data;
the Cartesian product combination module is used for acquiring a multi-set direct product of the input parameter data based on a Cartesian product combination algorithm;
the multiplexing preposed judging module is used for judging whether the current test interface can multiplex the test cases acquired by the previous test interface based on a preset judging mode;
the first test case generation module is used for updating the test case corresponding to the previous test interface if the test case can be reused, and taking the updated test case as the test case of the current test interface;
the second test case generation module is used for taking the first distinguished name, the second distinguished name, the assertion data and the multi-set direct product as test data and constructing a test case corresponding to the current test interface if the multiplexing cannot be performed;
and the record integration module is used for acquiring the test cases corresponding to each test interface respectively, recording the test cases one by one and taking the final recording result as the test case of the whole test script.
10. A computer device comprising a memory having computer readable instructions stored therein and a processor that when executed implement the steps of the automated interface test case generation method of any one of claims 1 to 8.
11. A computer readable storage medium having computer readable instructions stored thereon which, when executed by a processor, implement the steps of the automated interface test case generation method of any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210707047.6A CN115061916B (en) | 2022-06-21 | 2022-06-21 | Method for automatically generating interface test case and related equipment thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210707047.6A CN115061916B (en) | 2022-06-21 | 2022-06-21 | Method for automatically generating interface test case and related equipment thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115061916A true CN115061916A (en) | 2022-09-16 |
| CN115061916B CN115061916B (en) | 2024-07-16 |
Family
ID=83201925
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210707047.6A Active CN115061916B (en) | 2022-06-21 | 2022-06-21 | Method for automatically generating interface test case and related equipment thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115061916B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117009249A (en) * | 2023-09-15 | 2023-11-07 | 天津赛象科技股份有限公司 | Test method, system and medium for automatically generating interface use cases and codes |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170060734A1 (en) * | 2015-08-30 | 2017-03-02 | International Business Machines Corporation | Method and system for creating functional model of test cases |
| CN111737140A (en) * | 2020-06-28 | 2020-10-02 | 深圳前海微众银行股份有限公司 | Interface automation test method, device, equipment and computer readable storage medium |
| CN113434396A (en) * | 2021-06-22 | 2021-09-24 | 中国农业银行股份有限公司 | Interface test method, device, equipment, storage medium and program product |
| CN113836045A (en) * | 2021-11-29 | 2021-12-24 | 深圳市明源云链互联网科技有限公司 | Logic generation method and device for interface automation assertion and storage medium |
-
2022
- 2022-06-21 CN CN202210707047.6A patent/CN115061916B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170060734A1 (en) * | 2015-08-30 | 2017-03-02 | International Business Machines Corporation | Method and system for creating functional model of test cases |
| CN111737140A (en) * | 2020-06-28 | 2020-10-02 | 深圳前海微众银行股份有限公司 | Interface automation test method, device, equipment and computer readable storage medium |
| CN113434396A (en) * | 2021-06-22 | 2021-09-24 | 中国农业银行股份有限公司 | Interface test method, device, equipment, storage medium and program product |
| CN113836045A (en) * | 2021-11-29 | 2021-12-24 | 深圳市明源云链互联网科技有限公司 | Logic generation method and device for interface automation assertion and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117009249A (en) * | 2023-09-15 | 2023-11-07 | 天津赛象科技股份有限公司 | Test method, system and medium for automatically generating interface use cases and codes |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115061916B (en) | 2024-07-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN117033249A (en) | Test case generation method and device, computer equipment and storage medium | |
| CN115794437A (en) | Calling method and device of microservice, computer equipment and storage medium | |
| CN115712422A (en) | Form page generation method and device, computer equipment and storage medium | |
| CN115061916B (en) | Method for automatically generating interface test case and related equipment thereof | |
| CN117057935A (en) | Data processing method, device, equipment and storage medium based on field design | |
| CN111552663A (en) | File consistency verification method and device, computer equipment and storage medium | |
| CN116483425A (en) | Micro-service gray level edition issuing method, device, equipment and storage medium thereof | |
| CN115756692A (en) | Method for automatically combining and displaying pages based on style attributes and related equipment thereof | |
| CN116383787A (en) | Page creation method, page creation device, computer equipment and storage medium | |
| CN114626352A (en) | Report automatic generation method and device, computer equipment and storage medium | |
| CN115543428A (en) | Simulated data generation method and device based on strategy template | |
| CN114637672A (en) | Automatic data testing method and device, computer equipment and storage medium | |
| CN115185625A (en) | Self-recommendation type interface updating method based on configurable card and related equipment thereof | |
| CN115203672A (en) | Information access control method and device, computer equipment and medium | |
| CN112069807A (en) | Text data theme extraction method and device, computer equipment and storage medium | |
| CN115250200B (en) | Service authorization authentication method and related equipment thereof | |
| CN115578050A (en) | Approval progress identification method and device, computer equipment and storage medium | |
| CN117850842A (en) | Plug-in updating method, device, equipment and storage medium thereof | |
| CN114218191A (en) | System function migration method and device, computer equipment and storage medium | |
| CN115828018A (en) | Electronic magazine interface material replacing method and related equipment thereof | |
| CN115731057A (en) | Information generation method and device, computer equipment and storage medium | |
| CN115712441A (en) | Model deployment method and device, computer equipment and storage medium | |
| CN114371886A (en) | Front-end frame assembly conversion method and device, computer equipment and storage medium | |
| CN114969482A (en) | Method for automatically completing request by online configuration interface and related equipment thereof | |
| CN114528220A (en) | Test case generation method and device, computer equipment and storage 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 |