56 lines
2.3 KiB
Gherkin
56 lines
2.3 KiB
Gherkin
Feature: Cloud Features Identification
|
|
As a developer creating a self-hosted CleverAgents
|
|
I want to identify cloud-only features in Plandex
|
|
So that I can remove or replace them appropriately
|
|
|
|
Background:
|
|
Given the Plandex Go codebase is available
|
|
And the cloud features extractor is initialized
|
|
|
|
Scenario: Extract all cloud features
|
|
When I run the cloud features extraction
|
|
Then I should identify features in all categories
|
|
And each feature should have an action specified
|
|
And each feature should have a priority assigned
|
|
And the statistics should include feature counts
|
|
|
|
Scenario: Identify billing features
|
|
When I scan for billing features
|
|
Then I should find billing_ui feature
|
|
And I should find usage_limits feature
|
|
And each billing feature should have replacement strategy
|
|
|
|
Scenario: Identify telemetry features
|
|
When I scan for telemetry features
|
|
Then I should find usage_telemetry feature
|
|
And I should find error_reporting feature
|
|
And telemetry should default to opt-in local alternatives
|
|
|
|
Scenario: Identify authentication features
|
|
When I scan for managed auth features
|
|
Then I should find managed_auth feature
|
|
And I should find api_keys_cloud feature
|
|
And auth features should have local replacements
|
|
|
|
Scenario: Generate replacement strategies
|
|
When I extract cloud features and generate strategies
|
|
Then features should be categorized by action
|
|
And remove features should be listed
|
|
And replace features should have alternatives
|
|
And strategies should be sorted by priority
|
|
|
|
Scenario: Save cloud features analysis
|
|
Given I have identified cloud features
|
|
When I save the cloud features results
|
|
Then a JSON file should be created with feature data
|
|
And a YAML file should be created with feature data
|
|
And a cloud features Markdown documentation should be generated
|
|
And the documentation should include replacement strategies
|
|
|
|
Scenario: Calculate cloud feature statistics
|
|
When I extract all cloud features
|
|
Then the statistics should include total features
|
|
And the statistics should count features by category
|
|
And the statistics should count features by action
|
|
And the statistics should count features by priority
|
|
And the statistics should count affected Go files |