eleven-category-test-structure

Organize iTerm plugin shell script tests into 11 categories.

Updated Nov 9, 2025
One-click install
npx skills add https://github.com/manifoldlogic/claude-code-plugins --skill eleven-category-test-structure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eleven-category-test-structure
Source: https://github.com/manifoldlogic/claude-code-plugins/tree/main/plugins/iterm/skills/eleven-category-test-structure
Command: npx skills add https://github.com/manifoldlogic/claude-code-plugins --skill eleven-category-test-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures consistent and comprehensive testing of iTerm plugin shell scripts by adhering to a standard 11-category organizational structure.

Core Features & Use Cases

  • 11-Category Testing: Organizes tests into 11 categories, covering all aspects of script behavior.
  • Script Existence: Validates script file existence and permissions.
  • Help/Usage: Verifies help text completeness and accessibility.
  • Dry-Run Mode: Checks if dry-run generates correct AppleScript without execution.
  • Argument Parsing: Ensures all flags are parsed correctly.
  • Exit Codes: Validates error conditions produce correct exit codes.
  • AppleScript Structure: Verifies generated AppleScript has correct structure.
  • Error Paths: Tests error handling for bad input.
  • Combined Options: Verifies multiple flags work together.
  • Context Detection: Checks script can source utilities and detect environment.
  • Edge Cases: Handles special characters and complex inputs.
  • Shell Compatibility: Ensures script structure and shell configuration are correct.
  • Use Case: When creating or reviewing tests for iTerm plugin shell scripts, ensure comprehensive coverage and consistency.

Quick Start

Run the skill to test the 'test-script.sh' file:

/path/to/skill --script test-script.sh

Frequently Asked Questions about eleven-category-test-structure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure shell script tests for iTerm plugins?

Structure iTerm plugin shell script tests using an 11-category framework covering script existence, argument parsing, dry-run mode, AppleScript generation, exit codes, error paths, and shell compatibility to ensure comprehensive behavioral coverage.

What is the best way to validate AppleScript generation in iTerm plugin tests?

Validate AppleScript generation by checking the dry-run mode output and verifying the generated AppleScript structure within the 11-category testing framework to ensure correct syntax without executing the commands.

Can I test iTerm plugin bash scripts without executing the generated AppleScript?

Yes, you can test bash scripts without execution by utilizing the dry-run mode category, which checks if the script generates the correct AppleScript structure safely without applying changes to your iTerm environment.

How do I ensure my iTerm plugin script handles argument parsing and edge cases?

Ensure correct argument parsing and edge case handling by applying specific test categories that verify flag combinations, detect context environments, and validate script behavior with special characters and complex inputs.

Why do my iTerm plugin shell scripts fail exit code validation tests?

Exit code validation tests fail when error paths for bad input do not produce the correct exit codes, requiring a review of argument parsing logic and error handling structures within your bash script.

Does iTerm plugin testing require specific shell compatibility checks?

Yes, shell compatibility checks are required to ensure the script structure and shell configuration are correct, allowing the script to source utilities properly and detect the operating environment across different setups.