International Business Machines Corporation

John Erik Wittern

Jim Alain Laredo

Aleksander A Slominski

Yunhui Zheng

Christopher Charles Young

Maja Vukovic

Julian Timothy Dolby

Sriram K Rajagopal

Vinod Muthusamy

Philippe Suter

Annie Tsui Tsui Ying

Annie T Ying

Wei Tan

Gennaro A Cuomo

Hani Talal Jamjoom

Radu Marinescu

Shriram Rajagopalan

Arjun Natarajan

Alice-Maria Marascu

Charles Arthur Jochim

Daniel J Williams

Carlos A Alzate Perez

Annie T T Ying

Fei Wang

Biplav Srivastava

Fei C Wang

Salman Abdul Baset

Rong Nickle Chang

Fabio A Oliveira

Jinqiu Yang

Alan Cha

Gerald Schermann

A debugging tool and method for statically verifying programs that invoke web-based services through API calls is provided. The tool receives source code that comprises one or more invocation of web APIs for requesting web-based services. The tool also receives a set of web API specifications. The tool extracts a set of request information for each web API invocation in the source code, the set of request information including a usage string of an URL endpoint. The tool verifies whether the set of request information complies with the received web API specifications and reports a result of the verification.

Analysis to check web API code usage and specification

An application automatically composed using natural language processing. A natural language input comprising one or more application requirements is received via an interface. The natural language input is parsed to extract one or more chunks, each chunk representing one of the application requirements, and at least one of the chunks representing at least one of one or more main functionalities described by the application requirements. A coarse architecture logically arranging the main functionalities to satisfy the application requirements is inferred according to the chunks. Existing assets corresponding to the chunks are identified, each asset associated with at least one of the main functionalities. The identified assets are assembled according to the coarse architecture. The assembled assets are deployed as an application.

Automated application composer with natural language processing

Aspects of the invention include assessing, by a management layer executing on a first processor, a query from a client application requesting data from a server. The assessing occurs prior to the query being executed by a provider. The assessing includes extracting, by the management layer, characteristics of the query. The management layer compares the extracted query characteristics with a policy defined by the provider. Based at least in part on results of the comparing, it is determined by the management layer whether the query is permitted to be executed by the provider at the server. The management layer initiates execution of the query at the server in response to determining that the query is permitted to be executed. The management layer prevents execution of the query at the server in response to determining that the query is not permitted to be executed.

GraphQL management layer

A computer-implemented method for creating a web programming interface (API) description may include parsing an API usage dataset with a processor to identify a plurality of nodes in each of a plurality of uniform resource locators (URLs), and tagging path parameters for the plurality of nodes. Tagging the path parameters may include identifying, with the processor, which nodes are static parts of the URLs, and identifying, with the processor, which of the nodes are path parameters for the URLs. The method may further include aggregating, with the processor, a plurality of node types based on the tagged path parameters and the static parts of the URLs, and outputting, via the processor, an API description based on the aggregated plurality of node types.

Automated generation of web API descriptions from usage data

Techniques regarding autonomously generating one or more graph query language schemas are provided. For example, one or more embodiments described herein can comprise a system, which can comprise a memory that can store computer executable components. The system can also comprise a processor, operably coupled to the memory, and that can execute the computer executable components stored in the memory. The computer executable components can comprise an interface component, operatively coupled to the processor, that can generate a schema for a graph query language wrapper that can translate a query to a request against a target application programming interface. The schema can comprise a sanitation map that can delineate a relation between a raw data format expected by the target application programming interface and a sanitized data format exposed by the graph query language wrapper.

Autonomous generation of a graph query language interface on top of an application programming interface

A method and system of determining a health state of a microservice based application includes extracting traces of multiple variants of a microservice-based application. Topologies of the multiple variants are inferred based on the extracted traces. One or more topological differences of each of the multiple variants are identified based on the extracted traces. Each topological difference is ranked. The topological differences of the microservice-based application are displayed on a user interface, including a microservice map of the topological differences and a listing of a top ranking of the topological differences.

Topology-aware continuous evaluation of microservice-based applications

A method and system of matching an application program interface (API) code usage with an API specification are provided. A program having an API code usage is received and its features are extracted therefrom. Features from meta data of a plurality of API specifications are extracted. For each API specification of the plurality of API specifications, a match probability with the API code usage is determined. An API specification having a highest probability is determined. The API code usage is matched with the API specification having the highest probability.

Probabilistic matching of web application program interface code usage to specifications

A computer implemented method for testing an application according to usage data includes receiving an application to be tested and a set of usage data corresponding to the application to be tested, wherein the set of usage data corresponds to previously executed code sequences, identifying one or more code sequences of interest corresponding to the received application, wherein the code sequences of interest correspond to codes sequences that are configured to exercise the received application, extracting concrete usages of the code sequence of interest from the received set of usage data, generating one or more test cases for the application according to the extracted usages, and providing the one or more generated test cases. The method may additionally include testing the application according to the one or more generated test cases.

Gray-box testing based on concrete usages

Techniques for autonomously generating a code usage summary associated with a web application programming interface request are provided. In one example, a computer-implemented method can comprise evaluating, by a system operatively coupled to a processor, data from a data repository, wherein the evaluating is based on a defined machine learning process. Also, the computer-implemented method can comprise generating, by the system, a usage summary of the data, wherein the usage summary is based on a statistic derived from a web application programming interface request, and the web application programming interface request is associated with the data.

Approach to summarize code usage

A tool that automatically generates a web API specification from a web API documentation is provided. The tool extracts a base uniform resource locator (URL) string from the received documentation by identifying URL strings in the documentation that are valid web application programming interface (API) calls. The tool infers path templates by identifying and clustering path expressions in the documentation that invoke the same URL endpoints. The tool extracts hypertext transfer protocol (HTTP) request type and query parameters associated with the inferred path templates. The tool generates a specification that includes the extracted base URL, the inferred path templates, the extracted HTTP request types, and the extracted query parameters.

Generating web API specification from online documentation

A method and system of determining whether a specification is an accurate representation of an application program interface (API) is provided. The specification is received electronically over a network. Service calls to be tested are identified based on the specification. A test case is created for each of the identified service calls. A sequence is created for the test cases. A test plan is generated based on the created sequence. The generated test plan is executed. Upon identifying an error in response to the executed test plan, a notification is generated, indicating that the specification is not an accurate representation of the API.

Automatically running tests against WEB APIs based on specifications

Growing community of inventors

New York, NY, United States of America

John Erik Wittern