Imported from slingr-stack/qa-test-drumr (qa/agents/skills/testing-ci/SKILL.md). Install upstream with npx skills add slingr-stack/qa-test-drumr --skill testing-ci. Copyright stays with the author.

Skill: testing-ci

CI pipeline integration, commands, and artifact collection for Slingr E2E tests.

Scope

This skill covers how E2E tests fit into the monorepo CI pipeline, how to run them in headless mode, and how to collect artifacts and coverage reports.

Monorepo CI Pipeline

The Slingr monorepo uses GitHub Actions. CI is triggered by commenting /run-tests on a PR.

Test execution order

1. Linting (npm run lint)             ← Blocking
2. Building (build:framework → cli)  ← Blocking
3. Testing                            ← Blocking
   ├── npm run test:cli
   ├── npm run coverage:framework
   └── npm run coverage:cli
4. Security audit (npm audit)         ← Non-blocking

Root-level commands

npm test                          # All packages sequentially
npm run test:framework            # Framework (SQLite + PostgreSQL)
npm run test:framework:sqlite     # Fast — use during development
npm run test:framework:postgres   # Requires running PostgreSQL
npm run test:cli                  # CLI tests (Mocha)
npm run coverage                  # All coverage reports

E2E Tests in CI

E2E tests require a running Slingr app with a database. They are not included in the default CI pipeline but can be triggered separately.

Running E2E headless (CI-ready)

cd apps/<app-name>
npx playwright test                # Headless, single worker

Required infrastructure

Artifact collection

Configure in playwright.config.ts:

use: {
  screenshot: 'only-on-failure',
  video: 'retain-on-failure',
  trace: 'on-first-retry',
},

Artifacts are saved to test-results/ — add to .gitignore.