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 |
|---|---|---|---|
| #3 | 3272543-3.patch | 2.42 KB | danflanagan8 |
Comments
Comment #2
danflanagan8Here's a small one that is a novel scenario. It's a Kernel test that uses classy because the
mark.html.twigtemplate is easy to target. The mark template in the system module has absolutely zero markup, which makes selecting...uh...problematic.So in this case I went he route of creating a test theme in history that provides a copy of the
mark.html.twigtemplate from classy. Seems to me to be the smoothest path forward.Comment #3
danflanagan8Oops. That had a booboo. My new test theme wasn't in its own directory. This one is better.
Comment #4
larowlanShould this test just set $defaultTheme = 'history_test_theme'?
Comment #5
larowlanAh nevermind, its a kernel test
Comment #7
spokjeComment #8
alexpottCommitted and pushed e58aed3e18 to 10.0.x and eabf471d9f to 9.5.x and e095d1ac6c to 9.4.x and 9772963474 to 9.3.x. Thanks!
Backported to 9.3.x to keep tests aligned.