Use one-time login link instead of user login form in BrowserTestBase tests

Locally I have \Drupal\Tests\block_content\Functional\BlockContentListTest passing but it looks like there are lots of fails in other tests.

Well that was fun. There are three tests remaining that use the login form. One is the UserLoginTest, so we need to keep that. The other two seem to be oddities that could probably be fixed, perhaps in a followup.

It's hard to evaluate if this is overall faster than before because there is such variability in the test suite times. I did see one run that was under five minutes. In my local testing I found a saving of around 200ms per login. So that's roughly 5 mins total savings over 1500 logins.

Follow ups appear to be mentioned in the threads.

• Remove the duplicate ::userPassResetUrl method and updated the existing user_pass_reset_url function to use current time as discussed with @catch in Slack.
• Updated UserLoginTest::testLoginCacheTagsAndDestination to explicitly submit the login form instead of relying on ::drupalLogin
• Added 📌 Placeholder follow-up for 3469309 Postponed

So have re-ran twice and keep getting failures, but not entirely sure why.

HEAD was broken. Have rebased and it's green again.

Nice. Believe feedback has been addressed. The one thread wasn't sure about

LGTM.

nod_ → closed merge request !9269

Committed and pushed bf4ae81164 to 11.x and 39f2b9f40b to 11.0.x and b16714a919 to 10.4.x and 332f671c2d to 10.3.x. Thanks!

LocaleTranslationUiTest fails on 11.0.x, 10.4.x, and 10.3.x

We can probably add

protected bool $useOneTimeLoginLinks = FALSE;

to the failing test.

Added MR for 11.0.x

11.0 appears to be passing

Was confused for a second why 11.0 but see that 11.x wasn't reverted

Committed and pushed 104f82857d to 11.0.x and b868899be1 to 10.4.x and 47614c4759 to 10.3.x. Thanks!

nod_ → closed merge request !9442

LocaleTranslationUiTest fails on 11.x with PostgreSQL!

Setting the priority to critical.

I won't get to this for a bit, but see #17 and 21 and apply this to 11.x, it was already applied to the other branches.

I've cherry-picked 104f8285 forwards to 11.x, tentatively marking fixed but please re-open if there's still a problem.

catch → closed merge request !9513

Automatically closed - issue fixed for 2 weeks with no activity.