Switch over to GitLab CI

(I hope reopening an old but relevant ticket is not a problem rather than opening a new one instead and generating more noise in the issue queue.)

While working on the 📌 Automated Drupal 11 compatibility fixes for captcha Needs work @japerry → correctly pointed out that this project first needs its testing suite to pass cleanly on the default branch HEAD. Currently, this is not the case due to an error as per the latest pipeline (#138492 at the time of writing).

I chose this ticket for reviving because the message of the commit triggering the failed pipeline suggests that it was the latest point when changes were made on Apr 5, 2024.

To sum up, I think first we need to fix the erroneous test, get the pipeline green, and then get back to the topic of D11 compatibility.

Thanks @Balu Ertl you're right. Sorry for my mistake!

Balu Ertl → changed the visibility of the branch 2.x to hidden.

I want to open a debate on the practical value of these two tests: \Drupal\Tests\image_captcha\Functional\ImageCaptchaInstallationTest::testInstallation() and testUninstallation().

To my understanding, ensuring that sub-modules cannot get installed without their dependencies also being installed belongs to the responsibility domain of the core. (I found the \Drupal\Tests\TestRequirementsTrait::checkModuleRequirements() the most relevant here.) If my knowledge is correct, then I'd like to hear some arguments in favour of keeping these two tests.

Why is it a problem?

The wording of some localization UI strings (eg. “Some required modules must be…”) was corrected to the good between minor core versions:

• Core version 10.2.7 uses the verb “enabled”
• Core version 10.3.0 uses the verb “installed”

Therefore our single test suite of this contrib module is unable to cover both “current” and “previous minor” environments at the same time – one will always fail.

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