forked from cleveragents/cleveragents-core
CleverAgents Dev
44 lines
1.7 KiB
Gherkin
44 lines
1.7 KiB
Gherkin
@discovery
|
|
Feature: CLI Inventory Extraction
|
|
As a developer migrating Plandex to CleverAgents
|
|
I want to extract CLI command metadata from the Go codebase
|
|
So that I can ensure feature parity in the Python implementation
|
|
|
|
Background:
|
|
Given the Plandex Go codebase is available
|
|
And the CLI inventory extractor is initialized
|
|
|
|
Scenario: Extract CLI commands from Go source
|
|
When I run the CLI inventory extraction
|
|
Then the extraction should succeed
|
|
And at least 60 commands should be extracted
|
|
And the inventory should contain a root command
|
|
And the inventory should include command metadata
|
|
And the inventory files should be saved
|
|
|
|
Scenario: Validate extracted command structure
|
|
Given the CLI inventory has been extracted
|
|
When I check the command structure
|
|
Then each command should have a name
|
|
And each command should have a file_path
|
|
And auth requirements should be detected
|
|
And project requirements should be detected
|
|
|
|
Scenario: Export inventory in multiple formats
|
|
When I save the CLI inventory
|
|
Then a YAML file should be created at "docs/reference/cli_inventory.yaml"
|
|
And a JSON file should be created at "docs/reference/cli_inventory.json"
|
|
And both files should contain the same data
|
|
|
|
Scenario: Detect command aliases
|
|
Given the CLI inventory has been extracted
|
|
When I check for command aliases
|
|
Then commands with aliases should be identified
|
|
And the aliases should be properly formatted
|
|
|
|
Scenario: Extract command flags
|
|
Given the CLI inventory has been extracted
|
|
When I check for command flags
|
|
Then commands with flags should be identified
|
|
And flag metadata should include name and type
|
|
And flag descriptions should be captured |