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
40 lines
2.0 KiB
Gherkin
40 lines
2.0 KiB
Gherkin
Feature: Application Container coverage boost for _build_checkpoint_service and _build_trace_service
|
|
As a developer
|
|
I want to exercise the _build_checkpoint_service and _build_trace_service helper functions
|
|
So that lines 187-195 and 204-211 of container.py are covered by tests
|
|
|
|
Background:
|
|
Given a clean container state for coverage boost tests
|
|
|
|
# -----------------------------------------------------------------
|
|
# _build_checkpoint_service (lines 187-195)
|
|
# -----------------------------------------------------------------
|
|
|
|
Scenario: Build checkpoint service with in-memory database and no lifecycle service
|
|
When I build a checkpoint service with an in-memory database URL
|
|
Then the result should be a CheckpointService instance
|
|
And the checkpoint service should have a repository
|
|
And the checkpoint service should have no plan lifecycle service
|
|
|
|
Scenario: Build checkpoint service with an explicit plan lifecycle service
|
|
Given a mock plan lifecycle service
|
|
When I build a checkpoint service with the mock plan lifecycle service
|
|
Then the result should be a CheckpointService instance
|
|
And the checkpoint service should reference the mock plan lifecycle service
|
|
|
|
# -----------------------------------------------------------------
|
|
# _build_trace_service (lines 204-211)
|
|
# -----------------------------------------------------------------
|
|
|
|
Scenario: Build trace service with in-memory database using default settings
|
|
When I build a trace service with an in-memory database URL and no explicit settings
|
|
Then the result should be a TraceService instance
|
|
And the trace service should have a repository
|
|
And the trace service should have resolved settings from defaults
|
|
|
|
Scenario: Build trace service with explicit settings
|
|
Given explicit application settings for trace service
|
|
When I build a trace service with the explicit settings
|
|
Then the result should be a TraceService instance
|
|
And the trace service should use the explicitly provided settings
|