---
name: testing-strategy
description: Advises on appropriate testing approaches, recommends testing levels, and ensures comprehensive test coverage for business logic and edge cases.
title: testing-strategy
canonical_url: https://skilld.dev/gh/corey-alix/dwp-hours/testing-strategy
last_updated: 2026-10-07T01:30:59.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install corey-alix/dwp-hours/testing-strategy`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/testing-strategy`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/corey-alix/dwp-hours/testing-strategy) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/testing-strategy`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/testing-strategy --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/testing-strategy --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Testing Strategy Advisor

## Description

Advises on appropriate testing approaches, recommends testing levels, and ensures comprehensive test coverage for business logic and edge cases.

## Trigger

Activated when users mention testing, validation, or quality assurance needs.

## Comprehensive Validation Pipeline

When implementing code changes, follow this validation sequence:

1. **Build Validation**: `npm run build` - Ensure TypeScript compilation succeeds
2. **Lint Validation**: `npm run lint` - Check code quality and style compliance
3. **Unit Test Validation**: `npm run test:unit` - Verify business logic integrity
4. **E2E Test Validation**: `npm run test:e2e` - Confirm end-to-end functionality
5. **Documentation Update**: Update relevant TASKS files and READMEs

**Test File Convention Investigation**:

- Use `git log` to identify when violations were introduced
- Use `grep` patterns to find violations across multiple files
- Audit HTML files for inline attributes vs programmatic setup
- Validate that seedData.ts contains required test data

**Refactoring Safety**:

- Changes affecting only code organization (not functionality) can skip extensive manual testing
- Always run full test suite to catch unexpected side effects
- Update task documentation to reflect completed work

## Test File Convention Enforcement

Ensure test files follow web-components-assistant guidelines:

- **HTML Files**: Must NOT contain inline attributes on web components
- **TypeScript Files**: Handle all data and configuration programmatically
- **Data Sources**: Use seedData.ts for consistent test data
- **Strong Typing**: Unit tests should NOT cast components to `any`, but instead rely on proper TypeScript interfaces and component APIs
- **Validation**: Run build + lint + tests after refactoring

**Pattern**: HTML defines structure, TypeScript sets properties via `setAttribute()` or direct assignment.

**Test File Design Constraints**:

- **test.html**: Contains declarative HTML structure only. Imports from `/app.js` and calls aliased playground functions. No inline JavaScript for component setup.
- **test.ts**: Acts as component controller. Does NOT inject HTML markup. All DOM manipulation is programmatic using component APIs. Follows web component patterns where HTML is declarative and TypeScript handles behavior.

## Response Pattern

1. Suggest appropriate testing level (unit/integration/E2E) based on the feature
2. Reference Vitest for unit tests, Playwright for E2E tests
3. Provide testing patterns used in the existing codebase
4. Ensure test coverage for business logic and edge cases
5. Recommend manual testing steps for UI features
6. Include build and lint validation as part of testing strategy

## Testing Insights

### E2E Testing for Component Integration

- **Component Behavior Testing**: E2E tests excel at validating component integration and user workflows
- **Calendar Interaction Testing**: Use Playwright locators to test calendar day selection and tooltip behavior
- **Data Rendering Validation**: Test that components properly render fetched data in calendar views
- **Build Validation**: Always run `npm run build && npm run lint` before E2E tests to catch compilation issues

### Test Coverage Strategy

- **Unit Tests**: Business logic, validation functions, utility methods
- **E2E Tests**: Component integration, user workflows, data rendering
- **Build Tests**: TypeScript compilation, linting, bundle generation

## Examples

- "How should I test this PTO calculation function?"
- "What tests do I need for this API endpoint?"
- "How do I test the admin panel functionality?"

## Additional Context

This skill promotes the project's testing standards using Vitest for unit tests and Playwright for E2E tests, ensuring comprehensive coverage of business logic.
