US 11,853,197 B2
Testing automation for open standard cloud server applications
Andrew Leasck, Saint Louis, MO (US); Douglas Paul Schveninger, Wildwood, MO (US); Oded Le'Sage, Austin, TX (US); Bryan Strassner, Union, MO (US); and Kelly Carter, Allen, TX (US)
Assigned to AT&T Intellectual Property I, L.P., Atlanta, GA (US)
Filed by AT&T Intellectual Property I, L.P., Atlanta, GA (US)
Filed on Jun. 15, 2021, as Appl. No. 17/348,439.
Prior Publication US 2022/0398188 A1, Dec. 15, 2022
Int. Cl. G06F 11/36 (2006.01); H04L 67/00 (2022.01); G06F 9/451 (2018.01)
CPC G06F 11/3688 (2013.01) [G06F 9/451 (2018.02); G06F 11/3664 (2013.01); H04L 67/34 (2013.01)] 19 Claims
OG exemplary drawing
 
1. A method comprising:
monitoring, by a processing system including at least one processor, a software repository using a software program that checks for code changes;
detecting, by the processing system during the monitoring, a code change in a software instance that is stored in the software repository;
generating, by the processing system in response to the detecting, a container image of the software instance including the code change;
publishing, by the processing system, the container image to a continuous integration/continuous delivery pipeline mirror;
creating, by the processing system after the publishing the container image to the continuous integration/continuous delivery pipeline mirror, a container for the container image, wherein the container encapsulates software needed to run a test suite on the software instance;
configuring, by the processing system, a testing platform for a development environment used to create the software instance;
executing, by the processing system, the test suite for the software instance by running the software encapsulated in the container on the testing platform, wherein the executing is automated as a quality gate during a stage of a development of the software instance in a continuous integration/continuous delivery pipeline, and wherein the quality gate is designed to verify that the software instance meets a predefined standard before the development is permitted to proceed to a next stage of the development that follows the stage; and
publishing, by the processing system, a test output of the test suite as a human-readable scorecard for the software instance, wherein the human-readable scorecard identifies at least one of: the test suite, a number of test cases that were run during the executing of the test suite, a number of test cases that were skipped during the executing of the test suite, an amount of time for which the test suite was executed, a number of successful test cases run during the executing of the test suite, or a number of failing test cases run during the executing of the test suite.