Currently, the deployment pytest fixtures deploy all test ranges, run tests, and then destroy all infrastructure once all tests have finished. The issue with this approach is that every test range must wait until all tests have finished leaving infrastructure deployed longer than it needs to be.
The way to solve this is to create separate test deployed range fixtures allowing for clean up once all tests relevant to a specific test range complete.
Currently, the deployment pytest fixtures deploy all test ranges, run tests, and then destroy all infrastructure once all tests have finished. The issue with this approach is that every test range must wait until all tests have finished leaving infrastructure deployed longer than it needs to be.
The way to solve this is to create separate test deployed range fixtures allowing for clean up once all tests relevant to a specific test range complete.