Indeed - expunge, storage, account cleanups are set to 60s on all
automated test environments I've setup.
The cleanup process works as below:
setUpClass() -> creates user account, creates user resources
testXxx() -> test steps and verify within the account
tearDownClass() -> cleanup resources acq
I'm +1 on this. I feel global setting (relating to expunge and cleanup) should
be set to aggressively expunge deleted resources, then delete the user
resources... before deleting the account. That way we can verify garbage
collection of resources is working properly.
Ahmad
On Jun 14, 2013, at
+1
On 6/14/13 8:54 AM, "Rayees Namathponnan"
wrote:
>Many of the automation test cases are not tearing down the account
>properly; due to this resources are not getting released and followed
>test cases getting failed during VM deployment itself.
>
>During automation run accounts are created wi
Many of the automation test cases are not tearing down the account properly;
due to this resources are not getting released and followed test cases getting
failed during VM deployment itself.
During automation run accounts are created with random number without any
reference for test case (eg
