Usage
The extension-plus-context model - composing a context, registering it, configuring the traits it holds and switching their hooks off, and what happens to the entities a scenario creates.
Configuration
Behat Steps reads its configuration from suites and context arguments, the extension key, tags and environment variables. This page covers all 4 channels and lists every option and tag.
Scenario styles
The imperative and declarative scenario styles, the job each one does, and how to graduate from the shipped steps to domain steps built on the same helpers.
HTTP clients
The 3 clients a step sends its own requests through, where their settings come from, and how to change them.
Writing tests with AI assistants
Point an AI coding agent at the step and helper references that ship with the package, so it writes scenarios from steps that exist.