Closed (fixed)
Project:
DataBase Email Encryption
Version:
3.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Reporter:
Created:
15 Jul 2024 at 13:46 UTC
Updated:
18 Sep 2025 at 21:19 UTC
Jump to comment: Most recent
phpunit tests are failing:
1) Drupal\Tests\dbee\Functional\DbeeAllUsersBatchTest::testAllUsers
Behat\Mink\Exception\ResponseTextException: The text "been enabled" was not found anywhere in the text of the current page.
/drupal/vendor/behat/mink/src/WebAssert.php:907
/drupal/vendor/behat/mink/src/WebAssert.php:293
/drupal/web/core/tests/Drupal/Tests/WebAssert.php:975
/drupal/web/modules/contrib/dbee/tests/src/Functional/DbeeWebSwitchTestBase.php:102
/drupal/web/modules/contrib/dbee/tests/src/Functional/DbeeAllUsersTest.php:23
/drupal/vendor/phpunit/phpunit/src/Framework/TestResult.php:729
4) Drupal\Tests\dbee\Functional\DbeeEditUserTest::testEditUser
Behat\Mink\Exception\ResponseTextException: The text "The email address CVDWRJB4@EXAMPLE.COM is already taken." was not found anywhere in the text of the current page.
/drupal/vendor/behat/mink/src/WebAssert.php:907
/drupal/vendor/behat/mink/src/WebAssert.php:293
/drupal/web/core/tests/Drupal/Tests/WebAssert.php:975
/drupal/web/modules/contrib/dbee/tests/src/Functional/DbeeEditUserTest.php:143
/drupal/vendor/phpunit/phpunit/src/Framework/TestResult.php:729
Fix it, let's.
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
elc commentedThe remaining test failure is actually showing up a functionality failure.
The query alter isn't working like it should for the UserMailUnique constraint which was added to Drupal core here https://git.drupalcode.org/project/drupal/-/commit/fe0fd73a2fb6aee76dc14...
Comment #4
elc commentedUpdating description and category as this is failure is a bug.
Comment #6
thedut commentedHello elc,
Thank you for this issue.
Fix commited to the new 4.x branch.
Comment #7
elc commentedCould you make a 4.x-dev release so that it can be tested/used? And issues could be logged against 4.x-dev too. Is the 3.1.x branch being dropped?
It looks like the constraint could be ported back to 3.x so that it could still support Drupal 10 too (I'm stuck there are present). Would that need to target 3.0.x or 3.1.x?
Comment #8
thedut commentedHello,
I have made a mistake creating the v4 branch . Since the V3.1 is still as RC -> I wil stuck on in and release soon as v.3.1rc2 or directly v3.1
I keep supporting Drupal 10.
The v4 branch will for the future.
Comment #9
thedut commentedFixed into the 3.1.0-rc2 release.