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 |
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 |
20090249299 | Evaluation of Software based on Review History - A computer-implemented method for software processing includes obtaining review information pertaining to reviews that have been conducted on respective locations in software code. The review 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 via an output device in accordance with the assigned priorities. | 10-01-2009 |
20090271770 | METHOD, SYSTEM, AND COMPUTER PROGRAM PRODUCT FOR GENERATING UNIT TESTING SCRIPTS - A method, system, and computer program product are provided for generating unit testing scripts. The method includes receiving programming code having a condition expressed therein, and transforming the code by wrapping the condition into a mock function. The mock function receives a Boolean argument as an input and provides a Boolean value as an output irrespective of a pre-transformed input and a pre-transformed output of the condition. The Boolean value is capable of selectively being the Boolean argument received as the input or a different value specified by a user. The method further includes receiving a user input specifying a behavior relating to how a return value is generated for the mock function. The Boolean value is provided in accordance with the specified behavior. At least one pre-transformation output of the condition prior to the transforming step is direct-function independent. | 10-29-2009 |
20090319833 | Software Quality Assessment based on Semantic Similarities - A method for software processing includes accepting quality information, which includes names of elements of software code and respective quality indications regarding tested acceptability of the elements. The names are processed to extract a list of substrings that occur in the names. Respective metrics are assigned to the substrings responsively to the quality indications of the elements in whose names the substrings occur. At least some of the substrings are presented to a user in accordance with the assigned metrics. | 12-24-2009 |
20100050161 | Detecting Locking Discipline Violations on Shared Resources - Detecting locking discipline violations on shared resources. For example, a method of detecting locking discipline violations of shared resources of a computing platform, by a testing process to be executed concurrently with one or more other processes on said computing platform, the testing process comprising: locking a shared resource of said computing platform; reading a value of the shared resource; locally storing the value of the shared resource; rereading the value of the shared resource after a predefined time period; and generating a locking discipline violation report if the value of said shared resource as reread by said rereading is different from the value of said resource as locally stored by said locally storing. | 02-25-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 |
20100262866 | CROSS-CONCERN CODE COVERAGE ASSESSMENT - A method for software processing includes extracting from software code under test respective items of meta-information pertaining to elements of the software code and receiving respective quality data regarding the elements of software code. The quality data and meta-information are processed in a computer so as to assign respective metrics to the items of the meta-information responsively to the quality data regarding the elements of the software code to which the items pertain. At least some of the meta-information is presented to a user in accordance with the assigned metrics. | 10-14-2010 |
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 |
20130111272 | FAULT DETECTION BASED ON DIAGNOSTIC HISTORY | 05-02-2013 |
20130239094 | DETECTING LOCKING DISCIPLINE VIOLATIONS ON SHARED RESOURCES - Detecting locking discipline violations on shared resources. For example, a method of detecting locking discipline violations of shared resources of a computing platform, by a testing process to be executed concurrently with one or more other processes on said computing platform, the testing process comprising: locking a shared resource of said computing platform; reading a value of the shared resource; locally storing the value of the shared resource; rereading the value of the shared resource after a predefined time period; and generating a locking discipline violation report if the value of said shared resource as reread by said rereading is different from the value of said resource as locally stored by said locally storing. | 09-12-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 |
20140258991 | TRACE COVERAGE ANALYSIS - A method and apparatus for estimating coverage of a computer program from traces, the method comprising: receiving trace data generated by an execution of an executable unit; and estimating coverage of the executable unit from the trace data, wherein estimating coverage comprises estimating trace coverage. | 09-11-2014 |