testing

Define structured guidelines for unit, integration, contract, and performance testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The testing discipline codifies best-practice rules for unit, integration, contract, and performance testing to improve reliability, maintainability, and faster feedback across codebases.

Core Features & Use Cases

  • BDD-style testing conventions and naming guidelines
  • Coverage guidance for unit, integration, contract, and performance tests
  • References to integrated patterns and sample rules for Testcontainers, Pact, Spring Cloud Contract, and performance tools
  • Use Case: apply these rules when creating new test suites to ensure descriptive tests, robust assertions, and fast feedback

Quick Start

Write and apply BDD-based test rules across new and existing codebases to ensure descriptive tests, proper assertions, and fast feedback loops.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I write high-quality BDD-style tests for my project?

High-quality BDD-style tests require structured naming conventions and descriptive guidelines that enforce robust assertions and clear behavior specifications across your codebase.

What is contract testing and when do I need it?

Contract testing validates shared expectations between integrated services. You need it when connecting microservices to ensure compatibility and prevent breaking changes across distributed components.

How do I set up integration tests using Testcontainers?

Set up integration tests with Testcontainers by applying structured test guidelines that manage external dependencies in isolated containers, ensuring robust assertions and fast feedback execution loops.

Does this testing framework support performance testing workflows?

Yes, it supports performance testing workflows by providing explicit rules and reference patterns for performance tools, enforcing structured analysis artifacts to validate system responsiveness and stability.

What are the best practices for test coverage across unit and integration tests?

Best practices for test coverage involve applying structured rules across unit and integration tests, enforcing descriptive naming, preventing empty tests, and ensuring robust assertions for faster feedback.

Why do my integration tests fail to provide fast feedback?

Integration tests fail to provide fast feedback when lacking structured guidelines for naming and assertions. Applying BDD-based rules and proper coverage analysis ensures robust tests and quicker execution loops.