Sample Test Cases when Migrating SharePoint via csv using ShareGate Powershell
1. No Source Site:
- Test case: Attempt to migrate files from a non-existent source site
- Expected Result: The migration process fails with an error message indicating that the source site does not exist.
2. Incorrect Spelt Source Library:
- Test case: Attempt to migrate files from an incorrectly spelled source library
- Expected Result: The migration process fails with an error message indicating that the source library does not exist.
3. No Destination Site:
- Test case: Attempt to migrate files to a non-existent destination site
- Expected Result: The migration process fails with an error message indicating that the destination site does not exist.
4. Destination site but no library:
- Test case: Attempt to migrate files to a destination site but without specifying a destination library
- Expected Result: The migration process fails with an error message indicating that the destination library is not specified.
5. All migrations with folder and subfolder (in the same tenant):
- Test case: Migrate 20 files with multiple subfolders within the same SharePoint tenant.
- Expected Result: The migration process successfully transfers all files and folder structures to the destination library.
6. All migrations with folder and subfolder (in different tenants):
- Test case: Migrate 20 files with multiple subfolders from one SharePoint tenant to another.
- Expected Result: Migration process successfully transfers all files and folder structures to the destination library in the target tenant.
7. Source and Destination sites and libraries exist; result correct:
- Test case: Attempt to migrate files from a source library to a destination library, where both the source and destination sites and libraries exist, and the migration process completes successfully.
- Expected Result: All files are successfully migrated to the destination library without errors or data loss.
8. Adding one metadata field with destination not existing content type:
- Test case: Attempt to migrate files from a source library to a destination library while adding one metadata field to the destination library. The metadata field's content type does not exist in the destination site.
- Expected Result: The migration process fails with an error message indicating that the content type for the metadata field does not exist in the destination site. The files should not be migrated to the destination library.
9. Adding one metadata field with a destination exists column but not content-type:
- Test case: Attempt to migrate files from a source library to a destination library while adding one metadata field to the destination library. The metadata field's content type already exists in the destination site, but the column does not.
- Expected Result: The migration process fails with an error message indicating that the column for the metadata field does not exist in the destination library. The files should not be migrated to the destination library.