community 
Job Scheduling (SnQ) should allow for Command Scripts calls between Tests
When you edit a Suite, the Tests section should allow the user to intermingle Tests with calls to Blueprint or Resource Command Scripting. While the instantiation of the Blueprint lays down the initial architecture, there are situations where the environment needs to be "updated". It's not that the resources change (so it doesn't make sense to release and reacquire a sandbox), but rather the "overlay" needs to change. For example, you run a throughput test with the user account defined as unlimited, then you want to update the account to have a usage cap and rerun the exact same test to see the change; or it might be a cell phone switching from prepaid to postpaid (and do the tests still pass).
In both cases the resources haven't changed (it's the same path), but their settings may need altering
By allowing the operator to select commands between Tests these commands can act on the sandbox to update the environment. This keeps the "environmental actions" within Quali's purview, while allowing the Test Tool to focus on the "user experience" over that environment
- call Blueprint script 'Change to Unlimited'
- Robot\perform test A
- call Blueprint script 'Change to 20Mb'
- Robot\perform test A
