protected function TaxonomyTermReferenceFieldTest::setUp in Drupal 10
Same name and namespace in other branches
- 8 core/modules/taxonomy/tests/src/Unit/Plugin/migrate/field/TaxonomyTermReferenceFieldTest.php \Drupal\Tests\taxonomy\Unit\Plugin\migrate\field\TaxonomyTermReferenceFieldTest::setUp()
- 9 core/modules/taxonomy/tests/src/Unit/Plugin/migrate/field/TaxonomyTermReferenceFieldTest.php \Drupal\Tests\taxonomy\Unit\Plugin\migrate\field\TaxonomyTermReferenceFieldTest::setUp()
Overrides UnitTestCase::setUp
File
- core/
modules/ taxonomy/ tests/ src/ Unit/ Plugin/ migrate/ field/ TaxonomyTermReferenceFieldTest.php, line 29
Class
- TaxonomyTermReferenceFieldTest
- @coversDefaultClass \Drupal\taxonomy\Plugin\migrate\field\TaxonomyTermReference @group taxonomy
Namespace
Drupal\Tests\taxonomy\Unit\Plugin\migrate\fieldCode
protected function setUp() : void {
$this->plugin = new TaxonomyTermReference([], 'taxonomy', []);
$migration = $this
->prophesize(MigrationInterface::class);
// The plugin's defineValueProcessPipeline() method will call
// setProcessOfProperty() 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 setProcessOfProperty().
$migration
->setProcessOfProperty(Argument::type('string'), Argument::type('array'))
->will(function ($arguments) use ($migration) {
$migration
->getProcess()
->willReturn($arguments[1]);
});
$this->migration = $migration
->reveal();
}