CN116383056A - Quick positioning method, computer equipment and device for uncovered codes - Google Patents

Quick positioning method, computer equipment and device for uncovered codes Download PDF

Info

Publication number
CN116383056A
CN116383056A CN202310335289.1A CN202310335289A CN116383056A CN 116383056 A CN116383056 A CN 116383056A CN 202310335289 A CN202310335289 A CN 202310335289A CN 116383056 A CN116383056 A CN 116383056A
Authority
CN
China
Prior art keywords
file
class
code
item
files
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310335289.1A
Other languages
Chinese (zh)
Inventor
白雪枫
高超
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Bank Co Ltd
Original Assignee
Ping An Bank Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Ping An Bank Co Ltd filed Critical Ping An Bank Co Ltd
Priority to CN202310335289.1A priority Critical patent/CN116383056A/en
Publication of CN116383056A publication Critical patent/CN116383056A/en
Pending legal-status Critical Current

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/3676—Test management for coverage analysis
    • 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
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

The invention provides a quick positioning method for uncovered codes, computer equipment and a device, wherein the method comprises the following steps: extracting a source code file of an item from a code warehouse and storing the source code file into a local item file, wherein the local item file comprises a class file and a method file; searching service logic code files from the source code files, and storing the service logic code files into a first file list, wherein each service logic code file corresponds to a class; traversing the corresponding class in the first file list to obtain a member method name in the class, and storing the member method name in the second file list; judging whether the corresponding class in the first file list exists in a class file or not; if so, judging whether the member method names in the second file list exist in the method files or not; if yes, judging whether the member method carries an assertion statement; if the assertion statement is carried, it is determined that the corresponding code of the item has a complete unit test. The invention effectively improves the quality of submitted codes.

Description

Quick positioning method, computer equipment and device for uncovered codes
Technical Field
The present invention relates to the field of software development technologies, and in particular, to a method, a computer device, and an apparatus for quickly positioning an uncovered code.
Background
In the software development process, the quality of test codes submitted by developers is always concerned, and one of evaluation criteria is to check whether the submitted test codes are subjected to unit test, but many developers do not pay attention to code specification and unit test, and a series of problems, such as packaging and analysis failure, environment abnormality after deployment and the like, are caused after the code is submitted. Often, before code submission, a developer does not consider code quality issues for code writing convenience, and to avoid similar issues, the importance of code specifications and unit testing is usually announced to the developer. However, the method is not realized at the system level in a manual reminding mode at present, and the method is often ignored, has omission and affects the code development efficiency.
Disclosure of Invention
The invention provides a quick positioning method, computer equipment and a device for uncovered codes, which effectively reduce the error rate of submitted codes and improve the quality of submitted codes.
In a first aspect, an embodiment of the present invention provides a method for quickly locating an uncovered code, where the method includes: extracting a source code file of an item from a code warehouse, and storing the source code file of the item into a local item file, wherein the local item file comprises a unit test code file of the item, and the unit test code file comprises a class file and a method file and is used for verifying whether a corresponding code of the item is subjected to complete unit test; searching a service logic code file from the source code file, and storing the service logic code file into a first file list, wherein each service logic code file corresponds to a class, and each service logic code file takes a corresponding class name as a part of a file name; circularly traversing the corresponding class in the first file list to obtain a member method name in the class, and storing the member method name in a second file list; judging whether the corresponding class in the first file list exists in the class file or not; if the corresponding class in the first file list exists in the class file, judging whether a member method name in the second file list exists in the method file or not; if the member method names in the second file list exist in the method files, judging whether the member methods carry assertion sentences or not; if the member method carries an assertion statement, determining that the corresponding code of the item is subjected to complete unit test.
In a second aspect, an embodiment of the present invention provides a quick positioning device for an uncovered code, where the quick positioning device for an uncovered code includes an extracting unit, a searching unit, a traversing unit, a first judging unit, a second judging unit, a third judging unit, and a determining unit. The extraction unit is used for extracting a source code file of an item from the code warehouse and storing the source code file of the item into a local item file, wherein the local item file comprises a unit test code file of the item, and the unit test code file comprises a class file and a method file and is used for verifying whether the corresponding code of the item is subjected to complete unit test. And the searching unit is used for searching the service logic code files from the source code files and storing the service logic code files into a first file list, wherein each service logic code file corresponds to one class, and each service logic code file takes the corresponding class name as a part of the file name. And the traversing unit is used for circularly traversing the corresponding class in the first file list to obtain the member method name in the class, and storing the member method name into a second file list. And the first judging unit is used for judging whether the class corresponding to the first file list exists in the class file. And the second judging unit is used for judging whether the member method names in the second file list exist in the method files or not if the corresponding classes in the first file list exist in the class files. And the third judging unit is used for judging whether the member method carries an assertion statement or not if the member method name in the second file list exists in the method file. And the determining unit is used for determining that the corresponding code of the item is subjected to complete unit test if the member method carries an assertion statement.
In a third aspect, an embodiment of the present invention provides a computer device including a memory and a processor. A memory for storing a computer executable program, a processor for executing the computer executable program to implement the method for rapid location of uncovered code as described above.
In a fourth aspect, an embodiment of the present invention provides a computer readable storage medium, where computer executable instructions are stored, where the computer executable instructions are executed by a processor to implement a method for quickly locating uncovered codes as described above.
In the above embodiment, the file names of the corresponding codes in the source code file extracted from the code repository and the file names of the verification files in the local project are compared one by one, whether the source code of the project has the unit test is judged, and further, whether the code of the project has the complete unit test is further judged by the corresponding code content in the code file.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to the structures shown in these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flowchart of a method for quickly locating an uncovered code according to an embodiment of the present invention.
Fig. 2 is a schematic diagram of a first sub-flowchart of a quick positioning method for uncovered codes according to an embodiment of the present invention.
Fig. 3 is a schematic diagram of a quick positioning device module for uncovered codes according to an embodiment of the present invention.
Fig. 4 is a schematic diagram of a first judging unit module in a quick positioning device module for uncovered codes according to an embodiment of the present invention.
Fig. 5 is a schematic diagram of an internal structure of a computer device according to an embodiment of the present invention.
The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Detailed Description
The present invention will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present invention more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The terms "first," "second," "third," "fourth" and the like in the description and in the claims of this application and in the above-described figures, if any, are used for distinguishing between similar elements of a plan and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged under appropriate circumstances, or in other words, the described embodiments may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, may also include other items, such as processes, methods, systems, articles, or apparatus that include a series of steps or elements, are not necessarily limited to only those steps or elements explicitly listed, but may include other steps or elements not explicitly listed or inherent to such processes, methods, articles, or apparatus.
It should be noted that the description of "first", "second", etc. in this disclosure is for descriptive purposes only and is not to be construed as indicating or implying a relative importance or implying an indication of the number of technical features being indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature. In addition, the technical solutions of the embodiments may be combined with each other, but it is necessary to base that the technical solutions can be realized by those skilled in the art, and when the technical solutions are contradictory or cannot be realized, the combination of the technical solutions should be considered to be absent and not within the scope of protection claimed in the present invention.
Please refer to fig. 1, which is a flowchart of a method for quickly locating an uncovered code according to an embodiment of the present invention, wherein the method for quickly locating an uncovered code includes the following steps:
step S101, extracting a source code file of an item from a code warehouse, and storing the source code file of the item into a local item file, wherein the local item file comprises a unit test code file of the item, and the unit test code file comprises a class file and a method file and is used for verifying whether a corresponding code of the item is subjected to complete unit test.
In particular, the code repository is a collection of source code for an application, software component, or software system, which may be stored in different types of source code repositories for executing, running, or implementing a complete manually written source code file for an application or software solution. Typically, a developer or tester will clone the code in the code repository locally during the software development process, and submit the code to the remote code repository after local modification and testing, and it is understood that the code repository may be, but is not limited to, a Git repository, which is an open-source distributed version control system for agilely and efficiently handling any larger or smaller items. In this embodiment, the local project file is a test file of the project, includes a unit test code file of the project, and specifically includes a class file and a method file, where the class file and the method file are preset and are necessary files for verifying whether a source code of the project has been subjected to a unit test, where the class file and the method file include multiple class names and method names of the project, further, the class file name uses a class name corresponding to the file as a part of the file name, and the method file uses a method name corresponding to the file as a part of the file name of the file, for example, the class file name is named: the ProducServiceTest, method file name testProducSearch.
In this embodiment, the project source code file obtained from the code repository is the entire project file of the project, including several code files and configuration files implementing the project. In the project development stage, the codes developed by the developers are uploaded to a code warehouse, so that the testers are required to evaluate the uploaded codes, one of the evaluation standards is to judge whether the uploaded codes are subjected to unit test or not, and a series of problems caused by that the unit test is not performed on the source codes in the subsequent code submitting step are avoided. In this embodiment, the tester extracts the source code file of the item from the code repository to the local file, and the local test code file constitutes the test code file of the item.
Step S102, searching a service logic code file from the source code file, and storing the service logic code file into a first file list, wherein each service logic code file corresponds to a class, and each service logic code file takes a corresponding class name as a part of a file name.
Specifically, in step S101, the service logic code files are screened separately according to the screening of the code files in the source code files after the source code files of the project are pulled into the local project files. The Service logic code file is a file with a processing logic code, the file is a code file for realizing the core function of a project, and the file is also a code file which must be subjected to unit test.
For example, there is a corresponding code @ Service public class ProductService in the service logic code file, where the class of public authority is a product service, so the class name corresponding to the service logic code file is a product service, and the service logic code file is a product service.
Step S103, traversing the corresponding class in the first file list circularly to obtain the member method name in the class, and storing the member method name in a second file list.
Specifically, according to the step S102, there are a plurality of service logic code files in the first file list, and each service logic code file has a corresponding class in its code content, the classes in the first file list are sequentially searched, and the member method names of the classes are extracted at the same time.
Step S104, judging whether the corresponding class in the first file list exists in the class file.
Specifically, the class files include a plurality of class file lists that need to be subjected to unit test, the class file lists are named with corresponding class names, the corresponding class names in the service logic code files extracted from the code warehouse are matched with the corresponding class names in the class files, if the class names of the service logic files in the first file list are in the corresponding class names of the class files, the class is subjected to the unit test, and further, if the class names of the service logic files in the first file list are not in the corresponding class names of the class files, the class names of the service logic files in the first file list are extracted, and the extracted class names are sent to developers or development responsible persons.
Step S105, if the class corresponding to the first file list exists in the class file, determining whether a member method name in the second file list exists in the method file.
Specifically, if the file class name in the first file list exists in the corresponding class name of the class file, further judging whether the member method name in the second file list is in the method file, wherein the member method name in the method file is named by the corresponding member method name, and if so, the member method name in the second file is judged to be in the method file by comparing the member method name in the second file with the method name in the method file, and if not, the member method is judged to be not in the method file, and if so, the member method is not subjected to the unit test, and at the moment, the corresponding method name is extracted to inform a developer or a development responsible person.
And step S106, if the member method names in the second file list exist in the method files, judging whether the member methods carry assertion sentences or not.
Specifically, if the member method name in the second file list exists in the method file, it is further determined whether the method carries an assertion statement, and it is understood that the assertion (assertion) is a first-order logic (e.g., a logic judgment formula with a true or false result) placed in the program, so as to mark and verify the expected result of the program developer, and when the program runs to the position of the assertion, the corresponding assertion should be true. If the assertion is not true, the program will cease to run and give an error message.
For example, it may be determined from the following code that the BaseSARTest method has an assertion statement stored:
public class ProductConfigTest extends BaseSARTest{
@Test
public void testMaxProducts(){
List<String>maxHuaProducts＝productConfig.maxHuaProducts()；
Assert.assertTrue(CollectionUtils.isNotEmpty(maxHuaProducts))；
}
}
step S107, if the member method carries an assertion statement, determining that the corresponding code of the item has been subjected to complete unit test.
Specifically, if the member method does not carry an assertion sentence, it is indicated that the unit test of the member method does not meet the standard, and at this time, the unit test which does not meet the standard is sent to a developer or a development responsible person, so that the developer or the development responsible person further processes the code. If the method includes an asserted method in step S106, it is indicated that the corresponding code of the item has been subjected to a complete unit test.
In the above embodiment, the source code file of the project is downloaded from the code repository to the local project file, where the local project file includes a verification file for performing unit test on the project, including a class file and a method file, the service logic code file is first screened from the source code file, where the file is a file with a logic code and is a file that needs to be subjected to unit test, each service logic code file corresponds to a class, a class name of the class is used as a part of the service logic code file name, a member method name included in the class is obtained by analyzing the class in the service logic code file, the corresponding class name of the service logic code file and the corresponding class name in the class file are compared, if the comparison is consistent, the class is subjected to unit test, then it is determined whether the member method is subjected to unit test, if the member method name is in the method file, it is further determined whether the member method is subjected to unit test, if the member method is including an assertion statement, it is indicated that the member method is subjected to complete unit test, otherwise, the member method is not in line with the unit test and the unit test is not in line with the complete unit test, and the test unit test is not in line with the standard of the unit test is sent to the developer.
In the embodiment, the file names of the corresponding codes in the source code file extracted from the code warehouse and the file names of the verification files in the local project are compared one by one, whether the source code of the project code is subjected to the unit test is judged, further, whether the code of the project is subjected to the complete unit test is judged by judging the corresponding code content in the code file, a series of problems caused by the fact that the submitted project code is not subjected to the unit test are effectively avoided, and the submitting quality of the code is greatly improved.
Fig. 2 is a schematic diagram of a first sub-flowchart of a method for quickly locating uncovered codes according to an embodiment of the invention. The sub-process specifically comprises the following steps:
step S201, matching class names in the file names in the first file list with file class names in the class file list one by one.
Step S202, if the class names are matched and consistent, judging that the corresponding class in the first file list exists in the class file.
Specifically, the first file list is stored in the unit test directory, and is compared with the class file names in the unit test code files, because the file names in the first file list are named by the corresponding class names and the class file names in the unit test code files are named by the class names, whether the class is in the class files or not can be known by comparing the file names in the first file list with the file names in the class files, and further whether the class is subjected to unit test is judged.
In the above embodiment, whether the class exists in the class file is judged by comparing the class names in the two files, so that whether the class is subjected to the unit test is rapidly verified.
Referring to fig. 3, a schematic diagram of a quick positioning device module for an uncovered code according to an embodiment of the invention is shown, where the quick positioning device 100 for an uncovered code includes: the extraction unit 101, the search unit 102, the traversal unit 103, the first judgment unit 104, the second judgment unit 105, the third judgment unit 106, and the determination unit 107.
An extracting unit 101, configured to extract a source code file of an item from a code repository, and store the source code file to a local item file, where the local item file includes a unit test code file of the item, and the unit test code file includes a class file and a method file, and is configured to verify whether a corresponding code of the item has been subjected to a complete unit test.
And a searching unit 102, configured to search the service logic code files from the source code files, and store the service logic code files in a first file list, where each service logic code file corresponds to a class, and each service logic code file uses a corresponding class name as a part of the file name.
And a traversing unit 103, configured to circularly traverse the corresponding class in the first file list to obtain a member method name in the class, and store the member method name in the second file list.
A first determining unit 104, configured to determine whether a class corresponding to the first file list exists in the class file.
And a second judging unit 105, configured to judge whether a member method name in the second file list exists in the method file if a corresponding class in the first file list exists in the class file.
And a third judging unit 106, configured to judge whether the member method carries an assertion statement if the member method name in the second file list exists in the method file.
And the determining unit 107 is configured to determine that the corresponding code of the item has been subjected to a complete unit test if the member method carries an assertion statement.
Referring to fig. 4, which is a schematic block diagram of a first judging unit in the quick positioning device module for uncovered codes according to the embodiment of the present invention, the first judging unit 104 further includes: a matching unit 1041 and a determination unit 1042.
And a matching unit 1041, configured to match class names in the plurality of file names in the first file list with file class names in the class file list one by one.
And a determining unit 1042, configured to determine that the corresponding class in the first file list exists in the class file if the class names match.
It can be understood by those skilled in the art that, for convenience and brevity of description, the quick positioning device for uncovered codes according to the present embodiment may refer to the corresponding procedure of the quick positioning method for uncovered codes described in the foregoing embodiment, and will not be described herein.
Fig. 5 is a schematic diagram of an internal structure of a computer device according to an embodiment of the invention. The computer device 30 specifically includes a memory 302 and a processor 301. The memory 302 is used for storing program instructions and the processor 301 is used for executing the program instructions to implement the above-described method for fast locating uncovered code.
The processor 301 may be, in some embodiments, a central processing unit (Central Processing Unit, CPU), controller, microcontroller, microprocessor or other data processing chip for executing program instructions stored in the memory 302.
Memory 302 includes at least one type of readable storage medium including flash memory, hard disk, multimedia card, card memory (e.g., SD or DX memory, etc.), magnetic memory, magnetic disk, optical disk, etc. Memory 302 may be an internal storage unit of a computer device, such as a hard disk of a computer device, in some embodiments. The memory 302 may also be an external storage device of the computer device in other embodiments, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), etc. that are provided on the computer device. Further, the memory 302 may also include both internal storage units and external storage devices of the computer device. The memory 302 may be used not only for storing application software installed in a computer device and various types of data, such as codes implementing a quick positioning method of uncovered codes, but also for temporarily storing data that has been output or is to be output.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, if and when such modifications and variations of the present invention fall within the scope of the claims and the equivalents thereof, the present invention is intended to encompass such modifications and variations.
The above list of preferred embodiments of the present invention is, of course, not intended to limit the scope of the invention, and equivalent variations according to the claims of the present invention are therefore included in the scope of the present invention.

