# US 2021/0240597 A1 · A code editor for user interface component testing

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

- Number: US 2021/0240597 A1
- Document ID: US20210240597A1
- Status: Published application
- Kind: A1
- Application number: 16/778,059
- Filed: 2020-01-31
- Published: 2021-08-05
- Earliest claimed: 2020-01-31
- Assignees: salesforce.com, inc.
- Applicants: salesforce.com, inc.
- Inventors: Xiaoyi Chen; Billy Ma; William Braden Hays
- Web page: https://patentgrep.com/patent/US20210240597A1

## CPC

- G06F 11/3644: {by instrumenting at runtime}
- G06F 11/3688: {for test execution, e.g. scheduling of test suites}
- G06F 8/38: for implementing user interfaces
- G06F 11/362: Debugging of software
- G06F 11/3636: {by tracing the execution of the program}
- G06F 11/3698: Environments for analysis, debugging or testing of software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system for conducting user interface (UI) software component testing has been developed. The test of the UI software component is initiated and a display of the test results are shown to a user in a browser used in the testing. A code editor used for debugging by the user receives the test results from the browser and presents the test results to the user for debugging. The browser webview and the code editor are simultaneously displayed to the user in a dual screencast window during the UI software testing.

## Claims

### Claim 1

A system for conducting user interface (UI) software component testing, comprising:
a browser for use in testing a UI software component, where the test of the UI software component is initiated and a display of the test results are shown to a user in the browser;
a code editor for debugging by the user, where the code editor receives the test results from the browser and presents the test results to the user for debugging; and
where the browser and the code editor are simultaneously displayed to the user in a dual screencast window during the UI software testing.

### Claim 2 (depends on 1)

The system of claim 1, where the browser is a headless browser.

### Claim 3 (depends on 1)

The system of claim 1, where the browser is launched through a debugging port.

### Claim 4 (depends on 3)

The system of claim 3, where the debugging port is remotely located.

### Claim 5 (depends on 1)

The system of claim 1, where the code editor utilizes an application programming interface (API).

### Claim 6 (depends on 5)

The system of claim 5, where the API is extensible.

### Claim 7 (depends on 1)

The system of claim 1, where the code editor is an inline code editor.

### Claim 8 (depends on 1)

The system of claim 1, where the code editor launches a webview prior to testing the UI software component.

### Claim 9 (depends on 8)

The system of claim 8, where the browser screencasts the webview of the copy editor for the user.

### Claim 10 (depends on 8)

The system of claim 8, where the webview shows the testing actions for the UI software component.

### Claim 11 (depends on 8)

The system of claim 8, where the webview shows the testing progress for the UI software component.

### Claim 12 (depends on 8)

The system of claim 8, where the webview shows the testing results at the testing break points for the UI software component.

### Claim 13

A method for conducting user interface (UI) software component testing, comprising:
parsing code of the UI software component to generate test information at test locations in the code of the UI software component with a code editor;
displaying testing actions with the code editor;
setting testing breakpoints at various line locations in the code of the UI software component;
launching a browser with a debugging port;
launching a webview with the code editor;
displaying the UI software component testing progress to a user with a screencast from the browser of the webview;
launching a debug configuration with the code editor with the test information and attaching to the debugging port of the browser;
navigating to a test uniform resource locater (URL) with the browser from the parsed test information;
collecting the test results with the browser; and
presenting the test results in the code editor to a user.

### Claim 14 (depends on 13)

The method of claim 13, where the browser is a headless browser.

### Claim 15 (depends on 13)

The method of claim 13, where the debugging port is remotely located.

### Claim 16 (depends on 13)

The method of claim 13, where the code editor utilizes an extensible application programming interface (API).

### Claim 17 (depends on 13)

The method of claim 13, where the code editor is an inline code editor.

### Claim 18 (depends on 13)

The method of claim 13, where the webview shows the testing results at the testing break points for the UI software component.