-
Notifications
You must be signed in to change notification settings - Fork 157
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
Test setup for all share scenarios #2896
Comments
Here I'm not sure how many of those scenarios are already covered in some scenario setups. To me, ideal is that those tests are grouped together so we can refer back to the sharing scenarios. |
We could also port over the scenarios that were created for OC 10: https://github.com/owncloud/core/pull/36572/files#diff-d5a7b47bf7d40f4780417db046827793R377 but would need to double check whether they cover all the scenarios that the script illustrates. |
Here's the output of the script which also contains info about what shares were created:
|
I think using such script to setup all users and shares is good idea if we want to cover each and every possible combination but it is not essential IMO. Also those tests will be kind of inconsistent with the current acceptance tests suite. Maybe we can do just like in core (https://github.com/owncloud/core/pull/36572/files#diff-d5a7b47bf7d40f4780417db046827793R377) and try to cover all essential scenarios. |
@dpakach yeah, it is likely easier to reuse those tests first. As this is blocking my PR #2060 I'll port the OC 10 tests over to Phoenix and adjust them accordingly, then add the share indicator check. Once we touch further aspects like "collaborators list" and "share owner" for the same scenarios, we can simply add more "Then" steps to validate those. |
I've managed to port most tests to #2877, at least for the share indicators for now. I decided to not go with the "create user without skeleton" as I found it too cumbersome. |
Fixed through #2877 |
In order to be able to test the share indicators and share owner, we need to first have a setup available with all possible shares on which we can base the tests.
See owncloud/product#40 for a Python script that generates and illustrates all share scenarios we need to consider.
The idea is to:
We'll need this as a base to write acceptance tests for the share indicators, as we'll be asserting that the indicator and some information is visible in the share panel for specific folders.
@individual-it thoughts ?
The text was updated successfully, but these errors were encountered: