Open phil-davis opened 5 years ago
@phil-davis I have come with following scenario lists that can be added. Please see if these are relevant:
@sakshamgurung That seems good.
The scenarios could mix up file and folder - one share is for a folder "x.y" and the other share is for a file "x.y". Brian should be able to see both received shares somehow.
Also try with different case - "x.y" and "X.Y" to make sure that there is no problem. I think that 2 shares like that should be nicely received separately.
Background
Currently the sharing acceptance tests mostly use files and folders that are in the "standard" acceptance test webUI or API skeleton. e.g.
user1
anduser2
both havesimple-folder
. Whenuser1
sharessimple-folder
withuser2
thenuser2
receives a folder calledsimple-folder (2)
. So we have "accidentally" created lots of test scenarios for the case where the share receiver already has a matching file or folder name.As part of speeding up CI, we are reducing the use of the "standard" skeleton (it takes significant time to create for every user of every scenario). Scenarios will (soon) usually result in the share receiver not already having a matching file or folder. So the
(2)
naming thing will not get tested much.To Do
Create explicit test scenarios for sharing where the share receiver already has a matching file or folder name.