I'm still seeing test coupling: if test_versioning_check_acl fails then it leaves an object in ther versions ocntainer. SInce all tests in this class use the same ocntainers, that stray object causes test_versioning_dlo to fail when asserting object count in the versions container.
See attached modified patch:
I think we need a tearDown method that will clear out the containers between tests.
Also, if test_versioning_check_acl assertion on ResponseError being raises fails, the second account token remains set inthe connection, causing subsequent operations to fail, including teardown. So, wrap request with a try/finally.
-1 for the patch attached to #18
I'm still seeing test coupling: if test_versioning _check_ acl fails then it leaves an object in ther versions ocntainer. SInce all tests in this class use the same ocntainers, that stray object causes test_versioning_dlo to fail when asserting object count in the versions container.
See attached modified patch:
I think we need a tearDown method that will clear out the containers between tests.
Also, if test_versioning _check_ acl assertion on ResponseError being raises fails, the second account token remains set inthe connection, causing subsequent operations to fail, including teardown. So, wrap request with a try/finally.
Added another unit test suggestion.