Patent application number | Description | Published |
20080244536 | EVALUATING STATIC ANALYSIS RESULTS USING CODE INSTRUMENTATION - A computer-implemented method for evaluating software code includes receiving from a static analysis of the software code a warning indicating a respective location in the software code of a potential bug and a possible execution path leading to the potential bug. Responsively to the warning, instrumentation is added to the code at one or more locations along the execution path. Upon executing the instrumented code, an output is generated, responsively to the instrumentation, indicating that the execution path was traversed while executing the instrumented code. | 10-02-2008 |
20100064280 | SYSTEMS AND METHODS FOR IMPLEMENTING TEST APPLICATIONS FOR SYSTEMS USING LOCKS - A method of testing a system includes providing a shared memory including at least one value and at least one lock associated with the at least one value, the at least one lock including one or more shared read sublocks and an exclusive write sublock, providing a plurality of subsystems in communication with the shared memory and configured to access and update the at least one value, providing a test application on at least one of the plurality of subsystems, and running the test application on the one of the plurality of subsystems. A list of locks and values given to the test application includes a pre-existing list of locks and values in the system under the testing. | 03-11-2010 |
20100131930 | Selective Code Coverage Instrumentation - 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. | 05-27-2010 |
20110093745 | SYSTEMS AND METHODS FOR IMPLEMENTING TEST APPLICATIONS FOR SYSTEMS USING LOCKS - The present invention generally relates to systems and methods for implementing test applications of systems using locks. | 04-21-2011 |
20110202904 | Hierarchical aggregation system for advanced metering infrastructures - A coverage analysis tool may determine coverage in respect to heterogeneous coverage tasks associated with different hierarchy levels of a tasks hierarchy. The coverage analysis tool may iteratively refine coverage tasks to determine coverage of sub-tasks. In some cases, coverage tasks may be unrefined in order to reduce overhead of coverage analysis in performance of the software under test, such that the software under test may perform in an essentially similar manner as in non-testing mode. | 08-18-2011 |
20130024804 | Navigation History Tracking In a Content Viewing Environment - Systems and methods for monitoring user actions, while a user is viewing first content displayed on a display screen, wherein the user views a first portion of the first content within a first context that defines scope of view for the first content; determining whether the user's actions resulted in second content being displayed on the display screen; associating the first portion of the first content with the second content; and maintaining a record of the association between the first portion of the first content and the second content. | 01-24-2013 |
20130110489 | AUTOMATIC DESIGNATION OF EQUIVALENT VARIAVLE VALUES | 05-02-2013 |
20130110880 | TEST PLANNING USING ATTRIBUTE VALUE PROPERTIES | 05-02-2013 |
20130117005 | COVERAGE ANALYSIS FOR MULTIPLE TEST METHODOLOGIES - Systems and methods for constructing a model to test the functionality of a target system are provided. When a first test methodology is used to test the target system, a model is proposed to test the target system based on a second test methodology. A subset of the target system's properties covered by the model is selected according to the second test methodology. It is determined whether the selected subset of the target system's properties, as covered by the second test methodology, is covered by the first test methodology. | 05-09-2013 |
20140033174 | SOFTWARE BUG PREDICTING - A method, apparatus and product for software bug prediction. The method comprising obtaining from a plurality of developers probability estimates to areas in a plurality of code partitioned areas of a code, wherein a probability estimate is representative of an estimated probability of the area having a software bug according to a developer of the plurality of developers; and determining a testing strategy of the plurality of code partitioned areas based on the probability estimates. | 01-30-2014 |
Patent application number | Description | Published |
20080276226 | DEVICE, METHOD AND COMPUTER PROGRAM PRODUCT FOR EVALUATING A DEBUGGER SCRIPT - A method for evaluating a debugger script, the method includes: (i) receiving a debugger script that includes a first debugger breakpoint that is associated with a certain program line number; and determining a validity of the first debugger breakpoint in response to a comparision between expected content associated with the first debugger breakpoint and between an actual content of at least a portion of a certain program line group that comprises a certain program line identified by the certain program line number. | 11-06-2008 |
20090106737 | Using Cross-entropy to Test Executable Logic Code - A method for detecting the occurrence of rare events in an executable logic code includes assigning a first probability of a chance of traversal of one or more decision paths, in which each path connects two decision points defined by execution of the logic code. As a result of execution of the logic code, the decision paths traversed are evaluated to determine whether said traversal conforms to a predefined performance function. The performance function defines a goal to be achieved pursuant to the execution of the logic code. A second probability is assigned to the chance of traversal of at least one of said one or more decision paths to increase the likelihood that the one or more decision paths are traversed in a subsequent execution of the logic code in a closer conformity with the predefined performance function. | 04-23-2009 |
20090106740 | Replay of program executions using cross-entropy - A method for replay of program executions using cross-entropy is provided. The method comprises identifying a first sequence of decision points, wherein the first sequence represents a first execution of a logic code; identifying a second sequence of decision points, wherein the second sequence represents a second execution of the logic code; computing a distance between the first and second executions; and minimizing the distance between the first and second executions using cross-entropy, in response to determining that the second execution is not within a predetermined threshold distance of the first execution. | 04-23-2009 |
20090249298 | Evaluation of Software based on Change History - A method for software processing includes obtaining change information, which records changes that have been performed in respective locations in software code. The change information is processed so as to assign to at least some of the locations respective priorities, which are indicative of respective likelihoods that the locations contain program faults. The at least some of the locations are presented to a user in accordance with the assigned priorities. | 10-01-2009 |
20110126173 | VERIFYING SYNCHRONIZATION COVERAGE IN LOGIC CODE - A computer implemented system and method for measuring synchronization coverage for one or more concurrently executed threads is provided. The method comprises updating an identifier of a first thread to comprise an operation identifier associated with a first operation, in response to determining that the first thread has performed the first operation; associating the identifier of the first thread with one or more resources accessed by the first thread; and generating a synchronization coverage model by generating a relational data structure of said one or more resources, wherein a resource is associated with at least the identifier of the first thread and an identifier of a second thread identifier, such that the second thread waits for the first thread before accessing said resource. | 05-26-2011 |
20110225103 | EFFICIENCY OF COMPUTER MODELING AND ANALYSIS OF COMPLEX PROCESSES - A system and method for constructing and analyzing a graphical representation of a complex process comprises steps and means for receiving input of content related to the complex process; processing said input to identify entities and actions instrumental in the execution of the complex process; constructing a graphical representation of the process as a network comprising first nodes, representing decision points, second nodes representing primary stakeholders and actions providing direct input to decision making points, and leaves representing secondary stakeholders providing indirect input to decision making points; and applying at least one analytic approach for evaluating the decision points of the graphical representation of the process. | 09-15-2011 |
20110238613 | COMPARING DATA SERIES ASSOCIATED WITH TWO SYSTEMS TO IDENTIFY HIDDEN SIMILARITIES BETWEEN THEM - A method that includes: sampling a plurality of parameters associated with a first and a second system to yield a first and a second set of data series, respectively, each data series being associated with samples of a respective parameter; applying, for each two respective data series, a transformation associated with a specified order selected from a plurality of ordered transformations, such that the selected transformation is applied repeatedly to at least one of the two respective data series, wherein, in each repeated application, the transformation is assigned with a different value of a transformation parameter; determining, for each parameter, a one of the plurality of transformation parameters for which the correlation level of the two respective time series is above a specified value; and repeating the applying and the determining with a transformation that is associated with a higher order of the ordered transformations. | 09-29-2011 |
20120331449 | DEVICE, METHOD AND COMPUTER PROGRAM PRODUCT FOR EVALUATING A DEBUGGER SCRIPT - A method for evaluating a debugger script, the method includes: (i) receiving a debugger script that includes a first debugger breakpoint that is associated with a certain program line number; and determining a validity of the first debugger breakpoint in response to a comparison between expected content associated with the first debugger breakpoint and between an actual content of at least a portion of a certain program line group that comprises a certain program line identified by the certain program line number. | 12-27-2012 |
20130185696 | MANIPULATING SOURCE CODE PATCHES - A computerized apparatus, a computer-implemented method and a computer program product for manipulating source code patches. The apparatus comprising a processor that is configured to: obtain a source code patch comprising plurality of source code modification instructions with respect to a source code and to automatically split the source code patch into plurality of sub-patches, wherein applying the plurality of sub-patches on the source code in an order is equivalent to applying the source code patch. | 07-18-2013 |
20130185697 | SOURCE CODE PATCHES - Apparatus, process and product useful for source code patches. The computerized apparatus having a processor, the apparatus comprising: a source code obtainer for obtaining a source code of a computer program; a patch instructions obtainer for obtaining a set of source code patches instructions, wherein a first patch instructions comprise a set of modification instructions to the source code associated with a first source code patch, wherein a second patch instructions comprise a set of modification instruction to the source code associated with a second source code patch; a source code editor configured to display to a user the source code and annotations associated with applying each source code patch simultaneously; and wherein said source code editor is further configured to edit the source code in accordance with user input, wherein based on user input the first and second source code patch instructions are modified. | 07-18-2013 |
20130247062 | VERIFYING SYNCHRONIZATION COVERAGE IN LOGIC CODE - A computer implemented system and method for measuring synchronization coverage for one or more concurrently executed threads is provided. The method comprises updating an identifier of a first thread to comprise an operation identifier associated with a first operation, in response to determining that the first thread has performed the first operation; associating the identifier of the first thread with one or more resources accessed by the first thread; and generating a synchronization coverage model by generating a relational data structure of said one or more resources, wherein a resource is associated with at least the identifier of the first thread and an identifier of a second thread identifier, such that the second thread waits for the first thread before accessing said resource. | 09-19-2013 |
20130283258 | Techniques for Objective Assessment and Improvement of Software Quality - Techniques for quantifying and improving consumability of software bundles are provided. In one aspect, a method for quantifying a consumability of a software bundle is provided which includes the following steps. Constituent software products of the bundle are identified. Software components an installation of which is a pre-requirement for an installation of the software products are identified. Software units an installation of which is a pre-requirement for an installation of the software components are identified. Dependency graphs are created for the software components. The dependency graphs for the components are merged to create dependency graphs for the products. The dependency graphs for the products are merged to create a dependency graph for the bundle. The dependency graph for the bundle is used to quantify the consumability of the bundle. | 10-24-2013 |