Files
freemo f61f29ac26
CI / benchmark-publish (pull_request) Has been skipped
CI / helm (pull_request) Successful in 24s
CI / build (pull_request) Successful in 31s
CI / lint (pull_request) Failing after 34s
CI / security (pull_request) Successful in 56s
CI / quality (pull_request) Successful in 3m45s
CI / typecheck (pull_request) Successful in 3m56s
CI / coverage (pull_request) Has been skipped
CI / benchmark-regression (pull_request) Has been skipped
CI / unit_tests (pull_request) Failing after 5m45s
CI / docker (pull_request) Has been skipped
CI / e2e_tests (pull_request) Failing after 15m5s
CI / integration_tests (pull_request) Failing after 22m5s
CI / status-check (pull_request) Failing after 1s
test(integration): workflow example 16 — devcontainer-driven development (supervised profile)
Add Robot Framework integration test suite and Python helper for
Specification Workflow Example 16: Devcontainer-Driven Development.

Files added:
- robot/wf16_devcontainer.robot: 5 Robot Framework test cases
- robot/helper_wf16_devcontainer.py: Python helper with 5 subcommands

Test coverage:
- WF16 Step 1: Resource auto-detection of .devcontainer/devcontainer.json
  via discover_devcontainers() API
- WF16 Step 2: Project create and link-resource with git-checkout resource
- WF16 Step 3: Plan creation with supervised automation profile
- WF16 Step 4: Plan execute with devcontainer lazy activation (mocked
  container runtime via _MockRunner)
- WF16 Step 5: Plan apply writing changes to host via bind mount tracking

Design decisions:
- Container operations fully mocked via DevcontainerHandler and
  DevcontainerLifecycleService using _MockRunner (no real Docker)
- Container IDs use valid lowercase hex format matching
  _CONTAINER_ID_PATTERN (^[a-f0-9]{12,64}$)
- .devcontainer/devcontainer.json fixture created in temp directory
  for auto-detection testing
- Exercises 6-level execution environment precedence chain (level 3:
  nearest-ancestor devcontainer)

Quality gates: lint PASS, typecheck PASS (0 errors), 5/5 WF16 tests PASS

ISSUES CLOSED: #780
2026-04-02 17:07:24 +00:00
..