testing

Establish guidelines for writing, reviewing, and planning software tests.

Updated Jan 15, 2022
One-click install
npx skills add https://github.com/AntonioCandinho/dotfiles --skill testing-antoniocandinho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/AntonioCandinho/dotfiles/tree/main/skills/testing
Command: npx skills add https://github.com/AntonioCandinho/dotfiles --skill testing-antoniocandinho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a comprehensive framework and best practices for writing, reviewing, and planning tests to ensure software quality and reliability.

Core Features & Use Cases

  • Confidence-First Testing: Prioritizes tests that provide genuine confidence over mere coverage metrics.
  • Behavior-Driven Development: Encourages testing user behavior rather than implementation details.
  • Language-Specific Guidelines: Offers tailored advice for languages like Swift, promoting modern testing frameworks.

Quick Start

Follow the principles outlined in this skill to write a new integration test for the user authentication module.

Frequently Asked Questions about testing

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

FAQPage Schema
What is behavior-driven development in software testing?

Behavior-driven development is a testing approach that focuses on verifying user behavior rather than internal implementation details. It shifts the emphasis of software testing toward building confidence in real-world outcomes rather than simply chasing coverage metrics.

How do I write an integration test that builds confidence?

To write an integration test that builds confidence, prioritize tests that validate real user behavior end-to-end. Avoid aggressive mocking and instead follow a test-first approach to ensure your integration tests provide genuine quality assurance.

Does this testing strategy support Swift and other specific languages?

Yes, this testing strategy supports multi-language environments and offers tailored guidelines for Swift. It advocates for using modern testing frameworks in Swift to establish robust behavior-driven development and integration test strategies.

When should I use integration and end-to-end tests over aggressive mocking?

You should use integration and end-to-end tests over aggressive mocking whenever you need genuine confidence in software quality. Aggressive mocking often hides integration failures, so prioritizing broader test strategies ensures your user behavior validation remains robust.

What is the best way to plan a test-first approach for a new module?

The best way to plan a test-first approach is to establish guidelines for writing and reviewing tests before implementation begins. Focus on behavior-driven development and plan integration tests that validate actual user behavior for your new module.