Verified:GitHub

test-design-techniques

Generate systematic test designs using boundary value analysis and equivalence partitioning.

436|78|Updated Sep 11, 2025

Search Tags:#test coverage #test design #combinatorial testing #BVA #equivalence partitioning #pairwise #decision tables

Ready to run

npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill test-design-techniques

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-design-techniques
Source: https://github.com/proffesor-for-testing/agentic-qe/tree/main/.claude/skills/test-design-techniques
Command: npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill test-design-techniques

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides systematic methods to design comprehensive and efficient test cases, reducing redundancy and maximizing bug detection with fewer tests compared to random approaches.

Core Features & Use Cases

Boundary Value Analysis (BVA): Focuses testing on input boundaries where bugs are most likely to occur.
Equivalence Partitioning (EP): Divides input into groups that behave similarly, reducing the number of test cases needed.
Pairwise (Combinatorial) Testing: Dramatically reduces the number of test combinations while ensuring high coverage for interacting parameters.
Use Case: For a user age input field (18-120), use BVA to generate test cases for 17, 18, 19, 119, 120, and 121, ensuring boundary conditions are correctly handled.

Quick Start

Use the test-design-techniques skill to generate boundary value analysis test cases for an integer field named 'quantity' with a valid range of 1 to 100.

Frequently Asked Questions about test-design-techniques

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

FAQPage Schema

How do I design test cases for boundary value analysis?▼

Boundary value analysis focuses testing on input edges where bugs occur most frequently. Identify the valid range limits (e.g., 1–100 for quantity), then generate test cases at and just outside those boundaries: values like 0, 1, 2, 99, 100, and 101 to catch off-by-one errors and edge-case handling failures.

What's the difference between equivalence partitioning and boundary value analysis?▼

Equivalence partitioning groups inputs that behave identically, reducing redundant test cases across similar ranges. Boundary value analysis targets specific edge points within those groups where defects cluster. Together, they minimize test volume while maximizing coverage of distinct behaviors and failure modes.

How does pairwise testing reduce the number of test combinations?▼

Pairwise testing ensures every pair of parameter values is tested together at least once, dramatically cutting combinations compared to exhaustive testing. For multi-parameter scenarios, it maintains high interaction coverage while eliminating redundant permutations, delivering faster test execution and bug detection.

When should I use decision tables for test design?▼

Decision tables map business rules with multiple conditions to expected outcomes, making them ideal for rule-heavy logic with interdependent inputs. Use them for workflows with conditional branches, pricing rules, or approval logic where you need to verify all condition combinations systematically.

Can I apply boundary value analysis to non-numeric inputs?▼

Boundary value analysis applies to any ordered or ranged input: numeric fields, date ranges, string lengths, and list sizes. For strings, test minimum length (empty, single character) and maximum length boundaries; for dates, test year/month/day limits to catch validation and formatting bugs.

How do state-transition testing and pairwise testing work together?▼

State-transition testing maps allowed state changes and validates transitions systematically. Pairwise testing reduces redundancy when multiple parameters influence state behavior. Together, they ensure stateful workflows handle parameter interactions correctly without exhaustive test explosion.