Google Inc.

Townsend Street Labs, Inc.

Okta, Inc.

Appurify, Inc.

Jay Srinivasan

Pratyus Patnaik

Manish Lachwani

Nathaniel Ackerman Rook

David Colby Kaneda

Rajhans Samdani

Suchit Agarwal

Marissa Mary Montgomery

Rahul Jain

Raymond Tonsing

Timothy D Wang

William Stone Potter

Systems for processing queries may first determine correspondence between the parameters of the query and a set of existing data entries, a set of previous queries that have been received, or both the existing data entries and the previous queries. If the query parameters do not correspond to the data entries or pervious queries, correspondence is determined between the query parameters and group data that associates at least a subset the query parameters with a particular group that may generate a response to the query. The same group or the generated response may be used when similar queries are received. If the group transmits the query to a different group or if negative user feedback is received, the group data may be modified to indicate the different group or to remove the association with the initial group that received the query.

System for routing of requests

Systems and methods for determining whether a data entry has deprecated may receive a query from a user device and provide a data entry responsive to the query. If user feedback associated with the response indicates that the response resolved the query, confirmation data that associates the data entry with the query parameters is generated. If the user feedback indicates that the response did not resolve the query, existing confirmation data is accessed to determine whether a previous association between the data entry and the parameters of the query was generated. If correspondence between the confirmation data and the query and response is determined, a notification indicating the deprecation of the data entry is generated and the data entry may be suppressed from future output.

System for determining and modifying deprecated data entries

A system for processing queries from a user device may first generate an augmented query by determining weight values and synonyms for at least a portion of the parameters in the query, and adding or removing one or more query parameters. Correspondence between the augmented query and an existing set of data entries may be used to determine a subset of data entries that may be responsive to the query. Correspondence may then be determined between the augmented query and previous queries that were addressed by the subset of data entries, to determine a particular previous query having the greatest correspondence with the augmented query. The data entry associated with the particular previous query may be used to generate a response to the query received from the user device.

Request processing system

Described herein is a system generating and sending shortcuts from a sending device to a receiving device. In one implementation, the sending device generates shortcut reference data (SRD) which includes application data indicative of a state of an application and a hash based on the application data. The SRD is sent to a shortcut server, while shortcut delivered data (SDD) which includes the hash value is sent to a recipient device. The recipient device may use the hash value of the SDD to request and receive the application data from the shortcut server. Once received, an application installed on the recipient device recreates on the recipient device the state of the application as originally presented on the sending device. As a result, a user at the sending device may share their experience with a user at the receiving device. Fees associated with the use of the system may be calculated.

Application experience sharing system

Application validation is performed based on object level hierarchy data associated with the application. An application is executed on a physical or emulated host device, and assembly code is generated for the executing application. The assembly code is analyzed to identify objects associated with the application, and to identify relationships between the objects. Based on the object and relationship data, an object level hierarchy is generated for the application. Validation of the application may be performed by comparing an object level hierarchy for a current version of the application to a previously generated hierarchy for a previous version of the application to identify differences between the two hierarchies.

Validating applications using object level hierarchy analysis

A system is described for testing markup language-based applications, such as a web page, executing on an external computing device. A development device executes development tool modules which may include a proxy module and a driver module. The proxy module enables communication between one or more modules which execute on the development device and one or more embedded test tools on the computing device. The driver module provides a command line interface to facilitate automated testing, and generates commands appropriate to the use of the embedded test tools and may use the proxy module to communicate with the computing device. Using the proxy module, the driver module, or both, a developer is able to test and interact with a markup language application executing on the computing device with a variety of development modules.

System for testing markup language applications on a device

A system is described for testing an application on one or more host devices in a host device farm. A build server uses an application programming interface ('API') to send a test package containing an application to a test server. The sending may be initiated by a single action such as a click on a control in a user interface, or may be automatic such as on completion of a build. The test server may then execute and test the application across one or more host devices. These host devices may include smartphones, tablet computers, televisions, set-top boxes, in-vehicle computer systems, home entertainment systems, and so forth. Test results based at least in part on the execution of the application module on the one or more host devices may then be provided to the build server.

Application testing system with application programming interface

Systems and methods are described for generating a test executable used for testing an application locally on a host device. A user interface allows selection of particular test modules for use. Based on the selected modules a test executable is generated. The test executable functionality may integrated with the application or be independent of the application. The host device executes the test executable which enables testing and debugging on the local device.

System for module selection in software application testing including generating a test executable based on an availability of root access

A system is described for remotely testing markup language and script language based applications executing on a computing device. A development device such as a desktop computer executes one or more development tool modules. A communication module and an unpack module are deployed to a computing device which executes the application under test. These modules serve to connect the development tool module executing on the development device to an embedded test tool executing on the computing device. Using this connection, the development tool module is able to interactively test and interact with the application executing on the computing device.

System for testing markup language applications

Testing of a service is enabled through extraction of object data from an application interacting with the service. An application is executed on a physical or emulated host device, and assembly code is generated for the executing application. The assembly code is analyzed to identify objects associated with the application, and to identify relationships between the objects. Data stored in member variables of the objects is retrieved by setting analysis points at which to extract member variable data during execution of the application. Based on the object data, relationship data, and retrieved member variable data, transaction data is identified for a transaction between the application and the service. The transaction data may be provided to enable a test device to replay the transaction during load testing or other testing of the service.

Application testing through object level code inspection

Techniques are described for debugging an application executing on a remote host device. A daemon executing on the host device is instructed, from a server device, to install an application to be debugged and to launch a remote debug module on the host device. A communication session is established between the remote debug module and a local debug module executing on the server device. Debug commands received at the local debug module are communicated to the remote debug module and employed during the debugging of the application. Debug output from the debugging session may be provided to the server device via a mount point into shared memory on the host device.

Remote application debugging

A network profile describes one or more characteristics of a network including bandwidth, latency, rate of packet loss, duplication, corruption, or reordering, and so forth. Using the network profile, one or more adjustments are made to network traffic between a server device and an application executing on a client device. These adjustments virtualize the profiled network and emulate how the profiled network affects traffic. Such virtualization may enable an application to be tested under different network conditions corresponding to different network profiles.

Growing community of inventors

San Francisco, CA, United States of America

Jay Srinivasan