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
{{ message }}
This repository has been archived by the owner on Jun 21, 2024. It is now read-only.
migration of a user from OC A to OC B without mapping
migration of a user from OC A to OC B with mapping
migration of user shares through the different steps of remapping
check that a locked user (during migration) only has read-only access over APIs (Webdav, OCS)
migration of other metadata (to be expanded)
after migration of two users U1 and U2 from OC A to OC B, check that data is still accessible and that the shares still point to the correct users (incoming and outgoing)
after migration of just one user to OC B, check that the existing shares are pointing to OC A and still accessible
The text was updated successfully, but these errors were encountered:
The first idea which comes to mind is to have acceptance tests working across two instances. But there might be a simplification in that we use one instance but import under a different alias and re-export again.
Ideas of what needs testing:
The text was updated successfully, but these errors were encountered: