Draft: Tests for non-purge delete
2 unresolved threads
2 unresolved threads
Compare changes
Files
7- I. Nüske authored
# Conflicts: # manager_test/manager_fdo/test_delete_fdo.py
+ 217
− 173
@@ -15,10 +15,11 @@ from fdo_manager_service_api_client.models \
@@ -31,201 +32,224 @@ class TestClassCreateFDO: # pylint: disable=fixme
@@ -268,29 +292,41 @@ class TestClassCreateFDOChecks: # pylint: disable=fixme
@@ -337,8 +373,11 @@ class TestClassCreateFDOChecks: # pylint: disable=fixme
@@ -346,14 +385,17 @@ class TestClassCreateFDOChecks: # pylint: disable=fixme
@@ -362,6 +404,8 @@ class TestClassCreateFDOChecks: # pylint: disable=fixme
The return prevents the four checks after that from being run, because they always fail when run against the GWDG instances. If run against the testbed, it can be removed. As soon as the hdl.handle.net entry is updated, it needs to be removed. I added the skip instead of an xfail, as the external-create-fdo-checks tend to cover a lot of failures in fdo creation that cannot be detected with the other tests, and an xfail would hide those failures. If that is not a concern, an xfail would be the more appropriate solution.