Move test methods not directly related to updates for the Drupal project into their own class

Created on 13 April 2020, about 4 years ago
Updated 13 April 2024, 2 months ago

Problem/Motivation

follow up to #3100386: Create contrib update module test cases that use semantic versioning β†’
\Drupal\Tests\update\Functional\UpdateCoreTest mostly has test methods that deal with updates to the core Drupal project has it's name implies.

Certain test methods such as \Drupal\Tests\update\Functional\UpdateCoreTest::testLocalActions() are just general update module tests.

Proposed resolution

Move test methods from \Drupal\Tests\update\Functional\UpdateCoreTest that don't deal with Drupal core update releases to their own class.

Remaining tasks

Review MR 1358, https://git.drupalcode.org/project/drupal/-/merge_requests/1358

User interface changes

API changes

Data model changes

Release notes snippet

πŸ“Œ Task
Status

Fixed

Version

10.3 ✨

Component
UpdateΒ  β†’

Last updated about 14 hours ago

  • Maintained by
  • πŸ‡ΊπŸ‡ΈUnited States @tedbow
  • πŸ‡ΊπŸ‡ΈUnited States @dww
Created by

πŸ‡ΊπŸ‡ΈUnited States tedbow Ithaca, NY, USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.69.0 2024