owncloud / owncloud/ocis

[QA] Add e2e tests for Vault mode

Open
#12,890 0 comments 0 reactions 0 assignees View on GitHub
QA:team
Dominant language
Go
Stars
2.1k
Forks
274
Avg merge
2d 1h
Merged PRs (30d)
103

Description

The original issue : https://github.com/owncloud/web/issues/13864
The `API tests` for vault have already been covered. This issue mainly focuses on the `e2e tests` for the Vault mode.

## [OCISDEV-1403]

## Overview

Vault Mode provides a dedicated, separately stored vault storage with MFA protection capabilities. Vault resources are isolated from default Drive storage and have separate search, shares, personal spaces, and project spaces.

Drive - Default storage
Vault - Vault storage

---

# Vault Mode QA Test Plan.
* Create the test scenarios where the user Brian creates the folders and files in a personal space and create the project space then create folders and files inside the project space. Next step the user brain do the same for Vault mode. Check if the drive mode resources and world mode resources reliable separated.
* Create the test scenario where the user Brian in the Drive and Vault mode, shares the folder and file from the personal and project space to user Alice. And user Alice receives the shares in a corresponding place, Drive or Vault.
* Create the test scenario where the user Brian invites user Alice to the project space in a drive and vault mode and user Alice receives the invite and sees the project space in a corresponding place, Drive or Vault.
* Create the test scenarios where the user Brian searches through the drive and volt mode and get a corresponding result.

## Acceptance Criteria

### AC-1: Vault Mode Access Control
**Criterion:** User can switch between Drive and Vault modes based on permissions
- **Precondition:** User has vault mode permission enabled
- **Action:** User navigates to switch mode option
- **Expected Result:** User can toggle between Drive and Vault modes
- **Related:** Requires permission check in proxy/auth service

### AC-2: Second Factor Authentication on Vault Entry
**Criterion:** MFA is enforced when accessing Vault mode
- **Precondition:** User switches from Drive mode to Vault mode, MFA is configured
- **Action:** User initiates Vault mode access
- **Expected Result:** User is redirected to second factor authentication
- **Post-Auth:** User is redirected to Vault mode notification page upon successful verification

### AC-3: Resource Isolation - Drive vs Vault
**Criterion:** Resources in Drive and Vault are isolated
- **Precondition:** User has resources in both Drive and Vault
- **Action:** User navigates Drive mode, then switches to Vault mode
- **Expected Result:** Drive resources are not visible in Vault; Vault resources are not visible in Drive
- **Storage:** Verified in storage-users and storage-users-vault services

### AC-5: Unidirectional Copy - Drive to Vault Only
**Criterion:** Copy operations are restricted to Drive → Vault direction only
- **Precondition:** User has files in both Drive and Vault
- **Action Positive:** User copies file from Drive to Vault
- **Expected Result:** Copy succeeds
- **Action Negative:** User attempts to copy file from Vault to Drive
- **Expected Result:** Copy operation is blocked with error message

### AC-6: Public Links Disabled for Vault
**Criterion:** Public link sharing is not allowed for Vault resources
- **Precondition:** User has files/folders in Vault
- **Action:** User attempts to create public link for Vault resource
- **Expected Result:** Public link creation option is disabled/unavailable

### AC-7: Scoped Search - Drive and Vault Separate
**Criterion:** Search results are isolated by storage mode
- **Precondition:** User has identical file names in both Drive and Vault
- **Action:** User performs search in Drive mode
- **Expected Result:** Only Drive resources appear in search results
- **Action:** User switches to Vault and searches
- **Expected Result:** Only Vault resources appear in search results
- **Implementation:** Search uses `vault:true` query token

### AC-9: Shares Isolation
**Criterion:** Shared items are isolated between Drive and Vault
- **Precondition:** User shares resources in both Drive and Vault
- **Action:** Recipient receives shares
- **Expected Result:** Drive shares appear in Drive share section; Vault shares appear in Vault share section

### AC-10: Vault/Drive in Breadcrumbs
**Criterion:** Breadcrumbs (Filepath) includes Drive or Vault in Spaces and Personal Spaces
- **Precondition:** User has access to a Vault, thus the ability to switch between Vault and Drive
- **Action:** None, the breadcrumbs should include Drive/Vault if the user has access to Vault
- **Expected Result:** Breadcrumbs include information regarding which view the user is on (Drive/Vault)

Contributor guide

Open the contributing guide

Research direction

Read the original issue at owncloud/web#13864 and the Vault Mode QA Test Plan first. Run or inspect the existing e2e test setup, then cover the listed Drive/Vault scenarios: access and MFA, isolation, copying, public links, search, shares, invitations, and breadcrumbs. Done means the acceptance criteria have executable e2e coverage for each applicable behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.