The authenticatedAs testing option makes use of an authorization header to authenticate the user, this only works on the api frontend, for forum or admin frontends we've always had to make a normal identification/password request to the login endpoint and use the generated cookie to run our tests. This isn't ideal.
This PR changed the autheticatedAs option to rely on a remember cookie by default. Which makes testing easier.
Necessity
[x] Has the problem that is being solved here been clearly explained?
[x] If applicable, have various options for solving this problem been considered?
[x] For core PRs, does this need to be in core, or could it be in an extension?
[x] Are we willing to maintain this for years / potentially forever?
Confirmed
[x] Tests have been added, or are not appropriate here.
Fixes #3834
Changes proposed in this pull request:
authenticatedAs
testing option makes use of an authorization header to authenticate the user, this only works on theapi
frontend, for forum or admin frontends we've always had to make a normal identification/password request to the login endpoint and use the generated cookie to run our tests. This isn't ideal.autheticatedAs
option to rely on a remember cookie by default. Which makes testing easier.Necessity
Confirmed