International Business Machines Corporation

Honeywell International Inc.

Satish Chandra

Saurabh Sinha

Suresh Thummalapenta

Vibha Singhal Sinha

Bikram Sengupta

Leigh Allen Williamson

Pankaj Dhoolia

Nishant Kumar Sinha

Manu Sridharan

Yandrapally Rahulkrishna

Emina Torlak

Anand Krishna Vaishampayan

Julian Timothy Dolby

Diptikalyan Saha

Stephen Fink

Frank Tip

Monika Gupta

Debdoot Mukherjee

Amol Gandhi

Ganesan Ramalingam

Mangala Gowri Nanda

Krishna Nandivada Venkata

John H Field

Rudrapatna Kallikote Shyamasundar

Vilas Ramdas Ingle

Mangala Gowri, Iii

Lokesh Sambasivan

Prashanth Lingala

Achin K Das

Srinivas Mangipudi

Vasanta K Lakshmi

Ganapathy Viswanath

Kommineni Vasanta Lakshmi

Shaon K Barman

Raghavan Komondoor

Vilas Ingle

Techniques, an apparatus and computer program product for generating test cases for covering enterprise rules and predicates are disclosed by receiving data associated with at least one of a business requirement and a business scenario as input, wherein the data comprise at least one of a set of predefined rules; based on the data, generating at least one or more test cases as output without any human intervention, wherein the output comprises a test script for the business requirement or the business scenario, and wherein the data associated with the at least one of a business requirement and a business scenario comprise at least one of a business rule, business requirement and predicate, the data associated with the at least one of business requirement and business scenario are stored as a linked graph in a repository, and wherein each node of the linked graph is mapped to previously stored data in the repository, wherein the repository comprises either one of a structured or unstructured data, and the data are obtained from the requirement specifications.

Efficiently generating test cases

A method for creating agnostic test automation script commands associated with a specified action and a user interface (UI) is provided. The method may include receiving a target element associated with the specified action. The method may also generate at least one anchor uniquely identifying the target element, wherein the target element is ambiguous. The method may further include generating an agnostic test automation script command based on the received target element and the at least one generated anchor. Additionally, the method may analyze, using the generated agnostic test automation script command, the at least one generated anchor to locate the target element within the user interface (UI), wherein the analyzing is based on an application on which the agnostic test automation script command is to be executed. The method may also include performing, using the generated agnostic test automation script command, the specified action on the located target element.

System and method for creating change-resilient scripts

A computer system, method and computer program product for automatically converting, through automating-test-automation software, a manual test case representation (in a natural language), for testing a target software, into a machine-readable test case representation. In preferred embodiments, the machine-readable test case is in the form of a keyword-based test case that is made from action-target-data tuples. The automation-test-software uses a methodical process of trial-and-error to resolve ambiguities that are generally present (and generally resolvable by humans) in the manual test case representation.

System and method for automating test automation

Techniques, an apparatus and an article of manufacture for generating test cases for covering enterprise rules and predicates. A method includes obtaining a web application and a specification of at least one enterprise rule, constructing a link graph that captures at least one navigation path in the web application, and performing a traversal of the web application guided by the link graph to generate an executable test case that drives the web application along one of the at least one navigation paths in which the at least one enterprise rule is covered to determine the web application's conformance to the at least one enterprise rule, wherein the executable test case is a sequence of one or more test steps, each test step representing an action to be performed on the web application and/or a verification of the application state.

Generating test cases for covering enterprise rules and predicates

Methods, systems, and devices for determining a deployment of a wireless network are described herein. One method includes receiving, via a computing device, radio frequency data associated with a structure, wherein the structure includes a number of sensor nodes, receiving physical parameters associated with the structure, determining a number of relay nodes to deploy in the structure based, at least in part, on the radio frequency data and the physical parameters, and determining a location to deploy each of the number of relay nodes in the structure based, at least in part, on the radio frequency data and the physical parameters.

Determining a deployment of a wireless network

Methods and arrangements for localizing faults in programs. A program is assimilated, the program comprising statements. Output behavior of the statements is modeled, and statement occurrences are annotated. Passing and failing spectra are differenced to yield a difference, and a fault is located via employing the difference.

