Repository navigation
test: add e2e for most called files and folders endpoints - #1261
Merged
Merged
Conversation
apsantiso
had a problem deploying
to
development
October 30, 2026 15:52 — with 
GitHub Actions
Failure
GitHub Actions
Failure
|
jzunigax2
approved these changes
Oct 30, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
E2E tests for
POST /files,GET /files/sync,POST /files/thumbnail,GET /folders/content/:uuid/folders,POST /folders/content/:uuid/files/existenceandGET /folders/:id/metadata, covering the happy path and access to another user's resources.Why
These are among the most called endpoints, so we want them covered: they should return the expected data, persist correctly, and not let users reach resources they don't own.