forked from cleveragents/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
20 lines
1008 B
Gherkin
20 lines
1008 B
Gherkin
@mock_only
|
|
Feature: TDD expected-fail result inversion demo
|
|
Demonstrates the @tdd_expected_fail tag inverting a deliberately failing
|
|
scenario so it is reported as passed. This exercises the Scenario.run()
|
|
wrapper logic installed by _install_tdd_expected_fail_patch() in
|
|
features/environment.py.
|
|
See CONTRIBUTING.md > TDD Issue Test Tags for the three-tag specification.
|
|
|
|
Note: The "unexpected pass" path (where a @tdd_expected_fail scenario
|
|
passes and is forced to fail) cannot be tested as an integration scenario
|
|
because the forced failure would break the test suite. That path is
|
|
tested via mock-based unit tests in tdd_tag_validation.feature and via
|
|
real Scenario objects in tdd_expected_fail_infrastructure.feature.
|
|
|
|
@tdd_issue @tdd_issue_999 @tdd_expected_fail
|
|
Scenario: Demo bug 999 expected failure is inverted to pass
|
|
Given tdd demo a step that always succeeds
|
|
When tdd demo a deliberately failing assertion is executed
|
|
Then tdd demo this step is never reached
|