nextcloud / nextcloud/nextcloudfileproviderkit
Implement full end-to-end testing
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 8
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
At present, the macOS virtual files client's automated test suite is limited.
NextcloudFileProviderKit features an extensive test suite that covers the expected behaviour of many units within the package, using extensive mocking of a real Nextcloud server instance and of the types of tasks the system's fileproviderd process would require a File Provider Extension to perform. However:
- There is no testing against a real server
- There is no testing using the complete File Provider app extension bundled into the client
This task requires you to implement proper end-to-end tests using Apple's File Provider testing APIs. Ideally, these tests should check the expected behaviour against a real server instance that is spun up and shut down on demand in a CI/CD environment in GitHub.
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
The issue names Apple's File Provider interactive testing APIs, the complete File Provider app extension, and a real server in GitHub CI, but no repository files or existing test target. Start by locating the extension's test target and current CI configuration, then verify the API's interactive mode and server lifecycle; done means repeatable tests exercise the bundled extension against a real server and run in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, swift
- Domain
- ci-cd, desktop, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100