forked from cleveragents/cleveragents-core
58 lines
2.4 KiB
Gherkin
58 lines
2.4 KiB
Gherkin
Feature: Workflow Parity Matrix
|
|
As a developer migrating from Plandex to CleverAgents
|
|
I want to extract and map workflows between implementations
|
|
So that I can ensure complete feature parity
|
|
|
|
Background:
|
|
Given the Plandex Go codebase is available
|
|
And the workflow parity extractor is initialized
|
|
|
|
Scenario: Extract all workflow categories
|
|
When I run the workflow parity extraction
|
|
Then I should get workflow mappings for all categories
|
|
And each workflow should have Go components mapped
|
|
And each workflow should have Python modules assigned
|
|
And the statistics should include workflow counts
|
|
|
|
Scenario: Generate parity matrix
|
|
When I extract workflows and generate the parity matrix
|
|
Then the matrix should map Go components to Python modules
|
|
And the matrix should identify coverage gaps
|
|
And the matrix should provide implementation order
|
|
And the implementation order should respect dependencies
|
|
|
|
Scenario: Save workflow parity results
|
|
Given I have extracted workflow mappings
|
|
When I save the workflow parity results
|
|
Then a JSON file should be created with workflow data
|
|
And a YAML file should be created with workflow data
|
|
And a Markdown documentation should be generated
|
|
And the documentation should include all workflows by category
|
|
|
|
Scenario: Extract plan lifecycle workflows
|
|
When I extract plan-related workflows
|
|
Then I should find plan_create workflow
|
|
And I should find plan_build workflow
|
|
And I should find plan_apply workflow
|
|
And each workflow should have stages defined
|
|
And each workflow should have test coverage specified
|
|
|
|
Scenario: Extract context management workflows
|
|
When I extract context workflows
|
|
Then I should find context_load workflow
|
|
And I should find context_auto workflow
|
|
And the workflows should include heuristics information
|
|
|
|
Scenario: Extract execution workflows
|
|
When I extract execution workflows
|
|
Then I should find exec_command workflow
|
|
And I should find auto_debug workflow
|
|
And the workflows should include retry logic details
|
|
|
|
Scenario: Calculate statistics
|
|
When I extract all workflows
|
|
Then the statistics should include total workflows
|
|
And the statistics should include workflows per category
|
|
And the statistics should include total Go components
|
|
And the statistics should include total Python modules
|
|
And the statistics should include test coverage metrics |