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>
107 lines
5.7 KiB
Gherkin
107 lines
5.7 KiB
Gherkin
Feature: Config CLI coverage boost
|
|
Supplementary scenarios targeting uncovered lines in
|
|
cleveragents/cli/commands/config.py to increase branch and line coverage.
|
|
|
|
Background:
|
|
Given a cfg-boost isolated temp config directory
|
|
|
|
# ── _env_var_for_key: line 135 ──────────────────────────────────────
|
|
|
|
Scenario: _env_var_for_key returns the registered env_var for a known key
|
|
When I call cfg-boost _env_var_for_key with a registered key "core.log.level"
|
|
Then the cfg-boost returned env var should match the registry for "core.log.level"
|
|
|
|
# ── _resolve_source error path: lines 145-146 ──────────────────────
|
|
|
|
Scenario: _resolve_source returns default when resolve raises ValueError
|
|
When I call cfg-boost _resolve_source with a key that triggers ValueError
|
|
Then the cfg-boost returned source should be "default"
|
|
|
|
# ── _resolution_chain error path: lines 155-156 ─────────────────────
|
|
|
|
Scenario: _resolution_chain returns empty list when resolve raises KeyError
|
|
When I call cfg-boost _resolution_chain with a key that triggers KeyError
|
|
Then the cfg-boost returned chain should be empty
|
|
|
|
# ── config_set --project with non-scopable key: line 210 ────────────
|
|
|
|
Scenario: config set --project fails for non-project-scopable key
|
|
When I invoke cfg-boost config set "core.data-dir" "val" with project "myproj"
|
|
Then the cfg-boost CLI result should have failed
|
|
And the cfg-boost CLI output should include "not project-scopable"
|
|
|
|
# ── config_set --project with corrupted project section: line 213 ───
|
|
|
|
Scenario: config set --project handles corrupted project section (not a dict)
|
|
Given the cfg-boost config file has a non-dict "project" value
|
|
When I invoke cfg-boost config set "plan.concurrency" "8" with project "myproj"
|
|
Then the cfg-boost CLI result should have succeeded
|
|
And the cfg-boost CLI output should include "plan.concurrency"
|
|
|
|
# ── config_set --project with corrupted proj overrides: line 216 ────
|
|
|
|
Scenario: config set --project handles corrupted project override entry (not a dict)
|
|
Given the cfg-boost config file has a non-dict project override for "myproj"
|
|
When I invoke cfg-boost config set "plan.concurrency" "6" with project "myproj"
|
|
Then the cfg-boost CLI result should have succeeded
|
|
And the cfg-boost CLI output should include "plan.concurrency"
|
|
|
|
# ── config_get verbose non-rich with Path value in chain entry: line 306 ──
|
|
|
|
Scenario: config get verbose non-rich format serialises Path values in resolution chain
|
|
When I invoke cfg-boost config get "core.data-dir" verbose format "json" with path-like chain
|
|
Then the cfg-boost CLI result should have succeeded
|
|
And the cfg-boost JSON resolution chain entries should have string values
|
|
|
|
# ── config_list --project with key regex filter skipping: lines 398-401 ──
|
|
|
|
Scenario: config list --project filters keys by regex pattern
|
|
Given the cfg-boost config file has project "testproj" override "plan.concurrency" as "10"
|
|
When I invoke cfg-boost config list with project "testproj" pattern "nonexistent"
|
|
Then the cfg-boost list output should show no matching overrides
|
|
|
|
# ── config_list --project with value filter skipping: line 405 ──────
|
|
|
|
Scenario: config list --project filters values by regex
|
|
Given the cfg-boost config file has project "testproj" override "plan.concurrency" as "10"
|
|
When I invoke cfg-boost config list with project "testproj" value-filter "NOMATCH999"
|
|
Then the cfg-boost list output should show no matching overrides
|
|
|
|
# ── config_list --project with secret masking: line 410 ─────────────
|
|
|
|
# @tdd_issue @tdd_issue_4237 @tdd_expected_fail @skip
|
|
@skip
|
|
Scenario: config list --project masks secret keys by default
|
|
Given the cfg-boost config file has project "secproj" secret override "provider.openai.api-key" as "sk-supersecret"
|
|
When I invoke cfg-boost config list project "secproj" format "json"
|
|
Then the cfg-boost CLI result should have succeeded
|
|
And the cfg-boost JSON list should show masked secret values
|
|
|
|
# ── config_list --project non-rich with Path fspath: line 430 ───────
|
|
|
|
# @tdd_issue @tdd_issue_4237 @tdd_expected_fail @skip
|
|
@skip
|
|
Scenario: config list --project non-rich format serialises Path values
|
|
Given the cfg-boost config file has project "pathproj" override "core.data-dir" as "/tmp/somepath"
|
|
When I invoke cfg-boost config list project "pathproj" format "json" with path value
|
|
Then the cfg-boost CLI result should have succeeded
|
|
And the cfg-boost JSON list entries should have only primitive values
|
|
|
|
# ── config_list --project rich format table rendering: lines 434-452 ──
|
|
|
|
Scenario: config list --project renders rich table for project overrides
|
|
Given the cfg-boost config file has project "richproj" override "plan.concurrency" as "12"
|
|
When I invoke cfg-boost config list project "richproj" in default rich format
|
|
Then the cfg-boost CLI result should have succeeded
|
|
And the cfg-boost CLI output should include "plan.concurrency"
|
|
And the cfg-boost CLI output should include "12"
|
|
|
|
# ── config_list all non-rich with Path fspath: line 501 ─────────────
|
|
|
|
# @tdd_issue @tdd_issue_4237 @tdd_expected_fail @skip
|
|
@skip
|
|
Scenario: config list non-rich format serialises Path objects in all-keys mode
|
|
When I invoke cfg-boost config list format "json" with path value in resolve_all
|
|
Then the cfg-boost CLI result should have succeeded
|
|
And the cfg-boost JSON all-keys list should have stringified path values
|