CN112433933A - Method and equipment for automatically testing interface - Google Patents
Method and equipment for automatically testing interface Download PDFInfo
- Publication number
- CN112433933A CN112433933A CN202010275782.5A CN202010275782A CN112433933A CN 112433933 A CN112433933 A CN 112433933A CN 202010275782 A CN202010275782 A CN 202010275782A CN 112433933 A CN112433933 A CN 112433933A
- Authority
- CN
- China
- Prior art keywords
- interface
- test case
- assertion
- test
- template
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 158
- 238000000034 method Methods 0.000 title claims abstract description 40
- 230000015654 memory Effects 0.000 claims description 17
- 238000013500 data storage Methods 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 10
- 239000000306 component Substances 0.000 description 6
- 238000004590 computer program Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 230000005291 magnetic effect Effects 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000010354 integration Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000009530 blood pressure measurement Methods 0.000 description 1
- 239000008358 core component Substances 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
- 230000003936 working memory 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
-
- 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
-
- 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/3692—Test management for test results analysis
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 method comprises the steps of compiling a test case for testing an interface, and associating the test case with an account pool; executing the test case by using a timing task, and acquiring an interface login request from the account pool; receiving feedback data of the interface login request, and asserting the feedback data according to a template assertion mode to obtain an assertion result of executing the test case; and analyzing the assertion result to generate an html test report. Therefore, by introducing the account pool, the test case writing and the interface authentication are separated, and the test case writing can be more concentrated. And a user-defined assertion mode is provided, the interface return data can be verified by maintaining one template, and the generated html test report can facilitate reading and positioning problems conveniently.
Description
Technical Field
The present application relates to the field of computers, and in particular, to a method and an apparatus for automated interface testing.
Background
The interface test is a test for testing interfaces among components of the system, and is mainly used for detecting interaction points between an external system and the system and between each internal subsystem. At present, when interface testing is carried out, the used HTTPrunner is an open-source interface testing framework facing to an HTTP protocol, but a yaml/json maintenance test case is used, complex business logic cannot be verified, and a custom assertion method is not provided. When using a built-in native test framework, such as the Python built-in unit test framework (unittest), the following disadvantages are present: the generated test report is simple and crude, and is not beneficial to reading and positioning; no specific assertion method for interface test exists, the interface test case flow is complicated when the built-in assertion is used, and the compiling difficulty is high; the use case classification statistical function is not used per se. In addition, for some pressure measurement tools, the use cases are written and managed by ui & yaml, and the operation is complex and the flow is long in the aspects of realizing assertion complex business scenes and continuous integration.
Disclosure of Invention
An object of the present application is to provide a method and a device for automatically testing an interface, which solve the problems that in the prior art, a complex business logic cannot be verified, a custom assertion method is not available, and a generated test report is simple and crude, which is not conducive to reading and positioning.
According to one aspect of the present application, there is provided a method for automated testing of an interface, the method comprising:
compiling a test case for testing an interface, and associating the test case with an account pool;
executing the test case by using a timing task, and acquiring an interface login request from the account pool;
receiving feedback data of the interface login request, and asserting the feedback data according to a template assertion mode to obtain an assertion result of executing the test case;
and analyzing the assertion result to generate an html test report.
Further, associating the test case with an account pool, including:
acquiring user identity information of a test case, wherein the user identity information comprises an interface login validity period of a user;
acquiring configuration information of the test case from a configuration file, and calling a login component for logging in the account pool according to the configuration information;
and associating the test case with the account pool according to the login component, and storing the user identity information of the test case into a database.
Further, the method comprises:
determining identity information of a user to be invalidated in the account pool;
and calling a renewal interface to renew the interface login validity period of the user in the user identity information to be invalidated.
Further, compiling the test case for the test interface includes:
compiling a file in a structured data storage format to generate a client corresponding to the file;
and compiling a test case for testing the interface according to the client and the case template.
Further, when the template assertion manner includes a template json, asserting the feedback data according to the template assertion manner includes:
analyzing all json paths from a template json, and reading return values from the feedback data;
judging whether a custom assertion grammar exists, if so, asserting the return value according to the custom assertion grammar, and if not, comparing whether the values in the template json are consistent with the types of the return value.
Further, before determining whether the custom assertion syntax exists, the method includes:
and judging whether the return value is empty or whether the data format belongs to json.
Further, after parsing the assertion result and generating the html test report, the method includes:
and displaying the html test report on an interface according to the use case category, wherein the use case category is determined according to the item identification, the service identification, the path and the use case of the use case in the item in a classified manner.
According to another aspect of the present application, there is also provided an apparatus for automated interface testing, the apparatus including:
the compiling device is used for compiling a test case for testing the interface and associating the test case with the account pool;
the execution device is used for executing the test case by using a timing task and acquiring an interface login request from the account pool;
the assertion device is used for receiving the feedback data of the interface login request, and asserting the feedback data according to a template assertion mode to obtain an assertion result for executing the test case;
and the generating device is used for analyzing the assertion result and generating the html test report.
According to another aspect of the present application, there is also provided an apparatus for automated interface testing, the apparatus comprising:
one or more processors; and
a memory storing computer readable instructions that, when executed, cause the processor to perform the operations of the method as previously described.
According to yet another aspect of the present application, there is also provided a computer readable medium having computer readable instructions stored thereon, the computer readable instructions being executable by a processor to implement the method as described above.
Compared with the prior art, the test case for testing the interface is compiled, and the test case is associated with the account pool; executing the test case by using a timing task, and acquiring an interface login request from the account pool; receiving feedback data of the interface login request, and asserting the feedback data according to a template assertion mode to obtain an assertion result of executing the test case; and analyzing the assertion result to generate an html test report. Therefore, by introducing the account pool, the test case writing and the interface authentication are separated, and the test case writing can be more concentrated. And a user-defined assertion mode is provided, the interface return data can be verified by maintaining one template, and the generated html test report can facilitate reading and positioning problems conveniently.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
FIG. 1 illustrates a method flow diagram of automated testing of an interface provided in accordance with an aspect of the subject application;
FIG. 2 is a schematic diagram of an account pool in an embodiment of the present application;
fig. 3 is a schematic diagram illustrating an implementation of calling interface login information by using an account pool in an embodiment of the present application;
FIG. 4 is a schematic diagram illustrating an assertion flow of an assertion template in an embodiment of the present application;
FIG. 5 is a schematic diagram illustrating a sample html test report in a specific application scenario in an embodiment of the present application;
FIG. 6 is a system diagram illustrating a test interface in an embodiment of the present application;
fig. 7 is a schematic structural diagram of an apparatus for automated interface testing according to another aspect of the present application.
The same or similar reference numbers in the drawings identify the same or similar elements.
Detailed Description
The present application is described in further detail below with reference to the attached figures.
In a typical configuration of the present application, the terminal, the device serving the network, and the trusted party each include one or more processors (e.g., Central Processing Units (CPUs)), input/output interfaces, network interfaces, and memory.
The Memory may include volatile Memory in a computer readable medium, Random Access Memory (RAM), and/or nonvolatile Memory such as Read Only Memory (ROM) or flash Memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, Phase-Change RAM (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), flash Memory or other Memory technology, Compact Disc Read-Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, magnetic cassette tape, magnetic tape storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory computer readable media (transient media), such as modulated data signals and carrier waves.
Fig. 1 is a flow chart illustrating a method for automated interface testing according to an aspect of the present application, the method including: step S11 to step S14,
in step S11, compiling a test case for testing an interface, and associating the test case with an account pool; in the system, firstly, a test case for testing an interface is compiled, an account pool is set as a part of the attribute of the test case for association, wherein account resources with various attributes of a development environment and a production environment are integrated in the account pool. Therefore, by introducing the account pool, the test case writing and the interface authentication are separated, and the test case writing can be more concentrated.
In step S12, executing the test case using a timing task, and acquiring an interface login request from the account pool; after the written test case is pushed to a distributed version control system (such as git), a timing task executes the current test case, and when an interface needs to be logged in, an interface login request is obtained from an account pool, so that the interface is logged in according to the interface login request.
In step S13, receiving feedback data of the interface login request, and asserting the feedback data according to a template assertion manner to obtain an assertion result of executing the test case; here, feedback data when the interface is logged in according to the interface login request is received, where the feedback data is data required for a service performed by the current test case, for example, when a login account is performed, the feedback data includes a logged-in user account, a password, and the like, and further, when an order is placed, the feedback data includes an order placing account, and data information such as an order placing time and an order placing amount. And after the interface login request finishes returning data, calling a template assertion mode, wherein the mode can verify all data returned by the interface according to the template, judge whether the feedback data meet expectations or not, and embed assertion grammar in the template, so that more complex service verification can be performed in the template. And obtaining an assertion result of the current test case through the assertion of the template, wherein the assertion result is, for example, a result verified to be in line with the expectation or a result not in line with the expectation.
In step S14, the assertion result is parsed, and an html test report is generated. After all the test cases are executed, analyzing the assertion results of the test cases to generate an html test report, customizing an html template, and generating the html test report according to the html template, namely after the test cases are executed, formatting the assertion results into the html template; the test result may include the start and end time of the test case, the total number of cases, the number of pass and fail, and errors, and the specific fail and error information, and the execution assertion information. Thereby being beneficial to reading and being convenient to position.
In an embodiment of the present application, in step S11, user identity information of the test case is obtained, where the user identity information includes an interface login validity period of the user; acquiring configuration information of the test case from a configuration file, and calling a login component for logging in the account pool according to the configuration information; and associating the test case with the account pool according to the login component, and storing the user identity information of the test case into a database. When the test case is written, authentication is needed to be used for authenticating the identity information of the user, the authenticated interface login (access) has expiration time, the access which is manually obtained cannot be automatically renewed, manual updating is needed after the expiration time, and the test account number of each tester is not shared. In the embodiment of the present application, an account pool is used for maintaining access to a batch of development environments and production environments, and the access can be automatically renewed and can be directly called in a project, where the account pool is shown in fig. 2, a first column in the account pool is a user name, a second column is a key (key) used for authentication, and a third column is a remark, and characteristics corresponding to the account can be remarked. Specifically, the access information of the account pool is stored in a database, and a renewal interface is periodically called to a test account which is close to expiration for renewal through background service; when an account is newly added to the account pool, an access of the obtained account needs to be logged in, the account needing to be newly added is configured through the configuration file, the association of the test case and the account pool is completed, a login component is called, and the obtained access information is stored in the database after logging in.
As for the above embodiment, the identity information of the user to be invalidated in the account pool can be determined; and calling a renewal interface to renew the interface login validity period of the user in the user identity information to be invalidated. Here, the user identity information includes interface login information of the user, the interface login information has a validity period, the user identity information to be invalidated is that the access of the user is close to expiration, the access close to expiration in the account pool is determined, and thus a renewal interface is called to carry out renewal of the validity period on the access in the user identity information, the calling mode is shown in fig. 3, Users are the account pool, Uat is an identifier of a development environment, and the default is a production environment; the Username is the user name, and the Access key is the authentication identification value of the user identity. Therefore, automatic renewal and direct calling of the access are realized through the account pool.
In an embodiment of the present application, in step S11, a file in a structured data storage format is compiled to generate a client corresponding to the file; and compiling a test case for testing the interface according to the client and the case template. The file of the structured data storage format can be a proto file, the test case adopts a grpc test case, the test case is compiled into an executable file by using a provided compiling tool according to the defined proto file, then the executable file is introduced to compile a server and a client, the compiled client can communicate with the server, each proto file corresponds to a special client, the test case can generate a client (client) by compiling the proto file, and the grpc test case can be quickly compiled according to the client and a case template.
In an embodiment of the present application, when the template assertion manner includes a template json, in step S13, all json paths are parsed from the template json, and a return value is read from the feedback data; judging whether a custom assertion grammar exists, if so, asserting the return value according to the custom assertion grammar, and if not, comparing whether the values in the template json are consistent with the types of the return value. Specifically, as shown in fig. 4, the content of the template json is traversed first, all json paths are analyzed, and since the data returned by the interface may return to be empty or not belong to a json structure under some conditions, when the template is set to be empty, the data is normally compared with the template when the interface returns to the json structure, and the judgment cannot be performed forcibly even if the data does not return. Before judging whether the self-defined assertion grammar exists, whether the return value is empty or whether the data format belongs to json can be judged. Here, a return value (value) is acquired from data returned from the interface based on a json path (json path) analyzed from the template, and if the value of the template defines the custom assertion syntax, the custom syntax is asserted. If the custom speech-breaking rule is not available, whether the value of the template is consistent with the interface return value type is judged, if so, whether the path of the interface return data is empty is continuously judged, and if not, the assertion result is that the interface return data does not pass.
In an embodiment of the application, after the assertion result is analyzed and an html test report is generated, the html test report can be displayed on an interface according to a case category, where the case category is determined according to a project identifier, a service identifier, a path, and a case of the case in a project. Here, the timed task executes the current test case, automatically counts and classifies the test case through the background service, after the case execution is completed, stores the result in the local database according to classification, outputs the html test report, and displays the html test report on the interface according to the case category, wherein the test case can be classified according to the hierarchy of identifying the project name-service name-path-case in the project, and is displayed on the interface after classification, as shown in fig. 5, a sample schematic diagram of the html test report in a specific application scenario. The test cases are classified and counted, the test cases are conveniently classified, summarized and managed, the web interface can be displayed and downloaded in an allowable mode, and reading and positioning problems are convenient and fast.
In a specific embodiment of the present application, as shown in a system framework schematic diagram of a test interface shown in fig. 6, when a written test case is used in a web service, the test case is stored in a message queue through the web service, the test case is started, a consumer calls a core component to execute the test case in the message queue after obtaining a start message, executes the test cases by triggering a timing task, asserts interface data returned in an execution process by using an assertion manner, automatically counts and classifies the test cases through a background service, finishes executing the cases, stores an assertion result, and generates an html test report. Therefore, interface logic can be verified through less case compiling, continuous integration is realized through simple configuration, and complex service logic verification is realized on the basis of less codes; a user-defined assertion method can be provided, a template interface is maintained to verify data returned by the interface, an account pool is introduced, and the compiling case is separated from the interface authentication and is more concentrated on the compiling case; and the test cases are classified and counted, the test cases are conveniently classified and summarized and managed, and the generated html test report can be beneficial to reading and conveniently positioning problems.
In addition, the embodiment of the present application further provides a computer readable medium, on which computer readable instructions are stored, the computer readable instructions being executable by a processor to implement the foregoing method for interface automation test.
In correspondence with the method described above, the present application also provides an apparatus, which includes modules or units capable of executing the method steps described in the above fig. 1 or various embodiments, and these modules or units can be implemented by hardware, software or a combination of hardware and software, and the present application is not limited thereto. For example, in an embodiment of the present application, there is also provided an apparatus for interface automation test, the apparatus including:
one or more processors; and
a memory storing computer readable instructions that, when executed, cause the processor to perform the operations of the method as previously described.
For example, the computer readable instructions, when executed, cause the one or more processors to:
fig. 7 is a schematic structural diagram of an apparatus for automated interface testing according to another aspect of the present application, where the apparatus includes: the system comprises a compiling device 11, an executing device 12, an asserting device 13 and a generating device 14, wherein the compiling device 11 is used for compiling a test case for testing an interface and associating the test case with an account pool; the execution device 12 is configured to execute the test case by using a timing task, and obtain an interface login request from the account pool; the assertion device 13 is configured to receive feedback data of the interface login request, and assert the feedback data according to a template assertion manner to obtain an assertion result for executing the test case; and the generating device 14 is used for analyzing the assertion result and generating an html test report.
It should be noted that the contents executed by the compiling device 11, the executing device 12, the asserting device 13 and the generating device 14 are the same as or corresponding to the contents in the above steps S11, S12, S13 and S14, respectively, and for brevity, are not described again here.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
It should be noted that the present application may be implemented in software and/or a combination of software and hardware, for example, implemented using Application Specific Integrated Circuits (ASICs), general purpose computers or any other similar hardware devices. In one embodiment, the software programs of the present application may be executed by a processor to implement the steps or functions described above. Likewise, the software programs (including associated data structures) of the present application may be stored in a computer readable recording medium, such as RAM memory, magnetic or optical drive or diskette and the like. Additionally, some of the steps or functions of the present application may be implemented in hardware, for example, as circuitry that cooperates with the processor to perform various steps or functions.
In addition, some of the present application may be implemented as a computer program product, such as computer program instructions, which when executed by a computer, may invoke or provide methods and/or techniques in accordance with the present application through the operation of the computer. Program instructions which invoke the methods of the present application may be stored on a fixed or removable recording medium and/or transmitted via a data stream on a broadcast or other signal-bearing medium and/or stored within a working memory of a computer device operating in accordance with the program instructions. An embodiment according to the present application comprises an apparatus comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein the computer program instructions, when executed by the processor, trigger the apparatus to perform a method and/or a solution according to the aforementioned embodiments of the present application.
It will be evident to those skilled in the art that the present application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it is obvious that the word "comprising" does not exclude other elements or steps, and the singular does not exclude the plural. A plurality of units or means recited in the apparatus claims may also be implemented by one unit or means in software or hardware. The terms first, second, etc. are used to denote names, but not any particular order.
Claims (10)
1. A method of automated testing of an interface, wherein the method comprises:
compiling a test case for testing an interface, and associating the test case with an account pool;
executing the test case by using a timing task, and acquiring an interface login request from the account pool;
receiving feedback data of the interface login request, and asserting the feedback data according to a template assertion mode to obtain an assertion result of executing the test case;
and analyzing the assertion result to generate an html test report.
2. The method of claim 1, wherein associating the test case with a pool of accounts comprises:
acquiring user identity information of a test case, wherein the user identity information comprises an interface login validity period of a user;
acquiring configuration information of the test case from a configuration file, and calling a login component for logging in the account pool according to the configuration information;
and associating the test case with the account pool according to the login component, and storing the user identity information of the test case into a database.
3. The method of claim 2, wherein the method comprises:
determining identity information of a user to be invalidated in the account pool;
and calling a renewal interface to renew the interface login validity period of the user in the user identity information to be invalidated.
4. The method of claim 1, wherein compiling test cases for a test interface comprises:
compiling a file in a structured data storage format to generate a client corresponding to the file;
and compiling a test case for testing the interface according to the client and the case template.
5. The method of claim 1, wherein asserting the feedback data in accordance with a template assertion manner when the template assertion manner comprises template json comprises:
analyzing all json paths from a template json, and reading return values from the feedback data;
judging whether a custom assertion grammar exists, if so, asserting the return value according to the custom assertion grammar, and if not, comparing whether the values in the template json are consistent with the types of the return value.
6. The method of claim 5, wherein determining whether a custom assertion grammar exists comprises, prior to:
and judging whether the return value is empty or whether the data format belongs to json.
7. The method of claim 1, wherein parsing the assertion result to generate an html test report comprises:
and displaying the html test report on an interface according to the use case category, wherein the use case category is determined according to the item identification, the service identification, the path and the use case of the use case in the item in a classified manner.
8. An apparatus for automated testing of an interface, wherein the apparatus comprises:
the compiling device is used for compiling a test case for testing the interface and associating the test case with the account pool;
the execution device is used for executing the test case by using a timing task and acquiring an interface login request from the account pool;
the assertion device is used for receiving the feedback data of the interface login request, and asserting the feedback data according to a template assertion mode to obtain an assertion result for executing the test case;
and the generating device is used for analyzing the assertion result and generating the html test report.
9. An apparatus for automated testing of an interface, wherein the apparatus comprises:
one or more processors; and
a memory storing computer readable instructions that, when executed, cause the processor to perform the operations of the method of any of claims 1 to 7.
10. A computer readable medium having computer readable instructions stored thereon which are executable by a processor to implement the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010275782.5A CN112433933A (en) | 2020-04-09 | 2020-04-09 | Method and equipment for automatically testing interface |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010275782.5A CN112433933A (en) | 2020-04-09 | 2020-04-09 | Method and equipment for automatically testing interface |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112433933A true CN112433933A (en) | 2021-03-02 |
Family
ID=74690281
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010275782.5A Pending CN112433933A (en) | 2020-04-09 | 2020-04-09 | Method and equipment for automatically testing interface |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112433933A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112860581A (en) * | 2021-03-18 | 2021-05-28 | 浙江诺诺网络科技有限公司 | Test case execution method, device, equipment and storage medium |
| CN115114135A (en) * | 2021-03-17 | 2022-09-27 | 中国联合网络通信集团有限公司 | Software data testing method, device, equipment, medium and product |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106919509A (en) * | 2017-03-09 | 2017-07-04 | 腾讯科技（深圳）有限公司 | A kind of client generation method, device and electronic equipment |
| CN107122297A (en) * | 2017-04-18 | 2017-09-01 | 上海雷腾软件股份有限公司 | The method and apparatus that request message for test interface is generated |
| CN107122258A (en) * | 2017-04-18 | 2017-09-01 | 上海雷腾软件股份有限公司 | Method and apparatus for the state code check of test interface |
| CN107179986A (en) * | 2016-03-10 | 2017-09-19 | 阿里巴巴集团控股有限公司 | The method for testing pressure and device of operation system |
| CN110209569A (en) * | 2018-05-10 | 2019-09-06 | 腾讯科技（深圳）有限公司 | Interface test method, interface test device and storage medium |
| CN110442524A (en) * | 2019-08-09 | 2019-11-12 | 中国建设银行股份有限公司 | It is a kind of for have Certificate Authority web service interface test method and device |
-
2020
- 2020-04-09 CN CN202010275782.5A patent/CN112433933A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107179986A (en) * | 2016-03-10 | 2017-09-19 | 阿里巴巴集团控股有限公司 | The method for testing pressure and device of operation system |
| CN106919509A (en) * | 2017-03-09 | 2017-07-04 | 腾讯科技（深圳）有限公司 | A kind of client generation method, device and electronic equipment |
| CN107122297A (en) * | 2017-04-18 | 2017-09-01 | 上海雷腾软件股份有限公司 | The method and apparatus that request message for test interface is generated |
| CN107122258A (en) * | 2017-04-18 | 2017-09-01 | 上海雷腾软件股份有限公司 | Method and apparatus for the state code check of test interface |
| CN110209569A (en) * | 2018-05-10 | 2019-09-06 | 腾讯科技（深圳）有限公司 | Interface test method, interface test device and storage medium |
| CN110442524A (en) * | 2019-08-09 | 2019-11-12 | 中国建设银行股份有限公司 | It is a kind of for have Certificate Authority web service interface test method and device |
Non-Patent Citations (6)
| Title |
|---|
| 于敞: "基于微服务架构的接口自动化 测试服务与测试报告的设计与实现", 基于微服务架构的接口自动化 测试服务与测试报告的设计与实现, pages 24 - 26 * |
| 于敞: "基于微服务架构的接口自动化测试服务与测试报告的设计与实现", 基于微服务架构的接口自动化测试服务与测试报告的设计与实现, no. 9, pages 24 - 26 * |
| 全栈测试开发日记: "HTMLTestRunner原始报告模板添加饼", Retrieved from the Internet <URL:https://blog.csdn.net/liudinglong1989/article/details/89477054> * |
| 刘国庆: "基于Charles录制会话的HTTP接口自动化测试框架设计与实现", 基于CHARLES录制会话的HTTP接口自动化测试框架设计与实现, vol. 2019, no. 6, pages 1 - 7 * |
| 小木墩儿: "python中HTMLTestRunner测试报告美化", Retrieved from the Internet <URL:https://blog.51cto.com/u_7605937/2373414> * |
| 开源优测: "Python自定义HtmlTestRunner测试报告", Retrieved from the Internet <URL:https://baijiahao.baidu.com/s?id=1596508048936144376&wfr=spider&for=pc> * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115114135A (en) * | 2021-03-17 | 2022-09-27 | 中国联合网络通信集团有限公司 | Software data testing method, device, equipment, medium and product |
| CN115114135B (en) * | 2021-03-17 | 2024-05-17 | 中国联合网络通信集团有限公司 | Software data testing method, device, equipment, medium and product |
| CN112860581A (en) * | 2021-03-18 | 2021-05-28 | 浙江诺诺网络科技有限公司 | Test case execution method, device, equipment and storage medium |
| CN112860581B (en) * | 2021-03-18 | 2024-04-26 | 浙江诺诺网络科技有限公司 | Execution method, device, equipment and storage medium of test case |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107122258B (en) | Method and equipment for checking state code of test interface | |
| CN107122296B (en) | Method and apparatus for data assertion for test interface | |
| CN111177005B (en) | Service application testing method, device, server and storage medium | |
| CN107122297B (en) | Method and equipment for generating request message of test interface | |
| CN108628748B (en) | Automatic test management method and automatic test management system | |
| CN111240994B (en) | Vulnerability processing method and device, electronic equipment and readable storage medium | |
| CN107092535B (en) | Method and apparatus for data storage of test interface | |
| CN108984389B (en) | Application program testing method and terminal equipment | |
| CN112035363A (en) | Automatic interface testing method and device | |
| CN111124870A (en) | Interface testing method and device | |
| CN113836014A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN112433933A (en) | Method and equipment for automatically testing interface | |
| CN111897721A (en) | Automatic test method of API interface and storage medium | |
| CN111859205A (en) | Analytic method and equipment for batch processing tasks | |
| CN112367220A (en) | Interface testing method and device, storage medium and electronic equipment | |
| CN113609026B (en) | Method and device for pressure testing of server | |
| CN117194259A (en) | Interface testing method, system, electronic equipment and storage medium | |
| CN115470152A (en) | Test code generation method, test code generation device, and storage medium | |
| CN113238940B (en) | Interface test result comparison method, device, equipment and storage medium | |
| CN115543832A (en) | Software code standard detection method, system, equipment and storage medium | |
| CN112131611B (en) | Data correctness verification method, device, equipment, system and storage medium | |
| CN115098401A (en) | HTML report verification method and device, electronic equipment and storage medium | |
| CN113886216B (en) | Interface test and tool configuration method, device, electronic equipment and storage medium | |
| CN113419738A (en) | Interface document generation method and device and interface management equipment | |
| CN113094281B (en) | Test method and device for hybrid App |
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 |