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.
45 lines
1.9 KiB
Gherkin
45 lines
1.9 KiB
Gherkin
Feature: LangGraph Node Initialization, Execution, and Error Handling
|
|
As a CleverAgents developer
|
|
I want nodes to initialize correctly, execute across all node types, and handle errors with retries
|
|
So that graph execution is reliable for agent, function, conditional, subgraph, and tool nodes
|
|
|
|
Background:
|
|
Given the LangGraph nodes system is initialized
|
|
|
|
Scenario: Node initialization and core execution paths
|
|
Given I have various node configurations
|
|
When I test node initialization and basic execution
|
|
Then all node types should initialize correctly
|
|
And basic execution should work for each type
|
|
|
|
Scenario: Agent node execution scenarios
|
|
Given I have various node configurations
|
|
When I test agent node execution paths
|
|
Then agent execution should handle valid agents correctly
|
|
And error cases should be handled properly
|
|
|
|
Scenario: Function node execution scenarios
|
|
Given I have various node configurations
|
|
When I test function node execution paths
|
|
Then all built-in functions should execute correctly
|
|
And unknown functions should return empty results
|
|
|
|
Scenario: Conditional node execution scenarios
|
|
Given I have various node configurations
|
|
And I have conditional node test configurations
|
|
When I test conditional logic execution
|
|
Then all condition types should evaluate correctly
|
|
And conditional edge cases should be handled properly
|
|
|
|
Scenario: Node utility methods and properties
|
|
Given I have various node configurations
|
|
When I test node utility methods
|
|
Then timeout and parallel settings should work
|
|
And edge operations should function correctly
|
|
|
|
Scenario: Error handling and retry mechanisms
|
|
Given I have various node configurations
|
|
When I test error handling scenarios
|
|
Then errors should be captured and returned properly
|
|
And retry policies should work without delays
|