Problem/Motivation
Because of #3083275: [meta] Update tests that rely on Classy to not rely on it anymore and Classy being deprecated in Drupal 9 + removed in Drupal 10,: Tests that aren't specifically testing Classy yet declare $defaultTheme = 'classy'; should be refactored to use Stark as the default theme instead.
Proposed resolution
Change all tests in this module to use Stark as the default theme, and refactor the tests where needed so they continue to function properly.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 3274066-2.patch | 10.95 KB | danflanagan8 |
Comments
Comment #2
danflanagan8As anticipated, node was a little more complicated than most other modules. Some important notes for reviewers:
1.
NodeDisplayConfigurableTeststill has Classy in a data provider. I added a todo to remove it. The bigger problem withNodeDisplayConfigurableTestis that it has a huge reliance on RDF. I think it probably makes more sense to deal with that as part of #3273976: [Meta] Tasks to remove RDF from core and move to contrib.2.
PagePreviewTeststill uses Classy as the base theme. I added a todo with the reason and opened the followup: #3274077: Update PagePreviewTest to use starterkit3. In
FrontPageTestI essential changed a selector to find theviews-element-containerinstead of theviews-frontpageclass. I don't believe this effects the robustness of the test. This particular coverage was added in #2191011: PHP Warnings in views_preprocess_page() caused by frontpage view. It's a bug about views_preprocess_page, but there's nothing special about it being the front page. So just showing ANY view appears should be just fine, and even that is likely overkill. The test would fail before that assertion if there were a regression for that particular bug.UPDATE: Re: Item 3: On closer inspection views_preprocess_page doesn't even exist anymore! I think that test method
FrontPageTest::testAdminFrontPageis stale code that could be removed entirely.Comment #3
danflanagan8tagging
Comment #4
larowlanLet's put item 3 into a followup to not halt progress here.
This looks good to me
Comment #5
alexpottCommitted and pushed 4fa09fb85c to 10.0.x and 532250841e to 9.4.x. Thanks!
Tagging with needs follow-up for #2.3
Comment #8
danflanagan8Thanks, @alexpott!
I created a followup, so I'm removing the tag. Cheers!