Problem/Motivation
The update module has a number of test fixtures that emulate Drupal.org's XML update data:
core/modules/update/tests/modules/update_test/drupal.sec.0.1_0.2.xml
core/modules/update/tests/modules/update_test/drupal.sec.0.2-rc2-b.xml
core/modules/update/tests/modules/update_test/drupal.sec.0.2-rc2.xml
core/modules/update/tests/modules/update_test/drupal.sec.0.2.xml
core/modules/update/tests/modules/update_test/drupal.sec.1.2.xml
core/modules/update/tests/modules/update_test/drupal.sec.1.2_insecure.xmlMost of these are named for the latest releases included in the update data. However, two fixtures added in #2990511: Add comprehensive test coverage for update status for security releases seem to be misnamed:
core/modules/update/tests/modules/update_test/drupal.sec.0.2-rc2-b.xml
and
core/modules/update/tests/modules/update_test/drupal.sec.0.2-rc2.xml
In these two fixtures, the latest release is 8.2.0-rc2, not 8.0.2-rc2. This led to a little confusion during the review process.
Proposed resolution
Rename the fixtures.
Remaining tasks
Confirm that the fixtures should in fact be renamed, rename them, and update the tests that use them.
User interface changes
None.
API changes
Text fixtures are renamed (internal API change for a very recent commit; does not need a CR).
Data model changes
None.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | 2995367-9.patch | 5.59 KB | quietone |
Comments
Comment #2
xjmComment #3
xjmComment #8
larowlanComment #9
quietone commentedI'm working through a list of issue related to updates so even though this is tagged novice I'd like to work on this.
Comment #10
lendudeLooks good, checked some of the others and it does seem that these are the only files affected by this.
Comment #15
xjmCommitted to... let's just say lots of branches. Thanks!