Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[contract testing] [share ng] Extend propfind contract testing #9119

Open
amrita-shrestha opened this issue May 9, 2024 · 3 comments
Open
Labels

Comments

@amrita-shrestha
Copy link
Contributor

amrita-shrestha commented May 9, 2024

While adding tests related to share-ng, found that ocis-tests miss some contract testing as mentioned below.
Scenario: remove share link and propfind resource to see if the response contain or not

<oc:share-types>
<oc:share-type>3</oc:share-type>
</oc:share-types>
<oc:privatelink>
https://localhost:9200/f/a3be74ba-6183-4942-9458-440b92c5895b$68962830-8cbb-4226-b3b4-458c50793487%210e590fe7-8816-4d75-bd42-5ffa2fa81410
</oc:privatelink>

Scenario: user Alice shared resource with user Brian, Brian is deleted , user Alice propfind the shared resource to check if the response contains shares details or not after share deleted

Question

  • Should we add such scenario to apiContract->propfind.feature ❓

cc @ScharfViktor @saw-jan @phil-davis

@S-Panta
Copy link
Contributor

S-Panta commented Jun 25, 2024

The bug is reported here . #9463

@SagarGi
Copy link
Member

SagarGi commented Jul 3, 2024

For the above issue first lets find out if we have covered propfind test when sharee is not deleted. If it is not covered then we can add one when sharee is not deleted. And then we can check the propfind when sharee gets deleted.

In summary:

Also consider this bug regarding it. #9463

@PrajwolAmatya
Copy link
Contributor

Moving this issue to blocked since there's an issue regarding PROPFIND request to shared resource when the user is deleted. Reported here: #9463

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants