← ClaudeAtlas

cella-testinglisted

Use when running a systematic test sweep of the cella worktree/task system from inside a container. Also use after modifying the daemon, agent CLI, or task manager, before releases, or after bug fixes.
eve0415/cella · ★ 2 · Testing & QA · score 72
Install: claude install-skill eve0415/cella
# Cella End-to-End Testing Systematic verification of the cella worktree-container-task system. Run this from inside a running cella container to validate that branch creation, exec routing, task dispatch, and lifecycle management all work correctly. ## Context Cella gives each git branch its own isolated dev container. This test sweep exercises the full stack: daemon connectivity, branch creation (typically 30-80s each depending on cache), cross-container exec, background task dispatch with timeouts, and container lifecycle (stop/start/remove/prune). It catches regressions in the daemon, agent CLI, and task manager. ## Prerequisites 1. You must be inside a cella container. Verify: ```sh cella doctor ``` Must exit 0. If it fails, the daemon is not reachable — no point continuing. 2. Check version: ```sh cella doctor --json ``` The JSON output contains a `daemon_version` field. The text output of `cella doctor` (without `--json`) also prints the agent version in its banner. Verify these match. **Pre-existing branches**: If `test/a`, `test/b`, or `test/deep/nested/name` already exist as git branches (e.g., from a previous failed run), `cella branch` handles them idempotently — it creates the worktree and container without error. ## Test Phases ### Phase 1: Baseline Diagnostics ```sh cella doctor cella doctor --json cella list cella list --json ``` **Expected results:** - `cella doctor` exits 0 - `cella doctor --json` returns valid JSON with a