-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use of baseURL in acceptance tests #30879
Comments
My suggestions:
|
@phil-davis I fully agree with changing this. But be aware that it involves changes in many functions, as many of them to create the request url starts using baseUrl, for example:
It will affect also acceptance tests of apps also (customgroups, guests, etc). |
Yes, it will need careful examination of everything that uses, passes... |
PRs merged. webUI acceptance tests now use the "API test" view of |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
The API acceptance tests are passed the base URL of the server-under-test in a format like:
when they want to access some API endpoint that does not start with
ocs/
then they take theocs/
off and then add the required string for the URL.The webUI acceptance tests are passed the base URL of the server-under-test in a format like:
and they add the
ocs/
or other endpoint URL as needed to access API endpoints.Also it is not currently consistent if the passed-in base URL always has a
/
at the end or not.This all makes a bit of a muddle for different methods that are in "API acceptance" classes and "webUI acceptance" classes.
To discuss/decide:
baseURL
\
at the end, or not, or be flexible parsing the passed-in value@individual-it @SergioBertolinSG @davitol
The text was updated successfully, but these errors were encountered: