Abstract: Techniques are provided for automated resiliency testing. In one example, a computer-implemented method comprises analyzing, by a system operatively coupled to a processor, an annotated state transition graph of a user interface of a microservices-based application, wherein the annotated state transition graph has edges annotated with application program interface call subgraphs. The computer-implemented method also comprises generating, by the system, an ordered list of the application program interface call subgraphs based on the analyzing.

Abstract: Techniques for automated generation of inputs for testing microservice-based applications are provided. In one example, a computer-implemented method comprises: traversing, by a system operatively coupled to a processor, a user interface of a microservices-based application by performing actions on user interface elements of the user interface; and generating, by the system, an aggregated log of user interface event sequences and application program interface call sets based on the traversing. The computer-implemented method also comprises: determining, by the system, respective user interface event sequences that invoke application program interface call sets; and generating, by the system, respective test inputs based on the user interface event sequences that invoke the application program interface call sets.

Abstract: Techniques for automated resiliency testing systems are provided. In one example, a computer-implemented method comprises traversing, by a system operatively coupled to a processor, an application program interface call subgraph of a microservices-based application in a depth first traversal. The computer-implemented method also comprises, during the traversing, performing, by the system, resiliency testing of parent application program interfaces of the application program interface call subgraph according to a systematic resilience testing algorithm that reduces and/or eliminates redundant resiliency testing of parent application program interfaces.

Abstract: This application provides to a method for identifying one or more prostate tissue samples in a database that are closest to a test prostate sample, which can be used to aid pathologists when examining prostate tissues to attain reliable and consistent diagnoses of prostate cancer. Also provided are databases and computer algorithms that can be used with such methods.

Abstract: Embodiments provide a computerized method for adapting automating test scripts, said method including: utilizing at least one processor to execute computer code that performs the steps of: receiving, at an input device, an original test script created to test an application; utilizing the original test script to test, using the processor, a variant of the application; identifying, using the processor, failures in the original test script when the variant of the application is being tested; and modifying, using the processor, the original test script to overcome the identified failures.

Abstract: One embodiment provides a method of identifying discrepancies of an application operating on multiple operating platforms, said method comprising: utilizing at least one processor to execute computer code that performs the steps of: obtaining a first source code associated with an application of a first operating platform, the first source code comprising at least one feature of the application; generating, based on the first source code, a first context graph; obtaining a second source code associated with the application of a second operating platform, the second source code comprising the at least one feature of the application; generating, based on the second source code, a second context graph; comparing the first and second context graph; and identifying, based on the comparison, at least one discrepancy. Other variants and embodiments are broadly contemplated herein.

Abstract: Subject matter disclosed herein may relate to programmable fabrics including correlated electron switch devices.

Abstract: Methods, systems, and computer program products for automated modularization of GUI test cases are provided herein. A method includes grouping test steps derived from one or more application test cases into multiple candidate sub-routines based on a manner in which one or more user interface elements are accessed in each of the test steps; refining the multiple candidate sub-routines to generate a given set of one or more sub-routines; and refactoring the one or more application test cases by replacing the test steps in the one or more application test cases with one or more calls to the given set of one or more sub-routines.

Abstract: Embodiments provide a computerized method for adapting automating test scripts, said method including: utilizing at least one processor to execute computer code that performs the steps of: receiving, at an input device, an original test script created to test an application; utilizing the original test script to test, using the processor, a variant of the application; identifying, using the processor, failures in the original test script when the variant of the application is being tested; and modifying, using the processor, the original test script to overcome the identified failures.

Abstract: Methods and arrangements for employing a software model transform. A software model transform is accepted, and the transform is manipulated to obtain a transform representation. At least one functional path is explored with respect to the transform representation. A trace is conducted of at least one explored path, and an abstraction of the transform is produced via utilizing the trace, the abstraction comprising a simplified semantic view of the transform.

Abstract: 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.

Abstract: This application provides to a method for identifying one or more prostate tissue samples in a database that are closest to a test prostate sample, which can be used to aid pathologists when examining prostate tissues to attain reliable and consistent diagnoses of prostate cancer. Also provided are databases and computer algorithms that can be used with such methods.

Abstract: The present disclosure relates to methods of diagnosing prostate cancer using different imaging methods. For example, it is shown herein that combining a Fourier transform infrared (FT-IR) spectroscopic image with an optical image (such as a hematoxylin and eosin image) allows for automated detection of prostate cancer with high accuracy.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: Systems and associated methods for automated repair support for input model faults are described. Embodiments automate generation of fault repair support by producing one or more repair action suggestions for a given input model containing faults. Responsive to an indication of one or more faults within the model, embodiments utilize a fault index to ascertain the nature of faults within the model and to compile one or more repair action suggestions. Users can review the repair action suggestions, and preview the impact each of these suggestions will have on the model if implemented, and select an appropriate repair action for repairing a model containing faults.

Abstract: 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