test(19.6.1-03): screens test env and the superuser flag rule over HTTP
- administrators_harness_test.go: newScreensEnv with extra plugins, seedAdmin, seedRole, login, isolateSuperusers, row snapshots and error decoders; the harness moved out of backend_screens_smoke_test.go and gained cleanup - export_test.go: SuperuserLockKey for the last-superuser race - TestAdministratorsSuperuserFlag (D-05) through the assembled handler
This commit is contained in:
@@ -102,3 +102,8 @@ func IsReorderStale(err error) bool {
|
||||
var stale reorderStale
|
||||
return errors.As(err, &stale)
|
||||
}
|
||||
|
||||
// SuperuserLockKey is the advisory lock key guardLastSuperuser takes. The
|
||||
// last-superuser race tests hold it in a transaction of their own, so both
|
||||
// racing requests queue on it before either counts the other superusers.
|
||||
const SuperuserLockKey = superuserLockKey
|
||||
|
||||
Reference in New Issue
Block a user