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.
39 lines
1.9 KiB
Gherkin
39 lines
1.9 KiB
Gherkin
Feature: Agent Memory Lock and Operator Error Propagation
|
|
As a developer
|
|
I want agents to handle event loop edge cases and propagate operator errors correctly
|
|
So that agent memory locks and streaming operators are robust under concurrent and error conditions
|
|
|
|
Background:
|
|
Given a fresh agents base final test context (abf)
|
|
|
|
Scenario: AgentWithMemory _memory_lock handles RuntimeError from get_event_loop
|
|
Given a fresh agents base final test context (abf)
|
|
When I access _memory_lock from a thread with no event loop (abf)
|
|
Then a new event loop should be created by _memory_lock (abf)
|
|
|
|
Scenario: AgentWithMemory _memory_lock creates new loop when loop is closed
|
|
Given a fresh agents base final test context (abf)
|
|
When I access _memory_lock after closing the current event loop (abf)
|
|
Then _memory_lock should create and set a new event loop (abf)
|
|
|
|
Scenario: AgentWithMemory dispose clears lock and calls parent dispose
|
|
Given a fresh agents base final test context (abf)
|
|
When I dispose an AgentWithMemory instance (abf)
|
|
Then _memory_lock_instance should be set to None (abf)
|
|
And parent dispose should be called (abf)
|
|
|
|
Scenario: StreamableAgent as_operator propagates on_error
|
|
Given a fresh agents base final test context (abf)
|
|
When I use as_operator with an error-producing source (abf)
|
|
Then the error should propagate through on_error (abf)
|
|
|
|
Scenario: StreamableAgent map_operator processes value through agent
|
|
Given a fresh agents base final test context (abf)
|
|
When I use map_operator in a pipeline with a value (abf)
|
|
Then the value should be processed and result set on the future (abf)
|
|
|
|
Scenario: StreamableAgent filter_operator applies condition to output
|
|
Given a fresh agents base final test context (abf)
|
|
When I use filter_operator with a condition and value (abf)
|
|
Then the condition should be applied to agent output (abf)
|