WO2013174200A1 - 代码分析方法及代码分析系统、计算机存储介质 - Google Patents
代码分析方法及代码分析系统、计算机存储介质 Download PDFInfo
- Publication number
- WO2013174200A1 WO2013174200A1 PCT/CN2013/075095 CN2013075095W WO2013174200A1 WO 2013174200 A1 WO2013174200 A1 WO 2013174200A1 CN 2013075095 W CN2013075095 W CN 2013075095W WO 2013174200 A1 WO2013174200 A1 WO 2013174200A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- code
- analysis
- code analysis
- change list
- execution plan
- Prior art date
Links
- 238000004458 analytical method Methods 0.000 title claims abstract description 296
- 230000008859 change Effects 0.000 claims abstract description 117
- 238000013507 mapping Methods 0.000 claims abstract description 53
- 238000000034 method Methods 0.000 claims abstract description 41
- 230000008569 process Effects 0.000 claims description 32
- 238000001514 detection method Methods 0.000 claims description 6
- 230000010354 integration Effects 0.000 abstract description 4
- 230000008901 benefit Effects 0.000 description 7
- 238000000926 separation method Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 238000004590 computer program Methods 0.000 description 1
- 238000000354 decomposition reaction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3604—Software analysis for verifying properties of programs
- G06F11/3608—Software analysis for verifying properties of programs using formal methods, e.g. model checking, abstract interpretation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/75—Structural analysis for program understanding
-
- 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/3604—Software analysis for verifying properties of programs
Definitions
- the present invention relates to the field of code analysis technology, and in particular, to a code analysis method, a code analysis system, and a computer storage medium shield. Background technique
- a code analysis tool is a tool that analyzes the original code or compiled code and obtains an evaluation report without the need to execute code, aiming at finding the programming flaws of the original code, such as normativeness, logic, and security.
- the code analysis tool typically analyzes the code stored in the software configuration management library and outputs the results according to the established analysis rules.
- an object of the present invention is to provide a code analysis method
- another object of the present invention is to provide a code analysis device that can implement code analysis requirements of different types of programming languages and reduce development. The workload of personnel and testers improves the efficiency of code analysis.
- a code analysis method including steps: Get a list of code changes;
- a code analysis system including:
- a change detection unit configured to obtain a code change list
- a code pre-analysis unit configured to analyze the code change list, obtain a change list corresponding to each programming language type in the code change list, and determine a mapping relationship between the change list and a corresponding programming language type;
- An execution unit configured to acquire corresponding code analysis tool information and analysis rule information according to the mapping relationship, generate an execution plan, and execute a code analysis process by using a corresponding code analysis tool and an analysis rule according to the execution plan to obtain a code analysis result.
- One or more computer storage shields comprising computer executable instructions for performing a method of code analysis, the method comprising the steps of:
- the code change list is obtained, and the code change list is analyzed, and the change list corresponding to each programming language type in the code change list is obtained, and the mapping relationship between the change list and the corresponding programming language type is determined. And based on the mapping relationship, the matching code analysis tool and the analysis rule execution analysis process are obtained, and the analysis result is obtained, which realizes the integration of various code analysis tools and analysis rules, and can well adapt to the code of different types of programming languages. Analyze the requirements, reduce the workload of R & D personnel, testers, and improve the efficiency of code analysis.
- Embodiment 1 is a schematic flow chart of Embodiment 1 of a code analysis method according to the present invention
- Embodiment 2 is a schematic flow chart of Embodiment 2 of the code analysis method of the present invention.
- 3 is a schematic structural diagram of an embodiment of a code analysis system of the present invention
- 4 is a schematic block diagram of an operating environment in which the present invention may be implemented. detailed description
- FIG. 1 it is a schematic flowchart of the first embodiment of the code analysis method of the present invention. As shown in FIG. 1 , the code analysis method in the first embodiment includes the following steps:
- Step S101 obtaining a code change list, proceeds to step S102;
- Step S102 analyzing the code change list, obtaining a change list corresponding to each programming language type in the code change list, determining a mapping relationship between the change list and the corresponding programming language type, and proceeding to step S103;
- Step S 103 Obtain corresponding code analysis tool information and analysis rule information according to each mapping relationship, generate an execution plan, and proceed to step S104;
- Step S104 Perform a code analysis process by calling a corresponding code analysis tool and an analysis rule according to the execution plan to obtain a code analysis result.
- the code change list is obtained, and the code change list is analyzed, and the change list corresponding to each programming language type in the code change list is obtained, and the mapping relationship between the change list and the corresponding programming language type is determined. And based on the mapping relationship, the matching code analysis tool and the analysis rule execution analysis process are obtained, and the analysis result is obtained, which realizes the integration of various code analysis tools and analysis rules, and can well adapt to the code of different types of programming languages. Analyze the requirements, reduce the workload of R & D personnel, testers, and improve the efficiency of code analysis.
- the code change list may be obtained by setting different trigger conditions based on different application scenarios or consideration factors, wherein one way is to preset the scan frequency, and according to The preset scan frequency scans each code software configuration management library to obtain the above code change list.
- the code analysis instruction may be input by inputting code when the code analysis is required (for example, by clicking a button of a start code analysis process) Etc.) After receiving the code analysis command, scan each code software configuration management library to obtain the above code change list.
- the first mode described above can be used, thereby automatically detecting the status in the code software configuration management library, automatically triggering the execution of the code analysis process, and further reducing the workload of the developer, the tester, and the like. .
- Each of the above-mentioned code software configuration management libraries may be set according to actual needs, and may be one or more than two, and details are not described herein.
- the code change list is acquired in the above step S101, if the code is not changed, the subsequent steps are not entered, and if there is a change, the pre-analysis process of the subsequent step S102 is entered.
- the code change list since the code change list is extracted from different code software configuration management libraries, and the storage format of each code software configuration management library may not be the same, directly entering the subsequent processing may affect the efficiency of subsequent generation of the execution plan. Therefore, in the solution of the present invention, the code change list obtained above may be stored in the first preset format type to facilitate the reference of step S102.
- the first preset format type here can use various possible formats, as long as it can conform to the description manner expressed by the information structure, because the xml file format type is open, single, self-descriptive, structure and content.
- the advantages of separation, extensibility, and the like are independent of the platform. Therefore, in general, the first preset format type can be set to the xml format type.
- step S102 the code change list is analyzed, and when the mapping relationship is determined, the mapping relationship is determined according to different programming language types. For example, it is assumed that there are two programming language types in the code change list (C++, Java), then after the pre-analysis process of step S102, the mapping relationship between the C++ and the C++-encoded code change list and the change list of the java and the java-encoded code are obtained. Mapping relationship. After obtaining the mapping relationship between each programming language type and the corresponding change list, you can directly enter the subsequent process of generating the execution plan.
- each of the above mapping relationships may be converted into a second preset format type and then stored.
- the subsequent execution plan can be generated based on the same format regardless of the change list of the original format type.
- the second preset format type may be in various possible formats, as long as the description manner expressed by the information structure can be met, and the second preset format type may be the same as the first preset format type, or Not the same. Since the xml file format type has the advantages of openness, singleness, self-descriptiveness, separation of structure and content, strong extensibility, and platform-independent, in general, the second preset format type can be set to The xml format type.
- the corresponding code analysis tool information and the analysis rule information can be obtained, and an execution plan is generated, and the process can be performed in the background.
- the correspondence between each programming language type, the code analysis tool, and the analysis rule needs to be pre-stored.
- the execution plan is generated, the corresponding language relationship may be obtained according to the corresponding relationship.
- the code list needs to use which code analysis tool, which analysis rule to use for code analysis, and the information of the code analysis tool and the analysis rule information to generate the execution plan.
- the generated execution schemes may be stored in a third preset format type, so as to be executed based on an execution scheme of the same format type when performing analysis according to the execution scheme, so as to reduce the complexity of executing the execution scheme, and further improve effectiveness.
- the third preset format type may be in various possible formats, as long as the description manner expressed by the information structure can be met, and the third preset format type and the first preset format type and the second pre-predetermined The format types can be the same or different. Since the xml file format type has the advantages of openness, singleness, self-descriptiveness, separation of structure and content, and strong extensibility, and is platform-independent, in general, the third preset format type can be set to The xml format type.
- each of the generated execution schemes may be stored in a task queue manner, so that the code analysis process can be performed by discovering whether there is an execution scheme in the task queue.
- the corresponding code analysis tool and the analysis rule are called to execute the code analysis process, and the code analysis result is obtained, and the obtained code analysis result can be output and displayed for the user to view, on the other hand, the obtained code.
- the analysis result can also be saved in the analysis result library, and can be outputted at the same time or via the analysis result library, and the display mode can adopt various possible forms, for example, display by WEB interface and the like.
- FIG. 2 is a schematic flowchart of the second embodiment of the code analysis method of the present invention.
- the difference from the first embodiment is mainly that the embodiment obtains each mapping relationship and also generates The identifier bit corresponding to each mapping relationship acquires corresponding code analysis tool information and analysis rule information according to the identifier bit, and generates an execution plan.
- the code analysis method in the second embodiment includes the following steps:
- Step S201 Obtain a code change list, and proceed to step S202;
- Step S202 analyzing the code change list, obtaining a change list corresponding to each programming language type in the code change list, determining a mapping relationship between the change list and a corresponding programming language type, and generating a corresponding code analysis tool
- the information bit corresponding to the information and the analysis rule information proceeds to step S203;
- Step S203 Acquire corresponding code analysis tool information and analysis rule information according to each of the above identifiers, generate an execution plan, and proceed to step S204;
- Step S204 Perform a code analysis process by calling a corresponding code analysis tool and an analysis rule according to the execution plan to obtain a code analysis result.
- the foregoing identification bit may be generated according to a programming language type, a file type, an external user setting, etc., and the identification bit indicates, indicates or represents which type of feature file should use which code analysis tool, which analysis rule To carry out the code analysis process, the specific setting manner of the flag bit can be set according to actual needs, and will not be described here.
- Other technical features in the second embodiment are the same as those in the first embodiment, and are not described herein.
- the present invention also provides a code analysis system
- Fig. 3 is a block diagram showing the structure of the code analysis system embodiment of the present invention.
- the code analysis system in this embodiment includes:
- a change detecting unit 301 configured to obtain a code change list
- the code pre-analysis unit 302 is configured to analyze the code change list, obtain a change list corresponding to each programming language type in the code change list, and determine a mapping relationship between the change list and a corresponding programming language type;
- the unit 303 is configured to obtain corresponding code analysis tool information and analysis rule information according to each mapping relationship, generate an execution plan, and execute a code analysis process by using a corresponding code analysis tool and an analysis rule execution code analysis process according to the execution plan to obtain a code analysis result.
- the foregoing analysis execution unit 303 may specifically include:
- the execution plan generating unit 3031 is configured to obtain corresponding code analysis tool information and analysis rule information according to each mapping relationship, and generate an execution plan.
- the task execution unit 3032 is configured to execute a code analysis process according to each execution plan by calling a corresponding code analysis tool and an analysis rule to obtain a code analysis result.
- the code change list is acquired by the change detecting unit 301, and the code change list 302 analyzes the code change list to obtain a change list corresponding to each programming language type in the code change list, and determines the change list.
- a mapping relationship with a corresponding programming language type and the analysis execution unit 303 generates an execution plan based on the mapping relationship and calls an adapted code analysis tool and an analysis rule to perform an analysis process, and obtains an analysis result, which implements multiple code analysis.
- the integration of tools and analysis rules can adapt to the code analysis requirements of different types of programming languages, reducing the workload of developers and testers, and improving the efficiency of code analysis.
- the code change list may be obtained by setting different trigger conditions based on different application scenarios or consideration factors, wherein one way is to preset the scan frequency, and according to The preset scan frequency scans each code software configuration management library to obtain the above code change list.
- the code analysis instruction may be input by inputting code when the code analysis is required (for example, by clicking a button of a start code analysis process) Etc.) After receiving the code analysis command, scan each code software configuration management library to obtain the above code change list.
- the first mode described above can be used, thereby automatically detecting the status in the code software configuration management library, automatically triggering the execution of the code analysis process, and further reducing the workload of the developer, the tester, and the like. .
- Each of the above code software configuration management libraries can be set according to actual needs, and can be one or two. The above plurality will not be described here.
- the code change list acquired by the change detecting unit 301 is extracted from different code software configuration management libraries, and the storage format of each code software configuration management library may not be the same, directly entering the subsequent processing may affect subsequent generation execution. The efficiency of the program. Therefore, in the solution of the present invention, the code change list obtained by the change detecting unit 301 can be stored in the first preset format type to facilitate the application of the code pre-analysis unit 302.
- the first preset format type here can use various possible formats, as long as it can conform to the description manner expressed by the information structure, because the xml file format type is open, single, self-descriptive, structure and content.
- the advantages of separation, extensibility, and the like are independent of the platform. Therefore, in general, the first preset format type can be set to the xml format type.
- the code pre-analysis unit 302 determines the mapping relationship when determining the mapping relationship, and the mapping relationship is determined by different programming language types. For example, it is assumed that there are two programming language types in the code change list ( C++, java), then after the pre-analysis process, you will get the mapping relationship between C++ and the change list changed in C++ code, and the change list of java and java coded code. Mapping relations.
- the storage format of each code software configuration management library may not be the same, resulting in a mapping relationship between each programming language type and the change list.
- the format types are also different. Especially in the case of a large number of programming language types, direct entry into subsequent processing may affect the efficiency of subsequent generation of execution schemes. Therefore, in the solution of the present invention, the code pre-analysis unit 302 can also store the above mapping relationships into the second preset format type. Thus, when the execution plan is subsequently generated, the subsequent execution plan can be generated based on the same format regardless of the change list of the original format type.
- the second preset format type may use various possible formats, as long as the description manner expressed by the information structure can be met, and the second preset format type may be the same as the first preset format type, and may also be Not the same. Since the xml file format type has the advantages of openness, singleness, self-descriptiveness, separation of structure and content, strong extensibility, and platform-independent, in general, the second preset format type can be set to The xml format type.
- the analysis execution unit 303 can obtain corresponding code analysis tool information and analysis rule information based on the mapping relationship, and generate an execution plan, which can be performed in the background.
- the implementation of the solution of the present invention needs to pre-store the correspondence between each programming language type, the code analysis tool, and the analysis rule. Therefore, as shown in FIG. 3, in the solution of the present invention, :
- the information database 304 is configured to store the code analysis tool, the analysis rule, and the code analysis tool, and the correspondence between the analysis rule and each programming language type.
- the change list for the programming language type may be obtained according to the correspondence relationship. Which code analysis tool is used, which analysis rule is used for code analysis, and the information of the code analysis tool and the analysis rule information are generated according to the need to generate an execution plan.
- the generated execution schemes may be stored in a third preset format type, so as to be executed based on an execution scheme of the same format type when performing analysis according to the execution scheme, so as to reduce the complexity of executing the execution scheme, and further improve effectiveness.
- the third preset format type may be in various possible formats, as long as the description manner expressed by the information structure can be met, and the third preset format type and the first preset format type and the second pre-predetermined The format types can be the same or different. Since the xml file format type has the advantages of openness, singleness, self-descriptiveness, separation of structure and content, and strong extensibility, and is platform-independent, in general, the third preset format type can be set to The xml format type.
- the execution execution unit 303 or the execution plan generation unit 3031 may be stored in a task queue.
- the analysis execution unit 303 may further include:
- the task queue memory 3033 is configured to store each of the execution plans in a task queue manner.
- task execution unit 3032 can perform the code analysis process by discovering whether there is an execution plan in task queue memory 3033.
- the corresponding code analysis tool and the analysis rule are called to execute the code analysis process, and the code analysis result is obtained.
- the code analysis tool and analysis rules can be directly from the above information database
- the code analysis result obtained by the analysis execution unit 303 or the task execution unit 3032 can be output and displayed for the user to view, on the other hand, the obtained code analysis result can also be saved in the analysis result library, and can be simultaneously or via the
- the analysis result library is outputted and displayed in various possible forms, such as displaying on the WEB interface.
- the code pre-analysis unit 302 generates a flag corresponding to the corresponding code analysis tool information and analysis rule information while determining each mapping relationship; Therefore, the analysis execution unit 303 obtains the corresponding code analysis tool information and the analysis rule according to the identifier bit, and details are not described herein.
- the information stored in the information database 304 should include a code analysis tool, an analysis rule, and a code analysis tool, and a correspondence between the analysis rule and each identifier.
- the information database 304 in each embodiment of the solution of the present invention may be divided into several according to different functions to implement storage of different information, for example, may include a tool information base, an analysis rule base, a knowledge base, and are stored by the tool information base.
- Each code analysis tool, the analysis rule base stores the analysis rules
- the knowledge base can store code analysis tools, analysis rules and Correspondence between each programming language type and/or identification bit.
- a library of analysis results may be included to store the result of each code analysis obtained above, so that the user can view or output the code analysis result through the analysis result library.
- the above information database 304 may use the mysql database to store related data.
- analysis rule base it is used to store each analysis rule, mainly for the management of analysis rules supported by various code analysis tools.
- a specific example of the content included in the analysis rule base is shown in the following table:
- the decomposition result library As an example, it is mainly used to store code analysis results.
- a specific example of the contents of the analysis result library is shown in the following table: Field description
- F result id KEY primary key, non-empty, analysis result, mainly refers to the id of the analyzed code problem
- the severity level of the F level problem may be different according to actual needs, for example, only the source code may be needed according to requirements.
- the analysis is performed.
- the above code change list is a source code change list.
- FIG. 4 is a schematic block diagram of an operating environment in which the above-described embodiments can be implemented.
- the computer system 400 is configured to perform code analysis on one or more software entities.
- computer system 400 includes a processor 401 and a system memory 402.
- Computer system 400 is intended to broadly represent any processor-based system upon which software can be executed for the benefit of the user.
- computer system 400 can include a desktop computer system, a laptop computer, or a tablet computer.
- computer system 400 can include a video game system, a personal digital assistant (PDA), a smart phone, or a portable media player.
- PDA personal digital assistant
- Processor 401 includes one or more processors or processor cores configured to execute software modules and to access data stored in system memory 402.
- the software modules stored in the system memory 402 change at least the detection unit 301, the code pre-analysis unit 302, and the analysis execution unit 303.
- System memory 402 is intended to broadly represent any type of memory that can be used to store software modules and data to be executed and accessed by processor 401, respectively.
- system memory 402 includes volatile memory, such as random access memory (RAM).
- the storage medium shield may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
- Debugging And Monitoring (AREA)
Abstract
Description
Claims
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/402,821 US9378114B2 (en) | 2012-05-24 | 2013-05-02 | Code analysis method, code analysis system and computer storage medium |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201210164205.4A CN103425572B (zh) | 2012-05-24 | 2012-05-24 | 代码分析方法及代码分析系统 |
CN201210164205.4 | 2012-05-24 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013174200A1 true WO2013174200A1 (zh) | 2013-11-28 |
Family
ID=49623092
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2013/075095 WO2013174200A1 (zh) | 2012-05-24 | 2013-05-02 | 代码分析方法及代码分析系统、计算机存储介质 |
Country Status (3)
Country | Link |
---|---|
US (1) | US9378114B2 (zh) |
CN (1) | CN103425572B (zh) |
WO (1) | WO2013174200A1 (zh) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108804629A (zh) * | 2018-05-31 | 2018-11-13 | 北京五八信息技术有限公司 | 一种筛选项的处理方法、装置、存储介质及设备 |
CN112256575A (zh) * | 2020-10-22 | 2021-01-22 | 深圳我家云网络科技有限公司 | 一种代码质量管理方法、系统及相关设备 |
CN112399466A (zh) * | 2020-11-12 | 2021-02-23 | 国网江苏省电力有限公司信息通信分公司 | 一种基于领域规则库的通信规则缺陷的分析方法 |
Families Citing this family (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104133768A (zh) * | 2014-07-28 | 2014-11-05 | 中国银行股份有限公司 | 一种程序代码复查方法和装置 |
CN104407901B (zh) * | 2014-12-08 | 2018-04-06 | 北京国双科技有限公司 | 代码的添加方法和装置 |
CN107783892A (zh) * | 2016-08-25 | 2018-03-09 | 平安科技(深圳)有限公司 | 一种代码分析方法及终端 |
CN107045477B (zh) * | 2016-12-30 | 2021-08-17 | 上海富聪科技有限公司 | 一种可进行多维度检测的质量评估平台 |
CN109992502A (zh) * | 2017-12-30 | 2019-07-09 | 中国移动通信集团四川有限公司 | 应用软件性能自动检测分析方法、装置、设备及介质 |
CN108803561B (zh) * | 2018-05-22 | 2020-03-17 | 广州明珞汽车装备有限公司 | 针对白车身线体控制程序的程序自动检查方法及系统 |
US10534912B1 (en) * | 2018-10-31 | 2020-01-14 | Capital One Services, Llc | Methods and systems for multi-tool orchestration |
CN109871317A (zh) * | 2019-01-11 | 2019-06-11 | 平安普惠企业管理有限公司 | 代码质量分析方法及装置、存储介质及电子设备 |
CN109446107B (zh) * | 2019-01-23 | 2019-07-09 | 长沙软工信息科技有限公司 | 一种源代码检测方法及装置、电子设备 |
CN110688519B (zh) * | 2019-09-30 | 2022-07-15 | 腾讯音乐娱乐科技(深圳)有限公司 | 播放媒体数据的方法、装置、系统、设备及存储介质 |
CN111078577A (zh) * | 2019-12-31 | 2020-04-28 | 易票联支付有限公司 | 一种自动化代码审计方法、系统、装置及存储介质 |
CN112269774A (zh) * | 2020-10-16 | 2021-01-26 | 苏州浪潮智能科技有限公司 | 异构数据库应用代码适配评估装置、方法及存储介质 |
CN113641573B (zh) * | 2021-07-26 | 2024-05-07 | 安徽中科国创高可信软件有限公司 | 基于修订日志的程序分析软件自动化测试方法及系统 |
CN116756048B (zh) * | 2023-08-16 | 2023-10-31 | 北京安普诺信息技术有限公司 | 一种代码分析方法、装置、计算机设备及存储介质 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1983209A (zh) * | 2005-12-14 | 2007-06-20 | 中兴通讯股份有限公司 | 一种软件单元测试自动化系统及其方法 |
US20080052690A1 (en) * | 2006-08-08 | 2008-02-28 | Microsoft Corporation | Testing software with a build engine |
CN101145102A (zh) * | 2006-09-11 | 2008-03-19 | 国际商业机器公司 | 测试国际化软件的方法和设备 |
CN102419729A (zh) * | 2010-10-26 | 2012-04-18 | 微软公司 | 并行测试执行 |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6748584B1 (en) * | 1999-12-29 | 2004-06-08 | Veritas Operating Corporation | Method for determining the degree to which changed code has been exercised |
US20040122791A1 (en) * | 2002-12-19 | 2004-06-24 | Sea Brian S | Method and system for automated source code formatting |
WO2008110411A1 (en) * | 2007-03-14 | 2008-09-18 | International Business Machines Corporation | Automatic formatting of computer program source code |
US9594544B2 (en) * | 2012-06-07 | 2017-03-14 | Microsoft Technology Licensing, Llc | Visualized code review |
-
2012
- 2012-05-24 CN CN201210164205.4A patent/CN103425572B/zh active Active
-
2013
- 2013-05-02 WO PCT/CN2013/075095 patent/WO2013174200A1/zh active Application Filing
- 2013-05-02 US US14/402,821 patent/US9378114B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1983209A (zh) * | 2005-12-14 | 2007-06-20 | 中兴通讯股份有限公司 | 一种软件单元测试自动化系统及其方法 |
US20080052690A1 (en) * | 2006-08-08 | 2008-02-28 | Microsoft Corporation | Testing software with a build engine |
CN101145102A (zh) * | 2006-09-11 | 2008-03-19 | 国际商业机器公司 | 测试国际化软件的方法和设备 |
CN102419729A (zh) * | 2010-10-26 | 2012-04-18 | 微软公司 | 并行测试执行 |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108804629A (zh) * | 2018-05-31 | 2018-11-13 | 北京五八信息技术有限公司 | 一种筛选项的处理方法、装置、存储介质及设备 |
CN112256575A (zh) * | 2020-10-22 | 2021-01-22 | 深圳我家云网络科技有限公司 | 一种代码质量管理方法、系统及相关设备 |
CN112399466A (zh) * | 2020-11-12 | 2021-02-23 | 国网江苏省电力有限公司信息通信分公司 | 一种基于领域规则库的通信规则缺陷的分析方法 |
CN112399466B (zh) * | 2020-11-12 | 2024-02-09 | 国网江苏省电力有限公司信息通信分公司 | 一种基于领域规则库的通信规则缺陷的分析方法 |
Also Published As
Publication number | Publication date |
---|---|
US9378114B2 (en) | 2016-06-28 |
CN103425572A (zh) | 2013-12-04 |
US20150113332A1 (en) | 2015-04-23 |
CN103425572B (zh) | 2016-04-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2013174200A1 (zh) | 代码分析方法及代码分析系统、计算机存储介质 | |
US11281732B2 (en) | Recommending development tool extensions based on media type | |
US9235410B2 (en) | Tracking software package dependencies using a graph model | |
US8010844B2 (en) | File mutation method and system using file section information and mutation rules | |
US10318595B2 (en) | Analytics based on pipes programming model | |
US8387017B2 (en) | Black box testing optimization using information from white box testing | |
US9779158B2 (en) | Method, apparatus, and computer-readable medium for optimized data subsetting | |
US11681710B2 (en) | Entity extraction rules harvesting and performance | |
US8499197B2 (en) | Description language for identifying performance issues in event traces | |
US9880924B2 (en) | Source code unit testing using an indexing tool | |
US20120290560A1 (en) | Mechanism for efficiently querying application binary interface/application programming interface-related information | |
KR20150128711A (ko) | 컴퓨터 시스템 활동의 트레이스 타임라인을 분석하기 위한 방법 및 시스템 | |
US20190265954A1 (en) | Apparatus and method for assisting discovery of design pattern in model development environment using flow diagram | |
US10635483B2 (en) | Automatic synopsis generation for command-line interfaces | |
WO2022095410A1 (zh) | 组件开发方法、装置、存储介质及电子设备 | |
JP5121891B2 (ja) | 規則検査装置、規則検査方法及び規則検査プログラム | |
JP2016024477A (ja) | ソフトウェア欠陥予測装置、ソフトウェア欠陥予測方法、およびソフトウェア欠陥予測プログラム | |
US20120311520A1 (en) | Mechanism for Certifying Software Components Using a Defect Tracking System | |
US20130191813A1 (en) | Metamodeling Contextual Navigation of Computer Software Applications | |
WO2018116522A1 (ja) | 判定装置、判定方法及び判定プログラム | |
WO2024031983A1 (zh) | 一种代码管理方法及相关设备 | |
JP2019144873A (ja) | ブロック線図解析装置 | |
US20230004361A1 (en) | Code inspection interface providing method and apparatus for implementing the method | |
WO2022123763A1 (ja) | コールグラフ作成装置、コールグラフ作成方法及びプログラム | |
US20230305817A1 (en) | Dynamic importation of external dependency information to support autocompletion in an interactive development environment |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 13793376 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14402821 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205N DATED 17/04/2015) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 13793376 Country of ref document: EP Kind code of ref document: A1 |