brent.edwards
e801eb1ee8
- Rewrite .forgejo/workflows/ci.yml to route all jobs through nox sessions - Fix coverage_report nox session: serial behave mode replaces broken parallel mode (22% -> 97% accuracy), raise fail-under from 85% to 97% - Pass posargs through format nox session for CI --check support - Add 11 CI workflow validation scenarios (Behave) + Robot smoke test + ASV bench - Add 108 new Behave scenarios covering 6 largest coverage gaps to reach 97%: yaml_template_engine, actor/config, actor/registry, message_router, context_analysis, context_service - Update docs/development/ci-cd.md with nox-based CI docs and 97% threshold - Restore implementation_plan.md verbose style, check off completed CI tasks Verified: 1673 scenarios pass, 97% coverage, lint clean, typecheck clean
25 lines
1.0 KiB
Gherkin
25 lines
1.0 KiB
Gherkin
Feature: Message router new coverage
|
|
As a developer
|
|
I want the message_router module fully tested
|
|
So that node and edge builders stay stable
|
|
|
|
Scenario: build_message_router_node creates NodeConfig with correct type
|
|
When I build a message router node named "router1" with rules
|
|
Then the node name should be "router1"
|
|
And the node type should be MESSAGE_ROUTER
|
|
And the node metadata should contain rules
|
|
|
|
Scenario: build_message_router_edges creates edges from rules
|
|
When I build message router edges for "router1" with two target rules
|
|
Then the edge count should be 3
|
|
And the last edge target should be "end"
|
|
|
|
Scenario: build_message_router_edges handles empty rules
|
|
When I build message router edges for "router1" with no rules
|
|
Then the edge count should be 1
|
|
And the last edge target should be "end"
|
|
|
|
Scenario: build_message_router_edges skips rules without target
|
|
When I build message router edges for "router1" with a rule missing target
|
|
Then the edge count should be 1
|