forked from cleveragents/cleveragents-core
67 lines
2.2 KiB
Gherkin
67 lines
2.2 KiB
Gherkin
Feature: Templates Module Coverage
|
|
As a developer
|
|
I want to test template system functionality
|
|
So that coverage includes template processing and rendering
|
|
|
|
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 |