- Issue created by @kristiaanvandeneynde
- 🇬🇧United Kingdom longwave UK
Is there any way to inject something into the site under test to detect that this behaviour is being relied on, and issue a deprecation?
From #540008-370: Remove the special behavior of UID#1 → we can run all core tests with the super user access policy turned off, but we can't simply do the same for contrib without first discussing this further. For now, the property $usesSuperUserAccessPolicy is set to NULL and, unless specified otherwise, defaults to TRUE for contrib and custom tests.
N/A
I propose we keep the fallback behavior described above for D10.3 and use D11 as an opportunity to set the property to FALSE, removing the fallback mechanism. A major version update is a great opportunity to introduce breaking changes.
N/A
Tests who wrongly used user 1 to test permissions with will now fail
N/A
TBD
Active
11.0 🔥
Last updated
Is there any way to inject something into the site under test to detect that this behaviour is being relied on, and issue a deprecation?