Problem/Motivation

Drupal 11.4 removed the Article and Basic page content types from the Standard installation profile. Many of the module's functional tests rely on those content types existing (through DomainTestBase and the Standard profile), so they now fail on Drupal 11.4 with Behat/Mink ExpectationException errors on node forms and content assertions.

Around 25 functional test classes are affected across every submodule, for example DomainSourcePathAliasTest, DomainAccessPermissionsTest, DomainEntityAccessTest, DomainAccessDefaultValueTest, DomainContentCountTest and DomainSourceEntityReferenceTest.

This is unrelated to the PHPStan work in #3612201: that pipeline is green on phpstan, phpcs and cspell but red on phpunit for this reason.

Steps to reproduce

Run the functional test suite against Drupal 11.4.

Proposed resolution

Stop relying on the Standard profile providing the page and article content types. Create the required content types explicitly in the test setup (for example in DomainTestBase::setUp()) and adjust the field and form-display configuration the tests depend on.

Remaining tasks

Write a merge request; review; commit.

Issue fork domain-3612441

Command icon Show commands

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

mably created an issue. See original summary.

  • mably committed c4245073 on 4.x
    fix: #3612441 Functional tests fail on Drupal 11.4: Standard profile no...

  • mably committed cbf8ece7 on 3.x
    fix: #3612441 Functional tests fail on Drupal 11.4: Standard profile no...

  • mably committed 8bc478b2 on 3.0.x
    fix: #3612441 Functional tests fail on Drupal 11.4: Standard profile no...
mably’s picture

Status: Active » Needs review

  • mably committed 35e35a84 on 2.0.x
    fix: #3612441 Functional tests fail on Drupal 11.4: Standard profile no...
mably’s picture

Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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