A factory is a class that extends the CakephpFixtureFactories\Factory\BaseFactory. It should implement the following two methods:
getRootTableRegistryName()which indicates the model, or the table name in PascalCase, where the factory will insert its fixtures;setDefaultTemplate()which sets the default configuration of each entity created by the factory.
The Faker\Generator is used in order to randomly populate fields, and is anytime available using $this->getFaker().
Here is further documentation on Fake.
Let us consider for example a model Articles, related to multiple Authors.
This could be for example the ArticleFactory. Per default the fields title and body are set with Faker and two associated authors are created.
namespace App\Test\Factory;
use CakephpFixtureFactories\Factory\BaseFactory;
use Faker\Generator;
class ArticleFactory extends BaseFactory
{
/**
* Defines the Table Registry used to generate entities with
* @return string
*/
protected function getRootTableRegistryName(): string
{
return "Articles"; // PascalCase of the factory's table.
}
/**
* Defines the default values of you factory. Useful for
* not nullable fields.
* Use the patchData method to set the field values.
* You may use methods of the factory here
* @return void
*/
protected function setDefaultTemplate(): void
{
$this->setDefaultData(function(Generator $faker) {
return [
'title' => $faker->text(30),
'body' => $faker->text(1000),
];
})
->withAuthors(2);
}
public function withAuthors($parameter = null, int $n = 1): self
{
return $this->with('Authors', AuthorFactory::make($parameter, $n));
}
/**
* Set the Article's title as a random job title
* @return ArticleFactory
*/
public function setJobTitle()
{
return $this->setField('title', $this->getFaker()->jobTitle());
}
}You may add any methods related to your business model, such as setJobTitle to help you build efficient and reusable factories.
If a field is required in the database, it will have to be populated in the setDefaultTemplate method. You may simply set it to a fixed value, for example 1.
The factories will generate data in the locale of your application, if the latter is supported by faker.
Assuming your application namespace in App, factories should be placed in the App\Test\Factory namespace of your application.
Or for a plugin Foo, in Foo\Test\Factory.
You may change that by setting in your configuration the key FixtureFactories.testFixtureNamespace to the desired namespace. E.g.
in tests\bootstrap.php or in the setUp() method of a test case:
use Cake\Core\Configure;
Configure::write('FixtureFactories.testFixtureNamespace', 'MyApp\Test\Factory');By default, each entity's setters are applied. You may deactivate one or several setters by default
by defining the protected property skippedSetters of a given factory. You may also overwrite this set of setters
with the public method skipSettersFor.
namespace App\Test\Factory;
...
class UserFactory extends BaseFactory
{
protected $skippedSetters = [
'password',
];
...
}or
UserFactory::make([
'username' => '[email protected]',
'password' => 'secret',
])->skipSetterFor('password')->getEntity();This can be useful for setters with heavy computation costs, such as hashing.
It is not rare to have to create entities associated with an entity that should remain constant and should not be recreated once it was already persisted. For example, if you create 5 cities within a country, you will not want to have 5 countries created. This might collide with the constrains of your schema. The same goes of course with primary keys.
The fixture factories offer to define unique properties, under the protected property $uniqueProperties. For example given a country factory.
namespace App\Test\Factory;
...
class CountryFactory extends BaseFactory
{
protected $uniqueProperties = [
'name',
];
...
}Knowing the property name is unique, the country factory
will be cautious whenever the property name is set by the developer.
Running
CityFactory::make(5)->with('Country', 'Foo')->persist();will create 5 cities all associated to one unique country. If you perform that same operation again, you will have 10 cities, all associated to one single country.
The uniqueness of the primary keys is handled exactely the same way as described above, with the particularity that you do not have to define them as unique. The factory cannot read the uniqueness of a property in the schema, but it knows which properties are primary keys. Therefore, running:
CityFactory::make(5)->with('Country', ['myPrimaryKey' => 1])->persist();will behave the same as if the primary key myPrimaryKey had been defined unique. In short, the factories
do the job for you.
This and the following sub-sections address to CakePHP applications.
With the aim of persisting data in the database as straightforwardly as possible, all validations and rules
are deactivated when creating CakePHP entities and persisting them to the database. Validation and rules may be reactivated / customized by overwriting
the properties $marshallerOptions and $saveOptions in the factory concerned.
Per default, all model events of a factory's root table and their behaviors are switched off except those of the timestamp behavior.
The intention is to create fixtures as fast and transparently as possible without interfering with the model events.
It is however possible to activate an event model with the method listeningToModelEvents.
This can be made on the fly:
$article = ArticleFactory::make()->listeningToModelEvents('Model.beforeMarshal')->getEntity();or per default in the factory's initialize() method:
protected function initialize(): void
{
$this->listeningToModelEvents([
'Model.beforeMarshal',
'Model.beforeSave',
]);
}Note that you can provide either a single event, or an array of events. You will find a list of all model events here.
It is possible to activate the model events of a behavior in the same way with the method listeningToBehaviors.
This can be made on the fly:
$article = ArticleFactory::make()->listeningToBehaviors('Sluggable')->getEntity();or per default in the factory's setDefaultTemplate method.
Additionally, you can declare a behavior globally. This can be useful for behaviors that impact a large amount of tables and for which not nullable fields need to be populated.
You may save in your configuration file, under the key FixtureFactories.testFixtureGlobalBehaviors, all the behaviors that will be listened to, provided that the root table itself is listening to them.
use Cake\Core\Configure;
Configure::write('FixtureFactories.testFixtureGlobalBehaviors', [
'SomeBehaviorUsedInMultipleTables',
]);Note that even if the behavior is located in a plugin, you should, according to CakePHP conventions, provide the name of the behavior only. Provide BehaviorName and not SomeVendor/WithPluginName.BehaviorName.