integration-test-v4

Automate integration tests for merged code by providing the implementation PR number and metadata to a PR-driven workflow that branches from main and generates end-to-end tests. It validates real system behavior against production-like environments before PR validation.

Yes, you can generate integration tests using Testcontainers patterns that cover repository operations, HTTP endpoints, and database interactions. The workflow reads architecture docs and existing test fixtures to validate real infrastructure and data flows.

You need the merged implementation PR number and related metadata. The workflow reads the implementation PR, loads project standards, reads architecture docs, and uses existing test fixtures to generate and execute the integration tests.

Yes, the workflow includes an optional Fix Mode to address review feedback. It plans, executes, and validates changes in a PR-based workflow, allowing you to correct generated tests and resolve infrastructure validation failures.

The workflow ensures alignment by loading project standards and reading architecture docs before generating tests. It uses existing test fixtures and Testcontainers patterns to validate real system behavior across repository changes for production-like environments.

The best way to validate merged code is using a PR-driven workflow with Testcontainers to orchestrate end-to-end integration tests. It reads the implementation PR, branches from main, and validates repository operations and data flows before final PR validation.