#110735Prevent E2E backend user state leakage
Description
The MFA OTP E2E test creates a backend user named
mfa_test_user but does not remove it afterward.
Because E2E tests share the same test installation, the additional user
leaks into the backend users module tests. These tests assume a fixed
number and ordering of backend users, causing several failures during an
unsharded test run.
The MFA test should use a unique username and remove the created user in
guaranteed cleanup. Backend users module tests should locate their fixture
records by identity instead of relying on global record counts or row
positions.
Steps to reproduce:
1. Run the complete E2E suite without sharding.
2. Let the MFA OTP test create its backend user.
3. Observe failures in the backend users module tests caused by the
additional record.
Expected result:
- The MFA test leaves no backend user behind.
- Backend users tests operate on their defined fixture records.
- The MFA and backend users tests pass sequentially in the same instance.
Reviews 1
History 13
-
Gerrit Code Review pushed patch set 1 for main to change 95899 status
NewUnder Review <span data-processor="relativetime" data-value="2026-09-17T16:42:21+00:00" > 09/17/26, 16:42 </span> -
Gerrit Code Review pushed patch set 2 for main to change 95899 <span data-processor="relativetime" data-value="2026-10-02T18:59:54+00:00" > 10/02/26, 18:59 </span>
-
Wouter Wolters commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-10-03T18:20:11+00:00" > 10/03/26, 18:20 </span>
Applied in changeset commit:52f2de8d5cb023d9e9311b5789816e4a9a2e97e4.