Executable scenarios¶

Each scenario maps to its pytest-bdd test and recorded JUnit outcome. These examples are not exhaustive feature coverage; skipped/untested behavior is not a pass.

Raw feature source | Outcome data

Root help teaches the available command families¶

Result: PASS

Automated test: tests/features/test_journeys.py::test_root_help_teaches_the_available_command_families

Scenario: Root help teaches the available command families
  Given the root-only installed image
  When I run "livingproof --help"
  Then the exit status is 0
  And the output contains "capability"
  And the output contains "plugins"
  And the output contains "livingproof completion status"

Missing reporting plugin explains an explicit next step¶

Result: PASS

Automated test: tests/features/test_journeys.py::test_missing_reporting_plugin_explains_an_explicit_next_step

Scenario: Missing reporting plugin explains an explicit next step
  Given the root-only installed image
  When I run "livingproof capability report --help"
  Then the exit status is 1
  And the output contains "livingproof plugins install livingproof-capability-report"
  And the output contains "No packages are installed automatically"
  When I run "livingproof plugins install --help"
  Then the exit status is 0
  And the output contains "--version"

Installed root discovers the reporting plugin¶

Result: PASS

Automated test: tests/features/test_journeys.py::test_installed_root_discovers_the_reporting_plugin

Scenario: Installed root discovers the reporting plugin
  Given the reporting installed image
  When I run "livingproof plugins status livingproof-capability-report"
  Then the exit status is 0
  And the output contains "livingproof-capability-report"
  When I run "livingproof capability report --help"
  Then the exit status is 0
  And the output contains "validate"
  And the output contains "grade"
  And the output contains "render"

Installed root validates a published example bundle¶

Result: PASS

Automated test: tests/features/test_journeys.py::test_installed_root_validates_a_published_example_bundle

Scenario: Installed root validates a published example bundle
  Given the reporting installed image
  When I run "livingproof capability report validate /input/manifest.json"
  Then the exit status is 0
  And the output contains "Valid bundle structure"

Missing manifest fails with useful command usage¶

Result: PASS

Automated test: tests/features/test_journeys.py::test_missing_manifest_fails_with_useful_command_usage

Scenario: Missing manifest fails with useful command usage
  Given the reporting installed image
  When I run "livingproof capability report validate /input/missing.json"
  Then the exit status is 2
  And the output contains "Usage:"
  And the output contains "--help"
  And the output contains "does not exist"

Network installation/version flows, completion lifecycle, other platforms and independent manual review remain outside these five acceptance examples.