katalyst-bdd-architecture

BDD tests using ports and adapters architecture separate concerns into Test, Domain, Port, Adapter, and Infrastructure layers, enabling you to swap implementations without modifying your test suite. This strict boundary improves maintainability and testability across API and UI flows.

Dependency injection in a Playwright BDD framework uses the createBddTest function to wire together ports, adapters, and world state. This allows you to configure default or customized implementations for API, UI, authentication, and cleanup flows seamlessly.

The best way to write custom step definitions for hybrid API and UI tests is to extend the framework with new ports and custom adapters. This approach maintains clean boundaries while integrating both API and UI interactions within your behavior-driven development scenarios.

You need to implement custom ApiPort and UiPort adapters when extending the framework beyond built-in capabilities or swapping default implementations. This allows you to support specific hybrid test scenarios without altering the core domain logic or existing step definitions.

Yes, you can swap authentication and cleanup flows without changing existing BDD tests by implementing custom AuthPort and CleanupPort adapters. The ports and adapters architecture ensures that infrastructure changes do not impact your domain logic or test steps.