cli-e2e-test-authoring

Solid

Guide for adding new end-to-end tests for the Packmind CLI. This skill should be used when creating new test specs in the `apps/cli-e2e-tests/` directory that exercise CLI commands against a real binary and API.

Testing & QA 303 stars 15 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 86/100

Stars 20%
83
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# CLI E2E Test Authoring ## Overview Add end-to-end tests that exercise the Packmind CLI binary (`dist/apps/cli/main.cjs`) in realistic conditions. Tests run the actual CLI as a child process and, when authentication is needed, interact with a running API via HTTP gateways. ## Test File Location All spec files live in `apps/cli-e2e-tests/src/` and follow the naming convention `<command>.spec.ts`. ## Choosing a Test Wrapper Two wrappers are available depending on whether the command requires authentication. ### Unauthenticated commands — `describeWithTempSpace` Provides an isolated temporary directory. No API required. ```typescript import { describeWithTempSpace, runCli } from './helpers'; describeWithTempSpace('my-command without auth', (getContext) => { let result: Awaited<ReturnType<typeof runCli>>; beforeEach(async () => { const { testDir } = await getContext(); result = await runCli('my-command', { cwd: testDir }); }); it('exits with code 1', () => { expect(result.returnCode).toBe(1); }); it('shows an error message', () => { expect(result.stdout).toContain('No credentials found'); }); }); ``` ### Authenticated commands — `describeWithUserSignedUp` Extends `describeWithTempSpace` by creating a real user account, signing in, and generating an API key. Requires a running API at `http://localhost:4200`. ```typescript import { describeWithUserSignedUp, runCli } from './helpers'; describeWithUserSignedUp('my-command with auth', (g...

Details

Author
PackmindHub
Repository
PackmindHub/packmind
Created
10 months ago
Last Updated
today
Language
TypeScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Solid

create-run-e2e-tests

Guide for writing and running new Playwright end-to-end tests in the `apps/e2e-tests/` directory of the Packmind monorepo. Use this skill whenever you add or modify a spec that drives the real frontend and API — for example testing a user flow, a new page/route, a feature behind a flag, or a UI behavior end-to-end. Triggers on "write an e2e test", "add a Playwright test", "test this flow end-to-end", "cover this page with an e2e", "e2e for the frontend", or any work that lands a `*.spec.ts` under apps/e2e-tests/src/. Prefer this over hand-rolling raw Playwright `test()` calls — the codebase has mandatory fixtures and a Page Object Model you must follow.

303 Updated today
PackmindHub
Testing & QA Solid

e2e-setup

Set up an end-to-end test suite in any repo, following practices that make e2e a reliable per-PR gate: real flows over bypass, layered assertions, a reusable auth/session helper, video+trace evidence, and a compounding suite. Use when a repo has no e2e (or weak e2e) and you want system-level tests — "set up e2e", "add end-to-end tests", "scaffold a test gate".

1,102 Updated yesterday
AI-Builder-Club
Testing & QA Listed

playwright-e2e

End-to-end testing and click-verification of web apps with Playwright — install, write specs, drive authenticated pages, take screenshots, and run in CI. Use when verifying a web change actually works in a real browser, testing user flows, debugging a UI bug live, or confirming an authed/gated page before shipping. Keywords Playwright, e2e, browser test, click test, screenshot, headless.

1 Updated yesterday
5dive-ai