Claims (10)

1. A method for quickly locating an uncovered code, the method comprising:
extracting a source code file of an item from a code warehouse, and storing the source code file of the item into a local item file, wherein the local item file comprises a unit test code file of the item, and the unit test code file comprises a class file and a method file and is used for verifying whether a corresponding code of the item is subjected to complete unit test;
searching a service logic code file from the source code file, and storing the service logic code file into a first file list, wherein each service logic code file corresponds to a class, and each service logic code file takes a corresponding class name as a part of a file name;
circularly traversing the corresponding class in the first file list to obtain a member method name in the class, and storing the member method name in a second file list;
judging whether the corresponding class in the first file list exists in the class file or not;
if the corresponding class in the first file list exists in the class file, judging whether a member method name in the second file list exists in the method file or not;
if the member method names in the second file list exist in the method files, judging whether the member methods carry assertion sentences or not;
if the member method carries an assertion statement, determining that the corresponding code of the item is subjected to complete unit test.
2. The method for quickly locating uncovered codes according to claim 1, wherein the business logic code files are java-suffixed files, and annotation @ Service is stored in the corresponding code of each business logic code file.
3. The method for quickly locating an uncovered code according to claim 1, wherein the class files and method files include a plurality of corresponding class file lists and method file lists, the class file lists and method file lists are named by corresponding class names and method names, and the determining whether the class files exist in the corresponding class in the first file list specifically includes:
matching class names in a plurality of file names in the first file list with file class names in a class file list one by one;
and if the class names are matched and consistent, judging that the corresponding class in the first file list exists in the class file.
4. The method for quickly locating uncovered codes according to claim 1, wherein said determining whether the class file exists in the class corresponding to the first file list further comprises:
and if the corresponding class in the first file list does not exist in the class file, extracting the class name and notifying a developer.
5. The method for quickly locating an uncovered code according to claim 1, wherein the determining whether the member method name in the second file list exists in the method file further comprises:
and if the member method names in the second file list do not exist in the method files, extracting the member method names and notifying a developer.
6. The method for quickly locating uncovered code according to claim 1, wherein determining whether the member method carries an assertion statement further comprises:
if the member method does not carry an assertion statement, judging that the unit test of the corresponding code of the project does not accord with the standard;
and extracting the codes which do not meet the unit test standard, and notifying a developer.
7. A quick positioning device for uncovered codes, wherein the quick positioning device for uncovered codes comprises:
the extraction unit is used for extracting a source code file of an item from a code warehouse and storing the source code file of the item into a local item file, wherein the local item file comprises a unit test code file of the item, and the unit test code file comprises a class file and a method file and is used for verifying whether a corresponding code of the item is subjected to complete unit test;
the searching unit is used for searching the service logic code files from the source code files and storing the service logic code files into a first file list, wherein each service logic code file corresponds to one class, and each service logic code file takes the corresponding class name as a part of the file name;
the traversing unit is used for circularly traversing the corresponding class in the first file list to obtain a member method name in the class, and storing the member method name into a second file list;
a first judging unit, configured to judge whether a class corresponding to the first file list exists in the class file;
the second judging unit is used for judging whether the member method names in the second file list exist in the method files or not if the corresponding classes in the first file list exist in the class files;
a third judging unit, configured to judge whether the member method carries an assertion statement if a member method name in the second file list exists in the method file;
and the determining unit is used for determining that the corresponding code of the item is subjected to complete unit test if the member method carries an assertion statement.
8. The quick positioning device of uncovered codes as set forth in claim 7, wherein said first judgment unit further includes:
the matching unit is used for matching the class names in the file names in the first file list with the file class names in the class file list one by one;
and the judging unit is used for judging that the corresponding class in the first file list exists in the class file if the class names are matched and consistent.
9. A computer device, comprising:
a memory for storing a computer executable program,
a processor for executing the computer executable program to implement the method of fast locating uncovered code according to any of claims 1-6.
10. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to implement a method for fast locating uncovered code according to any of claims 1-6.
CN202310335289.1A 2023-03-29 2023-03-29 Quick positioning method, computer equipment and device for uncovered codes Pending CN116383056A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310335289.1A CN116383056A (en) 2023-03-29 2023-03-29 Quick positioning method, computer equipment and device for uncovered codes

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310335289.1A CN116383056A (en) 2023-03-29 2023-03-29 Quick positioning method, computer equipment and device for uncovered codes

