CoreRasurae
9753b31c7e
CI / quality (push) Successful in 36s
CI / lint (push) Successful in 38s
CI / typecheck (push) Successful in 49s
CI / security (push) Successful in 51s
CI / integration_tests (push) Successful in 55s
CI / unit_tests (push) Successful in 3m35s
CI / build (push) Successful in 33s
CI / coverage (push) Successful in 3m36s
CI / status-check (push) Successful in 3s
Add 13 BDD scenarios covering previously uncovered code paths: - SAFE_BUILTINS validation (sandbox.py: 0% → 100%) - ConfigurationError re-raise path (config.py: 99.3% → 100%) - CLI hello/main functions (cli.py: 72.7% → 90.9%) - GraphState message truncation (state.py: 98.7% → 100%) - ProgressBarManager update/context rendering (progress.py: 0% → 87.7%) - MessageRouter regex/exact/contains routing (message_router.py: 0% → 59.4%) - RoutingAdapter parse_routing_command (routing_adapter.py) - DynamicRouterNode pattern-based routing (dynamic_router.py) - EnhancedTemplateRegistry unknown template type (enhanced_registry.py: 99.2%) - CompositeAgent null-graph error path (composite.py: 97.8% → 98.6%) Cover routing_adapter.py (17% → 100%): all GOTO/ROUTE patterns, create_routing_node, create_conditional_router, dynamic config conversion. Cover dynamic_router.py (21% → 87%): execute with empty/dict/string messages, extract_message with colon parsing, config creation, graph extension with edge generation. Cover message_router.py (59% → 78%): regex, exact, contains, prefix, suffix match types, invalid regex handling, non-string message, set_state. Exercise Node._prepare_conversation_history with invalid configs, _runtime error paths, _execute_message_router with rules, _execute_agent with current_message and metadata propagation, _execute_function with dynamic_router, and _execute_conditional with content_contains/content_not_contains/content_starts_with and custom condition types. Improves nodes.py from 71.3% to 72.5%. Exercise PureGraphConfig, PureLangGraph init with dict/config, RxPyLangGraphBridge registration/connection/lookup, ReactiveStreamRouter operator creation and condition functions, ReactiveConfigParser config/route/graph parsing, ToolAgent tool execution with JSON, space-separated, single, file_read, progress_bar invocations, and ReactiveCleverAgentsApp init/dispose/visualization.
42 lines
2.3 KiB
Gherkin
42 lines
2.3 KiB
Gherkin
Feature: Config Parser List-Format Route Processing and Template Non-Dict Error Handling
|
|
As a developer
|
|
I want list-format routes to parse from/to fields correctly and template parse errors to raise ValueError for non-dict restored configs
|
|
So that route definitions in list format and template parsing errors are handled correctly
|
|
Given a ReactiveConfigParser instance (cpg)
|
|
When I call _build_reactive_config with list routes using from and to (cpg)
|
|
Then routes and merges should be generated from the list format (cpg)
|
|
|
|
Scenario: Parse list-format routes with agent targets
|
|
Given a ReactiveConfigParser instance (cpg)
|
|
When I call _build_reactive_config with list routes targeting agents (cpg)
|
|
Then agent-targeted routes should contain map operators (cpg)
|
|
|
|
Scenario: Parse list-format routes with multiple continuation points
|
|
Given a ReactiveConfigParser instance (cpg)
|
|
When I call _build_reactive_config with multiple continuation routes (cpg)
|
|
Then routes should connect via merge sources and cover route_map logic (cpg)
|
|
|
|
Scenario: Parse routes without from/to fields
|
|
Given a ReactiveConfigParser instance (cpg)
|
|
When I call _build_reactive_config with list routes lacking from_to fields (cpg)
|
|
Then routes should be stored with index-based names (cpg)
|
|
|
|
Scenario: Parse routes where from is an agent without feeding route
|
|
Given a ReactiveConfigParser instance (cpg)
|
|
When I call _build_reactive_config with an orphan agent from source (cpg)
|
|
Then the orphan agent merge source should fallback to agent name (cpg)
|
|
|
|
Scenario: Parse routes where from is a non-agent non-input name
|
|
Given a ReactiveConfigParser instance (cpg)
|
|
When I call _build_reactive_config with a non-agent non-input from source (cpg)
|
|
Then the merge source should be the raw from name (cpg)
|
|
|
|
Scenario: Template instance routes in list format
|
|
Given a ReactiveConfigParser instance (cpg)
|
|
When I call _build_reactive_config with template instance in list routes (cpg)
|
|
Then template instance route should be stored with template_config (cpg)
|
|
|
|
Scenario: Non-dict restored config raises ValueError
|
|
Given a ReactiveConfigParser instance (cpg)
|
|
When parse_files receives a template file yielding a non-dict result (cpg)
|
|
Then a ValueError should be raised for non-dictionary config (cpg) |