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.
73 lines
2.6 KiB
Gherkin
73 lines
2.6 KiB
Gherkin
Feature: Agent Module Integration
|
|
As a developer
|
|
I want key agent module functions to integrate correctly with the factory, chain, composite, and tool systems
|
|
So that the full agent ecosystem operates cohesively
|
|
|
|
Background:
|
|
Given the agent system is initialized
|
|
And I have agent test configurations
|
|
|
|
Scenario: Agent module basic functionality
|
|
When I import the agent module
|
|
Then the agent module should be accessible
|
|
And agent creation should work
|
|
|
|
Scenario: Agent decorators functionality
|
|
When I import the decorators module
|
|
Then decorators should be available
|
|
And decorator functions should work
|
|
|
|
Scenario: Agent states management
|
|
When I import the states module
|
|
Then state management should be available
|
|
And state transitions should work
|
|
|
|
Scenario: Agent factory functionality
|
|
Given I have agent factory configurations
|
|
When I use the agent factory
|
|
Then agents should be created correctly
|
|
And factory patterns should work
|
|
|
|
Scenario: Chain agent functionality
|
|
Given I have chain agent configurations
|
|
When I create chain agents
|
|
Then agents should be chained correctly
|
|
And message passing should work
|
|
|
|
Scenario: Composite agent functionality
|
|
Given I have composite agent configurations
|
|
When I create composite agents
|
|
Then agent composition should work
|
|
And parallel processing should work
|
|
|
|
Scenario: LLM agent functionality
|
|
Given I have LLM agent configurations
|
|
When I create LLM agents
|
|
Then LLM integration should work
|
|
And model communication should work
|
|
|
|
Scenario: Tool agent functionality
|
|
Given I have tool agent configurations
|
|
When I create tool agents
|
|
Then tool execution should work
|
|
And tool chaining should work
|
|
|
|
Scenario: Network module functionality
|
|
When I import the network module
|
|
Then network functionality should be available
|
|
And agent communication should work
|
|
|
|
Scenario: Agent factory comprehensive testing
|
|
Given the agent system is initialized
|
|
And I have comprehensive agent factory configurations
|
|
When I test agent factory edge cases
|
|
Then factory should handle composite agent invalid components
|
|
And factory should handle legacy agent missing from cache
|
|
And factory should handle agent configuration without config section
|
|
|
|
Scenario: Agent factory detailed coverage testing
|
|
Given the agent system is initialized
|
|
And I have detailed factory configurations for comprehensive testing
|
|
When I perform comprehensive factory testing scenarios
|
|
Then comprehensive factory functionality should work correctly
|