luigidemasi opened a new issue, #20: URL: https://github.com/apache/camel-kit/issues/20
> Imported from [luigidemasi/camel-kit#34](https://github.com/luigidemasi/camel-kit/issues/34), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-05-02. > Closed by commit [c2f5551](https://github.com/luigidemasi/camel-kit/commit/c2f55516fd68e12535e4fb1c3f7c3f28026954a5). --- ## Description Redesign the verification and testing architecture based on the [Environment-in-the-Loop (EITL)](https://arxiv.org/abs/2602.09944) paradigm (Li et al., ReCode '26). This is a significant architectural change that touches the verify loop, test generation, pipeline gates, and Iron Laws. ## Changes ### 1. Environment probe (first step of `camel-execute`) - Generate throwaway skeleton (pom.xml + docker-compose + empty route) before implementation - Classify probe failures as mechanical (auto-fix) or architectural (trigger re-plan) - New guide: `camel-execute/guides/environment-probe.md` ### 2. Eliminate `camel-implement` smoke test - Remove Step 11 (mandatory smoke test) from the orchestrator - Covered by environment probe (pre-implementation) + verify loop (post-implementation) ### 3. Replace verify loop Phases 1/3/4 with Citrus YAML tests - Replace `camel cmd send` + semantic comparison with `camel test run *.it.yaml` - Testcontainers replaces Docker Compose in the verify loop (Docker Compose stays as user artifact) - Citrus manages service lifecycle + app startup via `camel:jbang:run` - Verify loop simplifies from 5 phases to 3 steps (build, Citrus tests, report) - Update `camel-test` to generate Citrus YAML tests with Testcontainers actions ### 4. Test re-generation feedback path - New fix target in error taxonomy: `camel-test` (re-generate test when test is wrong, not code) ### 5. Remove plan→execute approval gate, enable automatic re-planning - Remove approval gate between `camel-plan` and `camel-execute` - Add re-plan loop (max 3 rounds) triggered by architectural failures in probe or verify - Revise Iron Law 3: "No Code Without Spec Approval" → "No Code Without Design Approval" - Update oversight matrix in `camel-ship` ### 6. Update documentation - Update project documentation to reflect the new architecture - Update skill documentation and shared guides ## Files Affected - `camel-execute/SKILL.md` — add probe step, remove plan gate reference - `camel-execute/guides/environment-probe.md` — **new** - `camel-execute/guides/re-plan-loop.md` — **new** (or `shared/re-plan-loop.md`) - `camel-implement/guides/orchestrator.md` — remove Step 11 (smoke test) - `camel-verify/SKILL.md` — update phase list - `camel-verify/guides/verify-loop.md` — replace Phases 1/3/4, simplify to 3 steps - `camel-verify/guides/error-taxonomy.md` — add `camel-test` fix target - `camel-test/guides/test-generation.md` — Citrus YAML with Testcontainers + `camel:jbang:run` - `camel-test/guides/test-runner.md` — `camel test run` instead of `run-tests.sh` - `camel-plan/SKILL.md` — remove execute gate reference - `shared/iron-laws.md` — revise Iron Law 3 - `camel-ship/guides/oversight-matrix.md` — simplify (one gate) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
