CN111143221A - Test method and device - Google Patents
Test method and device Download PDFInfo
- Publication number
- CN111143221A CN111143221A CN201911383609.0A CN201911383609A CN111143221A CN 111143221 A CN111143221 A CN 111143221A CN 201911383609 A CN201911383609 A CN 201911383609A CN 111143221 A CN111143221 A CN 111143221A
- Authority
- CN
- China
- Prior art keywords
- test
- field
- target
- data
- unit
- 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
- 238000010998 test method Methods 0.000 title claims abstract description 5
- 238000012360 testing method Methods 0.000 claims abstract description 512
- 238000000034 method Methods 0.000 claims abstract description 22
- 235000006719 Cassia obtusifolia Nutrition 0.000 claims description 16
- 235000014552 Cassia tora Nutrition 0.000 claims description 16
- 244000201986 Cassia tora Species 0.000 claims description 15
- 238000011161 development Methods 0.000 description 8
- 238000006243 chemical reaction Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 244000277285 Cassia obtusifolia Species 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 238000007689 inspection Methods 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
- 238000012795 verification Methods 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
Abstract
The application discloses a test method and a test device, wherein the method comprises the following steps: the test of the target test unit is realized by creating a test table with fields, field description and test data, acquiring a test set from the test table according to a target test field required by the test, and calling the test set through the target test unit. Therefore, the fields, the field descriptions and the test data required by the test can be visually displayed through the test form, the problem of disordered use of the test data caused by manual input or calling of developers can be avoided, and the accuracy and the efficiency of unit test are improved.
Description
Technical Field
The present application relates to the field of computers, and in particular, to a test method and apparatus.
Background
During the development and testing of software, development testers usually perform inspection and verification on software or testable units in a program, which is generally called unit testing. The unit test is performed to ensure that the unit functions normally, so that it can be confirmed that a part of the program composed of a plurality of units functions normally.
When a development tester performs a unit test, the development tester needs to input test data according to the content to be tested to test the unit, where the test data may be data manually input by the development tester and meeting a certain condition, or may be data in a database created in advance by the development tester. However, the above two methods need to be manually performed by development testers for inputting test data, and since the test data corresponds to the field, the manual input may cause the test data not to correspond to the field, which is likely to cause a problem of disordered use of the test data, resulting in low efficiency of unit testing.
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, an embodiment of the present application provides a testing method, where the method includes:
determining fields required by the test according to the target test unit;
creating a test table; wherein the test table has 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 current test, taking the field as a target test field, analyzing the test table by combining the target test field, and acquiring 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 test.
Optionally, when the test data is parameter 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, and converting the converted JavaBean into a corresponding entity class;
the target test unit calls the test set to perform testing, including:
and the target test unit calls the entity class to test.
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 calls the test set to perform testing, including:
and the target test unit calls a test database to test.
Optionally, the converting the converted JavaBean 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 finished and delete the database entity class from the test database.
Optionally, the test data is parameter test data and/or database test data.
Optionally, the method further includes:
and acquiring an operation result generated after the target test unit calls the test set to perform 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 includes: the test form will be presented to the user.
In a second aspect, an embodiment of the present application provides a testing apparatus, including:
the establishing unit is used for determining fields required by the test according to the target test unit; creating a test table; wherein the test table has the field, a field description corresponding to the field, and test data corresponding to the field;
the analysis unit is used for determining a field required to be tested by the target test unit in the current test, using 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 calling unit is used for calling the test set to test by the target test unit.
Optionally, the apparatus further comprises:
and the assertion unit is used for acquiring an operation result generated after the target test unit calls the test set 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 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 finished and delete the database entity class from the test database.
Optionally, the apparatus further comprises: and the display unit is used for displaying the test table to a user.
Compared with the prior art, the method has the following beneficial effects:
in the method provided by the embodiment of the application, a test table with fields, field descriptions and test data is created, a test set is obtained from the test table according to a target test field required by the current test, and the test set is called through a target test unit to realize the test of the target test unit. Therefore, the fields, the field descriptions and the test data required by the test can be visually displayed through the test form, the problem of disordered use of the test data caused by manual input or calling of developers 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 needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a flowchart of a testing method provided in an embodiment of the present application;
FIG. 2 is a flow chart of another testing method provided by embodiments of the present application;
FIG. 3 is a flow chart of another testing method provided by embodiments of the present application;
fig. 4 is a schematic structural diagram of a testing apparatus according to an embodiment of the present application.
Detailed Description
As described above, in the development and testing process, a developer often tests a smaller testable unit of a developed software or program to ensure that the smaller unit functions normally, and then performs a one-step test on the software or program. In the testing process, a developer needs to set some test data according to the functions of the unit to be tested and the content of the test, and the test data can be created by the developer according to the testing requirement, can be screened from the existing data according to the testing requirement, or can use the data in the existing database. A unit test is performed at the time of test based on a field of test data, a field description corresponding to the field, and the test data corresponding to the field.
The inventor finds that the existing data calling of the test data is performed manually by a developer, and the developer manually inputs the test data or manually triggers the test unit to call the database or the data. Because manual input or invocation is prone to errors, the data itself of the input or invocation may be erroneous or problematic. Moreover, due to the lack of display of the test data, developers cannot intuitively and clearly know the situation of the tested test data after carrying out multiple tests, and cannot accurately know the test situation.
The inventor finds that the field, the field description and the test data are required for testing when the unit test is carried out, the field description and the test data have corresponding relation, and the field required for testing can be determined firstly and then the corresponding test data can be determined when the unit test is carried out. And in order to solve the problems that test data display is not intuitive in the prior art and developers are easy to be confused when manually inputting or calling, a test table can be established, the test table can be provided with fields required by the test, field descriptions corresponding to the fields and test data corresponding to the fields, after the test table is generated, the test table can be analyzed according to the requirements of the test to obtain a test set required by the test, 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 unit testing by calling a test set. Therefore, the test data can be intuitively known through the test table, and the problem that a developer manually inputs or calls the test set in the test table is reduced through the test unit.
In order to make the technical solutions of the present application better understood, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
First embodiment
Referring to fig. 1, a flowchart of a testing method provided in an embodiment of the present application is shown.
In this embodiment, the method may be implemented, for example, by the following steps S101-S104.
S101: and determining fields required by the test according to the target test unit.
It should be noted that the field in the embodiment of the present application may be a request field corresponding to an interface service, or may also be a field corresponding to a database, and may be set according to the needs of the target test unit.
It should be understood that, in the embodiment of the present application, one or more fields required for the test may be provided, which is not limited in the embodiment of the present application and may be selected according to the requirement of the test.
S102: creating a test table; wherein 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 the specific form of the test table is not limited in the embodiment of the present application, and in a possible implementation manner, 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 and the subsequent row may be test data.
It should be noted that the test data in the embodiment of the present application may be data that can be used for testing. In this embodiment, a specific form of the test data is not limited, and in a possible implementation manner, the test data may be a number, or may also be a letter or other data having a test meaning. In this embodiment, the source of the test data is not limited, and in a possible implementation manner, the test data may be data input by the user according to the corresponding field, which is obtained by the test form, or may be test data preset 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 the field and the 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 embodiment of the present application may be generated by receiving a test instruction trigger. The field in the embodiment of the present application may be selected from existing fields according to the test requirement, or may be created according to the test requirement. Test data may be entered or imported after field determination.
It should be noted that, in the embodiment of the present application, a manner of creating the test table is not limited, and in a possible implementation manner, the test table may be implemented by related programming.
S103: determining a field required to be tested by the target test unit in the current test, taking the field as a target test field, analyzing the test table by combining the target test field, and acquiring a test set in the test table; the test set comprises the target test field, field description corresponding to the target test field and test data corresponding to the target test field.
It should be noted that the field in the embodiment of the present application is a field determined according to the requirement of the test for the target test unit, but the target field required when performing a test belongs to the field, and in a 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 analysis of the test table is performed in combination with the target test field, and may be to obtain the target test field and the field description and test data corresponding to the target test field in the test table according to the target test field.
It can be understood that one or more test data corresponding to the target test field may be acquired in the embodiment of the present application.
S104: and the target test unit calls the test set to test.
It should be noted that, in the embodiment of the present application, a manner of invoking the test set by the target test unit is not limited, and the invocation may be performed through a test interface in one possible implementation.
As can be seen from the above, in the embodiment of the application, by creating the test table, the fields, the field descriptions and the test data required by the test are displayed and called in the form of the table, the problems of data errors, test confusion and the like caused by manual input or test data calling by developers in the prior art can be avoided, and the accuracy of unit test and the efficiency of test are improved.
Second embodiment
In the first embodiment, before the target test unit is tested, the format of the test set parsed from the test table may not conform to the format directly called by the test unit. And the manner in which the test unit is invoked differs for different types of test data. For the parameter test data, the format of the parameter test data in the test table needs to be converted into a format that can be called by the target test unit.
In view of the above situation, the present application provides another testing method, and fig. 2 is a flowchart of another testing method provided in the embodiment of the present application.
This embodiment will be described in detail below.
S201: and determining fields required by the test according to the target test unit.
S202: creating a test table; wherein the test table has the field, a field description corresponding to the field, and parametric 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 a program such as an interface call parameter runs.
It is understood that, when the data to be tested is parameter test data, the corresponding field may be a request field directory, and the corresponding field description may be a request field description.
It is to be understood that the specific form of the parametric test data is not limited in the embodiments of the present application, and in a possible implementation, the parametric test data may be a test data type other than database data.
S203: determining a field required to be tested by the target test unit in the current test, taking the field as a target test field, analyzing the test table by combining the target test field, and acquiring 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 the data format of the test set in the embodiment of the present application may be a data format of a table. The form data format is not limited in the embodiment of the application, and can be determined according to the type of the test form used specifically.
S204: and converting the test set into a corresponding JavaBean, and converting the converted JavaBean into a corresponding entity class.
In the embodiment of the present application, a specific manner of format conversion for the test set is not limited, and format conversion may be performed according to the requirement of actual test.
In the embodiment of the application, the format conversion of the test set into the JavaBean first and then into the corresponding entity class is based on Java language.
It can be understood that the entity class corresponding to the test set in the embodiment of the present application is invokable by the target test unit
S205: and the target test unit calls the entity class to test.
S206: the test form will be presented to the user.
It is to be understood that the test table may be presented to the user, and in a possible implementation manner, both the test table and the operation result after the target test unit is tested may be presented to the user.
As can be seen from the above, in the embodiment of the present application, when the test data is the parameter test data, in the environment of the Java language, the test set in the table data format may be converted into the Java bean, and then converted into the corresponding entity class, so that the target test unit can call the test set. And the test table is displayed to the user, so that the user can conveniently know the test process, 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 parameter 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. In addition, test data after the test is finished should be deleted, otherwise 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 also manually deleted by the developer during deletion, data redundancy or garbage data is easily caused, and the use of the test data during the next test may be affected.
In view of the above situation, the present application provides another testing method, and fig. 3 is a flowchart of another testing method provided in the embodiment of the present application.
This embodiment will be described in detail below.
S301: and determining fields required by the test according to the target test unit.
S302: creating a test table; wherein the test table has 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 current test, taking the field as a target test field, analyzing the test table by combining the target test field, and acquiring 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 embodiment 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, the original database may be a database commonly used in the field, or a database specially set according to the program or software, the type of the original database is not limited in the embodiment of the present application, and the database test data may be selected according to the test need. In addition, the original database may 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, because the database test data cannot be directly called by the test unit, the test unit needs to be inserted into the test database, and the test unit is tested by calling the test database through 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 finished and delete the database entity class from the test database.
It should be noted that the data deletion instruction in the embodiment of the present application may be a Structured Query Language (SQL) script that is returned after the database test data is inserted and deletes the inserted database test data. And after the test is finished, 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 context of Java language, the target test unit may call the test Database through Java Database Connectivity (JDBC).
S307: and acquiring an operation result generated after the target test unit calls the test set to perform 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 data obtained after the target test unit calls the test set to operate, or may be an operation state of the test unit. And when the operation result is the data obtained after operation, judging whether the operation result is consistent with the preset correct data or not, if so, testing normally, and if not, testing wrongly.
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 by using the data in the test database can be realized. And the data inserted into the database is deleted, the obtained operation result is judged, and the test result of the test can be obtained.
Fourth embodiment
Fig. 4 is a schematic structural diagram of a testing apparatus according to an embodiment of the present application.
For example, the method may specifically include:
a building unit 401, configured to determine fields required for testing according to the target testing unit; creating a test table; wherein the test table has the field, a field description corresponding to the field, and test data corresponding to the field;
an analyzing unit 402, configured to determine a field to be tested by the target testing unit at this time, use the field as a target testing field, and analyze the test table in combination with the target testing 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 calling unit 403 may be configured to call the test set for testing by the target test unit.
The device may further include an assertion unit, where the assertion unit may be configured to obtain an operation result generated by the target test unit after the target test unit calls the test set to perform a test, determine whether the operation result is consistent with a preset correct result, and obtain a test result according to the determination 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 comprise a presentation unit, which may be configured to present the test form to a user.
It should be understood that in the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" for describing an association relationship of associated objects, indicating that there may be three relationships, e.g., "a and/or B" may indicate: only A, only B and both A and B are present, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of single item(s) or plural items. 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.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus embodiment, since it is substantially similar to the method embodiment, it is relatively simple to describe, and reference may be made to some descriptions of the method embodiment for relevant points. The above-described apparatus embodiments are merely illustrative, and the units and modules described as separate components may or may not be physically separate. In addition, some or all of the units and modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The foregoing is directed to embodiments of the present application and it is noted that numerous modifications and adaptations may be made by those skilled in the art without departing from the principles of the present application and are intended to be within the scope of the present application.
Claims (11)
1. A method of testing, comprising:
determining fields required by the test according to the target test unit;
creating a test table; wherein the test table has 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 current test, taking the field as a target test field, analyzing the test table by combining the target test field, and acquiring 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 test.
2. The method of claim 1, wherein when the test data is parametric test data, before the target test unit invokes a test set for testing, further comprising:
converting the test set into a corresponding JavaBean, and converting the converted JavaBean into a corresponding entity class;
the target test unit calls the test set to perform testing, including:
and the target test unit calls the entity class to test.
3. The method of claim 1, wherein when the test data is database test data, before the target test unit calls a test set for testing, further comprising:
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 calls the test set to perform testing, including:
and the target test unit calls a test database to test.
4. The method according to claim 3, wherein said further converting the converted JavaBean into the 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 finished and delete the database entity class from the test database.
5. The method according to claim 1, characterized in that the test data are parametric test data and/or database test data.
6. The method of claim 1, further comprising:
and acquiring an operation result generated after the target test unit calls the test set to perform testing, judging whether the operation result is consistent with a preset correct result, and obtaining a test result according to the judgment result.
7. The method of claim 1, further comprising:
the test form will be presented to the user.
8. 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; wherein the test table has the field, a field description corresponding to the field, and test data corresponding to the field;
the analysis unit is used for determining a field required to be tested by the target test unit in the current test, using 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 calling unit is used for calling the test set to test by the target test unit.
9. The apparatus of claim 8, further comprising:
and the assertion unit is used for acquiring an operation result generated after the target test unit calls the test set for testing, judging whether the operation result is consistent with a preset correct result, and obtaining a test result according to the judgment result.
10. The apparatus of claim 8, further comprising:
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 finished and delete the database entity class from the test database.
11. The apparatus of claim 8, further comprising:
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 true CN111143221A (en) | 2020-05-12 |
| CN111143221B 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 |
|---|---|
| CN111143221B (en) | 2024-01-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107992409B (en) | Test case generation method and device, computer equipment and storage medium | |
| CN105094783B (en) | method and device for testing stability of android application | |
| CN109302522B (en) | Test method, test device, computer system, and computer medium | |
| US11074162B2 (en) | System and a method for automated script generation for application testing | |
| US20070061641A1 (en) | Apparatus and method for generating test driver | |
| CN108509344B (en) | Daily cutting batch test method, equipment and readable storage medium | |
| CN112445197B (en) | Controller version information verification method, processor and whole vehicle test system | |
| CN111181805B (en) | Micro-service test baffle generation method and system based on test case | |
| CN108874649B (en) | Method and device for generating automatic test script and computer equipment thereof | |
| CN112650670A (en) | Application testing method, device, system, electronic equipment and storage medium | |
| CN111209185A (en) | Keyword-based automated testing method and computer-readable storage medium | |
| CN108710571A (en) | A kind of method and apparatus generating automatic test code | |
| CN114546738A (en) | Server general test method, system, terminal and storage medium | |
| CN110908915B (en) | Test coverage rate display method and device and computer system | |
| CN114185791A (en) | Method, device and equipment for testing data mapping file and storage medium | |
| CN105677569B (en) | Android automated test tools and method of testing based on event handler | |
| CN106557419B (en) | Program testing method and device | |
| CN110543429A (en) | Test case debugging method and device and storage medium | |
| CN106294109B (en) | Method and device for acquiring defect code | |
| CN113342692A (en) | Test case automatic generation method and device, electronic equipment and storage medium | |
| CN112559348A (en) | Test analysis method, system, equipment and medium based on jacoco | |
| CN111176995A (en) | Test method and test system based on big data test case | |
| CN111143221B (en) | Test method and device | |
| CN108153655B (en) | Method for detecting drawing call quantity of virtual reality software and storage medium | |
| CN110716859A (en) | Method for automatically pushing test cases for modified codes and related device |
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 |