You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue #4390 (PRs #4433#4441#4456 ) implements cleanup of personal spaces and project spaces at the end of each API test scenario - good.
But I think that only happens for the local API acceptance test suites. The AfterScenario is in SpacesContext, and SpacesContext is never loaded when the core API tests are run. The core API tests create users, and those users have a personal space when the test suite is run against an oCIS server. (The core API tests never create a porject space, so we do not need to worry about cleaning up those)
Design and implement a way to get at least the needed personal-space-cleanup code to run after each core scenario finishes.
The Behat test-runner does not guarantee the order that AfterScenario methods are run. It could be that the AfterScenario that deletes users runs before the AfterScenario that cleans up spaces. This could be a problem in both local and core API acceptance test runs.
Design and implement a way to make sure that project spaces and personal spaces are cleaned up before users are deleted.
The text was updated successfully, but these errors were encountered:
The clean-up of spaces after user deletion is implemented by these PRs #4532, #4533
Now, the user spaces created after running core test from ocis and ocis local tests are deleted properly.
So closing this issue on behalf of the above PRs.
Issue #4390 (PRs #4433 #4441 #4456 ) implements cleanup of personal spaces and project spaces at the end of each API test scenario - good.
But I think that only happens for the local API acceptance test suites. The
AfterScenario
is inSpacesContext
, andSpacesContext
is never loaded when the core API tests are run. The core API tests create users, and those users have a personal space when the test suite is run against an oCIS server. (The core API tests never create a porject space, so we do not need to worry about cleaning up those)The Behat test-runner does not guarantee the order that
AfterScenario
methods are run. It could be that theAfterScenario
that deletes users runs before theAfterScenario
that cleans up spaces. This could be a problem in both local and core API acceptance test runs.The text was updated successfully, but these errors were encountered: