-
Sub-task
-
Resolution: Done
-
L3 - Default
-
None
-
None
We should use the ES Mockserver to add tests to make sure that we are resilient to operations which require multiple requests. We should never leave orphaned entities, and should have tests verifying behaviour when certain aspects fail. Some examples in ATs:
ATs:
- Dashboard:
- Delete: Shares are deleted before dashboard is. If share delete fails, everything still exists. If dashboard delete fails, share has already been removed
- Move/Copy: the new dashboard is created before new entities, so entities cannot be orphaned if the new dashboard creation fails
- Report:
- Delete: Report is deleted after related resources and won't be deleted if related resource clearup fails
- Collection:
- Delete: Related entities are deleted before the collection itself is, so they cannot be orphaned
- Copy: Related entities are copied and moved after the new collection itself is created, so they cannot be orphaned
- EventBasedProcess:
- Delete: The process is deleted after the deletion of it's related entities (reports/collection scopes/publish state) to not leave orphan entities
- CollectionScopes:
- Delete: When a scope is deleted, the reports for that scope are deleted before the entry is removed from the collection