feat(integration-tests): add --verbose flag to runner.sh

[yu-iskw]

User description

Add comprehensive verbose logging to integration test runner to help understand
how 'caf' works at a glance. The verbose flag enables:

• Environment diagnostics (working directory, user, shell, PATH)
• Command availability checks (tree, git, pnpm, caf)
• Repository structure display using tree command
• Debug logs for git clone operations
• Installed skills/subagents directory structure visualization
• Final test summary with complete skills and subagents listings

Changes:

• runner.sh: Add --verbose/-v flag with debug_log() and show_structure() helpers
• runner.sh: Add --help/-h flag with usage information
• Dockerfile: Install 'tree' command for better directory visualization
• Makefile: Add 'test-verbose' target for easy verbose test execution

Usage:
./runner.sh --verbose
make test-verbose

https://claude.ai/code/session_01PV7rMwWhzGUphMgySRjX5r

---

PR Type

Enhancement

---

Description

• Add comprehensive verbose logging to integration test runner with debug output

• Implement --verbose and --help flags with environment diagnostics

• Display repository and directory structures using tree command

• Add debug logs for git clone operations and skill installations

• Enable verbose mode by default in GitHub Actions CI workflow

• Install tree command in Docker image for better visualization

---

Diagram Walkthrough

flowchart LR
  A["runner.sh"] -->|"Add --verbose flag"| B["Debug Logging"]
  A -->|"Add helper functions"| C["show_structure()"]
  A -->|"Add helper functions"| D["debug_log()"]
  B -->|"Output environment info"| E["Diagnostics"]
  C -->|"Display directory trees"| F["Visualization"]
  G["Dockerfile"] -->|"Install tree"| F
  H["Makefile"] -->|"Add test-verbose target"| I["CI Integration"]
  J["GitHub Actions"] -->|"Use test-verbose"| I

Loading

File Walkthrough

	Relevant files
