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
28 lines
1.4 KiB
Gherkin
28 lines
1.4 KiB
Gherkin
Feature: DetailLevelMap coverage for uncovered lines
|
|
Exercises previously uncovered code paths in detail_level.py:
|
|
lines 157, 166-170, 181, 250-252.
|
|
|
|
Background:
|
|
Given the detail level module is imported
|
|
|
|
Scenario: copy.copy produces an independent DetailLevelMap clone
|
|
Given a DetailLevelMap with domain "uko-code:" and levels {"MODULE": 0, "FULL": 9} and max_depth 9
|
|
When I shallow-copy the DetailLevelMap
|
|
Then the copy should be a distinct DetailLevelMap instance
|
|
And the copy should have the same domain and levels as the original
|
|
|
|
Scenario: __deepcopy__ with None memo creates a fresh memo dict
|
|
Given a DetailLevelMap with domain "uko-deep:" and levels {"A": 1} and max_depth 5
|
|
When I call __deepcopy__ with None memo
|
|
Then the deep copy should be a valid DetailLevelMap with the same data
|
|
|
|
Scenario: register rejects depth exceeding max_depth
|
|
Given a DetailLevelMap with domain "uko-bounded:" and levels {"BASE": 0} and max_depth 3
|
|
When I register a level "OVERFLOW" with depth 10
|
|
Then a ValueError should be raised mentioning exceeds max_depth
|
|
|
|
Scenario: __setattr__ defense-in-depth re-freezes levels when model validator is bypassed
|
|
Given a DetailLevelMap with domain "uko-defense:" and levels {"X": 1} and max_depth 5
|
|
When I assign a plain dict to levels while bypassing Pydantic model validation
|
|
Then levels should still be a MappingProxyType after the defense-in-depth re-freeze
|