refactor(tests): clarify roles of behave and robot framework in test architecture #9219

Open
HAL9000 wants to merge 3 commits from refactor/clarify-behave-robot-framework-roles into master

3 Commits

Author SHA1 Message Date
controller-ci-rerun 3e0b250170 chore: re-trigger CI [controller]
CI / lint (pull_request) Successful in 39s
CI / build (pull_request) Successful in 39s
CI / helm (pull_request) Successful in 33s
CI / quality (pull_request) Successful in 54s
CI / typecheck (pull_request) Successful in 1m7s
CI / push-validation (pull_request) Successful in 39s
CI / security (pull_request) Successful in 1m18s
CI / unit_tests (pull_request) Successful in 4m48s
CI / docker (pull_request) Successful in 1m45s
CI / integration_tests (pull_request) Failing after 7m54s
CI / coverage (pull_request) Successful in 8m34s
CI / status-check (pull_request) Failing after 3s
2026-06-05 17:09:01 -04:00
controller-ci-rerun dad0d6c913 chore: re-trigger CI [controller] 2026-06-05 17:09:00 -04:00
HAL9000 aa79f07988 refactor(tests): add TEST_ARCHITECTURE.md clarifying behave vs robot framework roles (#9049)
Create comprehensive documentation defining Behave (business-facing BDD/Gherkin)
and Robot Framework (technical integration/E2E) roles in the test architecture.
Includes decision criteria for framework selection, known duplication areas,
and consolidation recommendations.

Changes:
- docs/development/TEST_ARCHITECTURE.md: new file with framework guidelines
- CHANGELOG.md: added entry under [Unreleased] / ### Added
- CONTRIBUTORS.md: added contribution entry for this change

ISSUES CLOSED: #9049
2026-06-05 17:09:00 -04:00