Publications (1)

Publication Number Publication Date
CN116383056A true CN116383056A (en) 2023-07-04

Family

ID=86978227

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310335289.1A Pending CN116383056A (en) 2023-03-29 2023-03-29 Quick positioning method, computer equipment and device for uncovered codes

Country Status (1)

Country Link
CN (1) CN116383056A (en)

Similar Documents

Publication Publication Date Title
US7080357B2 (en) Software package verification
CN107678936B (en) Business system pre-inspection method, server and computer readable storage medium
US20140033174A1 (en) Software bug predicting
US11599453B2 (en) Vehicle function test apparatus and method of controlling the same
CN109446753A (en) Detect method, apparatus, computer equipment and the storage medium of pirate application program
CN110866258A (en) Method for quickly positioning bug, electronic device and storage medium
CN116245074A (en) Chip verification method, device and storage medium
CN107632909B (en) Method and system for automatically testing device functions
Blasi et al. Replicomment: identifying clones in code comments
US20120310849A1 (en) System and method for validating design of an electronic product
CN113312258A (en) Interface testing method, device, equipment and storage medium
CN116383056A (en) Quick positioning method, computer equipment and device for uncovered codes
CN112069073A (en) Test case management method, terminal and storage medium
CN113934617A (en) Data processing method, device, equipment and storage medium
CN116245076A (en) Automatic construction method of DRC test version gallery, DRC method, DRC system and readable storage medium
CN110688823A (en) XML file verification method and device
US6681347B1 (en) Method for testing keyboard complied with language code
CN112819565B (en) Method, system and storage medium for detecting buoy string
CN112631852B (en) Macro checking method, macro checking device, electronic equipment and computer readable storage medium
WO2021135369A1 (en) Sample processing method and apparatus
CN110442370B (en) Test case query method and device
CN101295314A (en) File management system, file management method, support device thereof, and program thereof
CN113434139A (en) Image packaging processing method and device, server and storage medium
CN110008108B (en) Regression range determining method, device, equipment and computer readable storage medium
CN113672512A (en) Code inspection rule generating method, code inspection method, device and 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