owncloud / owncloud/QA

Acceptance tests for sharing option variations

Open
#353 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

dev:acceptance-tests QA-p3 QA:team Server
Dominant language
Shell
Stars
16
Forks
16
Avg merge
11h 11m
Merged PRs (30d)
1

Description

There are many sharing options in the admin page:

We should make sure to cover these individually and also in some relevant combinations.

General
  • Allow/disallow resharing
  • Allow/disallow sharing with groups
  • Exclude group from sharing
    • sharing from one of these users must not be possible
    • received shares still appear but are not resharable
  • Allow users to send mail notification for shared files to other users (bäh... no public API, maybe let's skip this one for now)
  • Restrict users to only share with users in their groups https://github.com/owncloud/core/pull/35736 https://github.com/owncloud/core/pull/35733
    • a user can share with any other user in the same group
    • a user can only share with any group they are member in
    • a user cannot share with other groups
    • a user cannot share with users in other groups in which they are not member
  • Exclude groups from receiving shares
    • Sharing with that group is not possible
    • sharing with a user of that group is possible
    • users of that group can still initiate shares
  • Allow username autocompletion: I think should be testable with Sharee API
Link share specific
  • Allow link shares / disallow
  • Allow/disallow public upload
  • Enforce password protection: API refuses creating if no password was given
  • Set default expiration date + expire after X days
  • Enforced default expiration date
  • Allow users to send mail notification for shared files (boo, let's skip that one for now)

@owncloud/qa

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the admin page sharing options and the existing acceptance-test setup; the issue does not name specific files or test entry points. Cover the unchecked sharing variations and relevant combinations, including excluded groups and reshare behavior, while leaving the explicitly skipped mail-notification cases out.

Written by the indexing model from the issue text.

Assessment

Domain
testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.