CN117331850A - Test method combining function test and interface automation test - Google Patents
Test method combining function test and interface automation test Download PDFInfo
- Publication number
- CN117331850A CN117331850A CN202311635010.8A CN202311635010A CN117331850A CN 117331850 A CN117331850 A CN 117331850A CN 202311635010 A CN202311635010 A CN 202311635010A CN 117331850 A CN117331850 A CN 117331850A
- Authority
- CN
- China
- Prior art keywords
- test
- test case
- functional
- case
- interface
- 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 314
- 238000010998 test method Methods 0.000 title claims abstract description 9
- 238000011990 functional testing Methods 0.000 claims abstract description 164
- 238000013507 mapping Methods 0.000 claims description 18
- 238000000034 method Methods 0.000 claims description 17
- 230000008569 process Effects 0.000 claims description 4
- 238000012216 screening Methods 0.000 claims description 3
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 238000010276 construction Methods 0.000 description 4
- 238000013461 design Methods 0.000 description 2
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Abstract
The invention discloses a test method combining a functional test and an interface automation test, which comprises the steps of performing marking after performing association operation on the functional test case and the interface automation test case, associating a functional test plan corresponding to an iterative functional test to the functional test case and the interface automation test case, providing a marking function of an execution result of the functional test case in the functional test plan, performing automatic one-key execution function operation on the functional test plan, executing an interface automation execution service, writing back an execution result, and outputting a test report according to the execution result of the execution function test plan. Compared with the prior art, the invention has the following beneficial effects that the automatic execution of the duty ratio data in the total function test case can be quantized, the function test efficiency is improved, and the execution efficiency is improved.
Description
Technical Field
The invention belongs to the technical field of testing, and particularly relates to a testing method for combining functional testing and interface automation testing.
Background
Functional testing is the testing of the characteristics and operability of a product to determine that they meet design requirements based on product characteristics, operational descriptions, and user profiles. Functional testing is testing of software as required by functionality to ensure that a program is running in a desired manner, ensuring compliance with requirements and specifications by testing all features and functions of a system.
Interface automation testing is an automated test method for testing interfaces or APIs of an application. The purpose of the interface automation test is to verify whether the interface of the application is working as intended, and has the correct behaviour under different input and output combinations of the interface,
under the current general trend of front-end and back-end separation in the software industry, various software Internet companies have more or less construction for performing automatic interface test. However, in the functional iteration test of one project, the functional test and the automation test are split, the functional test case and the automation test case have no corresponding relation to be two different cases, and the execution result are required to be separately counted. Most testers execute all interface automation test cases in a full way after the function test is finished, and the test cases are used for carrying out historical function regression spam.
The following technical problems are needed to be solved by those skilled in the art.
1. In functional iterative testing, the role of interface automation construction cannot be quantified. The function test cases and the iteration test cases are split, so that the function is covered by the automatic test cases, and the proportion of the covered cases in the total number of the iteration function test cases cannot be counted.
2. In iterative functional testing, the effectiveness of automated interface construction is limited. There is no mapping relation between the functional test cases and the automated test cases, for example, 10 functional test cases are needed in functional iterative test, when different testers write hundreds of interface automated test cases together, it is actually unclear for the testers whether 10 functional test cases which can cover the test need exist in hundreds of interface automated test cases, so more time testers can select to manually execute the 10 functional test cases, and finally all the interface automated test cases are executed for one time to carry out regression test. The whole flow is mainly manual test, and the efficiency of automatic construction of interfaces is limited.
Disclosure of Invention
The invention aims to solve the technical problems that: a test method combining functional testing and interface automation testing is provided.
In order to achieve the above purpose, the technical scheme adopted by the invention is as follows:
a test method combining function test and interface automation test comprises the following steps:
step a, performing association operation on the functional test cases and the interface automation test cases, and then executing marking;
step b, a functional test plan corresponding to the iterative functional test is related to the functional test case and the interface automation test case;
step c, providing a marking function of the execution result of the functional test case in the functional test plan;
step d, performing automatic one-key execution function operation on the function test plan, performing interface automatic execution service, and writing back an execution result;
and e, outputting a test report according to the execution result of the execution function test plan.
Further, step a comprises: step a1, acquiring a page function test case in the function test cases, and constructing a page function test case pool; step a2, the functional test case provides an associated automation test case and two de-automation buttons; step a3, obtaining an associated automated test case, establishing an association relation between a function test case ID and the automated test case ID based on a database record, and marking tag fields of the function test case and the automated test case in a database corresponding table; step a4, the functional test cases and the automatic test cases are disassociated, an interface automatic test case is created, and the functional test case ID corresponding to the automatic test case ID is recorded; step a5, associating the interface with the automation test case and the function test case.
Further, the method for associating the automated test case buttons in the step a2 includes: all the automatic test cases are searched out from the database, one automatic test case is selected, the main key of the database function test case table corresponding to the function test case and the main key of the database of the selected automatic test case are associated, and the association relation is inserted into the mapping table in the database.
Further, the method for removing the automated test case button in the step a2 includes: and recording and storing an automatic test case information page, adding a new case record into the automatic test case table of the database after storing, associating a main key of the case record with a main key of the functional test case table, and inserting the association relationship into a mapping table in the database.
Further, the method for creating the interface automation test case in the step a4 includes: step a4.1, inputting interface information in a page, storing the interface information into an automatic test case table of a database after the interface information is stored, and generating an interface record; and a4.2, when automation is executed, the bottom automation execution service assembles records of the automation test cases and initiates a request, and compares and asserts the request result and the assertion result of the automation test cases.
Further, step b comprises: step b1, converting the execution process of the iterative functional test cases into a functional test plan, and associating the iterative functional test cases when the functional test plan is created; step b2, selecting a functional test case and an automatic test case, and acquiring a planned test case ID; step b3, establishing a mapping relation among the planned test case ID, the functional test case ID and the automatic test case ID; and b4, associating the functional test plan to the functional test case and the interface automation test case.
Further, step c comprises: step c1, acquiring a detail page of a functional test plan, wherein the functional test plan provides an execution result marking function; step c2, the functional test plan provides buttons for planning test case execution, and detail pages of a plurality of planned test cases are obtained; and c3, marking an execution result based on the execution result of the planned test cases, and transferring the functional test plan flow to test passing after the execution of all the planned test cases are passed.
Further, step d comprises: step d1, acquiring a detail page of a functional test plan, and acquiring an automatic test case corresponding to the planned test case; step d2, obtaining a functional test case corresponding to the planned test case, and obtaining an automatic test case related to the functional test case; step d3, merging and de-duplicating the automatic test cases obtained in the step d1 and the automatic test cases obtained in the step d2, and screening out the automatic test cases; step d4, calling the interface automatic test case and executing the automatic test case screened in the step d3 to obtain an execution result of the interface automatic test case; and d5, marking the acquired execution result, and associating the marked execution result with the functional test case.
Further, step e comprises: step e1, obtaining the total number of the functional test cases in the functional test plan, calculating the execution number of the automatic test cases executed in the step d3, and calculating the test-free rate = execution number/total number; step e2, firstly, obtaining all the automated functional test cases corresponding to the planned test cases in the functional test plan, and then accumulating the manual execution time consumption of the automated functional test cases to obtain the total manual test time consumption saved by the functional test plan; and e3, counting the total time saving of the multiple iterative function test cases in a period of time, and feeding back the total time saving to the interface automatic test cases.
Compared with the prior art, the invention has the following beneficial effects:
performing association operation on the functional test cases and the interface automation test cases, performing marking, associating the functional test plan to the functional test cases and the interface automation test cases, performing automatic one-key execution function operation, performing statistics on the execution results of the interface automation test cases and the execution results of the functional test cases together, and acquiring the functions covered by the interface automation test cases, so that the duty ratio data of the automation execution in the total functional test cases can be quantized.
The automatic test cases to be executed in the functional test plan are screened, the interface automatic test cases are called, and the screened automatic test cases are executed, so that all the interface automatic test cases do not need to be executed, the functional test efficiency is improved, and the execution efficiency is improved.
Drawings
FIG. 1 is a flow chart of the steps of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings, in order to make the objects, technical solutions and advantages of the present invention more apparent. It will be apparent that the described embodiments are only some, but not all, embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The database in the invention is internally provided with a planned test case table, a functional test case table and an automatic test case table, wherein the planned test case table comprises four fields of a self-increment ID, a functional test plan ID, an application case ID and an application case type, the functional test case table comprises a functional test case ID and functional test case detail content, and the automatic test case table comprises an automatic test case ID and case basic information.
As shown in fig. 1, the test method for combining functional test and interface automation test provided by the invention comprises the following steps:
step a, performing association operation on the functional test cases and the interface automation test cases, and then executing marking;
step b, a functional test plan corresponding to the iterative functional test is related to the functional test case and the interface automation test case;
step c, providing a marking function of the execution result of the functional test case in the functional test plan;
step d, performing automatic one-key execution function operation on the function test plan, performing interface automatic execution service, and writing back an execution result;
and e, outputting a test report according to the execution result of the execution function test plan.
Preferably, step a comprises: step a1, acquiring a page function test case in the function test cases, and constructing a page function test case pool. The page function test case in the step a1 is a function test case which needs to be manually executed by a tester in the subsequent iteration function test case, so that the embodiment converts the execution of the iteration function test case into the execution of the page function test case, the page function test case is added into a corresponding function test plan, and the page function test case is executed in the function test plan and marks an execution result; step a2, the functional test case provides an associated automation test case and two de-automation buttons; step a3, obtaining the associated automated test cases, establishing an association relation between the function test case ID and the automated test case ID based on the database records, and marking tag fields of the function test cases and the automated test cases in the database corresponding tables. In the step a3, the mapping table in the database is used for specially maintaining the mapping relation, and besides the primary key, the mapping table also comprises two fields, namely a functional test case ID and an automation test case ID, and the functional test case ID and the automation test case ID are inserted into the mapping table to establish the mapping relation; step a4, the functional test case and the automatic test case are disassociated, an interface automatic test case is created, and the functional test case ID corresponding to the automatic test case ID is recorded. In the step a4, the de-automation button in the step a2 binds a page link capable of creating an interface automation test case, meanwhile, the corresponding function test case ID is spliced into the page link as a routing parameter, the de-automation button is clicked to jump to a page for creating the interface automation test case, and after the interface automation test case information is input and stored, the front end transmits the routing parameter to the rear end for mapping; step a5, associating the interface with the automation test case and the function test case. In the step a5, after the back end records in the database for generating the interface automation test case, judging whether the function test case ID has a value, if so, inserting the interface automation test case and the corresponding function test case ID into the mapping table.
Preferably, the method for associating the automated test case buttons in the step a2 includes: all the automatic test cases are searched out from the database, one automatic test case is selected, the main key of the database function test case table corresponding to the function test case and the main key of the database of the selected automatic test case are associated, and the association relation is inserted into the mapping table in the database. In the step a2, whether the automation is performed or not may be determined by whether the function test case ID has an associated automation test case ID in the mapping table.
Preferably, the method for removing the automated test case button in the step a2 includes: and recording and storing an automatic test case information page, adding a new case record into the automatic test case table of the database after storing, associating a main key of the case record with a main key of the functional test case table, and inserting the association relationship into a mapping table in the database.
Preferably, the method for creating the interface automation test case in the step a4 includes: step a4.1, inputting interface information in a page, storing the interface information into an automatic test case table of a database after the interface information is stored, and generating an interface record; and a4.2, when automation is executed, the bottom automation execution service assembles records of the automation test cases and initiates a request, and compares and asserts the request result and the assertion result of the automation test cases. The interface information comprises interface protocol, request mode, request head, request body, corresponding assertion result and other information.
Preferably, step b comprises: step b1, converting the execution process of the iterative functional test cases into a functional test plan, and associating the iterative functional test cases when the functional test plan is created. In the step b1, when an iterative functional test case is tested, a tester needs to write a corresponding functional test case, including fields such as a precondition, an execution step, an expected result, etc., and save the above information into a functional test case table in a database, wherein the newly added record is a functional test case, and all functional test cases in the functional test case table are a functional case pool; and b2, selecting a functional test case and an automatic test case, and obtaining a planned test case ID. In the step b2, one functional test case or automatic test case may be multiplexed by different functional test plans, but execution results obtained in the different functional test plans are different, when the functional test plan is associated with the functional test case or the automatic test case, a functional test plan ID, an application case ID (functional test case ID and automatic test case ID) and an application case type are inserted into the plan test case table, a corresponding self-increment ID is generated after new record, and the self-increment ID is the plan test case ID; step b3, establishing a mapping relation among the planned test case ID, the functional test case ID and the automatic test case ID; and b4, associating the functional test plan to the functional test case and the interface automation test case. In the step b4, an association relationship between the automatic test case and the planned test case is established at the same time, and the association process is similar to that of the functional test case.
Preferably, step c comprises: step c1, acquiring a detail page of a functional test plan, wherein the functional test plan provides an execution result marking function. In the step c1, an execution result table in the data table includes two fields, namely a function test plan case ID and an execution result, when a tester executes the function test plan case, the case may be marked as failed or successful, and then the back-end interface is called to store corresponding data in the execution result table; and step c2, the functional test plan provides a button for planning test case execution, and obtains detail pages of a plurality of planned test cases. In the step c2, a functional test plan is regarded as a collection of a batch of functional test cases, and a database is provided with an association table of functional test plan IDs and functional test case IDs; and c3, marking an execution result based on the execution result of the planned test cases, and transferring the functional test plan flow to test passing after the execution of all the planned test cases are passed. In the step c3, the functions of executing and marking the planned test cases are provided in the detail page of the functional test plan, the content of the planned test cases is that of the functional test cases which are displayed through the association relation in the step b4, and the functional test plan has state concepts including non-start, in-process, test passing and test non-passing.
Preferably, step d comprises: step d1, acquiring a detail page of a functional test plan, and acquiring an automatic test case corresponding to the planned test case; step d2, obtaining a functional test case corresponding to the planned test case, and obtaining an automatic test case related to the functional test case; step d3, merging and de-duplicating the automatic test cases obtained in the step d1 and the automatic test cases obtained in the step d2, and screening out the automatic test cases; step d4, calling the interface automatic test case and executing the automatic test case screened in the step d3 to obtain an execution result of the interface automatic test case; and d5, marking the acquired execution result, and associating the marked execution result with the functional test case.
In the step d1, two data of an automated test case corresponding to the planned test case and an automated test case associated with the automated test case corresponding to the planned test case are obtained through the association table of the functional test plan and the planned functional test case, the association table of the planned functional test case and the automated test case or the association table of the functional test case, the association table of the functional test case and the automated test case, and the connection table of the automated test case; combining and deduplicating the automatic test case IDs of the two data, calling an automatic execution service to execute the two data sequentially, inquiring the complete information of the automatic test case in a database according to the automatic test case ID, splicing the domain name and the api of the automatic test case as request addresses, taking the request content in the automatic test case database as request parameters, taking the request head of the automatic test case as request combination to initiate an http request, comparing the request response with the expected result of the interface automatic test case, and if the expected result is consistent, executing the automatic test case successfully, otherwise, executing the test case successfully; respectively acquiring corresponding test plan case IDs through a continuous table query result of the automatic test case IDs, and synchronously marking execution results of the corresponding test plan case IDs; in the functional test plan, the planned test cases, to which the execution results have been marked, do not require additional use of a human to perform manual testing.
Preferably, step e comprises: step e1, obtaining the total number of the functional test cases in the functional test plan, calculating the execution number of the automatic test cases executed in the step d3, and calculating the test-free rate = execution number/total number; step e2, firstly, obtaining all the automated functional test cases corresponding to the planned test cases in the functional test plan, and then accumulating the manual execution time consumption of the automated functional test cases to obtain the total manual test time consumption saved by the functional test plan; and e3, counting the total time saving of the multiple iterative function test cases in a period of time, and feeding back the total time saving to the interface automatic test cases.
In step e2, a tester maintains a field of execution time of the functional test case when the functional test case is created, the field and other information of the functional test case are stored together in a database, and the field is marked as being automated after the functional test case is associated with an automated test case; and obtaining an automated functional test case corresponding to the planned functional test case in the functional test plan through the association relation table of the functional test plan and the planned functional test case, the planned functional test case and the automated test case or the association relation table of the functional test case and the table query, wherein the manual execution time of the automated functional test case is accumulated, and the total reduced manual test time is obtained.
Finally, it should be noted that: the above embodiments are merely preferred embodiments of the present invention for illustrating the technical solution of the present invention, but not limiting the scope of the present invention; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the corresponding technical solutions; that is, even though the main design concept and spirit of the present invention is modified or finished in an insubstantial manner, the technical problem solved by the present invention is still consistent with the present invention, and all the technical problems are included in the protection scope of the present invention; in addition, the technical scheme of the invention is directly or indirectly applied to other related technical fields, and the technical scheme is included in the scope of the invention.
Claims (9)
1. A test method combining function test and interface automation test is characterized by comprising the following steps:
step a, performing association operation on the functional test cases and the interface automation test cases, and then executing marking;
step b, a functional test plan corresponding to the iterative functional test is related to the functional test case and the interface automation test case;
step c, providing a marking function of the execution result of the functional test case in the functional test plan;
step d, performing automatic one-key execution function operation on the function test plan, performing interface automatic execution service, and writing back an execution result;
and e, outputting a test report according to the execution result of the execution function test plan.
2. A test method combining functional testing and interface automation testing according to claim 1, wherein step a comprises: step a1, acquiring a page function test case in the function test cases, and constructing a page function test case pool; step a2, the functional test case provides an associated automation test case and two de-automation buttons; step a3, obtaining an associated automated test case, establishing an association relation between a function test case ID and the automated test case ID based on a database record, and marking tag fields of the function test case and the automated test case in a database corresponding table; step a4, the functional test cases and the automatic test cases are disassociated, an interface automatic test case is created, and the functional test case ID corresponding to the automatic test case ID is recorded; step a5, associating the interface with the automation test case and the function test case.
3. The method for combining functional testing and interface automation testing according to claim 2, wherein the method for associating automation test case buttons in step a2 comprises: all the automatic test cases are searched out from the database, one automatic test case is selected, the main key of the database function test case table corresponding to the function test case and the main key of the database of the selected automatic test case are associated, and the association relation is inserted into the mapping table in the database.
4. The method for combining functional testing and interface automation testing according to claim 2, wherein the method for removing the automation test case button in step a2 comprises: and recording and storing an automatic test case information page, adding a new case record into the automatic test case table of the database after storing, associating a main key of the case record with a main key of the functional test case table, and inserting the association relationship into a mapping table in the database.
5. The method for combining functional testing and interface automation testing according to claim 2, wherein the method for creating interface automation test cases in step a4 comprises: step a4.1, inputting interface information in a page, storing the interface information into an automatic test case table of a database after the interface information is stored, and generating an interface record; and a4.2, when automation is executed, the bottom automation execution service assembles records of the automation test cases and initiates a request, and compares and asserts the request result and the assertion result of the automation test cases.
6. A testing method combining functional testing and interface automation testing according to claim 1, wherein step b comprises: step b1, converting the execution process of the iterative functional test cases into a functional test plan, and associating the iterative functional test cases when the functional test plan is created; step b2, selecting a functional test case and an automatic test case, and acquiring a planned test case ID; step b3, establishing a mapping relation among the planned test case ID, the functional test case ID and the automatic test case ID; and b4, associating the functional test plan to the functional test case and the interface automation test case.
7. A testing method combining functional testing and interface automation testing according to claim 1, wherein step c comprises: step c1, acquiring a detail page of a functional test plan, wherein the functional test plan provides an execution result marking function; step c2, the functional test plan provides buttons for planning test case execution, and detail pages of a plurality of planned test cases are obtained; and c3, marking an execution result based on the execution result of the planned test cases, and transferring the functional test plan flow to test passing after the execution of all the planned test cases are passed.
8. A testing method combining functional testing and interface automation testing according to claim 1, wherein step d comprises: step d1, acquiring a detail page of a functional test plan, and acquiring an automatic test case corresponding to the planned test case; step d2, obtaining a functional test case corresponding to the planned test case, and obtaining an automatic test case related to the functional test case; step d3, merging and de-duplicating the automatic test cases obtained in the step d1 and the automatic test cases obtained in the step d2, and screening out the automatic test cases; step d4, calling the interface automatic test case and executing the automatic test case screened in the step d3 to obtain an execution result of the interface automatic test case; and d5, marking the acquired execution result, and associating the marked execution result with the functional test case.
9. A testing method combining functional testing and interface automation testing according to claim 1, wherein step e comprises: step e1, obtaining the total number of the functional test cases in the functional test plan, calculating the execution number of the automatic test cases executed in the step d3, and calculating the test-free rate = execution number/total number; step e2, firstly, obtaining all the automated functional test cases corresponding to the planned test cases in the functional test plan, and then accumulating the manual execution time consumption of the automated functional test cases to obtain the total manual test time consumption saved by the functional test plan; and e3, counting the total time saving of the multiple iterative function test cases in a period of time, and feeding back the total time saving to the interface automatic test cases.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311635010.8A CN117331850B (en) | 2023-12-01 | 2023-12-01 | Test method combining function test and interface automation test |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311635010.8A CN117331850B (en) | 2023-12-01 | 2023-12-01 | Test method combining function test and interface automation test |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117331850A true CN117331850A (en) | 2024-01-02 |
| CN117331850B CN117331850B (en) | 2024-03-15 |
Family
ID=89279658
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311635010.8A Active CN117331850B (en) | 2023-12-01 | 2023-12-01 | Test method combining function test and interface automation test |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117331850B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103049374A (en) * | 2012-12-03 | 2013-04-17 | 瑞斯康达科技发展股份有限公司 | Automatic testing method and device |
| WO2015184404A1 (en) * | 2014-05-30 | 2015-12-03 | Verinata Health, Inc. | Detecting fetal sub-chromosomal aneuploidies and copy number variations |
| CN106708718A (en) * | 2015-07-22 | 2017-05-24 | 北京京东尚科信息技术有限公司 | Service framework interface testing method and device |
| CN106874174A (en) * | 2015-12-11 | 2017-06-20 | 阿里巴巴集团控股有限公司 | Interface testing and the implementation method and device of functional test |
| CN108959059A (en) * | 2017-05-19 | 2018-12-07 | 腾讯科技（深圳）有限公司 | A kind of test method and test platform |
| CN109446060A (en) * | 2018-09-13 | 2019-03-08 | 百富计算机技术（深圳）有限公司 | A kind of generation method, terminal device and the storage medium of server-side test use cases |
| US10596289B1 (en) * | 2017-04-10 | 2020-03-24 | Carl L. Ricciardi | Pivoting cable holder for multi-function disinfection cabinet |
| CN116244188A (en) * | 2023-01-10 | 2023-06-09 | 中信百信银行股份有限公司 | Automatic test method and system for interface isolation control |
-
2023
- 2023-12-01 CN CN202311635010.8A patent/CN117331850B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103049374A (en) * | 2012-12-03 | 2013-04-17 | 瑞斯康达科技发展股份有限公司 | Automatic testing method and device |
| WO2015184404A1 (en) * | 2014-05-30 | 2015-12-03 | Verinata Health, Inc. | Detecting fetal sub-chromosomal aneuploidies and copy number variations |
| CN106708718A (en) * | 2015-07-22 | 2017-05-24 | 北京京东尚科信息技术有限公司 | Service framework interface testing method and device |
| CN106874174A (en) * | 2015-12-11 | 2017-06-20 | 阿里巴巴集团控股有限公司 | Interface testing and the implementation method and device of functional test |
| US10596289B1 (en) * | 2017-04-10 | 2020-03-24 | Carl L. Ricciardi | Pivoting cable holder for multi-function disinfection cabinet |
| CN108959059A (en) * | 2017-05-19 | 2018-12-07 | 腾讯科技（深圳）有限公司 | A kind of test method and test platform |
| CN109446060A (en) * | 2018-09-13 | 2019-03-08 | 百富计算机技术（深圳）有限公司 | A kind of generation method, terminal device and the storage medium of server-side test use cases |
| CN116244188A (en) * | 2023-01-10 | 2023-06-09 | 中信百信银行股份有限公司 | Automatic test method and system for interface isolation control |
Non-Patent Citations (2)
| Title |
|---|
| C. M. KIRCHSTEIGER 等: "Automatic Test Generation From Semi-formal Specifications for Functional Verification of System-on-Chip Designs", 《2008 2ND ANNUAL IEEE SYSTEMS CONFERENCE, MONTREAL》, pages 1 - 8 * |
| 周绍凯 等: "面向网络游戏的自动化接口测试系统设计", 《现代计算机》, no. 10, pages 81 - 84 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117331850B (en) | 2024-03-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107622014B (en) | Test report generation method and device, readable storage medium and computer equipment | |
| CN106909510B (en) | Method for obtaining test case and server | |
| US7383170B2 (en) | System and method for analyzing automatic speech recognition performance data | |
| US20110161132A1 (en) | Method and system for extracting process sequences | |
| US6708185B2 (en) | SQL execution analysis | |
| US7353230B2 (en) | Dynamic distributed customer issue analysis | |
| CN110134663B (en) | Organization structure data processing method and device and electronic equipment | |
| CN111782635A (en) | Data processing method and apparatus, storage medium, and electronic apparatus | |
| CN112965912B (en) | Interface test case generation method and device and electronic equipment | |
| Briand et al. | Using machine learning to refine category-partition test specifications and test suites | |
| CN111258876B (en) | Accurate regression testing method and device under micro-service architecture | |
| CN117331850B (en) | Test method combining function test and interface automation test | |
| CN112860581B (en) | Execution method, device, equipment and storage medium of test case | |
| CN117057942B (en) | Intelligent financial decision big data analysis system | |
| CN109636303B (en) | Storage method and system for semi-automatically extracting and structuring document information | |
| Banush et al. | Rehabilitating Killer Serials | |
| CN115757175A (en) | Transaction log file processing method and device | |
| US10162849B1 (en) | System, method, and computer program for automatic database validation associated with a software test | |
| April et al. | SM/sup CMM/model to evaluate and improve the quality of the software maintenance process | |
| CN113312256A (en) | Automatic dock system interface automatic test system and method | |
| CN111026654A (en) | Automatic testing method based on interface | |
| CN111309370A (en) | Version number directed graph sorting audit method and system for multi-project and multi-system environment | |
| De Medeiros et al. | ProM Framework Tutorial | |
| US11256708B2 (en) | Method of creating process protocols | |
| CN110765020B (en) | Test case generation method based on domain knowledge |
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 |