Fault localization for data-centric programs

Techniques for static code analysis are provided. The techniques include routing a code analysis request to a set of one or more static code analysis tools based on a context of the request, merging one or more tool-specific outputs of the code analysis, wherein merging the one or more tool-specific outputs comprises using one or more tool-specific mappings to one or more static code analysis abstractions and one or more source linkages of one or more static code analysis defects, performing a deep analysis on a set of one or more defect categories, and combining results of the merging with the deep analysis to filter out one or more false-positives and to add one or more new true positives to create an optimal set of defects.

Static code analysis

A novel system, computer program product, and method are disclosed for transforming a program to facilitate points-to analysis. The method begins with accessing at least a portion of program code, such as JavaScript. In one example, a method with at least one dynamic property correlation is identified for extraction. When a method m is identified for extraction with the dynamic property correlation, a body of the loop l in the method m is extracted. A new method mis created to include the body of the loop l with the variable i as a parameter. The loop l is substituted in the program code of the method m with the new method mto create a transformed program code.

Scalable property-sensitive points-to analysis for program code

Systems and methods for detecting resource leaks in a program using static analysis are disclosed. Dynamically adjustable sets of must-access paths can be employed for aliasing purposes to track resources intra- and inter-procedurally through a program. Actionable reports are also disclosed, in which resource leaks are prioritized, filtered and clustered to improve utility.

Systems and methods for resource leak detection

Systems and methods for identifying expressions that are potential causes of program bugs are disclosed. A program and at least one input resulting in at least one passing test of the program can be received. Further, at least one plausible repair candidate expression in the program can be identified. In addition, the methods and systems can determine whether replacement of the at least one identified expression with at least one value, which is different from a value provided by the at least one identified expression, maintains the passage of the at least one passing test. Moreover, the at least one identified expression can be output when the replacement maintains the passage of the at least one passing test to enable a determination of a modification of the program that repairs a bug in the program.

Precise fault localization

A technique for feedback-directed call graph expansion includes performing symbolic analysis on an interprocedural control flow graph representation of software code, skipping over a virtual method call in the control flow graph, using information obtained from the symbolic analysis as feedback to identify a target of the virtual method call, and iterating the symbolic analysis on a modified version of the control flow graph that associates the target with the virtual method.

Feedback-directed call graph expansion

A data visualization device comprises a focal attribute calculator for calculating a focal value of each of a plurality of data input items, and for categorizing each of the plurality of data input items as either non-cluster blobs or second blobs. The device further comprises a clustering attribute calculator for clustering data input items categorized as second blobs into one or more cluster blobs, and a visualization shaper for arranging the one or more cluster blobs and the non-cluster blobs, relative to each other in accordance with the focal values of the data input items of respective blobs.

Data visualization device and method

Traceability links between software specification requirements are evidentially enriched. A traceability link indicates that a second specification requirement is dependent to some degree on a first specification requirement. A likelihood that the second specification requirement for software changes due to the first specification requirement for the software changing, and/or a degree of change of the second specification requirement due to the first specification requirement changing, are determined. A coupling value for the traceability link may be determined as directly proportional to the likelihood that the second specification requirement changes due to the first specification requirement changing, and to the degree of change of the second specification requirement due to the first specification requirement changing.

Evidentiary enrichment of traceability links between software specification requirements

Disclosed is a method of and a system for establishing a logical-model based understanding of a legacy application. The method comprises the steps of providing a physical data model of the legacy application, said physical data model having a plurality of physical elements; establishing a logical data model for the legacy application, said logical data model having a plurality of logical model elements; and establishing links between said logical model elements and said physical elements. One of said physical or logical elements is selected, and said links are used to identify all of the physical or logical elements that are linked to said selected one of said elements. The preferred system may include a component for browsing and navigating the physical data model, logical data model, or the links between them, a component to answer queries about the application expressed using the logical data model, and a component to create a relational data model to support the migration of data stored in legacy databases (including flat files) to relational databases.

Growing community of inventors

White Plains, NY, United States of America

Satish Chandra