HAL9000
e2df239bd8
CI / lint (pull_request) Failing after 38s
CI / typecheck (pull_request) Successful in 47s
CI / quality (pull_request) Successful in 36s
CI / push-validation (pull_request) Successful in 27s
CI / helm (pull_request) Successful in 35s
CI / build (pull_request) Successful in 41s
CI / security (pull_request) Successful in 1m38s
CI / coverage (pull_request) Has been skipped
CI / e2e_tests (pull_request) Successful in 3m24s
CI / integration_tests (pull_request) Successful in 4m18s
CI / unit_tests (pull_request) Successful in 6m15s
CI / docker (pull_request) Has been skipped
CI / status-check (pull_request) Failing after 1s
CI / benchmark-publish (pull_request) Has been skipped
CI / benchmark-regression (pull_request) Has been skipped
Ensure tool and validation CLI commands initialize the SQLite persistence layer on first use and add regression coverage.\n\nISSUES CLOSED: #6885
18 lines
939 B
Gherkin
18 lines
939 B
Gherkin
@tdd_issue @tdd_issue_6885
|
|
Feature: TDD Issue #6885 — Tool CLI bootstraps database automatically
|
|
As a developer
|
|
I want `agents tool list` and `agents validation add` to work on a fresh install
|
|
So that users do not have to run a manual database upgrade before using the registry
|
|
|
|
Scenario: Tool list command bootstraps the database automatically
|
|
Given a CLI runner without a bootstrapped registry database
|
|
When I invoke tool list without prior bootstrap
|
|
Then the tool list command should exit successfully
|
|
And the tool list output should indicate that no tools are registered
|
|
|
|
Scenario: Validation add command bootstraps the database automatically
|
|
Given a CLI runner without a bootstrapped registry database
|
|
When I invoke validation add without prior bootstrap
|
|
Then the validation add command should exit successfully
|
|
And the validation add output should report the registered validation in JSON
|