testing

Design and implement unit, integration, and end-to-end tests across frontend and backend projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams document behavior with fast, deterministic tests that prevent regressions, ensuring software behaves as intended.

Core Features & Use Cases

  • Design and implement unit, integration, and E2E tests for frontend and backend projects.
  • Enforce accessibility (a11y) and internationalization (i18n) testing to widen software quality.
  • Apply a mandatory testing workflow that prevents commits without passing tests in all ecosystems.

Quick Start

Run the testing workflow by writing tests for a new feature, then execute the test suite with the project’s standard command (e.g., npm test, pytest, or go test) and verify all tests pass.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I design unit and integration tests for frontend and backend projects?

To design unit and integration tests, you write behavioral specifications for your frontend and backend components that run quickly and deterministically. This approach documents behavior and prevents regressions by ensuring software functions as intended across the stack.

Can I enforce a mandatory testing workflow that prevents commits without passing tests?

Yes, you can enforce a mandatory testing workflow that blocks commits without passing tests. This ensures software quality across Node, Python, Go, and Rust ecosystems by integrating with common test runners like npm test, pytest, or go test.

How do I include accessibility and i18n testing in my end-to-end test suite?

You include accessibility (a11y) and internationalization (i18n) testing by applying these considerations directly within your end-to-end test design. Widening your software quality scope ensures applications are usable and properly localized across different regions.

Does this testing approach support E2E tests with Playwright?

Yes, this testing approach supports E2E tests with Playwright. It enables designing and implementing end-to-end tests that prevent regressions, integrating seamlessly with common test runners to verify behavior across your frontend and backend projects.

What is the best way to prevent regressions across multiple ecosystems like Node, Python, Go, and Rust?

The best way to prevent regressions across Node, Python, Go, and Rust is to design fast, deterministic tests that document behavior. Executing the test suite with each ecosystem's standard command verifies all tests pass before commits.