Create common assert entity methods for migration tests

Created on 12 September 2019, over 5 years ago
Updated 22 April 2024, 9 months ago

Problem/Motivation

Many of the Migrate Kernel tests have a method for asserting an entity and the method exists in both the d6 and d7 version of the test. Instead there should be one assertEntity method that is used by both the d6, d7 and future d8 tests. Note that the methods for an entity type may be different from d6 and d7.

Instead, we should use either a base class or a trait to create a set of assertions for all entities.

This has been on my mind for a while but not a priority. However, larowlan asked about making a base class of trait for asserting node revisions [#3079298]-comment #5 β†’ and that drove me to make this issue.

Proposed resolution

Decide if this is worth doing.
Decide if a trait or base class is preferred.
Do the work

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

πŸ“Œ Task
Status

Closed: won't fix

Version

11.0 πŸ”₯

Component
MigrationΒ  β†’

Last updated about 13 hours ago

Created by

πŸ‡³πŸ‡ΏNew Zealand quietone

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.

  • πŸ‡³πŸ‡ΏNew Zealand quietone

    This is really a 'nice to have'. The value of having this is done a bit easier maintenance but it is also not a significant improvement. There are more important issues for people to choose from in core.

Production build 0.71.5 2024