Jeffrey Phillips Freeman
1fb91cba28
CI / lint (pull_request) Successful in 14s
CI / typecheck (pull_request) Successful in 28s
CI / security (pull_request) Successful in 23s
CI / quality (pull_request) Successful in 15s
CI / integration_tests (pull_request) Successful in 5m25s
CI / build (pull_request) Successful in 15s
CI / unit_tests (pull_request) Successful in 15m1s
CI / lint (push) Successful in 13s
CI / typecheck (push) Successful in 28s
CI / security (push) Successful in 23s
CI / quality (push) Successful in 15s
CI / integration_tests (push) Successful in 5m2s
CI / build (push) Successful in 16s
CI / unit_tests (push) Successful in 16m26s
CI / coverage (pull_request) Failing after 8m8s
CI / docker (pull_request) Successful in 40s
CI / docker (push) Successful in 8s
CI / coverage (push) Failing after 8m24s
77 lines
2.9 KiB
Gherkin
77 lines
2.9 KiB
Gherkin
Feature: Legacy plan persistence removal
|
|
As a developer migrating to the v3 plan lifecycle,
|
|
I want legacy plan paths to emit deprecation warnings,
|
|
so that I know to use PlanLifecycleService instead.
|
|
|
|
Background:
|
|
Given a clean test environment for legacy removal
|
|
|
|
# --- PlanService deprecation ---
|
|
|
|
Scenario: PlanService emits deprecation warning on instantiation
|
|
When I instantiate PlanService
|
|
Then a DeprecationWarning mentioning "PlanService is deprecated" is raised
|
|
|
|
Scenario: PlanService still functions after deprecation warning
|
|
When I instantiate PlanService
|
|
And I call create_plan on the legacy service
|
|
Then the plan is created successfully
|
|
|
|
# --- PlanRepository deprecation ---
|
|
|
|
Scenario: PlanRepository emits deprecation warning on instantiation
|
|
When I instantiate PlanRepository
|
|
Then a DeprecationWarning mentioning "PlanRepository is deprecated" is raised
|
|
|
|
# --- ChangeRepository deprecation ---
|
|
|
|
Scenario: ChangeRepository emits deprecation warning on instantiation
|
|
When I instantiate ChangeRepository
|
|
Then a DeprecationWarning mentioning "ChangeRepository is deprecated" is raised
|
|
|
|
# --- CLI programmatic wrappers deprecation ---
|
|
|
|
Scenario: tell_command emits deprecation warning
|
|
When I call tell_command programmatically
|
|
Then a DeprecationWarning mentioning "legacy" is raised
|
|
|
|
Scenario: build_command emits deprecation warning
|
|
When I call build_command programmatically
|
|
Then a DeprecationWarning mentioning "legacy" is raised
|
|
|
|
Scenario: apply_command emits deprecation warning
|
|
When I call apply_command programmatically
|
|
Then a DeprecationWarning mentioning "legacy" is raised
|
|
|
|
Scenario: new_command emits deprecation warning
|
|
When I call new_command programmatically
|
|
Then a DeprecationWarning mentioning "legacy" is raised
|
|
|
|
Scenario: current_command emits deprecation warning
|
|
When I call current_command programmatically
|
|
Then a DeprecationWarning mentioning "legacy" is raised
|
|
|
|
Scenario: list_command emits deprecation warning
|
|
When I call list_command programmatically
|
|
Then a DeprecationWarning mentioning "legacy" is raised
|
|
|
|
Scenario: cd_command emits deprecation warning
|
|
When I call cd_command programmatically
|
|
Then a DeprecationWarning mentioning "legacy" is raised
|
|
|
|
Scenario: continue_command emits deprecation warning
|
|
When I call continue_command programmatically
|
|
Then a DeprecationWarning mentioning "legacy" is raised
|
|
|
|
# --- PlanLifecycleService is NOT deprecated ---
|
|
|
|
Scenario: PlanLifecycleService does NOT emit deprecation warnings
|
|
When I instantiate PlanLifecycleService
|
|
Then no DeprecationWarning is raised
|
|
|
|
# --- UnitOfWorkContext plans accessor is deprecated ---
|
|
|
|
Scenario: UnitOfWorkContext plans property emits deprecation warning
|
|
When I access the plans property on UnitOfWorkContext
|
|
Then a DeprecationWarning mentioning "deprecated" is raised
|