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.
68 lines
2.3 KiB
Gherkin
68 lines
2.3 KiB
Gherkin
Feature: Template System Integration
|
|
As a developer
|
|
I want all template subsystem components to work together across agents, graphs, streams, registries, stores, and engines
|
|
So that the complete template pipeline produces valid configurations end-to-end
|
|
|
|
Background:
|
|
Given the template system is available
|
|
And I have template test configurations
|
|
|
|
Scenario: Agent templates functionality
|
|
When I load agent templates
|
|
Then the agent templates should be accessible
|
|
And template rendering should work
|
|
|
|
Scenario: Graph templates processing
|
|
Given I have graph template configurations
|
|
When I process graph templates
|
|
Then graph structures should be generated
|
|
And templates should be validated
|
|
|
|
Scenario: Stream templates handling
|
|
Given I have stream template definitions
|
|
When I process stream templates
|
|
Then stream configurations should be created
|
|
And template inheritance should work
|
|
|
|
Scenario: Template registry management
|
|
Given I have a template registry
|
|
When I register multiple templates
|
|
Then templates should be stored correctly
|
|
And template lookup should work
|
|
|
|
Scenario: Enhanced registry features
|
|
Given I have an enhanced template registry
|
|
When I use advanced registry features
|
|
Then template caching should work
|
|
And template validation should be enforced
|
|
|
|
Scenario: Template store operations
|
|
Given I have a template store
|
|
When I perform store operations
|
|
Then templates should be persisted
|
|
And retrieval should be efficient
|
|
|
|
Scenario: YAML template engine processing
|
|
Given I have YAML templates with Jinja
|
|
When I process the templates
|
|
Then YAML should be rendered correctly
|
|
And variables should be interpolated
|
|
|
|
Scenario: Inline YAML Jinja processing
|
|
Given I have inline YAML Jinja templates
|
|
When I process inline templates
|
|
Then embedded templates should work
|
|
And syntax should be preserved
|
|
|
|
Scenario: Template loaders functionality
|
|
Given I have various template sources
|
|
When I use template loaders
|
|
Then templates should be loaded correctly
|
|
And different formats should be supported
|
|
|
|
Scenario: Smart YAML loader features
|
|
Given I have complex YAML structures
|
|
When I use the smart YAML loader
|
|
Then advanced YAML features should work
|
|
And schema validation should be applied
|