Accceptance tests for recovery key with encryption
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 16
- Forks
- 16
- Avg merge
- 11h 11m
- Merged PRs (30d)
- 1
Description
Note this ticket about behavior change, so we might want to write these tests directly after that: https://github.com/owncloud/core/issues/26847
The way I see it, this would be an addition feature set in behat that tests the recovery flow exclusively. So if the env has encryption disabled we skip this. Maybe could even be a separate behat config.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked behavior-change issue and the repository's Behat setup. Define recovery-key encryption scenarios that run when encryption is enabled and are skipped when it is disabled; consider whether a separate Behat configuration is needed. Done means the recovery flow is covered without running in unsupported environments.
Written by the indexing model from the issue text.
Assessment
- Domain
- security, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100