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
35 lines
1.6 KiB
Gherkin
35 lines
1.6 KiB
Gherkin
# Regression tests for bug #589 — project create must commit to the database.
|
|
Feature: Project create persists to database
|
|
As a developer using the agents CLI
|
|
I want projects created with "agents project create" to persist in the database
|
|
So that "agents project list" shows previously created projects
|
|
|
|
Background:
|
|
Given a fresh project-persist database is initialised
|
|
|
|
@tdd_issue @tdd_issue_589
|
|
Scenario: Created project appears in project list
|
|
When I create a project named "local/my-app" via the persist CLI
|
|
And I list projects via the persist CLI
|
|
Then the persist project list should contain "local/my-app"
|
|
|
|
@tdd_issue @tdd_issue_589
|
|
Scenario: Multiple created projects all appear in list
|
|
When I create a project named "local/alpha" via the persist CLI
|
|
And I create a project named "local/beta" via the persist CLI
|
|
And I list projects via the persist CLI
|
|
Then the persist project list should contain "local/alpha"
|
|
And the persist project list should contain "local/beta"
|
|
|
|
@tdd_issue @tdd_issue_589
|
|
Scenario: Bare project name uses default namespace and persists
|
|
When I create a project named "my-app" via the persist CLI
|
|
And I list projects via the persist CLI
|
|
Then the persist project list should contain "local/my-app"
|
|
|
|
@tdd_issue @tdd_issue_589
|
|
Scenario: Creating a duplicate project produces an error
|
|
When I create a project named "local/dup-proj" via the persist CLI
|
|
And I attempt to create a duplicate project named "local/dup-proj" via the persist CLI
|
|
Then the persist duplicate creation should fail with "already exists"
|