Make tests pass

The easiest solution may be to pin the version of the template. It could be pinned to the latest version of template 1.5.x.

Pinning the version would be a workable temporary solution, but we would then still have to update the template later.

It looks like the failures are just because in the test fixes introduced in ✨ Drupal 11 compatibility fixes for webform Active we are not making a distinction between Drupal 11.0 and 11.1. Now tests are running on Drupal 11.0.5, but some of the tests are checking features introduced in 11.1 (like ✨ Continuation Add Views EntityReference filter to be available for all entity reference fields Needs work and 📌 Use easily recognizable date format RTBC )

I'm hoping that fixing this will turn the pipelines green.

Yay green!

Tests were passing but now they are failing again. The "Previous major" tests are passing but not the current version tests.

The test failures are related to ckeditor so it is likely that they would be fixed by completing 📌 Remove legacy ckeditor from codebase. Active .

@liam morland The following issue is in RTBC. Please review and merge it so we can proceed with the current issue.
📌 Remove legacy ckeditor from codebase. Active

Tests are passing again.

Test are not passing again.

Let's see if we can get the tests to pass and potentially tag a beta release for Drupal CMS.

Yes, I was thinking it was time to tag an alpha once tests pass.

If this test was converted to XPath, checking for the needed elements and attributes instead of a specific string, it would probably work without the need for version_compare().

As soon as this test passes and I merge the change, tagging an alpha would be great. For now, I want to avoid any code refactoring.

For Drupal CMS, tagging a beta by 12/8 would be ideal. I will review tickets to see if anything is required for a beta release.

I switched the test to XPath and now the one test passes on all versions.

I initially included a test for the contents of the data-drupal-states attribute, but that didn't work. I suspect we don't need to test that anyway since it is a Drupal internal thing.

Unless you disagree with this approach, I will merge and tag an alpha today. If no release-blockers appear in two weeks, we can have a beta on December 6.

Let's merge it and tag an alpha release.

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

Tests are failing again.

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