HAL9000
8ebd922e77
CI / lint (pull_request) Successful in 35s
CI / helm (pull_request) Successful in 21s
CI / build (pull_request) Successful in 45s
CI / push-validation (pull_request) Successful in 31s
CI / quality (pull_request) Successful in 52s
CI / typecheck (pull_request) Successful in 1m3s
CI / security (pull_request) Successful in 1m15s
CI / unit_tests (pull_request) Successful in 4m23s
CI / docker (pull_request) Successful in 2m0s
CI / integration_tests (pull_request) Successful in 7m57s
CI / coverage (pull_request) Successful in 12m1s
CI / status-check (pull_request) Successful in 3s
Updated docs/specification.md to document the correct JSON/YAML output structure for the project delete command, replacing the legacy deletion_summary object with the deleted, success, and deleted_at fields that match the actual implementation introduced in PR #6639. Added BDD feature file and step definitions to validate the output format. ISSUES CLOSED: #7872
59 lines
3.2 KiB
Gherkin
59 lines
3.2 KiB
Gherkin
Feature: Project CLI delete spec alignment
|
|
As a developer
|
|
I want the project delete command output to match the v3 specification
|
|
So that JSON and YAML output include the deleted, success, and deleted_at fields
|
|
|
|
Background:
|
|
Given a project delete spec alignment CLI runner
|
|
And a project delete spec alignment mocked repository
|
|
|
|
Scenario: Project delete JSON output includes deleted field
|
|
Given a project delete spec alignment project "local/docs" exists
|
|
When I run project delete spec alignment for "local/docs" with format "json"
|
|
Then the project delete spec alignment output should contain "deleted"
|
|
|
|
Scenario: Project delete JSON output includes success field
|
|
Given a project delete spec alignment project "local/docs" exists
|
|
When I run project delete spec alignment for "local/docs" with format "json"
|
|
Then the project delete spec alignment output should contain "success"
|
|
|
|
Scenario: Project delete JSON output includes deleted_at field
|
|
Given a project delete spec alignment project "local/docs" exists
|
|
When I run project delete spec alignment for "local/docs" with format "json"
|
|
Then the project delete spec alignment output should contain "deleted_at"
|
|
|
|
Scenario: Project delete JSON output does not include deletion_summary
|
|
Given a project delete spec alignment project "local/docs" exists
|
|
When I run project delete spec alignment for "local/docs" with format "json"
|
|
Then the project delete spec alignment output should not contain "deletion_summary"
|
|
|
|
Scenario: Project delete YAML output includes deleted field
|
|
Given a project delete spec alignment project "local/docs" exists
|
|
When I run project delete spec alignment for "local/docs" with format "yaml"
|
|
Then the project delete spec alignment output should contain "deleted"
|
|
|
|
Scenario: Project delete YAML output includes success field
|
|
Given a project delete spec alignment project "local/docs" exists
|
|
When I run project delete spec alignment for "local/docs" with format "yaml"
|
|
Then the project delete spec alignment output should contain "success"
|
|
|
|
Scenario: Project delete YAML output includes deleted_at field
|
|
Given a project delete spec alignment project "local/docs" exists
|
|
When I run project delete spec alignment for "local/docs" with format "yaml"
|
|
Then the project delete spec alignment output should contain "deleted_at"
|
|
|
|
Scenario: Project delete YAML output does not include deletion_summary
|
|
Given a project delete spec alignment project "local/docs" exists
|
|
When I run project delete spec alignment for "local/docs" with format "yaml"
|
|
Then the project delete spec alignment output should not contain "deletion_summary"
|
|
|
|
Scenario: Project delete success field is true
|
|
Given a project delete spec alignment project "local/docs" exists
|
|
When I run project delete spec alignment for "local/docs" with format "json"
|
|
Then the project delete spec alignment JSON success field should be true
|
|
|
|
Scenario: Project delete deleted field matches project name
|
|
Given a project delete spec alignment project "local/docs" exists
|
|
When I run project delete spec alignment for "local/docs" with format "json"
|
|
Then the project delete spec alignment JSON deleted field should be "local/docs"
|