051ee7c290
CI / benchmark-publish (pull_request) Has been skipped
CI / lint (pull_request) Successful in 21s
CI / quality (pull_request) Successful in 31s
CI / typecheck (pull_request) Successful in 47s
CI / security (pull_request) Successful in 52s
CI / build (pull_request) Successful in 56s
CI / e2e_tests (pull_request) Successful in 5m1s
CI / integration_tests (pull_request) Successful in 5m30s
CI / unit_tests (pull_request) Successful in 5m42s
CI / docker (pull_request) Successful in 58s
CI / coverage (pull_request) Successful in 7m35s
CI / build (push) Successful in 21s
CI / docker (push) Has been skipped
CI / benchmark-regression (pull_request) Failing after 49m24s
CI / lint (push) Successful in 22s
CI / quality (push) Successful in 39s
CI / security (push) Successful in 48s
CI / typecheck (push) Successful in 1m26s
CI / benchmark-regression (push) Has been skipped
CI / e2e_tests (push) Successful in 5m53s
CI / coverage (push) Successful in 9m4s
CI / benchmark-publish (push) Successful in 19m10s
CI / integration_tests (push) Failing after 19m18s
CI / unit_tests (push) Failing after 19m20s
Added 52 new .feature files and corresponding _steps.py files targeting previously uncovered code paths in the following areas: - TUI layer: app, commands, persona (state/schema/registry), widgets, input (shell_exec, reference_parser) - Application services: plan lifecycle/service/executor, session, project, repo indexing, correction, checkpoint, actor, llm_actors, strategy coordinator, resource file watcher, service retry wiring - CLI commands: session, resource, repl, plan, db, automation_profile - Domain models: retry_policy, resource_type, cost_budget, docker_compose_analyzer, detail_level, _sql_string_aware, _postgresql_helpers - Core: circuit_breaker, retry_service_patterns - Infrastructure: repositories, transaction_sandbox, strategy_registry, plugins/loader, container - Config: settings - Agents: plan_generation, context_analysis, auto_debug - A2A: facade All new tests follow the Behave/Gherkin BDD standard. Resolved step definition collisions with unique prefixes. Fixed Alembic fileConfig logger disabling issue (disable_existing_loggers=False). ISSUES CLOSED: #1068
29 lines
1.4 KiB
Gherkin
29 lines
1.4 KiB
Gherkin
Feature: Settings coverage boost
|
|
Additional scenarios that exercise previously uncovered code paths
|
|
in the Settings class (settings.py lines 561-563 and 602-611).
|
|
|
|
Background:
|
|
Given the settings coverage module is imported
|
|
|
|
Scenario: Model validator rejects retry_max_delay less than retry_base_delay
|
|
When I create Settings with retry_max_delay less than retry_base_delay
|
|
Then a ValidationError should be raised about delay ordering
|
|
And the error message should mention both delay values
|
|
|
|
Scenario: repr masks sensitive field values when set
|
|
Given I have a Settings instance with openai_api_key set to a secret value
|
|
When I call repr on the settings instance
|
|
Then the repr output should contain REDACTED for the openai_api_key field
|
|
And the repr output should start with "Settings(" and end with ")"
|
|
|
|
Scenario: repr shows non-sensitive fields normally
|
|
Given I have a Settings instance with default values
|
|
When I call repr on the settings instance
|
|
Then the repr output should contain the env field with its actual value
|
|
And the repr output should not contain REDACTED for non-sensitive fields
|
|
|
|
Scenario: repr shows REDACTED only for non-None sensitive keys
|
|
Given I have a Settings instance where all sensitive keys are None
|
|
When I call repr on the settings instance
|
|
Then the repr output should show None for sensitive key fields without redaction
|