You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In theory, the acceptance tests are "black box". They should not need to run as the web server user name (e.g. www-data). They should be just accessing the API and webUI. When they want to do setup, run/test an occ command then they use the testing app API to do that.
We should be able to remove su-exec www-data from our run.sh acceptance test commands.
The text was updated successfully, but these errors were encountered:
Possibly related issues are #22485 (test), #31579 (test), #22492 (test), #30855 ([Stable10] Acceptance tests not being able to run from daily-stable10-qa tarball), and #32040 (fix acceptance tests).
core and testing PRs reference above make this work in core.
Other PRs in apps have also successfully removed su-exec www-data from before run.sh
The test runner code is another step more independent from the server-under-test.
In theory, the acceptance tests are "black box". They should not need to run as the web server user name (e.g.
www-data
). They should be just accessing the API and webUI. When they want to do setup, run/test anocc
command then they use the testing app API to do that.We should be able to remove
su-exec www-data
from ourrun.sh
acceptance test commands.The text was updated successfully, but these errors were encountered: