461 results about "Code coverage" patented technology

The present invention is directed to automatically analyzing software systems for identifying faults or bugs and / or detection of malicious code. In various embodiments, the present invention measures code coverage for high priority invocable program elements, uses a relaxed coverage estimation technique that, instead of guaranteeing which code units will be executed, guarantees that at least a certain number of code units will be executed, determines and solves constraints in code to identify infeasible paths containing one or more selected nodes, determines, for a composite data type, a range of values for each of at least two non-composite data fields, and / or translates, prior to code analysis complex code into simpler code having fewer operators.

The present invention is directed to automatically analyzing software systems for identifying faults or bugs and / or detection of malicious code. In various embodiments, the present invention measures code coverage for high priority invocable program elements, uses a relaxed coverage estimation technique that, instead of guaranteeing which code units will be executed, guarantees that at least a certain number of code units will be executed, determines and solves constraints in code to identify infeasible paths containing one or more selected nodes, determines, for a composite data type, a range of values for each of at least two non-composite data fields, and / or translates, prior to code analysis complex code into simpler code having fewer operators.

Dynamic test coverage to evaluate an artifact code is provided. Code of an artifact to be tested is identified. The code coverage of the test code is analyzed. The current coverage information is stored. Code coverage information for one or more prior versions of the test code is retrieved. The current coverage information is compared with the prior coverage information. Responsive to a determination that a difference between the current coverage information and the prior coverage information exists, the difference is collected. Responsive to a determination that test cases are to be generated automatically, generating, automatically, new test cases based on the difference. The new test cases are stored. Code coverage of the test code is analyzed based on the new test case. The new coverage information is stored. The new coverage information is sent to the user.

A binary rewriter that can provide complete code coverage without relocation information is provided, together with a method of performing such rewriting. The method can include processing a binary file as an original binary file. The method can also include disassembling the binary file to provide a disassembled binary file. The method can further include rewriting the disassembled binary file without relocation information to provide a rewritten binary file. The rewriting can provide a physical transformation in a recording medium relative to the binary file in the recording medium prior to the rewriting. The processing the binary file, disassembling the binary file, and rewriting the disassembled binary file can be performed by a particular machine.

A method and system for software code testing for an automated test execution environment is provided. Testing involves importing test case information into a tooling environment based on code coverage and targeted testing, the test information including test name and code coverage data including classes and methods exercised by the code; generating a test hierarchy by analyzing the individual test case information; selecting tests including one or more of: all tests for a full regression run, a subset of tests for basic quality assurance or testing a particular area of functionality, and tests that exercise a recently changed class; executing selected tests to generate a pass / fail result for each test and correlating the test results; performing test run prioritization to recommend which remaining tests to execute.

A method and system for software code testing for an automated test execution environment is provided. Testing involves importing test case information into a tooling environment based on code coverage and targeted testing, the test information including test name and code coverage data including classes and methods exercised by the code; generating a test hierarchy by analyzing the individual test case information; selecting tests including one or more of: all tests for a full regression run, a subset of tests for basic quality assurance or testing a particular area of functionality, and tests that exercise a recently changed class; executing selected tests to generate a pass / fail result for each test and correlating the test results; performing test failure analysis prioritization to prioritize any failures.

A method, apparatus, and computer instructions for generating coverage data during execution of code in the data processing system. During execution of the code, a determination is made as to whether an access indicator is associated with an instruction in response to executing the instruction in the code by a processor in the data processing system. If the access indicator is associated with the instruction, a state of the access indicator is changed, by the processor, when the instruction is executed. In this manner, coverage data for executed instructions is generated by the processor during execution of the code.

A method and system is provided for instrumenting a program by optimizing probe insertion. The number of probe insertions into instrumented code is reduced by providing optimal probe insertion points. The control flow of the code is analyzed along with the arc and block relationships to build a post-dominator tree. An optimization map is generated from the post-dominator tree that provides the optimal probe insertion points. Once the probes are inserted and data is collected by running the binary representing the code and probes, the data may be overlaid onto the optimization map and arc and block relationships to provide code coverage data.

An approach is provided to identify test cases based on changed test code. In the approach, test cases are compared to a current test environment that includes an instrumented software program that results in matching test cases. Matching test cases are selected based on a detection of one or more substantive changes to the current test environment. The current test environment is tested using the selected test cases. In an alternate approach, the current environment is tested with multiple test cases and code coverage metrics are retained. After the initial testing, modification of the software program results in comparing of the modification to the retained code coverage metrics whereupon a set of the test cases are selected and used to re-test the software program.

An exemplary method includes receiving source code having a plurality of code segments, providing a desired level of quality for the source code, analyzing the source code to assign a complexity measure to each of the plurality of code segments and assigning a level of code coverage to each of the plurality of code segments based at least in part on the desired level of quality and the complexity measures. An exemplary system prioritizes quality improvements to source code based, in part, on a quality assessment. Such a system can improve code quality by assigning higher test coverage levels to modules with higher complexity.

A method, system, and article are provided for evaluating software test comprehensiveness of an application. A subset of the software-under-test basic blocks is identified for emphasized and / or deemphasized testing. During test, execution of the basic blocks is monitored, and then aggregated into a weighted code coverage result which factors in the prioritization assignments of the subset of basic blocks.

Methods and apparatuses that collect code coverage information for selected code locations when executing executable code are described. Source code in one or more files may be annotated at the selected code locations. The executable code may be compiled from the annotated source code using standard compilers. The code coverage information may be collected into a run time data store accessible by other applications. In response to receiving a code coverage request, the code coverage information can be retrieved from the data store to compare with annotations identified from the source code. A code coverage report can be generated to indicate whether one or more of the selected code locations are not covered when executing the executable code.

The invention relates to a controlled mutation-based test case generation method for improving fuzzy test coverage, and belongs to the field of loophole mining in information safety. Aiming at the problem that the existing fuzzy test coverage optimization methods are high in time cost, incomplete in test range and low in automation degree, the invention discloses a controlled mutation-based test case generation method. According to the method, feedback is carried out on test case generation processes by utilizing an instrumentation technology, and a random mutation manner and a controlled mutation manner are combined to optimize the test case generation. Experimental results show that when being compared with the un-optimized test methods, the method has the advantages of improving the code coverage by 35-47% and decreasing the number of test cases required under same code coverage by more than 48%. The method is not only capable of improving the test case coverage and decreasing the test case redundancy, but also has the characteristics of being low in time cost, complete in test range and free of manual intervention in test processes.

The various embodiments herein disclose a system and method for generating a delta code coverage information. The system for generating delta code coverage information comprises, a source control module configured for storing a plurality of software program code files to be processed and a plurality of code coverage data corresponding to the plurality of software program code files, a processor configured to generate a delta code coverage data for analysis for each of the plurality of software program code files on a line level or at a branch level by performing a time based delta code coverage process and a path based delta code coverage process.

A method and apparatus for evaluating code. A likelihood that a set of segments of the code will not run as desired based on a policy is identified. A risk of the code not performing as desired is evaluated based on a result from a code coverage test and the likelihood that the set of segments of the code will not run as desired.

The invention relates to the computer field. The embodiment of the invention discloses a method for confirming code coverage and a test method thereof. The test method comprises the following steps: confirming the total code amount and the basic address of a tested program, as well as relative virtual addresses of all code lines; setting interruption in the code lines according to the basic address and the virtual addresses of the code lines; detecting whether interruption takes place in the process of the tested program, if yes, marking the code line the interruption belongs; detecting whether the test is completed, if no, returning to the step of detecting whether interruption takes place, and if yes, accumulating marked total code in the code lines to acquire executed total code amount; and obtaining the code coverage of a tested program according to the executed total code amount and the total code amount thereof. By adopting the technical scheme of the embodiment of the invention, the code coverage of the tested program can be accurately obtained and the stability of the tested program can be guaranteed.

The present invention discloses a method and an apparatus for acquiring a code coverage rate, and belongs to the field of communication. The method comprises: a testing device acquiring compilation results and compilation numbers of m APPs; the testing device acquiring a testing case, configured by a user, of each of the m APPs; the testing device testing each compilation result according to the testing case of each APP, and generating a first code coverage information file; and the testing device sending the first code coverage information file to a server, so that the server calculates a code coverage rate according to the first code coverage information file. The method and apparatus solve the problem that a valid code coverage rate cannot be accurately acquired in the case that a parallel crossed test is performed on multiple users, multiple testing devices or multiple versions of APPs, thereby enhancing convenience of acquiring the code coverage rate and improving working efficiency of testers.

Concepts and technologies are described herein for incremental compositional dynamic test generation. The concepts and technologies described herein are used to increase the code coverage and security vulnerability identification abilities of testing applications and devices, without significantly increasing, and in some cases decreasing, computational and time costs associated with the testing. Test summaries that describe how code is tested by a test engine are generated and stored during testing of code. These test summaries can be evaluated when additional iterations or versions of the code are tested. If functions corresponding to the test summaries are unchanged from, or logically equivalent to, a version of the function previously tested, the test summary may be used when testing the new version of the code.

A method for visualization of a software program includes receiving code coverage data generated by the software program, the code coverage data being associated with a test case, by a visualization tool in a computing system; and generating, by the visualization tool, a visualization of an execution of the test case by the software program based on the code coverage data; and displaying the visualization to a user.

A method and system for determining code coverage of one or more software modules is disclosed. The disclosed method and system uses an enumeration module, a code coverage module and an analysis module. The enumeration module is used to identify portions of the code in the software module for which code coverage data is desired. The code coverage module collects code coverage data when the software module is loaded. The analysis module summarizes and reports results of the collected code coverage data.

A system and method for instrumenting a software build to automatically generate code coverage data without the use of external code coverage tools is presented. A software build is generated. The software build is independently executable. The software build is then instrumented to automatically generate code coverage data when executed. The instrumented software is executable independent of any external code coverage tools.

In a verification supporting apparatus, when an obtaining unit obtains a verification scenario, a substituting unit substitutes an undefined value for a variable value in the verification scenario. A first executing unit executes a logic simulation using an input pattern. From a result of the logic simulation, a determining unit generates code-coverage upper-limit information. A setting unit sets input patterns by giving an arbitrary logic value to the variable value. A second executing unit executes a logic simulation using the input patterns set. A generating unit generates code coverage from the input patterns set. A calculating unit calculates a level of achievement of the code coverage with respect to the code-coverage upper-limit information.

The invention provides a dynamic symbolic execution method and a device of the dynamic symbolic execution method based on an overall situation super block dominator graph and belongs to the field of computer software testing and software security. The method is as follows: a control flow diagram of a tested executable program is obtained, and the control flow diagram is transformed to a super block dominator graph according to relevant theories of a dominance relation. Each nodal point in the super block dominator graph is marked with 'weight' which is updated before symbolic execution at each time, and the 'weight' indicates the least number of basic blocks which can be covered when the nodal point is executed. When one dynamic symbolic execution is over, the nodal point with the largest 'weight' value is selected from the super block dominator graph, and corresponding forecasting path constraint conditions are generated, and then a new testing use case is generated by solving of a solver, so that the next execution is driven. Compared with the prior art, the dynamic symbolic execution method and the device of the dynamic symbolic execution method based on the overall situation super block dominator graph are capable of covering code blocks as many as possible with least testing use cases, so that the growth rate of the code coverage rate is effectively accelerated, and the problem of path explosion is relieved. The dynamic symbolic execution method and the device of the dynamic symbolic execution method based on the overall situation super block dominator graph is of great importance for the performance of testing large-scale utility software of the dynamic symbolic execution.

