testing

Enforce unit and E2E tests with pytest, moto, and Playwright.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces rigorous testing practices to prevent bugs, ensure code quality, and maintain the reliability of the application.

Core Features & Use Cases

  • Mandatory Testing: Ensures all code has corresponding unit and E2E tests.
  • Strict Assertions: Prevents ignoring test failures or masking errors.
  • Use Case: Before merging any new feature, this Skill ensures that both backend logic (unit tests) and user-facing interactions (E2E tests) are thoroughly validated, preventing regressions and ensuring a stable release.

Quick Start

Run the unit tests for the backend services.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I enforce unit and e2e tests for all new features?

To enforce unit and e2e tests for all features, you need a strict testing strategy that mandates both test types before merging. This approach prevents the masking of test failures and ensures comprehensive code coverage for critical business logic.

What is the best way to prevent masking test failures in code quality assurance?

The best way to prevent masking test failures in code quality assurance is to apply strict assertions and test-driven development principles. This ensures errors are explicitly caught and resolved rather than ignored during backend and frontend validation.

Can I use pytest with moto for backend unit tests?

Yes, you can use pytest with moto for backend unit tests. This combination is required to thoroughly validate backend logic, prevent regressions, and ensure stable releases as part of a comprehensive test-driven development workflow.

Does Playwright work for frontend e2e tests in a test-driven development workflow?

Yes, Playwright works for frontend e2e tests and is required to validate user-facing interactions. Using it ensures frontend behavior is thoroughly tested alongside backend logic to maintain application reliability and prevent regressions.

When do I need both unit and end-to-end tests for reliable software?

You need both unit and end-to-end tests for reliable software before merging any new feature. This dual approach validates both internal backend logic and user-facing interactions, ensuring comprehensive code coverage and preventing regressions.