TE

testing-workflow

A layer-by-layer testing guide covering database, backend, frontend, and E2E validation.

Install

mkdir -p .claude/skills/testing-workflow && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/473" && unzip -o skill.zip -d .claude/skills/testing-workflow && rm skill.zip

Installs to .claude/skills/testing-workflow

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Comprehensive testing workflow for E2E, integration, and unit tests. Use when testing applications layer-by-layer, validating user journeys, or running test suites.
164 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • Validates SQL queries and RLS policies
  • Tests Edge Functions and API endpoints
  • Verifies frontend component rendering
  • Executes Playwright E2E user journey tests

How it works

The skill follows a layer-by-layer testing approach, starting from database validation and moving through backend functions to frontend components and full E2E journeys.

Inputs & outputs

You give it
Test suite execution command
You get back
Test pass or fail results

When to use testing-workflow

  • Verify SQL and RLS policies
  • Test edge functions and API endpoints
  • Validate component rendering
  • Run Playwright E2E suites

About this skill

Testing Workflow Skill

Purpose

Guide comprehensive testing following the layer-by-layer approach. Test systematically from database → backend → frontend → E2E.


Testing Philosophy

DON'T: Test entire system at once DO: Test each layer independently, bottom-up

Layer 1: Database ✅ → SQL queries
Layer 2: Backend ✅ → API/Edge Functions
Layer 3: Frontend 🟡 → Component testing
Layer 4: E2E 🔴 → Complete user journeys

Quick Navigation

🗄️ Layer 1: Database

Test SQL, RLS policies, migrations

  • See DATABASE.md
  • Quick SQL tests, RLS verification, policy checks

⚙️ Layer 2: Backend

Test Edge Functions, APIs

  • See BACKEND.md
  • Function deployment, secrets, logs

🎨 Layer 3: Frontend

Test components, UI

  • See FRONTEND.md
  • Component rendering, TypeScript, build

🚀 Layer 4: E2E

Test complete user journeys

  • See E2E.md
  • Playwright tests, full workflows

Quick Test Commands

Pre-Commit Check (30 sec)

pnpm tsc && pnpm build

Full Test Suite (5 min)

pnpm tsc && pnpm build && npx playwright test

Watch Mode

npx playwright test --ui

Testing Layers

LayerWhatToolsTime
1. DatabaseSQL, RLSSupabase, psql2 min
2. BackendEdge Functionscurl, Supabase CLI3 min
3. FrontendComponentsTypeScript, Build2 min
4. E2EUser journeysPlaywright5 min

Pre-Deployment Testing

Complete Test Run (15 min)

# 1. Type check
pnpm tsc --noEmit

# 2. Build
pnpm build

# 3. Start dev server (background)
pnpm dev &

# 4. Manual smoke test
# - Visit /pitch-deck-wizard
# - Send message
# - Verify response

# 5. Run E2E tests
npx playwright test

# 6. Check production build
pnpm preview

Production Readiness Checklist

Code Quality

  • pnpm tsc --noEmit → 0 errors
  • pnpm lint → 0 warnings
  • pnpm build → succeeds
  • No console.log in production code

Functionality

  • Wizard works (AI responds)
  • Progress tracking (0-100%)
  • Deck generation works
  • All slides render

Backend

  • Edge Functions deployed
  • Secrets configured
  • Database migrations applied
  • RLS enabled

Testing

  • Manual tests pass
  • E2E tests pass
  • No console errors
  • No network errors

Common Issues

Tests Fail Due to RLS

-- Set test presentation public
UPDATE presentations
SET is_public = true
WHERE id = 'd4a27c1c-8b2d-48a9-99c9-2298037e9e81';

Playwright Timeout

// Increase timeout
await page.waitForSelector('element', { timeout: 30000 });

TypeScript Errors

# Find all errors
pnpm tsc --noEmit | grep "error TS"

Resources

  • Daily Checklist: lovable-plan/management/903-DAILY-TESTING-CHECKLIST.md
  • Full Strategy: lovable-plan/docs/004-TESTING-STRATEGY-AND-IMPROVEMENTS.md
  • Playwright Docs: https://playwright.dev

Start testing: Begin with DATABASE.md for Layer 1

When not to use it

  • When the application does not have a defined testing framework
  • When performing manual testing without automated suites

Prerequisites

Playwright installedSupabase CLI for backend testing

Limitations

  • Requires manual configuration of test environments
  • E2E tests are dependent on application state

How it compares

It enforces a systematic bottom-up testing philosophy rather than testing the entire system as a single unit.

Compared to similar skills

testing-workflow side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
testing-workflow (this skill)169moReviewIntermediate
code-review06moNo flagsIntermediate
dependency-upgrade265moReviewIntermediate
playwright-pro83moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry