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
16 lines
770 B
Plaintext
16 lines
770 B
Plaintext
*** Settings ***
|
|
Documentation Fixture: a test with tdd_expected_fail and tdd_issue but
|
|
... missing tdd_issue_N.
|
|
... Used by helper_tdd_tag_validation.py to verify tag
|
|
... validation catches the missing tdd_issue_N tag.
|
|
... This file must NOT be picked up by the main pabot runner --
|
|
... it is excluded via the tdd_fixture tag.
|
|
|
|
*** Test Cases ***
|
|
Missing TDD Issue N Tag Causes Validation Error
|
|
[Tags] tdd_issue tdd_expected_fail tdd_fixture
|
|
[Documentation] This test has tdd_expected_fail and tdd_issue but no
|
|
... tdd_issue_N tag. The listener should detect this and force a
|
|
... validation failure.
|
|
Log This should not matter -- validation should fail first.
|