# US 2017/0286267 A1 · Fast and efficient continuous integration test system for large scale services

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0286267 A1
- Document ID: US20170286267A1
- Status: Published application
- Kind: A1
- Application number: 15/088,891
- Filed: 2016-04-01
- Published: 2017-10-05
- Earliest claimed: 2016-04-01
- Assignees: Google Inc.
- Applicants: Google Inc.
- Inventors: Sonal JAIN; Nathan BAIN; Panchao YANG
- Web page: https://patentgrep.com/patent/US20170286267A1

## CPC

- G06F 11/3698: Environments for analysis, debugging or testing of software
- G06F 11/368: {for test version control, e.g. updating test cases to a new software version}
- G06F 11/3684: {for test design, e.g. generating new test cases}
- G06F 11/3688: {for test execution, e.g. scheduling of test suites}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Methods and systems for implementing proxy layers an a proxy layer management framework for performing integration testing of test components in a target test environment. Proxy layers are established between components that interact in a system and provide an interface based on a communication protocol, such as HTTP or RPC. Proxy layers axe configured, via a proxy layer manager to reroute communication, based on the communication protocol, to and from test components to simulate integration testing of the components in the target environment. Proxy layers may also apply rules that reroute traffic based on certain conditions for more effective, safer, and specific testing. Also, the routed communications may be traced and logged for testing and debugging.

## Claims

### Claim 1

A method for testing a component in a software system, the method comprising:
establishing a target test environment which includes multiple components that interact with each other via proxy layers;
adding a test component having functionality that corresponds to a specific target component in the target test environment;
configuring the proxy layers associated with the specific target component to route traffic intended for the specific target component to the test component, and receive traffic from the test component;
executing one or more tests in the target test environment on the test component; and
routing traffic, via the proxy layers, between the test component and one or more components of the target test environment instead of the specific target component.

### Claim 2 (depends on 1)

The method of claim 1, further comprising of a proxy layer manager to configure the routing settings of the proxy layers in the target test environment.

### Claim 3 (depends on 2)

The method of claim 2, further comprising of a web front end for managing and configuring the routing settings of the proxy layer manager in the target test environment.

### Claim 4 (depends on 1)

The method of claim 1, further comprising of a web front end for managing and configuring the routing settings of the proxy layers in the target test environment.

### Claim 5 (depends on 1)

The method of claim 1, further comprising of applying routing-rules to the proxy layers for rule-based routing of traffic through the proxy layers.

### Claim 6 (depends on 5)

The method of claim 5, wherein the routing-rules are configured to route traffic from some users to the test component and traffic from other users to the specific target component.

### Claim 7 (depends on 1)

The method of claim 1, further comprising of generating trace and session data of traffic between the proxy layers.

### Claim 8 (depends on 1)

The method of claim 1, further comprising of a service manager to launch and manage the test component in the target test environment.

### Claim 9 (depends on 1)

The method of claim 1, wherein adding a test component includes adding multiple test components that each contain a portion of functionality of the specific target component in the target environment.

### Claim 10 (depends on 1)

The method of claim 1, wherein adding a test component includes adding a single test component that contains functionalities of multiple specific target components in the target environment.

### Claim 11

A proxy layer management system for testing a component in a software system, the system comprising:
one or more processing devices and one or more storage devices storing instructions that, when executed by the one or more processing devices, causes the one or more processing device to:
establish a target test environment which includes multiple components that interact with each other via proxy layers;
add a test component having functionality that corresponds to a specific target component in the target test environment;
configure the proxy layers associated with the specific target component to route traffic intended for the specific target component to the test component, and receive traffic from the test component;
execute one or more tests in the target test environment on the test component; and
route traffic, via the proxy layers, between the test component and one or more components of the target test environment instead of the specific target component.

### Claim 12 (depends on 11)

The system of claim 11, further comprising of a proxy layer manager to configure the routing setting of the proxy layers in the target test environment.

### Claim 13 (depends on 12)

The system of claim 12, further comprising of a web front end for managing and configuring the routing settings of the proxy layer manager in the target test environment.

### Claim 14 (depends on 11)

The system of claim 11, further comprising of a web front end for managing and configuring the routing settings of the proxy layers in the target test environment.

### Claim 15 (depends on 11)

The system of claim 11, further comprising of applying routing-rules to the proxy layers for rule-based routing of traffic through the proxy layers.

### Claim 16 (depends on 15)

The system of claim 15, wherein the routing-rules are configured to route traffic from some users to the test component and traffic from other users to the specific target component.

### Claim 17 (depends on 11)

The system of claim 11, further comprising of generating trace and session data of traffic between the proxy layers.

### Claim 18 (depends on 11)

The system of claim 11, further comprising of a service manager to launch and manage the test component in the target test environment.

### Claim 19 (depends on 11)

The system of claim 11, wherein adding a test component includes adding multiple test components that each contain a portion of functionality of the specific target component in the target environment.

### Claim 20 (depends on 11)

The system of claim 11, wherein adding a test component includes adding a single test component that contains functionalities of multiple specific target components in the target environment.
