API page: https://api.drupal.org/api/drupal/core%21tests%21Drupal%21Tests%21UiHelp...
UiHelperTrait.php
There is an issue when creating javascript functional testing, this problem occurs when trying to log in an admin user.
Drupal\Tests\PhpUnit\ExistingSiteJavascript\TestingTest::testPage
Behat\Mink\Exception\ElementNotFoundException: Element matching xpath "./ancestor::form" not found.
/var/www/site/vendor/behat/mink/src/WebAssert.php:418
/var/www/site/docroot/core/tests/Drupal/Tests/UiHelperTrait.php:78
/var/www/site/docroot/core/tests/Drupal/Tests/UiHelperTrait.php:250
/var/www/site/tests/phpunit/src/ExistingSiteJavascript/JavascriptTestBase.php:23
This error happens when there is more than one button called Log in or having the value Login, this logic is looking for the log in form using the button Log in, which it is not accurate if there is another element similar to the Log in on the page.
$this->submitForm([
'name' => $account->getAccountName(),
'pass' => $account->passRaw,
], t('Log in'));
In order to prevent this issue to happen, it is better to use the form id instead of t('Log in').
Postponed: needs info
11.0 🔥
phpunit
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Is this still relevant since
✨
Use one-time login link instead of user login form in BrowserTestBase tests
Fixed
? In most cases the test no longer requires the login form, unless the $useOneTimeLoginLinks property is false. Furthermore, the report in the issue summary suggests you're using
Drupal Test Traits →
, so you could always override the drupalLogin method in your own test base class.