test(integration): workflow example 18 — container with remote repo clone (trusted profile) #782

Open
opened 2026-03-12 19:40:50 +00:00 by freemo · 0 comments
Owner

Metadata

  • Commit Message: test(integration): workflow example 18 — container with remote repo clone (trusted profile)
  • Branch: test/int-wf18-container-clone

Background

Integration test for Specification Workflow Example 18: Container with Remote Repo Clone. Exercises container-instance with --clone-into for remote repo cloning, plan-level execution environment with fallback priority, and commit+push apply mode using mocked LLM providers and mocked container/git operations.

Runs within the standard nox -s integration_tests session using mocked LLM providers.

Expected Behavior

The integration test validates container clone lifecycle with mocked LLM and mocked container/git runtime. Clone-into registration, fallback execution environment priority, and commit+push apply mode are verified.

Acceptance Criteria

  • Robot Framework test suite in robot/ directory (standard integration tests)
  • Test uses integration-appropriate mocking (mocked LLM, mocked container/git)
  • Test registers container-instance with --clone-into
  • Test executes plan with --execution-environment and --execution-env-priority fallback
  • Test verifies container clone and ready sequence
  • Test verifies commit+push apply mode
  • Test passes via nox -s integration_tests
  • Coverage >=97% maintained

Subtasks

  • Write Robot Framework integration test suite for workflow example 18
  • Configure mocked LLM and container/git responses
  • Implement container clone workflow with fallback priority
  • Verify via nox -s integration_tests
  • Verify coverage >=97% via nox -s coverage_report
  • Run nox (all default sessions), fix any errors

Definition of Done

This issue is complete when:

  • All subtasks above are completed and checked off.
  • A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details.
  • The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
  • The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.
## Metadata - **Commit Message**: `test(integration): workflow example 18 — container with remote repo clone (trusted profile)` - **Branch**: `test/int-wf18-container-clone` ## Background Integration test for Specification Workflow Example 18: Container with Remote Repo Clone. Exercises container-instance with `--clone-into` for remote repo cloning, plan-level execution environment with fallback priority, and commit+push apply mode using mocked LLM providers and mocked container/git operations. Runs within the standard `nox -s integration_tests` session using mocked LLM providers. ## Expected Behavior The integration test validates container clone lifecycle with mocked LLM and mocked container/git runtime. Clone-into registration, fallback execution environment priority, and commit+push apply mode are verified. ## Acceptance Criteria - [ ] Robot Framework test suite in `robot/` directory (standard integration tests) - [ ] Test uses integration-appropriate mocking (mocked LLM, mocked container/git) - [ ] Test registers container-instance with --clone-into - [ ] Test executes plan with --execution-environment and --execution-env-priority fallback - [ ] Test verifies container clone and ready sequence - [ ] Test verifies commit+push apply mode - [ ] Test passes via `nox -s integration_tests` - [ ] Coverage >=97% maintained ## Subtasks - [ ] Write Robot Framework integration test suite for workflow example 18 - [ ] Configure mocked LLM and container/git responses - [ ] Implement container clone workflow with fallback priority - [ ] Verify via `nox -s integration_tests` - [ ] Verify coverage >=97% via `nox -s coverage_report` - [ ] Run `nox` (all default sessions), fix any errors ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done.
freemo added this to the v3.8.0 milestone 2026-03-12 19:40:51 +00:00
freemo self-assigned this 2026-04-02 18:45:30 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
cleveragents/cleveragents-core#782
No description provided.