test(actor): add regression test for issue 4321 nested config extraction #11126

Merged
CoreRasurae merged 1 commits from fix/actor-registry-provider-extraction into master 2026-05-12 13:03:03 +00:00

1 Commits

Author SHA1 Message Date
CoreRasurae f6ca9b7291 test(actor): add regression test for issue 4321 nested config extraction
CI / helm (pull_request) Successful in 40s
CI / build (pull_request) Successful in 53s
CI / lint (pull_request) Successful in 1m1s
CI / quality (pull_request) Successful in 1m12s
CI / security (pull_request) Successful in 1m28s
CI / typecheck (pull_request) Successful in 1m40s
CI / integration_tests (pull_request) Successful in 4m23s
CI / unit_tests (pull_request) Successful in 4m54s
CI / push-validation (pull_request) Successful in 22s
CI / docker (pull_request) Successful in 1m34s
CI / coverage (pull_request) Successful in 13m34s
CI / status-check (pull_request) Successful in 4s
Add BDD regression test for Forgejo issue 4321: ActorRegistry.add()
fails to extract provider and model from nested actor config.

The test verifies that when type is only at the nested actors map level
(not at top level), provider and model are correctly extracted from the
nested config block.

This scenario is already handled correctly by the _extract_nested_v3_config()
function added in commit 78be0887 (issue #4300). The test confirms the fix
works as expected and prevents future regressions.

Tags: @tdd_issue @tdd_issue_4321

ISSUES CLOSED: #4321
2026-05-12 13:42:41 +01:00