CN114741320B - Unit test case management method and device and readable storage medium - Google Patents
Unit test case management method and device and readable storage medium Download PDFInfo
- Publication number
- CN114741320B CN114741320B CN202210534112.XA CN202210534112A CN114741320B CN 114741320 B CN114741320 B CN 114741320B CN 202210534112 A CN202210534112 A CN 202210534112A CN 114741320 B CN114741320 B CN 114741320B
- Authority
- CN
- China
- Prior art keywords
- assertion
- unit test
- version
- test case
- case
- 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
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/368—Test management for test version control, e.g. updating test cases to a new software version
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a management method of unit test cases, which adopts corresponding methods to perform assertion enhancement on assertion data of different types, thereby improving the effectiveness of the unit test cases; the test cases of each version after assertion enhancement are subjected to duplicate removal according to a preset case duplicate removal rule, so that the duplication degree of the test cases among different versions is reduced; detecting whether the code texts of the test cases in different versions conflict or not by using a git merge technology, further matching different test functions in each version test case managed on the remote git and the test case of the current version managed on the local git in a test function name matching mode after obtaining a version list with the conflict, and then adding the function code segment corresponding to the matched test function managed on the remote git into the test case managed on the local git, thereby realizing the merging of the test cases in different versions. The invention also provides a unit test case management device and a readable storage medium.
Description
Technical Field
The invention relates to the technical field of software testing, in particular to a method and a device for managing unit test cases and a readable storage medium.
Background
The unit in the unit test is colloquially called a function for realizing simple functions. Unit testing is to test whether a function functions properly with a specific set of inputs (test cases) and returns the correct output. In the prior art, a plurality of methods for generating unit test cases exist, but if the generated unit test cases lack effective management, the delivery quality and the delivery efficiency of business software are influenced. At present, the management of the generated unit test cases mainly has the following difficulties:
1. the case effectiveness is low. The unit test cases need to have explicit assertions, and the automatically generated unit test cases may have inaccurate assertions, resulting in low effectiveness of the unit test cases.
2. The case repetition degree is high. The automatic generation method of the unit test case mainly comprises two methods of data construction and data recording, the function paths corresponding to the cases are possibly repeated, and the large number of the repeated cases can lead the number of the cases to be exponentially increased.
3. Case merging is difficult. When multiple persons code the same unit test case, code text collision may occur, for example, for case a, there are two different versions A1, A2 that are modified, assuming that the 10 th line of A1 is coded as c +2= d, and the 10 th line of A2 is coded as c-2= d, then A1 and A2 may have merging collision due to code text collision of the 10 th line when merging, resulting in case merging difficulty.
Disclosure of Invention
The invention provides a method and a device for managing unit test cases and a readable storage medium, aiming at improving the effectiveness of managing the unit test cases and improving the delivery quality and delivery efficiency of software.
In order to achieve the purpose, the invention adopts the following technical scheme:
a unit test case management method is provided, which comprises:
s1, for unit test cases with variable type or array type assertion data, performing assertion enhancement on the unit test cases with different versions according to a corresponding assertion data enhancement method;
s2, removing the duplicate of the unit test cases of each version after assertion enhancement according to a preset case duplicate removal rule;
and S3, detecting whether the code texts of the unit test cases among the different versions after the duplication removal have conflict by using a git merge code text merging technology, acquiring a version list with the conflict, and then overlaying each test function in each version test case managed on the remote git to the unit test case of the current version managed on the local git to complete the merging of each version test case.
Preferably, when the assertion data is of a variable type, in step S1, the method for performing assertion enhancement on the unit test cases of different versions includes:
step A1, judging whether the unit test case assertion of the current version fails,
if yes, turning to the step A2;
if not, terminating the assertion enhancement flow;
step A2, the assertion data is regularly matched with the rules in the rule base,
if the matching is successful, removing the format of the assertion data according to the matched rule, and then turning to the step A3;
if the matching fails, the assertion enhancement flow is terminated;
step A3, updating the assertion data with the removed format to the unit test case with the corresponding version;
step A4, the unit test case of the corresponding version after the data updating is finished is operated, whether the assertion is successful or not is judged,
if so, judging that the assertion is successfully enhanced and recording the assertion enhancement success information;
if not, judging that the assertion enhancement fails and recording assertion enhancement failure information.
Preferably, the assertion data includes an actual output result and an expected output result of the test function after the unit test case of the current version is run.
Preferably, in step S2, the method for removing duplicate of the unit test cases of different versions specifically includes:
step C1, operating the unit test cases of all versions corresponding to the same test function to obtain the unit test case of each operated version
The code path corresponding to the unit test case;
step C2, judging whether the code paths of the unit test cases among different versions are the same,
if the code paths are the same, any one of the version unit test cases with the same code paths is reserved;
if not, keeping different versions of the unit test case.
Preferably, in step S3, the method for merging the unit test cases of each version specifically includes:
step D1, obtaining test function names corresponding to the unit test cases of each version managed on the local git and each version managed on the remote git, then forming each test function name corresponding to the A1 version of the unit test case managed on the local git into a first array, and forming each test function name corresponding to each A2 version of the unit test case managed on the remote git into a second array;
step D2, performing test function name matching on each second array and the first array,
if different test function names are matched, the step D3 is carried out;
if the different test function names are not matched, filtering the second array currently participating in matching;
step D3, acquiring function code segments corresponding to the test functions with different names matched from the second array;
and D4, adding the acquired function code segments into the unit test cases of the A1 version managed on the local git.
The invention also provides a unit test case management device, which can realize the unit test case management method and comprises the following steps:
the assertion enhancing module is used for carrying out assertion enhancement on unit test cases with variable types or array types of assertion data according to corresponding assertion data enhancing methods;
the case duplication removing module is connected with the assertion enhancing module and used for removing duplication of the unit test cases of each version after assertion enhancement according to a preset case duplication removing rule;
and the case merging module is connected with the case deduplication module and used for detecting whether the code texts of the unit test cases among the deduplicated different versions have conflicts by using a git merge code text merging technology, acquiring a version list with the conflicts, and then overlapping each test function in each version test case managed on the remote git to the unit test case of the current version managed on the local git to complete merging of each version test case.
The present invention also provides a readable storage medium having computer readable instructions stored thereon, which when executed by a processor, the processor performs the unit test case management method.
The invention has the following beneficial effects:
1. for different types of assertion data, corresponding methods are adopted for assertion enhancement, so that the effectiveness of the unit test case is improved;
2. the unit test cases of each version after assertion enhancement are subjected to duplicate removal according to a preset case duplicate removal rule, so that the duplication degree of the unit test cases among different versions is reduced;
3. detecting whether the code texts of the unit test cases of different versions have conflicts through a git merge technology, further matching different test functions in the unit test cases of each version managed on the remote git and the unit test cases of the current version managed on the local git in a test function name matching mode after obtaining a version list with conflicts, and then adding the matched function code segments corresponding to the test functions managed on the remote git to the unit test cases managed on the local git, thereby realizing the merging of the unit test cases of different versions.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the embodiments of the present invention will be briefly described below. It is obvious that the drawings described below are only some embodiments of the invention, and that for a person skilled in the art, other drawings can be derived from them without inventive effort.
FIG. 1 is a diagram illustrating steps for implementing a method for managing unit test cases according to an embodiment of the present invention;
FIG. 2 is a diagram of implementation steps of a method for performing assertion enhancement on unit test cases of different versions when assertion data is of a variable type;
FIG. 3 is a diagram of method steps for deduplication of different versions of unit test cases;
FIG. 4 is a diagram of method steps for merging versions of unit test cases;
fig. 5 is a schematic structural diagram of a unit test case management apparatus according to an embodiment of the present invention.
Detailed Description
The technical scheme of the invention is further explained by the specific implementation mode in combination with the attached drawings.
Wherein the showings are for the purpose of illustration only and are shown by way of illustration only and not in actual form, and are not to be construed as limiting the present patent; to better illustrate the embodiments of the present invention, some parts of the drawings may be omitted, enlarged or reduced, and do not represent the size of an actual product; it will be understood by those skilled in the art that certain well-known structures in the drawings and descriptions thereof may be omitted.
The same or similar reference numerals in the drawings of the embodiments of the present invention correspond to the same or similar components; in the description of the present invention, it should be understood that if the terms "upper", "lower", "left", "right", "inner", "outer", etc. are used for indicating the orientation or positional relationship based on the orientation or positional relationship shown in the drawings, it is only for convenience of description and simplification of description, but it is not indicated or implied that the referred device or element must have a specific orientation, be constructed in a specific orientation and be operated, and therefore, the terms describing the positional relationship in the drawings are only used for illustrative purposes and are not to be construed as limitations of the present patent, and the specific meanings of the terms may be understood by those skilled in the art according to specific situations.
In the description of the present invention, unless otherwise explicitly specified or limited, the term "connected" or the like, if appearing to indicate a connection relationship between the components, is to be understood broadly, for example, as being fixed or detachable or integral; can be mechanically or electrically connected; they may be directly connected or indirectly connected through intervening media, or may be connected through one or more other components or may be in an interactive relationship with one another. The specific meanings of the above terms in the present invention can be understood in specific cases to those skilled in the art.
The unit test case management method provided by the embodiment of the invention, as shown in fig. 1, includes:
s1, for unit test cases with variable types or list types of assertion data, performing assertion enhancement on unit test cases with different versions according to a corresponding assertion data enhancement method;
the unit test cases are automatically generated by the existing unit test case generation tool, the generation method comprises but is not limited to data construction, data recording and other modes, and the unit test cases act on the function level and test the function. An assertion is a logic of a first order in a program (e.g., a logic predicate whose result is true or false) and is intended to represent and verify the result expected by a software developer — when the program is executed to the position of the assertion, the corresponding assertion should be true, and if not, the program will terminate execution and give an error message. In short, test data is input into the test function, and the resulting function output is compared to the expected output, which is the assertion. For example, a unit test case a corresponds to the test function B, and in the unit test case a, when the input of the function B is "1", and the expected output is, for example, 20220309, the function B is executed and "1" is input, and it is determined whether the output is 20220309, and if not, it is determined that the assertion fails.
In this embodiment, the assertion data includes the actual output result and the expected output result of the test function after the unit test case of the current version is run, for example, for the input data "1", the expected output result of the test function B is 20220309, but the actual output result is 2022-03-09. The types of the assertion data are divided into a variable type and a group type, the variable type of assertion data refers to assertion data with a variable expression type of data, for example, for assertion data with two zero, two years, march and nine days, the variable type of assertion data can be represented by the data type 20220309, and can also be represented by the data type 2022-03-09, and the variable expression type of assertion data is defined as variable type of assertion data. The assertion data of the list type refers to data which is deserialized and output according to the sorting rule after the return value of the list type is deserialized. For example, for the assertion data of the list type [ "ab", "ef", "cd" ] is converted into [ "ab", "cd", "ef" ] through processing the data, and the conversion result is used for participating in assertion comparison, so that the condition that the contents of the list data are the same, but the orders are different, so that assertion failure is avoided.
In this embodiment, the method for enhancing variable-type assertion data is shown in fig. 2, and includes:
step A1, judging whether the unit test case assertion of the current version fails (the existing methods for judging whether the assertion fails are many, so the specific judgment mode is not described),
if yes, turning to the step A2;
if not, terminating the assertion enhancement flow;
step A2, performing regular matching on the assertion data and the rules in the rule base,
if the matching is successful, removing the format of the assertion data according to the matched rule and then switching to the step A3;
if the matching fails, the assertion enhancement flow is terminated;
in this embodiment, the rule base includes a basic rule base and a customized rule base, where the basic rule base includes a general expression rule of assertion data, such as a common date data expression rule, for example, an expression form that uniformly expresses a date as "20220309" or "2022-03-09". The custom rule base then allows for the expression of custom assertion data, such as "20220309" which can be expressed as a custom expression of "2022# #03# # 09".
An example of a method for performing rule matching between assertion data and a rule base and clearing a data format is as follows:
for example, the actual output of the test function B based on the input data "1" is 2022-03-09, the output assertion data "2022-03-09" is matched with the expression rule of the relevant date in the rule base, for example, the expression rule of the date in the rule base is "year, month and day with numerical value representation at non-interval", and then the assertion data "2022-03-09" output by the test function B is expressed as "20220309" after being cleared from the format according to the matched expression rule of the date.
Step A3, updating the assertion data with the removed format to a unit test case of a corresponding version;
step A4, operating the unit test case of the corresponding version after finishing the data updating, and judging whether the assertion is successful,
if yes, judging that the assertion is successfully enhanced and recording assertion enhancement success information;
if not, judging that the assertion enhancement fails and recording assertion enhancement failure information.
After assertion enhancement is performed on unit test cases of different versions, as shown in fig. 1, the unit test case management method provided by this embodiment is shifted to:
step S2, performing deduplication on the unit test cases of each version after assertion enhancement according to a preset case deduplication rule, where a specific deduplication method is shown in fig. 3 and includes:
step C1, operating unit test cases of all versions corresponding to the same test function to obtain a code path corresponding to the unit test case of each version; the operation refers to calling unit test cases to test a function, a path refers to a code path in the function after one unit test case is operated, one unit test case corresponds to one code path, for example, a test function B has 10 lines of codes, and after a certain unit test case A is operated, the 1 st, 3 rd and 9 th lines of codes in the function B are read, so that the code path corresponding to the test case A is the 1 st, 3 rd and 9 th lines of the function B;
step C2, judging whether the code paths of the unit test cases among different versions are the same,
if the code paths are the same, any one of the version unit test cases with the same code paths is reserved;
if not, the unit test cases of different versions are reserved.
For example, for versions A1 and A2, and for the code paths of A1 and A2 which are all the 1 st, 3 rd and 9 th lines of the function B, it is determined that the code paths of the versions A1 and A2 are the same, but if the code path of the version A2 is the 2 nd, 3 rd and 9 th lines of the function B, it is determined that the code paths of the versions A1 and A2 are different;
after the unit test cases of each version are deduplicated, as shown in fig. 1, the unit test case management method provided in this embodiment is shifted to:
and S3, detecting whether the code texts of the unit test cases among the different versions after the duplication removal exist in a manner of using a git merge code text merging technology (for example, for the unit test case A, two different versions A1 and A2 after the unit test case A is changed, if the 10 th line code of the A1 is c +2= d, and the 10 th line code of the A2 is c-2= d, judging that the code text conflict exists between the A1 and the A2, namely the conflict occurs when the A1 and the A2 are merged), acquiring a version list with the conflict, and then overlaying each test function in each version test case managed on the remote git to the unit test case of the current version managed on the local git to complete the merging case of each version test case.
Specifically, as shown in fig. 4, the method for merging the unit test cases of each version includes:
step D1, obtaining test function names corresponding to the unit test cases of each version managed on a local git (an existing code version management tool) and managed on a remote git, for example, the test function names corresponding to the A1 version of the unit test case managed on the local git are functions A, B and C, the test function names corresponding to the A2 version of the unit test case managed on the remote git are functions A, B, C and D, then forming each test function name corresponding to the A1 version managed on the local git into a first array, and forming each test function name corresponding to the A2 version managed on the remote git into a second array;
step D2, performing test function name matching on each second array and the first array,
if different test function names are matched, the step D3 is carried out, for example, the step D3 is carried out when the test function name D which does not exist in the first array corresponding to the A1 version exists in the second array corresponding to the A2 version;
if different test function names are not matched, filtering out a second number group currently participating in matching, for example, filtering out a second number group corresponding to the version A2 when the test function names corresponding to the version A1 and the version A2 are all A, B and C;
step D3, acquiring function code segments corresponding to the test functions with different names matched from the second array;
and D4, adding the obtained function code segments into the unit test cases of the A1 version managed on the local git.
In conclusion, the invention realizes the effective management of different versions of the same unit test case under the multi-person coding scene through the ways of assertion data enhancement, test case duplication removal and test function combination, and is favorable for improving the delivery quality and the delivery efficiency of the developed software.
In addition, the present invention further provides a unit test case management apparatus, which can implement the above unit test case management method, as shown in fig. 5, the apparatus includes:
the assertion enhancing module is used for carrying out assertion enhancement on unit test cases with variable types or array types according to corresponding assertion data enhancing methods;
the case duplication removing module is connected with the assertion enhancing module and used for removing duplication of the unit test cases of each version after assertion enhancement according to a preset case duplication removing rule;
and the case merging module is connected with the case deduplication module and used for detecting whether the code texts of the unit test cases among the deduplicated different versions have conflicts by using a git merge code text merging technology, acquiring a version list with conflicts, and then overlapping each test function in each version test case managed on the remote git to the unit test case of the current version managed on the local git to complete the merging of each version test case.
The present invention also provides a readable storage medium storing computer readable instructions which, when executed by a processor, cause the processor to perform the unit test case management method described above.
It should be understood that the above-described embodiments are merely preferred embodiments of the invention and the technical principles applied thereto. It will be understood by those skilled in the art that various modifications, equivalents, changes, and the like can be made to the present invention. However, such variations are within the scope of the invention as long as they do not depart from the spirit of the invention. In addition, certain terminology used in the description and claims of the present application is not limiting, but is used for convenience only.
Claims (5)
1. A method for managing unit test cases, comprising:
s1, for unit test cases with variable types of assertion data, performing assertion enhancement on the unit test cases with different versions according to a corresponding assertion data enhancement method;
s2, removing duplication of the unit test cases of each version after assertion enhancement according to a preset case duplication removing rule;
s3, detecting whether the code texts of the unit test cases among the different versions after the duplication removal have conflicts or not by using a git merge code text merging technology, acquiring a version list with conflicts, and then overlaying each test function in each version test case managed on a remote git to the unit test case of the current version managed on a local git to complete the merging of each version test case;
when the assertion data is of a variable type, in step S1, the method for performing assertion enhancement on the unit test cases of different versions includes:
step A1, judging whether the unit test case assertion of the current version fails,
if yes, the step A2 is carried out;
if not, terminating the assertion enhancing flow;
step A2, the assertion data is regularly matched with the rules in the rule base,
if the matching is successful, removing the format of the assertion data according to the matched rule, and then turning to the step A3;
if the matching fails, terminating the assertion enhancing flow;
step A3, updating the assertion data with the cleared format to the unit test case with the corresponding version;
step A4, operating the unit test case with the corresponding version after finishing the data updating, and judging whether the assertion is successful,
if so, judging that the assertion is successfully enhanced and recording the assertion enhancement success information;
if not, judging that the assertion is failed to be enhanced and recording assertion enhancement failure information;
in step S2, the method for removing duplicate of the unit test cases of different versions specifically includes:
step C1, operating the unit test cases of all versions corresponding to the same test function to obtain a code path corresponding to the unit test case of each version;
step C2, judging whether the code paths of the unit test cases among different versions are the same,
if the code paths are the same, any one of the version unit test cases with the same code paths is reserved;
if not, different versions of the unit test case are retained.
2. The unit test case management method of claim 1, wherein the assertion data comprises an actual output result and an expected output result of the test function after running the current version of the unit test case.
3. The unit test case management method according to claim 1, wherein in step S3, the method for merging the unit test cases of each version specifically comprises:
step D1, obtaining test function names corresponding to the unit test cases of each version managed on the local git and each version managed on the remote git, then forming each test function name corresponding to the A1 version of the unit test case managed on the local git into a first array, and forming each test function name corresponding to each A2 version of the unit test case managed on the remote git into a second array;
step D2, performing test function name matching on each second array and the first array,
if different test function names are matched, the step D3 is carried out;
if the different test function names are not matched, filtering out the second array currently participating in matching;
step D3, acquiring function code segments corresponding to the test functions with different names matched from the second array;
and D4, adding the acquired function code segments into the unit test cases of the A1 version managed on the local git.
4. A unit test case management apparatus for implementing the unit test case management method according to any one of claims 1 to 3, comprising:
the assertion enhancing module is used for carrying out assertion enhancement on unit test cases with variable types of assertion data according to corresponding assertion data enhancing methods;
the case duplication removing module is connected with the assertion enhancing module and used for removing duplication of the unit test cases of each version after assertion enhancement according to a preset case duplication removing rule;
and the case merging module is connected with the case deduplication module and used for detecting whether the code texts of the unit test cases among the deduplicated different versions have conflicts by using a git merge code text merging technology, acquiring a version list with the conflicts, and then overlapping each test function in each version test case managed on the remote git to the unit test case of the current version managed on the local git to complete merging of each version test case.
5. A readable storage medium having computer readable instructions stored thereon which, when executed by a processor, the processor performs the unit test case management method of any of claims 1-3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210534112.XA CN114741320B (en) | 2022-05-17 | 2022-05-17 | Unit test case management method and device and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210534112.XA CN114741320B (en) | 2022-05-17 | 2022-05-17 | Unit test case management method and device and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114741320A CN114741320A (en) | 2022-07-12 |
| CN114741320B true CN114741320B (en) | 2022-11-15 |
Family
ID=82284873
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210534112.XA Active CN114741320B (en) | 2022-05-17 | 2022-05-17 | Unit test case management method and device and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114741320B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111221566A (en) * | 2019-12-28 | 2020-06-02 | 华为技术有限公司 | Method and device for combining multiple and changeable versions of software code |
| CN113127357A (en) * | 2021-04-21 | 2021-07-16 | 北京百度网讯科技有限公司 | Unit testing method, device, equipment, storage medium and program product |
| CN113535563A (en) * | 2021-07-19 | 2021-10-22 | 上海复深蓝软件股份有限公司 | Test case duplication removing method and device, computer equipment and storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104461578B (en) * | 2014-12-26 | 2018-09-11 | 广州品唯软件有限公司 | The automatic merging method of code and system |
| CN108614770B (en) * | 2018-04-09 | 2021-08-27 | 中国工商银行股份有限公司 | Automatic test assertion method, device, storage medium and equipment |
-
2022
- 2022-05-17 CN CN202210534112.XA patent/CN114741320B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111221566A (en) * | 2019-12-28 | 2020-06-02 | 华为技术有限公司 | Method and device for combining multiple and changeable versions of software code |
| CN113127357A (en) * | 2021-04-21 | 2021-07-16 | 北京百度网讯科技有限公司 | Unit testing method, device, equipment, storage medium and program product |
| CN113535563A (en) * | 2021-07-19 | 2021-10-22 | 上海复深蓝软件股份有限公司 | Test case duplication removing method and device, computer equipment and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| "测试驱动javascript开发 -- 2.单元测试一例：学习断言、测试用例函数的编写";weixin_30883311;《https://blog.csdn.net/weixin_30883311/article/details/97931740》;20121101;第1-4页 * |
| "解决git冲突两种方案";小白白白白白白反正就是特别白;《https://blog.csdn.net/m0_474310109/article/details/124459861》;20220427;第1-4页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114741320A (en) | 2022-07-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9390176B2 (en) | System and method for recursively traversing the internet and other sources to identify, gather, curate, adjudicate, and qualify business identity and related data | |
| CN101425132B (en) | Image recognition apparatus, image recognition method, and storage medium recording image recognition program | |
| US20130259314A1 (en) | Methods and systems for enhancing the performance of automated license plate recognition applications utilizing multiple results | |
| CN109948710B (en) | Micro-service identification method based on API similarity | |
| CN110083623B (en) | Business rule generation method and device | |
| US20040158562A1 (en) | Data quality system | |
| CN110705214A (en) | Automatic coding method and device | |
| JP2019502979A (en) | Automatic interpretation of structured multi-field file layouts | |
| CN115167891B (en) | Data updating method, device and equipment of interface control file and storage medium | |
| US20050182666A1 (en) | Method and system for electronically routing and processing information | |
| CN112711578B (en) | Big data denoising method for cloud computing service and cloud computing financial server | |
| CN1619546A (en) | Label system-translation of text and multi-language support at runtime and design | |
| CN114741320B (en) | Unit test case management method and device and readable storage medium | |
| JP6247976B2 (en) | Rule management support device and rule management support method | |
| JP5227120B2 (en) | Character string recognition apparatus and method, and program | |
| JPH05159101A (en) | Device and method for recognizing logical structure and contents of document | |
| CN106557569B (en) | Method and device for importing unstructured document based on meta-model | |
| US20210342689A1 (en) | Computer-implemented method, and device for producing a knowledge graph | |
| CN114637692B (en) | Test data generation and test case management method | |
| CN112445461A (en) | Business rule generation method and device, electronic equipment and readable storage medium | |
| CN112989795A (en) | Text information extraction method and device, computer equipment and storage medium | |
| US10417488B2 (en) | Re-application of filters for processing receipts and invoices | |
| JP2003141447A (en) | Form retrieval system | |
| CN116450717B (en) | Data integration method and information management system for cross-service modules | |
| CN113033832B (en) | Method and device for inputting automobile repair data, terminal equipment and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |