# US 2021/0173766 A1 · Testing as a service

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

- Number: US 2021/0173766 A1
- Document ID: US20210173766A1
- Status: Published application
- Kind: A1
- Application number: 16/705,495
- Filed: 2019-12-06
- Published: 2021-06-10
- Earliest claimed: 2019-12-06
- Assignees: Cerner Innovation, Inc.
- Applicants: Cerner Innovation, Inc.
- Inventors: Anindya Deb; Sujoy Acharya; Anand Janakunavar; Sambit Kumar Sahoo; Swaroop Chakraborty; Rahul Kar; Dibyojyoti Senapati; Saurav Kumar; Arnab Das; Sandipan Ghorai; Amit Das Sarkar
- Web page: https://patentgrep.com/patent/US20210173766A1

## CPC

- G06F 11/3688: {for test execution, e.g. scheduling of test suites}
- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 11/3684: {for test design, e.g. generating new test cases}
- G06F 11/3692: {for test results analysis}
- G06F 11/3698: Environments for analysis, debugging or testing of software
- G06Q 10/0633: Workflow analysis
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Embodiments of the present disclosure relate to systems, methods, and user interfaces that automate the workflow testing process. Users can configure, automate and execute repeating workflow tests associated with software updates or upgrades. In doing so, issues with the updates or upgrades are proactively prevented. To do so, a selection of one or more business processes is initially received. The one or more business processes are combined into a client workflow. Test data and assertion types are received for each business process of the one or more business processes. A script and metadata containing the client workflow name and the one or more business process names utilized to create the client workflow is stored and the client workflow can be executed in a target environment. Any errors in the client workflow are detected and a notification is provided to a user for follow-up and resolution.

## Claims

### Claim 1

One or more computer storage media having computer-executable instructions embodied thereon that, when executed by a computer, causes the computer to perform operations, the operations comprising:
receiving a selection of one or more business processes, the one or more business processes being combined into a client workflow;
receiving test data and assertion types for each business process of the one or more business processes;
storing a script and metadata containing a name of the client workflow and names of the one or more business processes utilized to create the client workflow;
executing the client workflow in a target environment; and
detecting errors in the client workflow and provide a notification to a user for follow-up and resolution.

### Claim 2 (depends on 1)

The media of claim 1, wherein each business process of the one or more business processes is associated with a system process that launches a separate user interface.

### Claim 3 (depends on 1)

The media of claim 1, further comprising prompting the user to interact with a user interface for each business process of the one or more business processes.

### Claim 4 (depends on 1)

The media of claim 1, further comprising prompting the user to validate expected results.

### Claim 5 (depends on 1)

The media of claim 1, wherein each business process of the one or more business processes is connected through connectors, each connector being a trigger to a next process in the client workflow.

### Claim 6 (depends on 1)

The media of claim 1, wherein the selection of one or more business processes is received by intercepting user interaction with the one or more business processes, determining a sequence of execution, and identifying document object model events.

### Claim 7 (depends on 1)

The media of claim 1, wherein the script and metadata containing the name of the client workflow and the names of the one or more business processes utilized to create the client workflow are stored in JSON format in a client environment for workflow code generation.

### Claim 8 (depends on 1)

The media of claim 1, wherein the client workflow verifies a stability and reliability of a software change or update.

### Claim 9 (depends on 1)

The media of claim 1, wherein the client workflow comprises one or business processes including an admission process, an encounter process, or a discharge process.

### Claim 10

A computerized method comprising:
receiving a selection of one or more business processes, the one or more business processes being combined into a client workflow;
receiving test data and assertion types for each business process of the one or more business processes;
storing a script and metadata containing a name of the client workflow and names of the one or more business processes utilized to create the client workflow;
executing the client workflow in a target environment; and
detecting errors in the client workflow and providing a notification to a user for follow-up and resolution.

### Claim 11 (depends on 10)

The method of claim 10, wherein each business process of the one or more business processes is associated with a system process that launches a separate user interface.

### Claim 12 (depends on 10)

The method of claim 10, further comprising prompting the user to interact with a user interface for each business process of the one or more business processes.

### Claim 13 (depends on 10)

The method of claim 10, further comprising prompting the user to validate expected results.

### Claim 14 (depends on 10)

The method of claim 10, wherein each business process of the one or more business processes is connected through connectors, each connector being a trigger to a next process in the client workflow.

### Claim 15 (depends on 10)

The method of claim 10, wherein the selection of one or more business processes is received by intercepting user interaction with the one or more business processes, determining a sequence of execution, and identifying document object model events.

### Claim 16 (depends on 10)

The method of claim 10, wherein the script and metadata containing the name of the client workflow and the names of the one or more business process names utilized to create the client workflow are stored in JSON format in a client environment for workflow code generation.

### Claim 17 (depends on 10)

The method of claim 10, wherein the client workflow verifies a stability and reliability of a software change or update.

### Claim 18 (depends on 10)

The method of claim 10, wherein the client workflow comprises one or business processes including an admission process, an encounter process, or a discharge process.

### Claim 19

A system comprising:
a processor; and
a computer storage medium storing computer-usable instructions that, when used by the processor, cause the processor to:
receive a selection of one or more business processes, the one or more business processes being combined into a client workflow, wherein the selection of one or more business processes is received by intercepting user interaction with the one or more business processes, determining a sequence of execution, and identifying document object model events;
receive test data and assertion types for each business process of the one or more business processes;
store a script and metadata containing a name of the client workflow and the names of the one or more business processes utilized to create the client workflow, wherein the script and metadata containing the client workflow name and the one or more business process names utilized to create the client workflow are stored in JSON format in a client environment for workflow code generation;
execute the client workflow in a target environment to verify a stability and reliability of a software change or update; and
detect errors in the client workflow and provide a notification to a user for follow-up and resolution.

### Claim 20 (depends on 19)

The system of claim 19, further comprising:
prompting the user to interact with a user interface for each business process of the one or more business processes; and
prompting the user to validate expected results.
