Drupal Answers is a question and answer site for Drupal developers and administrators. It only takes a minute to sign up.
Sign up to join this community
I am running a Functional test in a class derived from BrowserTestBase. Line 105 of the test method has this assertion:
$this->assertSession()->linkExists('10000003');
The test output says:
Behat\Mink\Exception\ExpectationException: Link with label 10000003 found.
identifying line 105 as the line where the exception occurred. If it found the link, why does it consider that an error?
Aha! It appears that the WebAssert class is inconsistent in what it reports for testing errors. Sometimes it describes what shouldn't have happened: the previous error I got was described as
Input "relationship-type" cannot take "2" as a value, ...
For this latest test, however, it did the opposite, describing not what went wrong, but what the test wanted to happen. Despite the output which seemed to say the link was found, when I captured the output I discovered that the link was, in fact, not there. Others may disagree, but I think a consistent approach would be a good thing here. 😅
[Edit: this is fixed in Drupal 10, which correctly reports what caused the failure.]
assert() method (called by WebAssert::linkExists()) states that the $message argument is the "failure message." All of the invocations of assert() by the class implementing it confirm that the message is supposed to describe the failure, rather than assert what should have happened. I will file a bug report.
Mar 25 at 11:48