Updated Drupal to 8.6. This goes with the following updates because it's possible...

[yaffs-website] / web / core / modules / file / tests / src / Unit / Plugin / migrate / field / d7 / FileFieldTest.php

diff --git a/web/core/modules/file/tests/src/Unit/Plugin/migrate/field/d7/FileFieldTest.php b/web/core/modules/file/tests/src/Unit/Plugin/migrate/field/d7/FileFieldTest.php
index 36ca6a43d3ca422ec857b0c299e8c02c44461398..8e859165706454de23a60d9297a1a22ddc674676 100644 (file)
--- a/web/core/modules/file/tests/src/Unit/Plugin/migrate/field/d7/FileFieldTest.php
+++ b/web/core/modules/file/tests/src/Unit/Plugin/migrate/field/d7/FileFieldTest.php
@@ -32,7 +32,7 @@ class FileFieldTest extends UnitTestCase {
 
     $migration = $this->prophesize(MigrationInterface::class);
 
-    // The plugin's processFieldValues() method will call
+    // The plugin's defineValueProcessPipeline() method will call
     // mergeProcessOfProperty() and return nothing. So, in order to examine the
     // process pipeline created by the plugin, we need to ensure that
     // getProcess() always returns the last input to mergeProcessOfProperty().
@@ -44,10 +44,10 @@ class FileFieldTest extends UnitTestCase {
   }
 
   /**
-   * @covers ::processFieldValues
+   * @covers ::defineValueProcessPipeline
    */
-  public function testProcessFieldValues() {
-    $this->plugin->processFieldValues($this->migration, 'somefieldname', []);
+  public function testDefineValueProcessPipeline($method = 'defineValueProcessPipeline') {
+    $this->plugin->$method($this->migration, 'somefieldname', []);
 
     $expected = [
       'plugin' => 'sub_process',
@@ -68,7 +68,7 @@ class FileFieldTest extends UnitTestCase {
     return [
       ['image', 'imagefield_widget'],
       ['file', 'filefield_widget'],
-      ['file', 'x_widget']
+      ['file', 'x_widget'],
     ];
   }