Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Posted by xjm
Problem/Motivation
The Field UI tests currently depend on the node module. This is less than ideal for two reasons:
- The tests are coupled to the node module, which means more overhead and more difficulty making changes.
- Node being "special" hides bugs like #1845372: Deleting a field from a non-node entity bundle results in an Entity Field Query Exception.
Proposed resolution
- Convert most Field UI tests to use a test entity type instead.
- Move tests of the field UI specific entity types (node, taxonomy, etc.) into separate test classes.
Comments
Comment #1
xjmComment #2
xjmComment #3
xjmComment #4
netsensei CreditAttribution: netsensei commentedComment #4.0
netsensei CreditAttribution: netsensei commentedRemoving myself from the author field so that I can unfollow the issue. --xjm
Comment #5
vurt CreditAttribution: vurt commentedI wanted to work on this but I could not find the tests referenced - is this issue still valid?
Comment #6
blackra CreditAttribution: blackra at SK Plus commentedI am removing the Novice tag from this issue because it is not clear what part of this a novice could usefully do at the moment.
I’m using this documentation as a source: https://www.drupal.org/core-mentoring/novice-tasks#avoid
Comment #7
blackra CreditAttribution: blackra at SK Plus commentedIt has been a while since there was any activity on this issue. Unassigning this so it is clear this can be worked on by anyone. If you have partial work that was done, please still post it, or post any questions you had from when you were working on it.