International Business Machines Corporation

David Richard Jones

Christopher N Bailey

Sandra Hayward

Matthew Paul Wilson

Ian O Partridge

Ian Partridge

Robert Bruce Nicholson

Andrew James Stanford-Clark

Andrew Michael Lees

Alwyn R Lobo

Stuart J Hayton

Johanna Saladas Zaaijer

Graeme P Vetterlein

Christopher Neil Bailey

A method, computer program product, and computer system for testing of robotic process automation robots that interact with user interfaces. The method includes obtaining analysis of commands in a robotic process automation script to determine interaction of the commands with one or more user interface applications. The method includes extracting a list of commands that interact with user interface controls and grouping the commands by user interface application. The method then generates a set of tests for each user interface application, with the set of tests including the commands for user interface control interactions and assertions of a state of each user interface control interacted with. The method provides a set of tests for a robot for each user interface application.

Test generation for robotic process automation robots that interact with user interfaces

Prefetch of microservices for incoming requests. The method determines for an incoming request a Service Level Objective (SLO) requirement for latency of a request type of the incoming request. The method generates a set of possible microservice sequences for the request including a probability of occurrence of each of the possible microservice sequences and determines a set of prefetch permutations for the set of possible microservice sequences. A latency score is calculated for each prefetch permutation and any prefetch permutations that do not meet the SLO requirement for latency of the request type are eliminated. An optimal prefetch permutation of the remaining prefetch permutations is selected by considering a total cost of the prefetch permutation based on a cost of running each microservice in the set of sequences.

Prefetch of microservices for incoming requests

Concepts for middleware in a web framework are presented. One example comprises defining a target object type configured to hold results of a middleware function. A first object for an application is received and a process of the middleware function is performed, using the first object, to generate a process result. Based on the process result, a second object of the target object type is generated, after which the second object is provided to the application.

Middleware in web framework

A method, system, and computer program product for predicting microservices required for incoming requests for reducing the start latency of serverless microservices. The method may include obtaining tracing data of microservices of an application for historical requests processed by the application. The method may also include grouping the tracing data based on common request attributes. The method may also include aggregating each group into rules relating the common request attributes to lists of microservices. The method may also include building a predictive model formed of the rules for processing incoming requests to obtain a list of predicted microservices required for the incoming request based on attributes of the incoming request.

Predicting microservices required for incoming requests

Disclosed is a program for validating a web cache independent of an origin server. A computer in between a client computer and the origin server computer receives a request for a resource and an entity tag (ETag) corresponding to the request. The computer forwards the request to the origin server and subsequently receives the resource. The computer generates an ETag for the received resource and compares the generated ETag to the ETag corresponding to the request. If the ETags match, the computer sends an indication toward the client computer that the resource has not been modified.

Using entity tags (ETags) in a hierarchical HTTP proxy cache to reduce network traffic

A broker-based publish/subscribe messaging system is administered in which a session-based network connection (such as TCP/IP) from an administrator publish/subscribe client application is established with a broker. Administration commands are received as messages from the administrator publish/subscribe client application at the broker via the session-based network connection and response messages are sent from the broker via the session-based network connection to only the administrator publish/subscribe client application.

Growing community of inventors

Eastleigh, United Kingdom

David Richard Jones