CN111143221B - Test method and device - Google Patents
Test method and device Download PDFInfo
- Publication number
- CN111143221B CN111143221B CN201911383609.0A CN201911383609A CN111143221B CN 111143221 B CN111143221 B CN 111143221B CN 201911383609 A CN201911383609 A CN 201911383609A CN 111143221 B CN111143221 B CN 111143221B
- Authority
- CN
- China
- Prior art keywords
- test
- field
- unit
- target
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000010998 test method Methods 0.000 title claims description 8
- 238000012360 testing method Methods 0.000 claims abstract description 508
- 238000000034 method Methods 0.000 claims abstract description 22
- 235000006719 Cassia obtusifolia Nutrition 0.000 claims description 20
- 235000014552 Cassia tora Nutrition 0.000 claims description 20
- 244000201986 Cassia tora Species 0.000 claims description 18
- 238000011161 development Methods 0.000 description 5
- 238000006243 chemical reaction Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 244000277285 Cassia obtusifolia Species 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Abstract
The application discloses a testing method and device, wherein the method comprises the following steps: the test set is called by the target test unit to realize the test of the target test unit. Therefore, the field description and the test data required by the test can be intuitively displayed through the test table, the problem of disordered use of the test data caused by manual input or calling of a developer can be avoided, and the accuracy and the efficiency of unit test are improved.
Description
Technical Field
The present disclosure relates to the field of computers, and in particular, to a testing method and apparatus.
Background
During the development and testing of software, development testers typically check and verify the software or testable units in a program, commonly referred to as unit testing. The unit test is performed to ensure that the unit functions normally, so that it is possible to confirm that the partial program composed of a plurality of units functions normally.
When a development tester performs unit testing, test data are required to be input according to the content to be tested to test the unit, wherein the test data can be data which are manually input by the development tester and meet certain conditions, or can be data in a database which is built in advance and called by the development tester. However, both the above two methods are manually performed by a developer and the test data are corresponding to the fields, and the manual input may cause the problem that the test data are not corresponding to the fields, which easily causes confusion in use of the test data, resulting in lower efficiency of unit test.
Disclosure of Invention
In order to solve the technical problems in the prior art, the application provides a testing method and a testing device, which can realize unit testing by creating a testing table with fields, field descriptions and testing data and calling a testing set in the testing table through a target testing unit, and can avoid the problem of disordered use of the testing data caused by manual input or calling of the testing data.
The embodiment of the application discloses the following technical scheme:
in a first aspect, embodiments of the present application provide a test method, where the method includes:
determining fields required for testing according to a target test unit;
creating a test table; the test table is provided with the field, a field description corresponding to the field and test data corresponding to the field;
determining a field required to be tested by the target test unit in the test, taking the field as a target test field, and analyzing the test table by combining the target test field to obtain a test set in the test table; the test set comprises the target test field, a field description corresponding to the target test field and test data corresponding to the target test field;
and the target test unit calls the test set to carry out the test.
Optionally, when the test data is parametric test data, before the target test unit invokes the test set to perform the test, the method further includes:
converting the test set into a corresponding JavaBean, and converting the converted JavaBean into a corresponding entity class;
the target test unit calling a test set for testing comprises the following steps:
and the target test unit calls the entity class for testing.
Optionally, when the test data is database test data, before the target test unit calls the test set to perform the test, the method further includes:
converting the test set into a corresponding JavaBean, converting the converted JavaBean into a corresponding database entity class, and inserting the database entity class into a test database;
the target test unit calling a test set for testing comprises the following steps:
and the target test unit calls a test database to test.
Optionally, the converting the converted java bean into a corresponding database entity class further includes:
and generating a data deleting instruction corresponding to the database entity class so as to execute the data deleting instruction after the test is completed, and deleting the database entity class from the test database.
Optionally, the test data is parametric test data and/or database test data.
Optionally, the method further comprises:
and acquiring an operation result generated by the target test unit after the test set is called for testing, judging whether the operation result is consistent with a preset correct result, and obtaining a test result according to the judgment result.
Optionally, the method further comprises: the test form will be presented to the user.
In a second aspect, embodiments of the present application provide a test apparatus, the apparatus including:
the establishing unit is used for determining fields required by the test according to the target test unit; creating a test table; the test table is provided with the field, a field description corresponding to the field and test data corresponding to the field;
the analyzing unit is used for determining a field required to be tested by the target testing unit at the time, taking the field as a target testing field, and analyzing the testing table by combining the target testing field to obtain a testing set in the testing table; the test set comprises the target test field, a field description corresponding to the target test field and test data corresponding to the target test field;
and the calling unit is used for calling the test set by the target test unit to test.
Optionally, the apparatus further includes:
the assertion unit is used for acquiring the operation result generated by the target test unit after the test set is called for testing, judging whether the operation result is consistent with a preset correct result, and obtaining a test result according to the judgment result.
Optionally, the apparatus further includes:
and the deleting unit is used for generating a data deleting instruction corresponding to the database entity class when the test data is database test data so as to execute the data deleting instruction after the test is completed and delete the database entity class from the test database.
Optionally, the apparatus further includes: and the display unit is used for displaying the test table to a user.
Compared with the prior art, the application has the following beneficial effects:
in the method provided by the embodiment of the application, the test set is obtained from the test table by creating the test table with the fields, the field description and the test data and according to the target test field required by the test, and the test set is called by the target test unit to realize the test of the target test unit. Therefore, the field description and the test data required by the test can be intuitively displayed through the test table, the problem of disordered use of the test data caused by manual input or calling of a developer can be avoided, the accuracy of unit test is improved, and the efficiency of unit test is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a testing method according to an embodiment of the present application;
FIG. 2 is a flow chart of another testing method according to an embodiment of the present application;
FIG. 3 is a flow chart of another testing method according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a testing device according to an embodiment of the present application.
Detailed Description
As described above, in the process of developing test, a developer often tests a smaller testable unit in the developed software or program to ensure that the smaller unit functions normally, and performs a one-step test on the software or program based on the test. In the testing process, a developer needs to set some testing data according to the functions of the units to be tested and the content of the tests, and the testing data can be created by the developer according to the testing requirements, can be screened out from the existing data according to the testing requirements, or can use the data in the existing database. The unit test is performed according to the field of the test data, the field description corresponding to the field, and the test data corresponding to the field at the time of the test.
The inventor finds that the data call of the existing test data is manually performed by a developer, and the developer manually inputs the test data or manually triggers the test unit to call the database or the data. Since manual input or call is easy to generate errors, errors may be caused to the input or call data, or problems may occur to the input or call. Moreover, because of lack of display of test data, a developer cannot intuitively and clearly know the tested test data after performing multiple tests, and cannot accurately know the tested test data.
The inventor finds that the fields, the field descriptions and the test data are required by the unit test, and have corresponding relations, and the fields required by the test can be determined first and then the corresponding test data can be determined. In order to solve the problem that the display of test data is not intuitive in the prior art, and disorder is easy to cause when a developer inputs or calls manually, a test table can be established, fields required by the test, field descriptions corresponding to the fields and test data corresponding to the fields can be arranged in the test table, after the test table is generated, the test table can be analyzed according to the requirement of the test, a test set required by the test is obtained, and the test set is provided with target test fields required by the test, and the field descriptions and the test data corresponding to the target test fields. The test unit may implement the unit test by invoking a test set. Therefore, the test data can be intuitively known through the test table, and the problem caused by manual input or calling of a developer is reduced by calling the test set in the test table through the test unit.
In order to make the present application solution better understood by those skilled in the art, the following description will clearly and completely describe the technical solution in the embodiments of the present application with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
First embodiment
Referring to fig. 1, a flowchart of a testing method according to an embodiment of the present application is shown.
In this embodiment, the method may be implemented by, for example, the following steps S101 to S104.
S101: the fields required for testing are determined from the target test unit.
It should be noted that, in the embodiment of the present application, the field may be a request field corresponding to the interface service, or may be a field corresponding to the database, and may be set according to the requirement of the target test unit.
It will be appreciated that the fields required for testing in the embodiments of the present application may be one or more, which are not limited in the embodiments of the present application, and may be selected according to the needs of testing.
S102: creating a test table; the test table has the field, a field description corresponding to the field, and test data corresponding to the field.
It should be noted that, in the embodiment of the present application, the specific form of the test table is not limited, and in one possible implementation, the first row in the test table may be a field, the second row may be a field description corresponding to each field, and the third row may be test data.
It should be noted that, the test data in the embodiment of the present application may be data that may be used for testing. The specific form of the test data is not limited in this embodiment, and in one possible implementation, the test data may be a number, a letter with a test meaning, or other data. In one possible implementation manner, the test data may be data input by a user according to a corresponding field and obtained by the test table, or may be preset test data by the user.
It should be noted that, in the embodiment of the present application, the field and the field description have a corresponding relationship, and the field and the test data also have a corresponding relationship. Also, the correspondence between fields and test data may be one-to-many, that is, one field may correspond to a plurality of data.
It is understood that the test table in the embodiments of the present application may be generated by receiving a trigger of a test instruction. The fields in the embodiment of the application can be selected from the existing fields according to the test requirements, and can also be created according to the test requirements. The test data may be entered after field determination or imported.
It should be noted that, in the embodiment of the present application, the manner of creating the test table is not limited, and in one possible implementation, the test table may be implemented through related programming.
S103: determining a field required to be tested by the target test unit in the test, taking the field as a target test field, and analyzing the test table by combining the target test field to obtain a test set in the test table; the test set comprises the target test field, a field description corresponding to the target test field and test data corresponding to the target test field.
It should be noted that, in the embodiment of the present application, the field is a field determined according to the test requirement for the target test unit, but the target field required for performing a test belongs to the field, and in one possible implementation, the target test field is the same as the field; in another possible implementation, the target test field is one or more of the fields.
It should be noted that, in the embodiment of the present application, the test table is parsed in combination with the target test field, which may be that the target test field, the field description corresponding to the target test field, and the test data are obtained in the test table according to the target test field.
It can be understood that the number of test data corresponding to the target test field obtained in the embodiment of the present application may be one or more.
S104: and the target test unit calls the test set to carry out the test.
It should be noted that, in the embodiments of the present application, the manner in which the target test unit calls the test set is not limited, and in one possible implementation, the call may be made through the test interface.
As can be seen from the above, in the embodiment of the present application, by creating the test table, fields, field descriptions and test data required for the test are displayed and called in the form of the table, so that the problems of data errors, test confusion and the like generated by manually inputting or calling the test data by a developer in the prior art can be avoided, and the accuracy of the unit test and the efficiency of the test are improved.
Second embodiment
In the first embodiment described above, the format of the test set parsed from the test table may not conform to the format directly called by the test unit before the target test unit is tested. And the manner in which the test unit is called is not the same for different types of test data. For parametric test data, the format of the parametric test data in the test table needs to be converted into a format which can be called by the target test unit.
In view of the foregoing, another test method is provided in the present application, and fig. 2 is a flowchart of another test method provided in an embodiment of the present application.
This embodiment will be described in detail below.
S201: the fields required for testing are determined from the target test unit.
S202: creating a test table; the test table is provided with the field, a field description corresponding to the field and parameter test data corresponding to the field.
It should be noted that, the parameter test data in the embodiment of the present application may be data used when the program such as the interface call parameter runs.
It will be appreciated that when the data being tested is parametric test data, the corresponding field may be a request field directory and the corresponding field description may be a request field description.
It will be appreciated that the specific form of parametric test data is not limited in embodiments of the present application, and in one possible implementation, the parametric test data may be a type of test data other than database data.
S203: determining a field required to be tested by the target test unit in the test, taking the field as a target test field, and analyzing the test table by combining the target test field to obtain a test set in the test table; the test set comprises the target test field, a field description corresponding to the target test field and parameter test data corresponding to the target test field.
It should be noted that, in the embodiment of the present application, the data format of the test set may be the data format of a table. The table data format is not limited in the embodiments of the present application, and may be determined according to the type of the test table specifically used.
S204: and converting the test set into a corresponding JavaBean, and converting the converted JavaBean into a corresponding entity class.
The embodiment of the application is not limited to a specific mode of converting the format of the test set, and the format conversion can be performed according to the requirement of the actual test.
In the embodiment of the application, the format conversion of the test set is converted into the Java bean first and then converted into the corresponding entity class, and the format conversion is based on Java language.
It can be appreciated that the entity class corresponding to the test set in the embodiment of the present application may be invoked by the target test unit
S205: and the target test unit calls the entity class for testing.
S206: the test form will be presented to the user.
It will be appreciated that the test form may be presented to the user, and in one possible implementation, both the test form and the running results of the target test unit after testing may be presented to the user.
It can be known that, in the embodiment of the present application, when the test data is parametric test data, in the Java language environment, the test set in the table data format may be converted into a Java bean, and then converted into a corresponding entity class, so as to be called by the target test unit. And the test table is displayed to the user, so that the user can know the test process conveniently, and the unit test is adjusted based on the test data in the test table.
Third embodiment
In the above embodiment, the test data is parametric test data, and the test unit may call the entity class after format conversion for testing. However, when the test data is database test data, the database test data needs to be inserted into the test database, and the test is performed by calling the test database. Moreover, the test data after the test is finished should be deleted, otherwise, the normal operation of the target test unit is affected, and in the prior art, because the test data is manually input or called by a developer, the test data is manually deleted by the developer during the deletion, the data redundancy is easy to be caused or the garbage data is easy to be generated, and the use of the test data during the next test is possibly affected.
In view of the foregoing, another test method is provided in the present application, and fig. 3 is a flowchart of another test method provided in an embodiment of the present application.
This embodiment will be described in detail below.
S301: the fields required for testing are determined from the target test unit.
S302: creating a test table; the test table is provided with the field, a field description corresponding to the field and database test data corresponding to the field.
S303: determining a field required to be tested by the target test unit in the test, taking the field as a target test field, and analyzing the test table by combining the target test field to obtain a test set in the test table; the test set comprises the target test field, a field description corresponding to the target test field and database test data corresponding to the target test field.
It should be noted that, the database test data in the embodiments of the present application may be basic data for implementing program operation. For example, for a unit that can implement a user information query, the test database may be a database with user information.
It should be noted that, the database test data in the embodiment of the present application may be database data that needs to be inserted into an original database, where the original database may be a common database in the field, or may be a database specifically set according to the present program or software, and in the embodiment of the present application, the type of the original database is not limited, and may be selected according to the test requirement. In addition, the original database can have preset data.
S304: and converting the test set into a corresponding JavaBean, converting the converted JavaBean into a corresponding database entity class, and inserting the database entity class into a test database.
It should be noted that, since the database test data cannot be directly called by the test unit, it is required to insert the database test data into the test database, and the test unit calls the test database to implement the test on the test unit.
S305: and generating a data deleting instruction corresponding to the database entity class so as to execute the data deleting instruction after the test is completed, and deleting the database entity class from the test database.
It should be noted that, the data deleting instruction in the embodiment of the present application may be a structured query language (Structured Query Language, SQL) script that deletes the inserted database test data, which is returned after the database test data is inserted. And after the test is completed, calling the SQL script, and deleting the inserted database test data.
S306: and the target test unit calls the test database to test.
It should be noted that when the test is performed in the Java language environment, the target test unit may call the test database through a Java database connection (Java Database Connectivity, JDBC).
S307: and acquiring an operation result generated by the target test unit after the test set is called for testing, judging whether the operation result is consistent with a preset correct result, and obtaining a test result according to the judgment result.
It should be noted that, the operation result in the embodiment of the present application may be that the data is obtained after the target test unit invokes the test set to perform operation, or may be the operation state of the test unit. When the operation result is the data obtained after operation, whether the operation result is consistent with the preset correct data or not can be judged, if so, the test is normal, and if not, the test is wrong.
As can be seen from the above, in the embodiment of the present application, the database test data is inserted into the test database, and the test database is called, so that the test can be performed by using the data in the test database. And deleting the data inserted into the database, judging the obtained operation result, and obtaining the test result of the test.
Fourth embodiment
Fig. 4 is a schematic structural diagram of a testing device according to an embodiment of the present application.
Examples may include:
a building unit 401, which may be used to determine the fields required for the test according to the target test unit; creating a test table; the test table is provided with the field, a field description corresponding to the field and test data corresponding to the field;
the parsing unit 402 may be configured to determine a field required to be tested by the target test unit in the current test, parse the test table with the field as a target test field, and obtain a test set in the test table; the test set comprises the target test field, a field description corresponding to the target test field and test data corresponding to the target test field;
and the calling unit 403 may be used for the target test unit to call the test set for testing.
The device can further comprise an assertion unit, wherein the assertion unit can be used for obtaining an operation result generated by the target test unit after the test set is called for testing, judging whether the operation result is consistent with a preset correct result, and obtaining a test result according to the judgment result.
The device may further include a deleting unit, where the deleting unit may be configured to generate a data deleting instruction corresponding to the database entity class when the test data is database test data, so as to execute the data deleting instruction after the test is completed, and delete the database entity class from the test database.
Further, the device may further include a display unit, where the display unit may be configured to display the test form to a user.
It should be understood that in this application, "at least one" means one or more, and "a plurality" means two or more. "and/or" for describing the association relationship of the association object, the representation may have three relationships, for example, "a and/or B" may represent: only a, only B and both a and B are present, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b or c may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments for relevant points. The apparatus embodiments described above are merely illustrative, wherein the units and modules illustrated as separate components may or may not be physically separate. In addition, some or all of the units and modules can be selected according to actual needs to achieve the purpose of the embodiment scheme. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
The foregoing is merely exemplary of the application and it should be noted that modifications and adaptations to those skilled in the art may be made without departing from the principles of the application and are intended to be comprehended within the scope of the application.
Claims (9)
1. A method of testing, comprising:
determining fields required for testing according to a target test unit;
creating a test table; the test table is provided with the field, a field description corresponding to the field and test data corresponding to the field; the test table is realized through related programming;
determining a field required to be tested by the target test unit in the test, taking the field as a target test field, and analyzing the test table by combining the target test field to obtain a test set in the test table; the test set comprises the target test field, a field description corresponding to the target test field and test data corresponding to the target test field;
the target test unit calls the test set for testing;
when the test data is parametric test data, before the target test unit calls the test set to perform the test, the method further comprises:
converting the test set into a corresponding JavaBean, and converting the converted JavaBean into a corresponding entity class;
the target test unit calling a test set for testing comprises the following steps:
the target test unit calls the entity class for testing;
when the test data is database test data, before the target test unit calls the test set to test, the method further comprises the following steps:
converting the test set into a corresponding JavaBean, converting the converted JavaBean into a corresponding database entity class, and inserting the database entity class into a test database;
the target test unit calling a test set for testing comprises the following steps:
and the target test unit calls a test database to test.
2. The method of claim 1, wherein the converting the converted java bean into a corresponding database entity class, further comprises:
and generating a data deleting instruction corresponding to the database entity class so as to execute the data deleting instruction after the test is completed, and deleting the database entity class from the test database.
3. The method according to claim 1, wherein the test data is parametric test data and/or database test data.
4. The method according to claim 1, wherein the method further comprises:
and acquiring an operation result generated by the target test unit after the test set is called for testing, judging whether the operation result is consistent with a preset correct result, and obtaining a test result according to the judgment result.
5. The method according to claim 1, wherein the method further comprises:
the test form will be presented to the user.
6. A test apparatus, the apparatus comprising:
the establishing unit is used for determining fields required by the test according to the target test unit; creating a test table; the test table is provided with the fields, field descriptions corresponding to the fields and test data corresponding to the fields, and is realized through related programming;
the analyzing unit is used for determining a field required to be tested by the target testing unit at the time, taking the field as a target testing field, and analyzing the testing table by combining the target testing field to obtain a testing set in the testing table; the test set comprises the target test field, a field description corresponding to the target test field and test data corresponding to the target test field;
the calling unit is used for calling the test set by the target test unit to test;
when the test data are parametric test data, the analysis unit is further configured to convert the test set into a corresponding java bean, and then convert the converted java bean into a corresponding entity class;
the calling unit is specifically used for calling the entity class by the target testing unit for testing;
when the test data is database test data, the analysis unit is further configured to convert the test set into a corresponding java bean, then convert the converted java bean into a corresponding database entity class, and insert the database entity class into a test database;
the calling unit is specifically used for calling the test database by the target test unit for testing.
7. The apparatus of claim 6, wherein the apparatus further comprises:
the assertion unit is used for acquiring the operation result generated by the target test unit after the test set is called for testing, judging whether the operation result is consistent with a preset correct result, and obtaining a test result according to the judgment result.
8. The apparatus of claim 6, wherein the apparatus further comprises:
and the deleting unit is used for generating a data deleting instruction corresponding to the database entity class when the test data is database test data so as to execute the data deleting instruction after the test is completed and delete the database entity class from the test database.
9. The apparatus of claim 6, wherein the apparatus further comprises:
and the display unit is used for displaying the test table to a user.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911383609.0A CN111143221B (en) | 2019-12-28 | 2019-12-28 | Test method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911383609.0A CN111143221B (en) | 2019-12-28 | 2019-12-28 | Test method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111143221A CN111143221A (en) | 2020-05-12 |
| CN111143221B true CN111143221B (en) | 2024-01-30 |
Family
ID=70521570
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911383609.0A Active CN111143221B (en) | 2019-12-28 | 2019-12-28 | Test method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111143221B (en) |
Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103853652A (en) * | 2012-11-29 | 2014-06-11 | 百度在线网络技术（北京）有限公司 | Test case generation method and device |
| CN104133772A (en) * | 2014-08-13 | 2014-11-05 | 广东电网公司信息中心 | Automatic test data generation method |
| CN105786787A (en) * | 2016-02-29 | 2016-07-20 | 四川长虹电器股份有限公司 | Efficient PDF report form testing method based on Java |
| CN106897205A (en) * | 2015-12-18 | 2017-06-27 | 阿里巴巴集团控股有限公司 | A kind of test data generating method and device |
| CN107943692A (en) * | 2017-11-17 | 2018-04-20 | 中国银行股份有限公司 | The automatic test approach and device that a kind of batch original table passes down |
| CN108241705A (en) * | 2016-12-27 | 2018-07-03 | 北京神州泰岳软件股份有限公司 | A kind of data insertion method and device |
| CN109117377A (en) * | 2018-08-31 | 2019-01-01 | 杭州安恒信息技术股份有限公司 | It is a kind of based on the automatic generation of test data, device and equipment of building table statement |
| CN109474488A (en) * | 2018-10-31 | 2019-03-15 | 中国银行股份有限公司 | Interface test method, device and computer equipment |
| CN110134584A (en) * | 2019-04-12 | 2019-08-16 | 深圳壹账通智能科技有限公司 | A kind of generation method, device, storage medium and the server of interface testing use-case |
| CN110188030A (en) * | 2019-04-08 | 2019-08-30 | 平安科技（深圳）有限公司 | A kind of test data generating method, device and computer equipment, storage medium |
| WO2019165691A1 (en) * | 2018-02-28 | 2019-09-06 | 平安科技（深圳）有限公司 | Method, apparatus and device for automatically generating test case, and readable storage medium |
| CN110471842A (en) * | 2019-07-12 | 2019-11-19 | 平安普惠企业管理有限公司 | A kind of test method, device and computer readable storage medium |
| CN110543428A (en) * | 2019-09-09 | 2019-12-06 | 中国工商银行股份有限公司 | Application system testing method and device |
| CN110597728A (en) * | 2019-09-20 | 2019-12-20 | 中国银行股份有限公司 | Method, device and system for constructing test data |
-
2019
- 2019-12-28 CN CN201911383609.0A patent/CN111143221B/en active Active
Patent Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103853652A (en) * | 2012-11-29 | 2014-06-11 | 百度在线网络技术（北京）有限公司 | Test case generation method and device |
| CN104133772A (en) * | 2014-08-13 | 2014-11-05 | 广东电网公司信息中心 | Automatic test data generation method |
| CN106897205A (en) * | 2015-12-18 | 2017-06-27 | 阿里巴巴集团控股有限公司 | A kind of test data generating method and device |
| CN105786787A (en) * | 2016-02-29 | 2016-07-20 | 四川长虹电器股份有限公司 | Efficient PDF report form testing method based on Java |
| CN108241705A (en) * | 2016-12-27 | 2018-07-03 | 北京神州泰岳软件股份有限公司 | A kind of data insertion method and device |
| CN107943692A (en) * | 2017-11-17 | 2018-04-20 | 中国银行股份有限公司 | The automatic test approach and device that a kind of batch original table passes down |
| WO2019165691A1 (en) * | 2018-02-28 | 2019-09-06 | 平安科技（深圳）有限公司 | Method, apparatus and device for automatically generating test case, and readable storage medium |
| CN109117377A (en) * | 2018-08-31 | 2019-01-01 | 杭州安恒信息技术股份有限公司 | It is a kind of based on the automatic generation of test data, device and equipment of building table statement |
| CN109474488A (en) * | 2018-10-31 | 2019-03-15 | 中国银行股份有限公司 | Interface test method, device and computer equipment |
| CN110188030A (en) * | 2019-04-08 | 2019-08-30 | 平安科技（深圳）有限公司 | A kind of test data generating method, device and computer equipment, storage medium |
| CN110134584A (en) * | 2019-04-12 | 2019-08-16 | 深圳壹账通智能科技有限公司 | A kind of generation method, device, storage medium and the server of interface testing use-case |
| CN110471842A (en) * | 2019-07-12 | 2019-11-19 | 平安普惠企业管理有限公司 | A kind of test method, device and computer readable storage medium |
| CN110543428A (en) * | 2019-09-09 | 2019-12-06 | 中国工商银行股份有限公司 | Application system testing method and device |
| CN110597728A (en) * | 2019-09-20 | 2019-12-20 | 中国银行股份有限公司 | Method, device and system for constructing test data |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111143221A (en) | 2020-05-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106909510B (en) | Method for obtaining test case and server | |
| CN105094783B (en) | method and device for testing stability of android application | |
| CN108446223B (en) | Business scene automatic testing method based on dynamic compilation | |
| US8904352B2 (en) | Systems and methods for processing source code during debugging operations | |
| CN111209185B (en) | Keyword-based automated testing method and computer-readable storage medium | |
| CN108509344B (en) | Daily cutting batch test method, equipment and readable storage medium | |
| CN109977012B (en) | Joint debugging test method, device, equipment and computer readable storage medium of system | |
| CN112445197B (en) | Controller version information verification method, processor and whole vehicle test system | |
| CN110704475A (en) | Method and system for comparing ETL loading table structures | |
| CN110297760A (en) | Building method, device, equipment and the computer readable storage medium of test data | |
| CN108874649B (en) | Method and device for generating automatic test script and computer equipment thereof | |
| CN108710571A (en) | A kind of method and apparatus generating automatic test code | |
| CN112650670A (en) | Application testing method, device, system, electronic equipment and storage medium | |
| CN114185791A (en) | Method, device and equipment for testing data mapping file and storage medium | |
| CN108427645B (en) | Method and system for realizing unattended operation in automatic test platform without command line interface | |
| CN113138937A (en) | Test method and device | |
| CN111143221B (en) | Test method and device | |
| CN109508203B (en) | Method, device and system for determining version consistency | |
| CN111176995A (en) | Test method and test system based on big data test case | |
| CN115599683A (en) | Automatic testing method, device, equipment and storage medium | |
| CN110716859A (en) | Method for automatically pushing test cases for modified codes and related device | |
| CN112559348B (en) | Test analysis method, system, equipment and medium based on jacoco | |
| CN111679983B (en) | JAVA interface static test method and device | |
| CN113900926A (en) | Batch test method, system and medium for test cases | |
| CN113434382A (en) | Database performance monitoring method and device, electronic equipment and computer readable 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 |