42 lines
1.7 KiB
Gherkin
42 lines
1.7 KiB
Gherkin
Feature: Application Context Analysis Agent coverage
|
|
As a developer
|
|
I want the placeholder workflow validated
|
|
So that the application context agent stays predictable
|
|
|
|
Scenario: Initializing the application context agent respects batch limits
|
|
When I instantiate the application context agent with max files per batch 5
|
|
Then the agent should track max files per batch of 5
|
|
And the base agent initializer should have been invoked with default settings
|
|
|
|
Scenario: Building the application context workflow graph wires placeholder nodes
|
|
When I construct the application context workflow graph
|
|
Then the workflow should target ContextAnalysisState as the graph state
|
|
And the workflow should include nodes:
|
|
"""
|
|
identify_files
|
|
analyze_files
|
|
extract_dependencies
|
|
build_structure
|
|
select_contexts
|
|
finalize
|
|
"""
|
|
And the workflow should define ordered edges:
|
|
"""
|
|
identify_files -> analyze_files
|
|
analyze_files -> extract_dependencies
|
|
extract_dependencies -> build_structure
|
|
build_structure -> select_contexts
|
|
select_contexts -> finalize
|
|
finalize -> END
|
|
"""
|
|
|
|
Scenario: Placeholder workflow nodes populate default state fields
|
|
Given I have a fresh application context agent state
|
|
When I run the placeholder context workflow nodes
|
|
Then the state should include an empty files_to_analyze list
|
|
And the state should include an empty analyzed_files map
|
|
And the state should include an empty dependencies map
|
|
And the state should include a project structure skeleton
|
|
And the state should include an empty relevant_contexts list
|
|
And the state should include a finalized result summary
|