aibdd.auto.csharp.it.handlers.aggregate-then

Verifying aggregate final state in Gherkin integration tests involves injecting AppDbContext, clearing the ChangeTracker to avoid cache interference, and querying PostgreSQL via EF Core composite-key lookups. This ensures persisted data matches domain expectations in .NET 8+ integration testing scenarios.

EF Core ChangeTracker returns stale data during SpecFlow integration testing because cached entities bypass database queries. Calling ChangeTracker.Clear() before asserting aggregate final state forces DbContext to query PostgreSQL directly, ensuring Gherkin tests validate actual persisted database outcomes rather than in-memory cached domain objects.

Asserting aggregate state queries the database directly via EF Core DbContext to verify persisted domain entity outcomes, while ReadModel verification checks projected query models. Aggregate-then testing clears the ChangeTracker and uses composite-key lookups to ensure the data layer matches Gherkin domain expectations accurately without cache interference.

Yes, Chinese Gherkin step text can be mapped to C# enum states for PostgreSQL integration testing. This Skill supports language mapping between domain states described in Gherkin scenarios and C# enums, ensuring status field consistency when verifying aggregate final state directly from the database through EF Core DbContext.

This aggregate state verification approach supports composite-key lookups with EF Core. It queries PostgreSQL through AppDbContext using composite primary keys to retrieve persisted entities, ensuring accurate verification of aggregate final state in Gherkin integration testing scenarios for .NET 8+ applications without ChangeTracker cache interference.

You should clear ChangeTracker in EF Core integration tests for BDD scenarios immediately before querying aggregate final state from the database. Calling ChangeTracker.Clear() prevents cached entities from interfering with Gherkin assertions, ensuring the test verifies actual PostgreSQL persistence outcomes rather than stale in-memory domain objects.