Determining code coverage of a computer program is disclosed. In an embodiment, the program is divided into a plurality of code sections, and the program including the plurality of code sections is run with a plurality of test data sets. In the first test run, all code sections of the plurality of code sections are instrumented, and in each of a current test run other than the first test run, only those code sections that were not executed in any one of the test runs prior to the current test run are instrumented. A code section being executed in any of one of the test runs of the plurality of test runs is considered covered by the test runs. Additionally, within the current test run, the code coverage measurement is only done on the first execution of a code section.

Embodiments of the present invention relate to a method and a device for obtaining test cases based on a code coverage. The method comprises creating a mapping between source code and test cases based on a code coverage; and obtaining, in response to a change in the source code, the test cases for the change based on the mapping. The device comprises: a creating module configured to create a mapping between source code and test cases based on a code coverage; and an obtaining module configured to, in response to a change in the source code, obtain a test case for the change based on the mapping. Through such method and device, the embodiments of the present invention can obtain test cases as few as possible to cover the changed source code.

The invention discloses a random test case generation method facing a Java program. The random test case generation method comprises the following steps of: (1) resolving a class definition of the Java program, and acquiring an object method list; (2) establishing a dependency relation graph comprising a method calling graph and a property dependency graph among object methods; (3) determining a target method list to be covered; (4) generating a calling chain by aiming at instantiation for public classes, and maintaining a class object base; (5) generating a calling chain by aiming at covering target methods, and maintaining a calling chain base; and (6) generating a test case set for the Java program based on the calling chain base. The method can be widely applied to automatic test work of medium-and large-size Java software systems and can automatically generate test cases completely; the highest code coverage rate is achieved by the least number of test cases; complicated data structures can be processed; test assertion can be automatically generated; and the test case generation method is simple and effective, and has high applicability and expandability.

A method, apparatus, and computer instructions for generating coverage data during execution of code in the data processing system. During execution of the code, a determination is made as to whether an access indicator is associated with an instruction in response to executing the instruction in the code by a processor in the data processing system. If the access indicator is associated with the instruction, a state of the access indicator is changed, by the processor, when the instruction is executed. In this manner, coverage data for executed instructions is generated by the processor during execution of the code.

The invention discloses an intelligent contract operation code coverage rate calculation method and system. The method comprises the steps that when a source code file of an intelligent contract is obtained, a deployment request is sent to a blockchain, and thus the blockchain can deploy the intelligent contract according to the deployment request and return a contract address of the intelligent contract; according to the contract address of the intelligent contract returned by the blockchain, identification information of the intelligent contract is obtained, a transaction request which contains the identification information is constructed, the transaction request is sent to the blockchain, and thus the blockchain can output a corresponding statistical result file to a preset storage medium according to the identification information of the transaction request; according to the identification information, the statistic result file is obtained in the storage medium, and according to the statistic result file and a preset formula, the intelligent contract coverage operation code rate is calculated. The method and system simplify the calculation process of the intelligent contract coverage rate and improve the calculation precision of the intelligent contract coverage rate.

Techniques and systems for analysis, diagnosis and debugging fabricated hardware designs at a Hardware Description Language (HDL) level are described. Although the hardware designs (which were designed in HDL) have been fabricated in integrated circuit products with limited input / output pins, the techniques and systems enable the hardware designs within the integrated circuit products to be analyzed, diagnosed, and debugged at the HDL level at speed. The ability to debug hardware designs at the HDL level facilitates correction or adjustment of the HDL description of the hardware designs. Moreover, various embodiments related to HDL code coverage are described.

Reporting on software test coverage, where a set of coverage tasks and a coverage task hierarchy have been established for a software under test (SUT). Establishing a coverage task subset, the subset including at least one coverage task hierarchy element at a level above the lowest coverage task hierarchy level. Identifying when, during a software test, a coverage task in the coverage task subset was completed. Outputting to a user the identity of those portions of the coverage task that have been completed. Refining the coverage task subset in one of the following fashions through the coverage task hierarchy in accordance with user input: depth first progression, breadth first progression.