When the pytess are running they create stacks in a test account. Without a unique stack name, we're limited to running the test in serial. To avoid this issue, I recommend adding a UUID to the stack names deployed by the test cases.
Also a big log flag when a test fails to delete a stack might be a good idea, our test stacks do not cost anything but it'd be nice to make sure who ever is running the tests knows that there are resources to clean up would be nice.
When the pytess are running they create stacks in a test account. Without a unique stack name, we're limited to running the test in serial. To avoid this issue, I recommend adding a UUID to the stack names deployed by the test cases.
Also a big log flag when a test fails to delete a stack might be a good idea, our test stacks do not cost anything but it'd be nice to make sure who ever is running the tests knows that there are resources to clean up would be nice.