x-troubleshooting

Diagnosing failing tests caused by local environment and .env issues involves running a read-only diagnostic script that collects actionable runtime context and checks relevant environment files to identify state mismatches.

The best way to troubleshoot Docker-dependent service failures is to capture running containers and process-level port usage signals, narrowing down connectivity issues and readiness problems affecting your local services.

Checking port binding and readiness problems when API tests fail requires executing a local diagnostic script with optional port arguments to collect process-level port usage data and narrow down connectivity issues.

Yes, you can use this diagnostic approach for BDD runner malfunctions; it guides you to split investigation paths for API versus browser runner failures and verify feature and tag discovery when needed.

The troubleshooting script does not require write permissions or modify Docker containers; it executes safe, read-only commands to collect local diagnostic snapshots without altering your runtime environment.

You need to collect runtime context snapshots for connectivity issues when tests behave unexpectedly, tying observed runtime context to test assumptions to spot differences between process-wide state and expected outcomes.