E2E Testing Nori Skillsets Subcommands

1. Run e2e-setup to build the project and create the isolated environment

source {{skills_dir}}/e2e-testing-skillsets/e2e-setup

The script prints the variables it exports. Verify E2E_DIR, SKS, and NORI_GLOBAL_CONFIG are set.

1. Read the TUI Puppeteering skill

Read {{skills_dir}}/tui-puppeteering-with-tmux/SKILL.md

Follow its instructions exactly. All tmux interaction goes through its scripts.

1. Write a test plan for the specified subcommand

Before touching tmux, write out a concrete plan:

• What subcommand you are testing and what behavior you want to verify
• What seed data you need to create in $E2E_DIR before launching the command
• The exact tui-start command you will use (must include the env wrapper shown below)
• The assert-act-assert sequence: what text you expect on screen, what input you will send, what text you expect after

1. Seed any required test data in $E2E_DIR

Many commands need pre-existing state. Create it directly in the filesystem:

# Example: create a fake skillset for switch/fork/edit to find
mkdir -p "$E2E_DIR/.nori/profiles/my-test-skillset"
echo '{"name":"my-test-skillset","version":"1.0.0","type":"skillset"}' > "$E2E_DIR/.nori/profiles/my-test-skillset/nori.json"

1. Execute the test using TUI puppeteering

Launch the command inside tmux with isolation env vars:

SCRIPTS="{{skills_dir}}/tui-puppeteering-with-tmux"
SESSION="sks-e2e-$$"

$SCRIPTS/tui-start "$SESSION" "env NORI_GLOBAL_CONFIG=$E2E_DIR node $SKS <subcommand> [args]"

Then follow the assert-act-assert loop from the TUI Puppeteering skill.

1. Verify filesystem side effects

After the command completes, check that the expected files were created/modified/deleted inside $E2E_DIR. Also verify that your real home directory was NOT touched.

1. Clean up

$SCRIPTS/tui-stop "$SESSION"
{{skills_dir}}/e2e-testing-skillsets/e2e-teardown

Always stop tmux first, then tear down the filesystem.

Isolation Rules

• All commands MUST run with NORI_GLOBAL_CONFIG=$E2E_DIR. This env var redirects every path that getHomeDir() resolves: ~/.nori/, ~/.nori-config.json, ~/.claude/, and anything else rooted at $HOME. Without it, the CLI writes to the real home directory.
• Always use env NORI_GLOBAL_CONFIG=$E2E_DIR node $SKS ... as the command passed to tui-start. Never run bare nori-skillsets or sks.
• Never run npm link. The built CLI is executed directly via node.
• The e2e directory is always /tmp/nori/skillsets-e2e-scenario/. The e2e-setup script wipes and recreates it on every run.
• After the test, verify isolation. Check that ~/.nori/ and ~/.claude/ were not modified. The e2e-teardown script does this automatically.