Files
HAL9000 2c2b4e8813
CI / push-validation (pull_request) Successful in 19s
CI / helm (pull_request) Successful in 30s
CI / lint (pull_request) Successful in 44s
CI / build (pull_request) Successful in 47s
CI / quality (pull_request) Successful in 50s
CI / typecheck (pull_request) Successful in 1m4s
CI / security (pull_request) Successful in 1m16s
CI / unit_tests (pull_request) Successful in 6m12s
CI / docker (pull_request) Successful in 1m23s
CI / coverage (pull_request) Successful in 16m5s
CI / integration_tests (pull_request) Successful in 22m39s
CI / status-check (pull_request) Successful in 2s
test(actor): add @tdd_issue_1429 regression tests for actor_ref field reading
Add Behave feature file and Robot Framework integration tests covering
the two compiler functions fixed in issue #1429:

- _map_node(): SUBGRAPH node's NodeConfig.subgraph is now populated from
  node.actor_ref instead of config.get("actor_ref") which always returned None
- compile_actor(): metadata.subgraph_refs is now populated from
  node_def.actor_ref instead of node_def.config.get("actor_ref", "") which
  always returned an empty string

Three Behave scenarios tagged @tdd_issue @tdd_issue_1429 covering:
  1. NodeConfig.subgraph field populated from actor_ref (_map_node fix)
  2. metadata.subgraph_refs populated from actor_ref (compile_actor fix)
  3. Both fields correct together with a realistic actor ref

Two Robot Framework integration tests in tdd_actor_compiler_actor_ref_1429.robot
with a self-contained Python helper that exercises both code paths in isolation.

ISSUES CLOSED: #1429
2026-05-30 02:07:41 -04:00
..