CLI test runner script and validation

[patrick91]

Objective

Create executable test scripts to validate all features through real CLI usage.

Tasks

E2E Test Script (scripts/test_e2e.sh)

• Create bash script for full workflow testing
• Set up isolated test environment (temp repo)
• Configure mock GitHub API endpoint
• Test workflow:
  • Create stack of 3 branches
  • Submit all PRs
  • Edit middle branch
  • Re-submit updated PR
  • Sync with main
  • Validate all operations
• Validate outputs at each step
• Validate git state (branches, commits, notes)
• Clean up test environment
• Return exit code 0 on success, 1 on failure
• Add colored output (green=pass, red=fail)
• Add verbose mode (--verbose)

Feature Validation Script (scripts/validate_features.py)

• Python script to check all commands
• Verify all commands have help text
• Smoke test each command
• Validate command output formats
• Check version display
• Check config operations
• Validate error handling
• Generate validation report (markdown)
• Can run against installed CLI or dev version
• Add --quick mode for fast checks

Integration with CI

• Add scripts/test_e2e.sh to CI pipeline
• Run on every PR
• Run on main branch pushes
• Add status badge to README

Documentation

• Document how to run scripts
• Add troubleshooting guide
• Document expected outputs

Acceptance Criteria

• scripts/test_e2e.sh successfully runs full workflow
• scripts/validate_features.py checks all commands
• Scripts run in CI successfully
• Clear output with pass/fail indicators
• Scripts handle failures gracefully
• Documentation complete

[patrick91]

Current status as of 2026-03-19:

Already in place:

• CLI-oriented e2e scaffolding exists, including the markdown runner and GitHub mock support.

Still missing from this issue:

• scripts/test_e2e.sh
• scripts/validate_features.py
• CI wired to those specific scripts

Partially stale; worth narrowing to the still-missing deliverables.

[patrick91]

Triaged against main at 52da8bd.

Still open for the named deliverables: there is no scripts/ directory, no scripts/test_e2e.sh, and no scripts/validate_features.py.

Related progress: pytest-based e2e tests exist under tests/e2e/, and CI runs them. That does not cover the standalone script/validation workflow described here.