[tests-only][full-ci] add test to enable sync of federated shared resource #11026
Conversation
prashant-gurung899
force-pushed
the
test/enable-sync-ocm-shares
branch
4 times, most recently
from
2754965 to
8cf9bef
Compare
prashant-gurung899
requested review from
anon-pradip,
saw-jan,
amrita-shrestha,
nabim777,
PrajwolAmatya and
nirajacharya2
prashant-gurung899
force-pushed
the
test/enable-sync-ocm-shares
branch
3 times, most recently
from
748700d to
70d1a31
Compare
| When user "Brian" lists the shares shared with him using the Graph API | ||
| Then the HTTP status code should be "200" | ||
| And the JSON data of the response should match |
There was a problem hiding this comment.
why we need to check share-with-me ?
I am confused bug occur in which step?
There was a problem hiding this comment.
I used that step to check the value of @client.synchronize in the response.
There was a problem hiding this comment.
The value of @client.synchronize in the response of enabling sync request is false. And when sharedWithMe is checked, it's set to true. May be it's a bug in OCM shares.
synchronize.webm
There was a problem hiding this comment.
should not enable sync step response should be check?
There was a problem hiding this comment.
Yeah but as you can see the value of @client.synchronize in the response of enable sync is false. So, i listed the shareWithMe to check the value. And I am not sure it it's the expected behaviour.
prashant-gurung899
force-pushed
the
test/enable-sync-ocm-shares
branch
from
70d1a31 to
6386aea
Compare
prashant-gurung899
force-pushed
the
test/enable-sync-ocm-shares
branch
from
6386aea to
1a06a8d
Compare
prashant-gurung899
force-pushed
the
test/enable-sync-ocm-shares
branch
from
1a06a8d to
fc32f5b
Compare
| When user "Brian" lists the shares shared with him using the Graph API | ||
| Then the HTTP status code should be "200" | ||
| And the JSON data of the response should match |
There was a problem hiding this comment.
should not enable sync step response should be check?
prashant-gurung899
force-pushed
the
test/enable-sync-ocm-shares
branch
from
fc32f5b to
e1b7fd6
Compare
prashant-gurung899
force-pushed
the
test/enable-sync-ocm-shares
branch
7 times, most recently
from
60a5aa2 to
2e6130b
Compare
Signed-off-by: prashant-gurung899 <[email protected]>
prashant-gurung899
force-pushed
the
test/enable-sync-ocm-shares
branch
from
2e6130b to
fe01fec
Compare
|
[tests-only][full-ci] add test to enable sync of federated shared resource
Description
This PR adds following test scenarios to enable sync of federated share.
Enabling sync of a federated share when there's only one share in
shared with medoesn't throw any error but enabling sync of a federated share when there are multiple shares inshared with megives400 Bad Requesterror but@client.synchronizeis set to true.See comments: #10719 (comment) and #10719 (comment)
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: