How Can We Help?
< All Topics
Print

11. SharePoint – Windows Check In, Check Out & Locked Files Test Cases

 

SharePoint to Windows

1.Use Case: Check Out file in SharePoint and open the same file in Windows

  • SharePoint and Windows sync is complete, and Project is in Active status
  • Create Word document in SharePoint or choose an existing word document
  • Check Out the word document in SharePoint
  • Open the Word Document in SharePoint, Edit and Save
  • Now, open the same word document in Windows, Edit document and Save
  • Close the document

Actual result:

  • No changes done in SharePoint document after checking out will be synced to Windows
  • Windows only has the changes done and saved in Windows file
  • 2 errors are logged in the Connection Log in Portal
Deleting: 11687 The file is currently checked out or locked for editing by another user. 7/6/2021 4:56:59 AM SharePoint 156daeef-0f86-4b96-82ad-24f60c1303e5
UseCase1.docx Response status code does not indicate success: 423 (Locked). 7/6/2021 4:57:00 AM SharePoint 74bd9fc2-64df-47e7-862d-5bdcd00f591c

Expected result: if same file is opened in both systems, it should create a .copy “Filename.copy.system” new file. System is the originating system that is syncing from. So if Procore is pushing it to SharePoint you name it “.procore”.

 

2.Use Case: Open file in SharePoint OneDrive and open file in Windows

  • SharePoint and Windows Full sync is complete, and Project is in Active status
  • Create Word document in SharePoint OneDrive or pick an existing word document and open it in SharePoint OneDrive [The SharePoint Library will reflect in OneDrive]
  • Open the Document in SharePoint OneDrive, Edit and Save
  • Open the same Document in Windows, Edit document and Save
  • Close the document

Actual result:

  • No changes done in SharePoint document when checked out will be synced to Windows
  • Windows only has the changes done and saved in Windows file
  • 2 errors are displayed in Portal:
Deleting: 11688 The file is currently checked out or locked for editing by another user. 7/6/2021 5:07:28 AM SharePoint e23c7a06-57c2-4c6e-944c-cbd03bcf0668
UseCase2.docx Response status code does not indicate success: 423 (Locked). 7/6/2021 5:07:29 AM SharePoint fce94061-016b-40e0-8056-466b3ba1c438

Expected result: if same file is opened in both systems, it should create a .copy “Filename.copy.system” new file. System is the originating system that is syncing from. So if Procore is pushing it to SharePoint you name it “.procore”.

 

3.Use Case: Check Out file in SharePoint and edit the same file in Windows

  • SharePoint and Windows Full sync is complete, and Project is in Active status
  • Create Word document in SharePoint or choose an existing word document
  • Check Out Word Document in SharePoint
  • Open the same Document in Windows, Edit and Save
  • Check In the Word Document in SharePoint
  • Verify changes in the files

Actual result:

  • No changes done in Windows when SharePoint document is checked out will be synced to SP
  • 2 errors are displayed in Portal:
Deleting: 11689 The file is currently checked out or locked for editing by another user. 7/6/2021 5:18:41 AM SharePoint 25e3dfbd-c4c9-4399-b537-a31df697ac79
UseCase3.docx Response status code does not indicate success: 423 (Locked). 7/6/2021 5:18:42 AM SharePoint 50d9a09a-79fd-4bdc-b49b-08e4e855ff19

Expected result: if same file open in both systems, it should create a .copy “Filename.copy.system” new file. System is the originating system that is syncing from. So if Procore is pushing it to SharePoint you name it “.procore”.

 

4.Use Case: Open file in Windows and open the same file in SharePoint

  • SharePoint and Windows Full sync is complete, and Project is in Active status
  • Create Word document in Windows or choose an existing Word document, Edit and Save
  • Open the same Document in SharePoint and try to Edit it

Actual result:

  • Changes made in Windows will be synced to SharePoint
  • As the file is opened in Windows, cannot edit the same document in SharePoint
  • Error in Portal
UseCase4.docx The process cannot access the file ‘C:\Synchronization\SharePoint\Use Cases\UseCase4.docx’ because it is being used by another process. 7/6/2021 5:28:38 AM Windows 2ad5d89f-30f5-c000-2dd8-2023bd2fcc92

Expected result: if same file open in both systems, it should create a .copy “Filename.copy.system” new file. System is the originating system that is syncing from. So if Procore is pushing it to SharePoint you name it “.procore”.

 

5.Use Case: Open file in Windows and open file in SharePoint OneDrive

  • SharePoint and Windows Full sync is complete, and Project is in Active status
  • Create Word document in Windows or choose an existing Word document, Edit and Save. Close the Word Document.
  • Open the Word Document in SharePoint OneDrive, Edit and Save
  • Close files and verify changes

Actual result:

  • Changes done in Windows will be synced to SharePoint
  • Changes done in SharePoint will be synced to Windows

Expected result: if same file open in both systems, it should create a .copy “Filename.copy.system” new file. System is the originating system that is syncing from. So if Procore is pushing it to SharePoint you name it “.procore”.

 

6.Use Case: Check Windows Service – Locked File scenario

  • Create a new Windows Service Connection from SharePoint to Windows
  • Start the sync from SharePoint to Windows
  •  From the Lock tool files – App Settings.Json file – change the windows path. “C:\\SN-Windows Service” and Save it [Give the path given upon installing the Windows Service]
  • When the sync is running, Start the Lock Tool
  • A new file will get created and displayed in Windows, which will be locked for 10 Minutes
  • Open the same File, make changes and Save
  • This new file with the changes done must be synced successfully to SharePoint
Previous 10. Windows – SharePoint Test Cases