forked from cleveragents/cleveragents-core
freemo
051ee7c290
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
31 lines
1.4 KiB
Gherkin
31 lines
1.4 KiB
Gherkin
Feature: DockerComposeAnalyzer Coverage Boost
|
|
Additional scenarios that exercise previously uncovered code paths
|
|
in the docker_compose_analyzer module (lines 142-145, 147, 164,
|
|
194, 255-263).
|
|
|
|
Background:
|
|
Given the docker compose analyzer module is imported
|
|
|
|
Scenario: Content exceeding the 1 MiB size limit is rejected
|
|
Given I have YAML content that exceeds the 1 MiB byte limit
|
|
When I analyze the oversized content
|
|
Then the analyzer should return an empty list
|
|
And a size-limit warning should have been logged
|
|
|
|
Scenario: YAML that parses to a non-dict scalar returns empty
|
|
Given I have YAML content that parses to a plain scalar string
|
|
When I analyze the non-dict YAML content
|
|
Then the analyzer should return an empty list for non-dict input
|
|
|
|
Scenario: Services key present but not a dict returns only deployment triples
|
|
Given I have compose YAML where services is a scalar instead of a mapping
|
|
When I analyze the compose YAML with non-dict services
|
|
Then the analyzer should return only the deployment unit triples
|
|
|
|
Scenario: Exception during service processing is caught and skipped
|
|
Given I have valid compose YAML with two services
|
|
And the port extraction method is patched to raise an error for one service
|
|
When I analyze the compose YAML with the faulty extractor
|
|
Then the analyzer should return triples for the non-failing service
|
|
And a service processing warning should have been logged
|