fix: #3621553 Temporarily remove the Entity Clone functional testing coverage, which fails now the module is not installed

Rajab Natshahrequested to merge
issue/varbase_starter-3621553:3621553-the-11-content-workflow-suite into 1.0.x

Issue: #3621553

The 1.0.x branch is red on one scenario:

1) Scenario: Check that the webmaster can access the Entity clone settings
   tests/features/11-content-workflow/11-03-cloning-content-and-entities.feature:8
   Then I should see "Entity Clone Settings"
   locator.waitFor: Timeout 5000ms exceeded.

Entity Clone was temporarily removed from the base recipes that required it (#3621449, #3621450, #3621451) because it has no stable release and a Drupal CMS site template must resolve at the default minimum-stability: stable. See #3189738.

The module is therefore not installed, /admin/config/system/entity-clone does not exist, and the test fails. The test is right about what it checks; what it checks is no longer part of Varbase.

What changed

  • Removed tests/features/11-content-workflow/11-03-cloning-content-and-entities.feature.
  • Updated the suite README.md table: 13 scenarios across 3 feature files.

The two negative scenarios in that file went with it. They passed only because nobody can see a page that is not there, which is not the access control they were written to prove.

Temporary. When Entity Clone has a stable release and returns to the base recipes, this coverage returns with it unchanged.

Checkpoints

  • Addition/Change/Update/Fix
  • Testing to ensure no regression
  • Reviewed by a human
  • Code review by maintainers
  • Release

This work was done with the help of AI, and reviewed by a human. Per the Drupal AI policy.

Edited by Rajab Natshah

Merge request reports