hurui200320
1878998b7a
CI / benchmark-publish (pull_request) Has been skipped
CI / build (pull_request) Successful in 25s
CI / lint (pull_request) Successful in 3m19s
CI / typecheck (pull_request) Successful in 3m56s
CI / security (pull_request) Successful in 4m6s
CI / quality (pull_request) Successful in 4m10s
CI / integration_tests (pull_request) Successful in 7m20s
CI / unit_tests (pull_request) Successful in 7m44s
CI / docker (pull_request) Successful in 1m8s
CI / e2e_tests (pull_request) Successful in 13m1s
CI / coverage (pull_request) Successful in 12m25s
CI / status-check (pull_request) Successful in 1s
CI / build (push) Successful in 26s
CI / lint (push) Successful in 3m31s
CI / quality (push) Successful in 3m40s
CI / typecheck (push) Successful in 3m57s
CI / benchmark-regression (push) Has been skipped
CI / security (push) Successful in 4m1s
CI / integration_tests (push) Successful in 8m55s
CI / unit_tests (push) Successful in 9m14s
CI / docker (push) Successful in 9s
CI / e2e_tests (push) Successful in 11m42s
CI / coverage (push) Successful in 11m37s
CI / status-check (push) Successful in 4s
CI / benchmark-publish (push) Successful in 29m25s
CI / benchmark-regression (pull_request) Successful in 54m8s
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
28 lines
1.5 KiB
Gherkin
28 lines
1.5 KiB
Gherkin
@tdd_expected_fail @tdd_issue @tdd_issue_1024
|
|
Feature: TDD Issue #1024 — SQLite DB URL resolves to CWD instead of CLEVERAGENTS_HOME
|
|
As a developer
|
|
I want to verify that the SQLite database file is created inside
|
|
CLEVERAGENTS_HOME (not the current working directory)
|
|
So that test isolation is maintained across CLI invocations
|
|
|
|
The default ``database_url`` in ``Settings`` is ``sqlite:///cleveragents.db``
|
|
— a relative path. When E2E tests (or any CLI invocation) run with
|
|
``CLEVERAGENTS_HOME`` set to a different directory, the DB file is still
|
|
created relative to CWD, NOT inside ``CLEVERAGENTS_HOME``. This breaks
|
|
test isolation: data persists across runs, causing UNIQUE constraint
|
|
failures.
|
|
|
|
Bug: https://git.cleverthis.com/cleveragents/cleveragents-core/issues/1024
|
|
TDD: https://git.cleverthis.com/cleveragents/cleveragents-core/issues/1034
|
|
|
|
Scenario: Default database_url resolves inside CLEVERAGENTS_HOME not CWD
|
|
Given a fresh CLEVERAGENTS_HOME temp directory for DB URL testing
|
|
When I resolve the effective database URL from Settings
|
|
Then the resolved database path should be inside CLEVERAGENTS_HOME
|
|
And the resolved database path should not be inside the original CWD
|
|
|
|
Scenario: Settings database_url default resolves inside CLEVERAGENTS_HOME
|
|
Given a fresh CLEVERAGENTS_HOME temp directory for DB URL testing
|
|
When I resolve the Settings database_url default
|
|
Then the settings database path should be inside CLEVERAGENTS_HOME
|