forked from cleveragents/cleveragents-core
CleverAgents Dev
41 lines
1.8 KiB
Gherkin
41 lines
1.8 KiB
Gherkin
@discovery
|
|
Feature: Environment Variable Extraction
|
|
As a developer migrating from Plandex to CleverAgents
|
|
I need to extract and map environment variables from Go code and docs
|
|
So that I can provide compatibility and migration guidance
|
|
|
|
Scenario: Extract environment variables from documentation
|
|
Given a Plandex directory with environment variable documentation
|
|
When I extract environment variables from documentation
|
|
Then the extractor should find documented variables
|
|
And each variable should have a description
|
|
And each variable should have a proposed CleverAgents name
|
|
|
|
Scenario: Extract environment variables from Go source code
|
|
Given a Plandex directory with Go source files
|
|
When I extract environment variables from Go code
|
|
Then the extractor should find code-referenced variables
|
|
And usage locations should be tracked
|
|
And variables should be categorized by source location
|
|
|
|
Scenario: Generate environment variable mapping
|
|
Given an extracted set of environment variables
|
|
When I generate the mapping table
|
|
Then PLANDEX variables should map to CLEVERAGENTS equivalents
|
|
And provider-specific variables should remain unchanged
|
|
And generic variables should get CLEVERAGENTS prefix
|
|
|
|
Scenario: Identify migration conflicts
|
|
Given an extracted set of environment variables
|
|
When I identify conflicts
|
|
Then PLANDEX_ prefixed variables should be flagged for migration
|
|
And development-only variables should be identified
|
|
And migration guidance should be provided
|
|
|
|
Scenario: Save environment variable results
|
|
Given an extracted set of environment variables
|
|
When I save the results
|
|
Then a JSON file should be created
|
|
And a YAML file should be created
|
|
And a mapping text file should be created
|
|
And a migration guide should be generated |