# US 11,310,680 B2 · Reusing provisioned resources during heterogeneous component-based testing in a portable automation framework > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,310,680 B2 - Document ID: US11310680B2 - Status: Granted - Kind: B2 - Application number: 17/003,959 - Filed: 2020-08-26 - Published: 2022-03-03 - Granted: 2022-04-19 - Earliest claimed: 2020-08-26 - Assignees: Spirent Communications, Inc. - Applicants: Spirent Communications, Inc. - Inventors: Saif Ahmed; Alireza Akbari McQuee; Andrea Holt - Web page: https://patentgrep.com/patent/US11310680B2 ## CPC - H04W 24/02: Arrangements for optimising operational condition - G06F 11/3414: {Workload generation, e.g. scripts, playback} - G06F 11/3684: {for test design, e.g. generating new test cases} - G06F 11/3688: {for test execution, e.g. scheduling of test suites} - G06F 11/3692: {for test results analysis} - H04W 24/06: Testing, {supervising or monitoring} using simulated traffic - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract The disclosed technology for utilizing already-provisioned components in a test scenario without need to purge and re-provision the already provisioned components includes interpreting first and second sections of a test script. In the first section, the method includes encountering a reusable-resource-tag and a first instance of requesting provisioning of an associated resource, and provisioning the associated resource and designating the associated resource as reusable. In the second section, the disclosed method includes encountering a second instance of requesting provisioning of the associated resource, determining that the associated resource was designated as being reusable, and reusing an already provisioned instance of the associated resource instead of provisioning a new instance and instead of destroying the already provisioned instance and re-provisioning the associated resource. Further, extending test scripting to determining whether an associated resource has already been provisioned, and the interpreter determining that the resource was designated as being reusable. ## Claims ### Claim 1 A method of utilizing already provisioned components in a test scenario, without need to purge and re-provision the already provisioned components, including: interpreting first and second sections of a test script; in the first section, encountering a reusable-resource-tag and a first instance of requesting provisioning of an associated resource, and provisioning the associated resource and designating the associated resource as reusable; and in the second section, encountering a second instance of requesting provisioning of the associated resource, determining that the associated resource was designated as being reusable, and reusing an already provisioned instance of the associated resource instead of provisioning a new instance and instead of destroying the already provisioned instance and re-provisioning the associated resource. ### Claim 2 (depends on 1) The method of claim 1, further comprising extending test scripting to specification of whether a provisioned test component is reusable, the extending of the test scripting including: providing a test script interpreter that checks the test script to determine whether an associated resource has already been provisioned in a current test session; and the test script interpreter encountering the second instance of requesting provisioning of the associated resource and determining that the associated resource was designated as being reusable. ### Claim 3 (depends on 2) The method of claim 2, wherein the test script utilizes one of a declaration of reusability and a property flag for declaring a component reusable. ### Claim 4 (depends on 1) The method of claim 1, further including maintaining a reusability state parameter that indicates whether a provisioned resource is reusable and setting the reusability state parameter for the associated resource when the associated resource is provisioned. ### Claim 5 (depends on 4) The method of claim 4, further including checking a value of the reusability state parameter of the associated resource when processing the second instance of the request for provisioning of the associated resource. ### Claim 6 A tangible non-transitory computer readable storage media impressed with computer program instructions for utilizing already provisioned components in a test scenario, without need to purge and re-provision the already provisioned components, the computer program instructions, when executed on one or more processors, causing the one or more processors to implement operations including: interpreting first and second sections of a test script; in the first section, encountering a reusable-resource-tag and a first instance of requesting provisioning of an associated resource, and provisioning the associated resource and designating the associated resource as reusable; and in the second section, encountering a second instance of requesting provisioning of the associated resource, determining that the associated resource was designated as being reusable, and reusing an already provisioned instance of the associated resource instead of provisioning a new instance and instead of destroying the already provisioned instance and re-provisioning the associated resource. ### Claim 7 (depends on 6) The tangible non-transitory computer readable storage media of claim 6, wherein the operations further include extending test scripting to specification of whether a provisioned test component is reusable, the extending of the test scripting including: providing a test script interpreter that checks the test script to determine whether an associated resource has already been provisioned in a current test session; and the test script interpreter encountering the second instance of requesting provisioning of the associated resource and determining that the associated resource was designated as being reusable. ### Claim 8 (depends on 7) The tangible non-transitory computer readable storage media of claim 7, wherein the test script utilizes one of a declaration of reusability and a property flag for declaring a component reusable. ### Claim 9 (depends on 6) The tangible non-transitory computer readable storage media of claim 6, wherein the operations further include maintaining a reusability state parameter that indicates whether a provisioned resource is reusable and setting the reusability state parameter for the associated resource when the associated resource is provisioned. ### Claim 10 (depends on 9) The tangible non-transitory computer readable storage media of claim 9, wherein the operations further include checking a value of the reusability state parameter of the associated resource when processing the second instance of the request for provisioning of the associated resource. ### Claim 11 A system including one or more processors coupled to memory, the memory loaded with computer instructions to utilize already provisioned components in a test scenario, without need to purge and re-provision the already provisioned components, the computer instructions, when executed on the one or more processors, causing the one or more processors to implement actions including: interpreting first and second sections of a test script; in the first section, encountering a reusable-resource-tag and a first instance of requesting provisioning of an associated resource, and provisioning the associated resource and designating the associated resource as reusable; and in the second section, encountering a second instance of requesting provisioning of the associated resource, determining that the associated resource was designated as being reusable, and reusing an already provisioned instance of the associated resource instead of provisioning a new instance and instead of destroying the already provisioned instance and re-provisioning the associated resource. ### Claim 12 (depends on 11) The system of claim 11, wherein the actions further include extending test scripting to specification of whether a provisioned test component is reusable, the extending of the test scripting including: providing a test script interpreter that checks the test script to determine whether an associated resource has already been provisioned in a current test session; and the test script interpreter encountering the second instance of requesting provisioning of the associated resource and determining that the associated resource was designated as being reusable. ### Claim 13 (depends on 12) The system of claim 12, wherein the test script utilizes one of a declaration of reusability and a property flag for declaring a component reusable. ### Claim 14 (depends on 11) The system of claim 11, wherein the actions further include maintaining a reusability state parameter that indicates whether a provisioned resource is reusable and setting the reusability state parameter for the associated resource when the associated resource is provisioned. ### Claim 15 (depends on 14) The system of claim 14, wherein the actions further include checking a value of the reusability state parameter of the associated resource when processing the second instance of the request for provisioning of the associated resource.