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
34 lines
1.7 KiB
Plaintext
34 lines
1.7 KiB
Plaintext
*** Settings ***
|
|
Documentation TDD Issue #783 — agents init --yes should not require user input
|
|
... Integration smoke tests verifying that the ``init --yes`` command
|
|
... completes without blocking for user input. Bug #783 reports that
|
|
... the migration runner still prompts for approval even with ``--yes``.
|
|
Resource ${CURDIR}/common.resource
|
|
Suite Setup Setup Test Environment auto_apply_migrations=${FALSE}
|
|
Suite Teardown Cleanup Test Environment
|
|
|
|
*** Variables ***
|
|
${HELPER} ${CURDIR}/helper_tdd_init_yes_no_input.py
|
|
|
|
*** Test Cases ***
|
|
TDD Init Yes No Input Completes Without Stdin
|
|
[Documentation] Verify that ``init --yes`` exits successfully without any
|
|
... stdin input. The helper runs the real CLI init command in
|
|
... a fresh directory with stdin closed.
|
|
[Tags] tdd_issue tdd_issue_783
|
|
${result}= Run Process ${PYTHON} ${HELPER} init-no-stdin cwd=${WORKSPACE} timeout=120s on_timeout=kill
|
|
Log ${result.stdout}
|
|
Log ${result.stderr}
|
|
Should Be Equal As Integers ${result.rc} 0
|
|
Should Contain ${result.stdout} tdd-init-yes-no-input-ok
|
|
|
|
TDD Init Yes No Migration Prompt
|
|
[Documentation] Verify that ``init --yes`` output does not contain the
|
|
... migration approval prompt text.
|
|
[Tags] tdd_issue tdd_issue_783
|
|
${result}= Run Process ${PYTHON} ${HELPER} init-no-prompt cwd=${WORKSPACE} timeout=120s on_timeout=kill
|
|
Log ${result.stdout}
|
|
Log ${result.stderr}
|
|
Should Be Equal As Integers ${result.rc} 0
|
|
Should Contain ${result.stdout} tdd-init-yes-no-prompt-ok
|