freemo
8ea00f5185
CI / unit_tests (push) Has been cancelled
CI / benchmark-publish (push) Has been cancelled
CI / lint (push) Has been cancelled
CI / typecheck (push) Has been cancelled
CI / security (push) Has been cancelled
CI / quality (push) Has been cancelled
CI / integration_tests (push) Has been cancelled
CI / e2e_tests (push) Has been cancelled
CI / coverage (push) Has been cancelled
CI / benchmark-regression (push) Has been cancelled
CI / build (push) Has been cancelled
CI / push-validation (push) Has been cancelled
CI / status-check (push) Has been cancelled
CI / docker (push) Has been cancelled
CI / helm (push) Has been cancelled
Co-authored-by: Jeffrey Phillips Freeman <the@jeffreyfreeman.me> Co-committed-by: Jeffrey Phillips Freeman <the@jeffreyfreeman.me>
32 lines
1.6 KiB
Gherkin
32 lines
1.6 KiB
Gherkin
@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
|
|
|
|
# @tdd_issue @tdd_issue_4288 @tdd_expected_fail @skip
|
|
@skip
|
|
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
|
|
|
|
# @tdd_issue @tdd_issue_4288 @tdd_expected_fail @skip
|
|
@skip
|
|
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
|