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
76 lines
3.7 KiB
Gherkin
76 lines
3.7 KiB
Gherkin
Feature: Context Analysis Coverage Boost
|
|
Additional scenarios targeting previously uncovered defensive code paths
|
|
in cleveragents.agents.graphs.context_analysis module.
|
|
|
|
Background:
|
|
Given the context analysis coverage module is imported
|
|
|
|
# ---- _with_retry fallback (line 183) ----
|
|
|
|
Scenario: _with_retry returns chain unchanged when it has no with_retry method
|
|
Given I have a context analysis agent for coverage boost
|
|
And I have a runnable without a with_retry method
|
|
When I call _with_retry on the runnable
|
|
Then the returned object should be the same runnable
|
|
|
|
# ---- _load_files exception handler (lines 239-240) ----
|
|
|
|
Scenario: _load_files records error when TextLoader raises an exception
|
|
Given I have a context analysis agent for coverage boost
|
|
And TextLoader.load is patched to raise an OSError
|
|
When I execute load_files with a real file path
|
|
Then the load_files result should contain an error mentioning the file
|
|
And the documents list should be empty in the result
|
|
|
|
# ---- _analyze_dependencies exception handler (lines 267-276) ----
|
|
|
|
Scenario: _analyze_dependencies records error when LLM chain raises
|
|
Given I have a context analysis agent with a raising LLM for coverage boost
|
|
And I have a state with one document for dependency analysis
|
|
When I execute analyze_dependencies on the state
|
|
Then the result should have an error about dependency analysis
|
|
And the dependencies for the document should be an empty list
|
|
|
|
Scenario: _analyze_dependencies combines errors with pre-existing state error
|
|
Given I have a context analysis agent with a raising LLM for coverage boost
|
|
And I have a state with one document and a pre-existing error
|
|
When I execute analyze_dependencies on the state
|
|
Then the result error should contain both the pre-existing and new error messages
|
|
|
|
# ---- _score_relevance exception handler (lines 351-358) ----
|
|
|
|
Scenario: _score_relevance records error when LLM chain raises
|
|
Given I have a context analysis agent with a raising LLM for coverage boost
|
|
And I have a state with chunks for relevance scoring
|
|
When I execute score_relevance on the state
|
|
Then the result should have an error about relevance scoring
|
|
And the relevance score for the file should default to 0.5
|
|
|
|
Scenario: _score_relevance combines errors with pre-existing state error
|
|
Given I have a context analysis agent with a raising LLM for coverage boost
|
|
And I have a state with chunks and a pre-existing error for scoring
|
|
When I execute score_relevance on the state
|
|
Then the scoring result error should contain both the pre-existing and new error messages
|
|
|
|
# ---- _summarize_context exception handler (lines 416-424) ----
|
|
|
|
Scenario: _summarize_context records error when LLM chain raises
|
|
Given I have a context analysis agent with a raising LLM for coverage boost
|
|
And I have a complete state ready for summarization
|
|
When I execute summarize_context on the state
|
|
Then the summary should be "Context analysis failed"
|
|
And the result should have an error about summarization
|
|
|
|
Scenario: _summarize_context combines errors with pre-existing state error
|
|
Given I have a context analysis agent with a raising LLM for coverage boost
|
|
And I have a complete state with a pre-existing error for summarization
|
|
When I execute summarize_context on the state
|
|
Then the summary should be "Context analysis failed"
|
|
And the summarization result error should contain both the pre-existing and new error messages
|
|
|
|
# ---- No LLM provided raises ValueError (lines 114-118) ----
|
|
|
|
Scenario: Agent constructor raises ValueError when no LLM is provided
|
|
When I try to create a ContextAnalysisAgent with no LLM
|
|
Then a ValueError should be raised about missing LLM provider
|