Containerized Test Automation for Cloud Service Code Changes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing CI/CD pipelines for open standard cloud services applications face challenges in efficient and comprehensive testing, particularly due to the need for large-scale testing on deployment nodes and limited custom test cases, which can lead to undetected code issues and disruptive testing processes.

Innovation Solution

Implementing a system that creates containers encapsulating the necessary software for test suites, automating their execution as quality gates in the CI/CD pipeline, and generating standardized human-readable scorecards for code changes, allowing early detection and correction of defects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If numerous tests are run on deployment nodes to test open standard cloud services applications, then testing coverage is improved, but operational disruptions increase

Engineering Contradiction:
Improvetesting coverageVSAvoidoperational efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent creates test containers and executes test suites before code changes are deployed to production environments. By performing testing in advance on isolated test containers rather than on deployment nodes, the system achieves comprehensive testing coverage while preventing operational disruptions to production systems.

Inventive Principle:
Principle #10Preliminary action

2Extent of automation

If standard test suites are used in CI/CD pipelines, then testing automation is improved, but detection of custom deployment issues deteriorates

Engineering Contradiction:
Improvetesting automationVSAvoiddefect detection accuracy
Core Design Contradiction:
Extent of automationVSMeasurement precision

Solution Approach 1:

The patent enables organizations to customize test suites for specific deployment scenarios and requirements while maintaining the automation framework. The system allows different test configurations, test cases, and parameters to be tailored to specific cloud service deployments, ensuring both automation efficiency and precise detection of custom deployment issues.

Inventive Principle:
Principle #3Local quality

3Stability of the object's composition

If testing is performed later in the release candidate process, then operational stability is maintained, but defect identification time increases

Engineering Contradiction:
Improveoperational stabilityVSAvoiddefect identification time
Core Design Contradiction:
Stability of the object's compositionVSLoss of time

Solution Approach 1:

The patent implements testing earlier in the CI/CD pipeline by creating and executing test containers before code changes reach production. This preliminary testing approach identifies defects early in the development process, reducing the time required for defect identification and correction while maintaining operational stability through isolated test environments.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12625796B2Testing automation for open standard cloud services applications
Publication Date: 2026.05.12 AT&T INTELLECTUAL PROPERTY I L P
  • US12625796B2 patent drawing
  • US12625796B2 patent drawing
  • US12625796B2 patent drawing

AI summary

A method performed by a processing system including at least one processor includes monitoring a software repository for code changes, detecting a code change in a software instance that is stored in the software repository, generating a container image of the software instance in response to the detecting, creating a container for the container image, wherein the container encapsulates software needed to run a test suite on the software instance, configuring a testing platform for a development environment used to create the software instance, executing the test suite for the software instance by running the software encapsulated in the container on the testing platform, and publishing a test output of the test suite as a human-readable scorecard for the software instance.