# US 2021/0240602 A1 · Unified test automation system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2021/0240602 A1 - Document ID: US20210240602A1 - Status: Published application - Kind: A1 - Application number: 17/049,403 - Filed: 2019-03-18 - Published: 2021-08-05 - Earliest claimed: 2018-03-23 - Assignees: Sungard Availability Services, LP - Applicants: Sungard Availability Services, LP - Inventors: David J. Allen; Umesh Kute; Steven Halzel - Web page: https://patentgrep.com/patent/US20210240602A1 ## CPC - G06F 11/3688: {for test execution, e.g. scheduling of test suites} - G06F 11/3476: {Data logging (G06F11/14, G06F11/2205 take precedence)} - G06F 11/3676: {for coverage analysis} - 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 An automated testing framework to coordinate functions among code management, build management, automated test, resource reservation, artifact repositories and team communication subsystems. In one embodiment specific to software development, software developers check new code into a code management subsystem, a development project tracking system, or other tools that automatically generate a build. Test suites are then automatically selected and executed based on a scope of the project or code that was built. This scope can include such attributes as what portion of the software was built, the purpose (objective) of the build, the maturity of developing that build, and so forth. In one implementation, label directives may be used to associate build scope to test suites. During or after the automated tests, other actions may then be automatically triggered, to store test results, inform the development team, stored data integrated with test definition and results, or update an artifact repository. ## Claims ### Claim 1 A programmatic, automatically executing method for executing a test suite comprising: (a) receiving notification of a code push event; (b) triggering a code build; (c) determining a test suite to execute against the code build by matching one or more label directives associated with a scope of the code build; (d) executing the test suite against a system under test; (e) if the test suite passes, i. updating test execution status to pass; (f) else if the test suite fails i. updating test execution status to fail; ii. recording a defect; and (g) storing results of the test execution. ### Claim 2 (depends on 1) The method of claim 1 wherein a build maturity attribute determines the scope. ### Claim 3 (depends on 1) The method of claim 1 wherein a purpose of the build determines the scope. ### Claim 4 (depends on 1) The method of claim 1 wherein the test suite comprises one or more test cases selected from a group consisting of must pass, sanity, regression, functional, performance, scalability, reliability, or endurance tests. ### Claim 5 (depends on 1) The method of claim 1 wherein the label directives are associated with some attribute of the test suite. ### Claim 6 (depends on 1) The method of claim 1 additionally comprising: (j) automatically reserving resources for executing the test suite; (k) releasing resources before test suite completes if at least one test case fails. ### Claim 7 (depends on 1) The method of claim 1 additionally comprising; (k) ensuring a configuration for the system under test is updated before executing the test suite. ### Claim 8 (depends on 1) The method of claim 1 additionally comprising: (l) performing a security integrity check. ### Claim 9 (depends on 1) The method of claim 1 additionally comprising: (m) copying a definition of the test suite to a clone copy in a project management system. ### Claim 10 (depends on 9) The method of claim 9 additionally comprising; (n) logging results of the test execution only to the clone copy and not to the definition of the test suite. ### Claim 11 (depends on 1) The method of claim 1 wherein the steps of detecting code push and triggering a build are performed in an integrated build management system. ### Claim 12 (depends on 1) The method of claim 1 wherein the test suite specifies execution dependencies among two or more test cases. ### Claim 13 (depends on 1) The method of claim 1 additionally comprising managing a defect lifecycle by one or more of: i. automatically logging defect details to log file; ii. entering defects into a defect management system; iii. assigning and tracking defect identifiers; iv. updating defect hit count statistics; and v. re-opening a previously resolved defect upon rediscovering the same defect. ### Claim 14 (depends on 1) The method of claim 1 executed as a service. ### Claim 15 (depends on 1) The method of claim 1 additionally comprising: performing one or more defect management lifecycle steps. ### Claim 16 A test automation system for testing a data processing system under test (SUT), the test automation system comprising: an interface to a code management system; an interface to a resource reservation system, for requesting reservation of resources within the system under test; a test suite execution engine, for executing program code for: (a) receiving notification of a code build event from the code management system; (b) determining a test suite to execute against the code build by matching one or more label directives associated with a scope of the code build; (c) requesting reservation of resources from the resource reservation system; (d) executing the test suite against the system under test; (e) if the test suite passes, i. updating a test execution status to pass; (f) else if the test suite fails i. updating a test execution status to fail; ii. recording a defect; and (g) storing results of the test execution. ### Claim 17 (depends on 16) The system of claim 16 wherein a build maturity attribute determines the scope. ### Claim 18 (depends on 16) The system of claim 16 wherein a purpose of the build determines the scope. ### Claim 19 (depends on 16) The system of claim 16 wherein the test suite comprises one or more test cases selected from a group consisting of must pass, sanity, smoke, regression, functional, performance, scalability, reliability, or endurance tests. ### Claim 20 (depends on 16) The system of claim 16 additionally comprising: (l) an interface to a project management system; and (m) wherein the program code is further for requesting the project management system to store a clone copy of the test suite before executing the test suite. ### Claim 21 (depends on 20) The system of claim 20 additionally wherein the program code is further for requesting the project management system to associate a result of the test execution only with the clone copy and not with the test suite.