Skip to content
This repository has been archived by the owner on Jun 21, 2024. It is now read-only.

Bootstrap acceptance tests #17

Closed
IljaN opened this issue Sep 17, 2018 · 1 comment
Closed

Bootstrap acceptance tests #17

IljaN opened this issue Sep 17, 2018 · 1 comment
Assignees
Labels
enhancement New feature or request QA:team

Comments

@IljaN
Copy link
Member

IljaN commented Sep 17, 2018

Ideas of what needs testing:

  • 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
@IljaN IljaN added enhancement New feature or request QA:team labels Sep 17, 2018
@IljaN IljaN added this to the backlog milestone Sep 17, 2018
@IljaN
Copy link
Member Author

IljaN commented Oct 5, 2018

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request QA:team
Projects
None yet
Development

No branches or pull requests

2 participants