forked from cleveragents/cleveragents-core
freemo
a808c395f9
Add 53 new .feature files and corresponding step definition files targeting uncovered lines identified in build/coverage.xml. Fix AmbiguousStep conflicts in 7 pre-existing step files by disambiguating step text. New tests cover: ACP clients/facade, actor CLI/config, application container, ACMS service/strategies, async worker, automation profile CLI, autonomy guardrail, bridge, change model, config CLI/service, context service, cross-plan correction, database models, decision service, decomposition clustering/service, discovery handler, langchain chat provider, langgraph nodes, materializers, multi-project service, plan apply/CLI/lifecycle/model/ preflight/resume/service, PostgreSQL analyzer, project CLI/context CLI, provider registry, reactive application/route, repositories, resolver handler, resource registry service, resume model, retry patterns, sandbox protocol, server CLI, skill CLI/service, skills registry, subplan execution/service, system CLI, UKO loader, UoW, and YAML template engine. Closes #645
37 lines
2.0 KiB
Gherkin
37 lines
2.0 KiB
Gherkin
Feature: Reactive application coverage boost
|
|
As a developer
|
|
I want to exercise the remaining uncovered lines in reactive/application.py
|
|
So that code coverage is maximized
|
|
|
|
Scenario: Logging adds a handler when root logger has no handlers
|
|
Given a reactive app with all root logger handlers removed
|
|
When I configure logging with verbose level 2
|
|
Then the root logger should have at least one handler
|
|
And the handler format should include the module name pattern
|
|
|
|
Scenario: Ensure agent registered creates instance from config when agent not already present
|
|
Given a reactive app with a route referencing an agent not yet registered but present in config
|
|
When I register agents from config triggering deferred registration
|
|
Then the deferred config agent should be registered in the stream router
|
|
And the deferred config agent alias should also be registered
|
|
|
|
Scenario: Initialize graph context refreshes stage order when stages are missing
|
|
Given a reactive app with a global context that has a partial stage order list
|
|
When I initialize the graph context
|
|
Then the stage order should be refreshed to the full default list
|
|
|
|
Scenario: Initialize graph context resets writing stage when current value is invalid
|
|
Given a reactive app with a global context that has an invalid writing stage
|
|
When I initialize the graph context
|
|
Then the writing stage should be reset to intro
|
|
|
|
Scenario: Follow chained edges returns immediately when next node is end
|
|
Given a reactive app configured for chained edge traversal to end node
|
|
When I follow chained edges starting from the end node
|
|
Then the chained edge result should be the current message with should_return true
|
|
|
|
Scenario: Follow chained edges falls through when next node becomes falsy
|
|
Given a reactive app configured for chained edge traversal to a falsy node
|
|
When I follow chained edges starting from a node that chains to a falsy node
|
|
Then the chained edge result should be the current message with should_return false
|