User Manual

Learn how to use TestPairs effectively to create pairwise test cases

Getting Started

TestPairs helps you create comprehensive test cases using pairwise testing methodology. This approach dramatically reduces the number of test cases needed while maintaining high coverage of potential defects.

The Basic Workflow
  1. Create a Test Set - A container for your testing scenario
  2. Add Attributes - The parameters you want to test
  3. Define Constraints - Rules to exclude invalid combinations
  4. Generate Test Cases - Automatic pairwise generation
  5. Export Results - Download as CSV or JSON for use in your testing tools

Test Sets

A test set is a collection of related test parameters for a specific testing scenario.

Creating a Test Set
  1. Click the Add Test Set button on your homepage
  2. Enter a descriptive name for your test set
  3. Click Add to create the test set
lightbulb Tip: Use descriptive names like 'Web Browser Testing' or 'Payment Form Validation' to easily identify your test sets later.

Attributes

Attributes are the test parameters that can have different values. They represent the dimensions of your testing space.

Adding Attributes
  1. In your test set, click Add Attribute
  2. Enter the attribute name (e.g., 'Browser', 'Operating System')
  3. Add possible values, one per line:
    • For 'Browser': Chrome, Firefox, Safari
    • For 'Screen Size': Desktop, Tablet, Mobile
  4. Click Add to save the attribute
Editing Attributes

Click the edit icon next to any attribute to modify its name or values. Note that changing attributes may affect existing constraints.

warning Important: You need at least 3 attributes to generate pairwise test cases automatically.

Constraints

Constraints help you exclude invalid or impossible combinations from your test cases. They make your test suite more realistic and focused.

Creating Constraints
  1. Click Add Constraint in your test set
  2. Build your constraint rule using the form:
    • Premises - The conditions that trigger the rule
    • Consequence - What should happen when conditions are met
  3. Choose appropriate operators:
    • is - Attribute equals one of the specified values
    • is not - Attribute does not equal any of the specified values
    • must - Attribute must be one of the specified values
    • must not - Attribute must not be any of the specified values
Example Constraints
Exclusion Rule

If Browser is Safari, then Operating System must not be Windows

Prevents invalid combinations
Requirement Rule

If Payment Method is Apple Pay, then Device must be iOS

Ensures required combinations
info Note: TestPairs automatically detects constraint conflicts and duplicates, helping you maintain a clean rule set.

Fixed Test Cases

Fixed test cases (seed rows) allow you to specify exact test combinations that must be included in your test suite, regardless of pairwise optimization.

Adding Fixed Test Cases
  1. Click Add Fixed Test Case in your test set
  2. Fill in the specific values for each attribute
  3. Leave fields empty (or select 'Auto') for attributes that can vary
  4. Click Add to save the fixed test case
When to Use Fixed Test Cases
  • Critical business scenarios that must always be tested
  • Edge cases that might not be covered by pairwise generation
  • Regression test cases from previous bugs
  • Specific combinations required by stakeholders

Coverage Levels

Coverage levels determine how thoroughly TestPairs covers parameter interactions.

2-Way Coverage (Default)

Covers all possible pairs of attribute values. Provides excellent defect detection with fewer test cases.

Recommended for most testing scenarios
3-Way Coverage

Covers all possible triplets of attribute values. More thorough but generates significantly more test cases.

Use for critical systems requiring maximum coverage

Export

Export your generated test cases to use in external testing tools or documentation.

Export Formats
table_chart CSV Export

Perfect for importing into test management tools, Excel, or other spreadsheet applications.

code JSON Export

Ideal for automated testing frameworks and programmatic test generation.

How to Export
  1. In your test set, click the Export button
  2. Choose your preferred format (CSV or JSON)
  3. Click Download to save the file

Tips & Best Practices

Effective Attribute Design
  • Use meaningful, descriptive attribute names
  • Keep attribute values concise but clear
  • Group related parameters into separate test sets
  • Consider the realistic range of values
Smart Constraint Usage
  • Start with broad constraints, then refine
  • Review constraint conflicts and duplicates
  • Use constraints to model real-world limitations
  • Test your constraints with small examples first
emoji_objects Pro Tip: Start with a small test set to familiarize yourself with the concepts, then scale up to more complex scenarios. The automatic test case generation happens when you have at least 3 attributes.
Back to Top