Cleanup double-slash URLs in acceptance tests #30863
Merged
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.
Description
In places where the acceptance tests use
baseURL
and append stuff to it, add checks that put a/
afterbaseURL
only ifbaseURL
does not already end in a/
That makes it flexible to have
baseURL
passed in with or without a trailing slash, and to not get double-slash sent in API requests.Related Issue
owncloud/QA#517
Motivation and Context
When running acceptance tests, on the PHP server we see requests like:
Nothing bad goes wrong, ownCloud copes with "random" double-slash in the URI. But it makes people ask questions when they notice this in acceptance test output. So it is good to clean it up.
How Has This Been Tested?
Local runs of some API acceptance tests now give requests like:
Types of changes
Checklist: