aibdd.auto.php.it.handlers.aggregate-given

Creating initial aggregate state for Given steps involves building required entities and persisting them via WP Factory Methods and Repository.save(). This handler maps natural keys to IDs, ensuring deterministic preconditions and supporting DataTables for multi-entity relationships in WordPress BDD tests.

The best way to persist test data using WordPress factory methods in BDD scenarios is to apply Repository.save() after entity creation. This approach ensures deterministic state creation by mapping natural keys to generated IDs for reliable subsequent test step references.

Yes, you can use DataTables to create multiple related entities in WordPress test repositories. The aggregate state handler supports DataTables and multi-entity relationships, allowing you to define complex pre-existing data structures and persist them via the repository layer.

You need natural key mapping when setting up WordPress test data for BDD steps to capture and link generated entity IDs back to readable keys. This ensures later Then and When steps can reliably reference the correct pre-existing aggregate state without hardcoding database identifiers.

No, this Given step handler relies on an existing repository layer and WP Factory Methods to persist data. You must have the WordPress test environment and repository infrastructure configured before using it to initialize aggregate states and save entities.