Problem/Motivation

The Automatic Updates module -- which will be moved into core -- and some of its contrib sub-modules, needs to be able to use fake release history XML in its functional tests, since it deals with the update system.

Right now, we achieve this by wholesale copying UpdateTestController::updateTest() into the Automatic Updates module's testing framework. We will probably continue to need hacks like that...unless core could change UpdateTestController::updateTest() in such a way that it can serve release history XML from any arbitrary path.

Steps to reproduce

N/A

Proposed resolution

Change UpdateTestController::updateTest() so that it can serve fake release history XML from any path, not just the update_test module's fixtures.

Remaining tasks

Make it happen.

User interface changes

None.

API changes

None. This is part of a test module, but as far as I can tell, it's not part of the official testing system.

Data model changes

None.

Release notes snippet

None needed.

Comments

phenaproxima created an issue. See original summary.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

dww’s picture

dww
we/he/they
commented

I'm open to improving this. MRs welcome. 😉

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.