forked from HAL9000/cleveragents-core
hurui200320
1878998b7a
Rename the TDD tag system from tdd_bug/tdd_bug_<N> to tdd_issue/tdd_issue_<N> across the entire codebase. The tdd_expected_fail tag is unchanged. The TDD expected-failure workflow is not limited to bug fixes — it applies equally to any issue type (features, tasks, refactors). The _bug suffix was misleading and narrowed the perceived scope. The new _issue suffix accurately reflects that the TDD tagging system applies to any Forgejo issue. Changes span 92 files: - features/environment.py: validate_tdd_tags(), should_invert_result(), and apply_tdd_inversion() updated — regex, variables, error messages - robot/tdd_expected_fail_listener.py: _validate_tdd_tags(), _should_invert_result(), start_test(), end_test() updated consistently - 33 Behave .feature files: all @tdd_bug/@tdd_bug_<N> tags renamed - 29 Robot .robot files: all tdd_bug/tdd_bug_<N> tags renamed - 3 Robot fixture files renamed (tdd_bug_alone, tdd_missing_tdd_bug, tdd_expected_fail_missing_bug_n) with content and references updated - Tag validation tests and helpers updated (function names, command dispatch keys, output strings, fixture references) - CONTRIBUTING.md: section renamed from 'TDD Bug Test Tags' to 'TDD Issue Test Tags', all tag references and examples updated - noxfile.py: comment references updated - Step definition files, mock helpers, and benchmark files: docstring references updated ISSUES CLOSED: #965
45 lines
2.2 KiB
Plaintext
45 lines
2.2 KiB
Plaintext
*** Settings ***
|
|
Documentation TDD Issue #823 — subplan spawn creates metadata but does not orchestrate
|
|
... child plan execution. Integration smoke tests verifying that
|
|
... SubplanService.spawn() creates real child Plan domain objects and
|
|
... triggers lifecycle progression. Currently spawn() only creates
|
|
... SubplanStatus records and SpawnMetadata without creating child Plans.
|
|
... Tests are tagged tdd_expected_fail so CI passes via result inversion.
|
|
Resource ${CURDIR}/common.resource
|
|
Suite Setup Setup Test Environment
|
|
Suite Teardown Cleanup Test Environment
|
|
|
|
*** Variables ***
|
|
${HELPER} ${CURDIR}/helper_tdd_subplan_spawn_orchestration.py
|
|
|
|
*** Test Cases ***
|
|
TDD Spawn Result Contains Child Plan Objects
|
|
[Documentation] Verify that spawn() returns actual child Plan domain objects,
|
|
... not just SubplanStatus metadata.
|
|
[Tags] tdd_issue tdd_issue_823
|
|
${result}= Run Process ${PYTHON} ${HELPER} spawn-child-plans cwd=${WORKSPACE} timeout=30s
|
|
Log ${result.stdout}
|
|
Log ${result.stderr}
|
|
Should Be Equal As Integers ${result.rc} 0
|
|
Should Contain ${result.stdout} tdd-spawn-child-plans-ok
|
|
|
|
TDD Child Plans Enter Strategize Phase
|
|
[Documentation] Verify that spawned child plans enter the strategize phase
|
|
... and have their lifecycle triggered.
|
|
[Tags] tdd_issue tdd_issue_823
|
|
${result}= Run Process ${PYTHON} ${HELPER} spawn-lifecycle cwd=${WORKSPACE} timeout=30s
|
|
Log ${result.stdout}
|
|
Log ${result.stderr}
|
|
Should Be Equal As Integers ${result.rc} 0
|
|
Should Contain ${result.stdout} tdd-spawn-lifecycle-ok
|
|
|
|
TDD Parent Plan Tracks Child Status
|
|
[Documentation] Verify that spawn() attaches SubplanStatus entries to
|
|
... the parent plan so lifecycle can be tracked.
|
|
[Tags] tdd_issue tdd_issue_823
|
|
${result}= Run Process ${PYTHON} ${HELPER} spawn-parent-tracking cwd=${WORKSPACE} timeout=30s
|
|
Log ${result.stdout}
|
|
Log ${result.stderr}
|
|
Should Be Equal As Integers ${result.rc} 0
|
|
Should Contain ${result.stdout} tdd-spawn-parent-tracking-ok
|