[QA] Test Password Protected Folders

[kobergj]

Password Protected Folders are a brand new feature that needs to be tested thoroughly (#12039)

Scenarios

1. folder creation

1. logged in user opens a create password protected folder dialog (via "New" dropdown)
2. logged in user enters folder name, password, selects permissions and creates folder
3. folder in the root of users personal space is created (a hidden folder) with a public link using the permissions and password specified when creating folder is created on the hidden folder, file with the same name as folder is created in the current folder (not hidden) with the Base64 encoded public link as content

Note

I think it would make sense to cover this scenario in both personal and created space to verify that the hidden folder is created in correct space but I leave the final decision up to you whether it makes sense

2. opening folder

1. logged in user clicks on the password protected folder (in the files list represented using a file with hidden .psec file extension)
2. a dialog with limited web UI is shown
3. user enters the password to access the folder

3. deleting folder

1. logged in owner of the password protected folder deletes it
2. the hidden folder, file, and public link are all deleted

Note

When deleting the folder as a user who is not the owner, only the file gets deleted

[saw-jan]

@LukasHirt You can update the necessary details in the ticket

[LukasHirt]

@saw-jan @nirajacharya2 I update the description with three scenarios to test. I think this covers the most important parts of the feature and there is not much point in testing much more of it using E2E tests. Let me know if you would need any more context.

[LukasHirt]

Please note that there are still two open PRs that need to be merged before everything can be tested. #12146 & #12152

[LukasHirt]

Let's move this ticket to web since this is FE-only feature?

[saw-jan]

Let's move this ticket to web since this is FE-only feature?

If it's web web-only feature then IMO yes. let's move it to the web repo