Enhancement	runner.sh Add verbose flag with debug logging and diagnostics            integration_tests/scripts/runner.sh Add --verbose/-v and --help/-h command-line argument parsing Implement debug_log() function for conditional debug output with blue color coding Implement show_structure() function to display directory trees using tree command or ls fallback Add environment diagnostics section showing working directory, user, shell, PATH, and command availability Add debug logs throughout test scenarios for git clone operations and workspace initialization Add directory structure visualization after each skill/subagent installation Add final test summary section with complete skills and subagents listings +109/-0  Makefile Add test-verbose make target                                                          integration_tests/Makefile Add test-verbose target to phony targets declaration Implement test-verbose target that builds image and runs container with --verbose flag +4/-1
Configuration changes	test.yml Enable verbose mode in CI workflow                                              .github/workflows/test.yml Update integration tests job to run with --verbose flag by default Change test command from make -C integration_tests test to make -C integration_tests test-verbose +1/-1
Dependencies	Dockerfile Install tree command for visualization                                      integration_tests/Dockerfile Add tree command to system dependencies installation Install tree alongside git, make, and ca-certificates for directory visualization +1/-1

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
⚪	Sensitive info exposure Description: Verbose mode prints potentially sensitive environment and filesystem information to CI logs (e.g., PATH, workspace listings, and recursive/hidden file trees via tree -a/ls -laR), which can inadvertently expose secrets or credentials if they exist in the workspace (especially since .github/workflows/test.yml now runs test-verbose by default). runner.sh [35-359] Referred Code # Debug logging function debug_log() { if [ "$VERBOSE" = true ]; then echo -e "${BLUE}[DEBUG]${NC} $1" fi } # Show directory structure with tree if available, otherwise use ls show_structure() { local dir="$1" local label="$2" if [ "$VERBOSE" = true ]; then echo -e "${YELLOW}=== $label ===${NC}" if command -v tree &> /dev/null; then tree -L 3 -a "$dir" 2>/dev/null || ls -la "$dir" else debug_log "tree command not available, using ls instead" ls -laR "$dir" | head -50 fi echo "" ... (clipped 304 lines)
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
🔴	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Fragile arg parsing: The new argument parsing loop uses shift inside a for arg in "$@" construct and silently ignores unknown flags, which can mis-handle inputs and makes failures harder to diagnose. Referred Code # Parse arguments VERBOSE=false for arg in "$@"; do case $arg in --verbose|-v) VERBOSE=true shift ;; --help|-h) echo "Usage: $0 [OPTIONS]" echo "" echo "Options:" echo " --verbose, -v Enable verbose output with debug logs and directory structures" echo " --help, -h Show this help message" echo "" echo "Example:" echo " $0 --verbose" exit 0 ;; *) ;; ... (clipped 2 lines) Learn more about managing compliance generic rules or creating your own custom rules
⚪	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Potential sensitive output: Verbose mode logs environment and filesystem details (e.g., whoami, $PATH, recursive directory listings) which could inadvertently expose sensitive information in CI logs depending on the runtime environment. Referred Code if [ "$VERBOSE" = true ]; then echo -e "${YELLOW}=== Environment Diagnostics ===${NC}" debug_log "Verbose mode enabled" debug_log "Working directory: $(pwd)" debug_log "User: $(whoami)" debug_log "Shell: $SHELL" debug_log "PATH: $PATH" echo -e "${BLUE}[DEBUG]${NC} Available commands:" command -v tree &> /dev/null && echo " ✓ tree" || echo " ✗ tree (will use ls instead)" command -v git &> /dev/null && echo " ✓ git" || echo " ✗ git" command -v pnpm &> /dev/null && echo " ✓ pnpm" || echo " ✗ pnpm" command -v caf &> /dev/null && echo " ✓ caf" || echo " ✗ caf" debug_log "CAF version: $(caf --version 2>&1 || echo 'not available')" echo "" fi Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
High-level	Consider making verbose logging opt-in for CI Change the CI pipeline to run the standard, non-verbose test by default to reduce log noise. The new verbose mode can be reserved for debugging purposes. Examples: .github/workflows/test.yml [75] run: make -C integration_tests test-verbose Solution Walkthrough: Before: # .github/workflows/test.yml ... - name: Run Integration Tests run: make -C integration_tests test-verbose # integration_tests/Makefile ... test: build docker run --rm $(IMAGE_NAME) test-verbose: build docker run --rm $(IMAGE_NAME) --verbose After: # .github/workflows/test.yml ... - name: Run Integration Tests run: make -C integration_tests test # integration_tests/Makefile ... test: build docker run --rm $(IMAGE_NAME) test-verbose: build docker run --rm $(IMAGE_NAME) --verbose Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies that enabling verbose logging by default in CI can make logs noisy, which is a valid developer experience concern, though not a functional bug.	Medium
General	✅ Improve directory structure display logic Suggestion Impact: Implemented a check to ensure the target directory exists before attempting to display its structure, returning early with a debug log if missing. Also adjusted the ls fallback to handle failure more explicitly when tree is unavailable, though tree error suppression and recursive fallback for tree failure were not fully implemented as suggested. code diff: if [ "$VERBOSE" = true ]; then echo -e "${YELLOW}=== $label ===${NC}" + if [ ! -d "$dir" ]; then + debug_log "Directory does not exist: $dir" + return 0 + fi if command -v tree &> /dev/null; then tree -L 3 -a "$dir" 2>/dev/null || ls -la "$dir" else debug_log "tree command not available, using ls instead" - ls -laR "$dir" | head -50 + ls -laR "$dir" 2>/dev/null | head -50 || echo "Failed to list directory" fi Improve the show_structure function by adding a check for directory existence before processing. Also, make the fallback logic consistent by using a recursive ls in all failure cases and avoid suppressing potentially useful error messages from the tree command. integration_tests/scripts/runner.sh [42-57] # Show directory structure with tree if available, otherwise use ls show_structure() { local dir="$1" local label="$2" if [ "$VERBOSE" = true ]; then echo -e "${YELLOW}=== $label ===${NC}" + if [ ! -d "$dir" ]; then + debug_log "Directory '$dir' not found for structure display." + echo "" + return + fi + if command -v tree &> /dev/null; then - tree -L 3 -a "$dir" 2>/dev/null || ls -la "$dir" + if ! tree -L 3 -a "$dir"; then + debug_log "tree command failed, using ls instead" + ls -laR "$dir" | head -50 + fi else debug_log "tree command not available, using ls instead" ls -laR "$dir" | head -50 fi echo "" fi } [Suggestion processed] Suggestion importance[1-10]: 7 __ Why: This suggestion correctly identifies multiple issues in the show_structure function, including lack of directory existence check, inconsistent fallback logic, and error suppression, offering a more robust and reliable implementation.	Medium
	✅ Use while loop for argument parsing Suggestion Impact: The commit removed an incorrect `shift` inside the `for`-loop case branch, partially addressing the argument-consumption issue highlighted by the suggestion, but it did not convert the parsing loop to a `while [ $# -gt 0 ]` pattern. code diff: @@ -14,7 +14,6 @@ case $arg in --verbose|-v) VERBOSE=true - shift ;; Replace the for loop used for argument parsing with a while [ $# -gt 0 ] loop. This ensures arguments are consumed correctly with shift and prevents potential issues with flag handling. integration_tests/scripts/runner.sh [13-33] -for arg in "$@"; do - case $arg in +while [ $# -gt 0 ]; do + case "$1" in --verbose|-v) VERBOSE=true - shift ;; --help|-h) echo "Usage: $0 [OPTIONS]" ... exit 0 ;; *) + break ;; esac + shift done [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies that using a for loop with shift for argument parsing is incorrect and proposes the standard while loop pattern, which improves the script's robustness and maintainability.	Medium
Possible issue	Enable pipefail for pipeline errors Enable the pipefail option by changing set -e to set -eo pipefail. This ensures that a pipeline command will return a failure status if any of its components fail, not just the last one. integration_tests/scripts/runner.sh [1-2] #!/bin/bash set -e +set -o pipefail [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 5 __ Why: This suggestion correctly recommends enabling pipefail to ensure that failures within a pipeline are caught, which is a shell scripting best practice that improves the script's reliability.	Low
Update