Problem/Motivation
One of the advantages of GitLab CI is the ability to test against multiple Drupal versions.
This change is to adopt tests for the previous and next major versions of Drupal.
It also tests against the maximum supported PHP version, so while the default tests run on 8.1, this will also test against PHP 8.3.
We also have the ability to test against the previous and next major releases. Since we don't support Drupal 9, there's no point in testing against previous Major. We can look at testing against next major after this, but that will require checking compatibility of dependencies.
Steps to reproduce
N/A
Proposed resolution
Enable testing against previous and next minor releases (currently 10.3)- RendererInterface::renderPlain() is deprecated
- Test failure of:
CoreExperimentalLabelTest::testCoreExperimentalLabel - Text changed in 10.3 Module Project Browser has been
enabledinstalled - #3450499: project_browser_test.time service tests fail on 10.3
Issue fork project_browser-3423697
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
Comment #3
lostcarpark commentedComment #4
chrisfromredfinComment #5
simeComment #6
simeComment #7
simeThe fix for this is suggested in comments https://www.drupal.org/node/3407994, please confirm if you want to proceed with this.
Comment #8
simeComment #9
simeI've listed the failures in the Proposed Resolution section. The main thing i don't know is how to variegate a test for two different outcomes - eg where the status message has changed after you install a module.
Comment #10
simeI temporarily disabled OPT_IN_TEST_PREVIOUS_MINOR coverage (10.1 becomes unsupported July) just to have better clarity on what needs to be done.
I have fixed everything except
InstallerControllerTest::testInstallUnlockMessage. I don't know what is happening there on 10.3. It should be running into a lock in this test but nothing is returned from the tempstore.Note that I merged the fixes on #3450499: project_browser_test.time service tests fail on 10.3 into this (to make it easier to track progress), so please merge that first to give credit to @kimpepper and @mstrelan.
Comment #11
simeAdding relationship to #3446528: Run tests on 11.x and declare compatibility with it as there is overlapping work.
Comment #12
simePassing, I picked a few things that seemed like improvements/fixes over head. Please also credit
kimpepperandmstrelanfor the deprecation helper help.Comment #13
phenaproximaI love that DeprecationHelper thing. Wish I'd known about it before! But hey, you gotta learn sometime.
The only thing is that we shouldn't be using Workspaces to test experimental stuff.
Comment #14
simeI'm not sure about Workspaces, the test is pre-existing and seems to just be a canary test. But now that Workspaces is marked stable in 10.3 do we even need this test?
Comment #15
phenaproximaYes. We do want to test that Project Browser handles experimental modules in a particular way. The use of Workspaces was probably just a convenience thing at the time.
Comment #16
simeOk i see where I've misunderstood the purpose of the test. Lemme fix.
Comment #17
simeComment #18
phenaproximaThis rocks!
Comment #20
chrisfromredfinwhen I bump you bump we bump (version numbers)