>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3431176. --> Reported by: [tr](https://www.drupal.org/user/202830) >>> <p>In regards to: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-17"><a href="https://www.drupal.org/project/ip2country/issues/3431105" title="Status: Closed (outdated)">#3431105: Automated Drupal 11 compatibility fixes for ip2country</a></span></p> <p>Since when is a $defaultTheme required in a subclass of UpdatePathTestBase ? Was the profile used by UpdatePath tests changed recently or something? I don't see any mention in the change records that this changed between D10 and D11.</p> <p>This has never triggered an error or warning in D9 or D10, on Drupal CI or on Gitlab CI.</p> <p>Yes, I am well aware of the old change record <a href="https://www.drupal.org/node/3083055">The 'testing' install profile's setting of a default theme (Classy) is now deprecated</a>, but as I said update path tests have never needed this, I assume because update path tests are run in a profile other than 'testing' or something like that?</p> <p>Core Drupal 10 contains 26 subclasses of UpdatePathTestBase, and only 16 of those declare a $defaultTheme (and apparently only when needed, like with the CKEditor update tests).</p> <p>For example, neither of these subclasses of UpdatePathTestBase declare a $defaultTheme:<br> core/modules/block_content/tests/src/Functional/Update/BlockContentRemoveConstraint.php<br> core/modules/block_content/tests/src/Functional/Update/BlockContentUpdateTest.php</p> <p>Regardless, Rector is telling me this is wrong, but it has never been wrong in the past and is apparently OK for core to do.</p>