testing

Consolidate testing guidance for unit, integration, API E2E, and UI E2E workflows.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/ajelinek/skills-stash --skill testing-ajelinek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/ajelinek/skills-stash/tree/main/testing
Command: npx skills add https://github.com/ajelinek/skills-stash --skill testing-ajelinek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Use this skill to streamline testing practices across unit, integration, API E2E, and UI E2E tests, helping teams write, review, and organize tests with consistent patterns and quality controls.

Core Features & Use Cases

Trigger on requests to write a test, add a spec file, set up test data, use Playwright for browser E2E, write API end-to-end tests in Vitest, create page objects, configure a TestContext, implement a setUp function, or decide what kind of test to write for a given feature. Also trigger when fixing failing tests, improving test coverage, or refactoring test structure.

Quick Start

Run the interactive skill installer to add this skill from the repository: npx skills add ajelinek/skills-stash testing

Frequently Asked Questions about testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure my Vitest and Playwright tests to reduce flakiness?

Reduce test flakiness by consolidating unit, integration, API E2E, and UI E2E workflows into structured test suites, applying consistent patterns for data seeding and test organization to maintain reliable test quality.

When should I write an API E2E test versus a UI E2E test using Playwright?

Write API E2E tests in Vitest to validate backend workflows and data seeding, while using Playwright for UI E2E tests to verify browser interactions, ensuring you apply the correct test type for each feature.

How do I set up test data and configure a TestContext for integration testing?

Set up test data for integration testing by implementing a setUp function and configuring a TestContext, which manages data seeding and test state to ensure reliable and isolated test execution.

What is the best way to organize page objects when writing browser E2E tests?

The best way to organize browser E2E tests is by creating page objects to encapsulate UI interactions, streamlining test structure and improving maintainability across your Playwright test suites.

Does this testing guidance apply to fixing failing tests and refactoring test coverage?

Yes, the testing guidance applies to fixing failing tests, improving test coverage, and refactoring test structure by providing consistent patterns and quality controls across unit, integration, and E2E workflows.