Test Suites Best Practices & Use Cases

Test suites help you control what gets executed, when, and why. A well-structured test suite strategy reduces maintenance effort while improving execution reliability.

This guide outlines recommended practices and common use cases.

---

Organizing Test Suites

1. Logical Grouping
   Group test cases by feature, module, workflow, or business capability.

2. Clear Naming
   Use names that clearly reflect intent, such as:

   • Login – Smoke
   • Payments – Regression
   • Calendar – High Priority

3. Meaningful Descriptions
   Describe why the suite exists and when it should be used.

4. Reusability First
   Design suites so they can be reused across multiple test runs and releases.

---

Using Manual Selection

Manual selection is best when test inclusion must be explicit and stable.

Recommended when:

1. Selecting critical-path test cases
2. Creating fixed regression or certification suites
3. Defining smoke suites with a small, known set
4. Ensuring specific test cases always execute

Why manual works well:

• Predictable execution
• No dependency on metadata
• Ideal for release gates

---

Using Filter-Based Selection

Filters are ideal for dynamic and evolving test coverage.

Recommended when:

1. Test cases change frequently
2. Coverage should grow automatically
3. You want a rule to decide which cases are included, rather than picking each one

Common filter strategies:

• Priority (e.g., High)
• Severity (e.g., Blocker, Critical)
• Labels (e.g., smoke, api)
• Automation status
• Folder location (entire modules or features)
• Dropdown custom fields

Why filters work well:

• Minimal maintenance
• Automatically includes new matching test cases
• Ideal for large or fast-moving repositories

---

Hybrid Approach (Best of Both)

Hybrid test suites combine manual selection and filters.

Best practices:

1. Manually include the test cases that must always run
2. Use filters for coverage expansion
3. Allow deduplication to handle overlaps automatically
4. Review filters periodically, not manually selected tests

Result:

• Stable core
• Flexible growth
• Minimal upkeep

---

Common Use Cases

Feature Testing

1. Create a suite per feature
2. Use folder or label filters
3. Manually add critical edge cases
4. Execute during feature validation cycles

---

Regression Testing

1. Create a regression suite
2. Manually include historically sensitive test cases
3. Add filters for high-priority or critical tests
4. Run regularly or before releases

---

Smoke Testing

1. Create a small, fast-executing suite
2. Manually select essential workflows
3. Keep the suite intentionally small
4. Use it post-deployment or post-build

---

Environment-Specific Testing

1. Label test cases by environment
2. Use filters to include environment-specific tests
3. Manually add exceptions if needed
4. Execute environment-aligned suites

---

Repository Organization

1. Create suites by test type (manual vs automated)
2. Use filters to separate automation-ready tests
3. Maintain suites aligned with testing phases
4. Avoid duplicating suites unnecessarily

---

Maintenance Tips

Keep Suites Healthy

• Review filters periodically
• Remove unused or obsolete suites
• Avoid deeply nested or overly broad filters
• Keep suite sizes manageable

Avoid Over-Engineering

• Don’t create a suite for every minor scenario
• Prefer fewer, purposeful suites
• Let filters do the heavy lifting

---

Common Pitfalls to Avoid

1. Overly complex filters
   Keep rules simple and readable.

2. Manual-only everywhere
   This increases maintenance effort over time.

3. Unclear suite intent
   Always document why a suite exists.

4. Ignoring hybrid capability
   Hybrid suites are often the most practical choice.

---

Next Steps

• Learn how to Create Test Suites
• Review how to Manage Test Suites
• Execute suites using Test Runs
• Group executions under Releases
• Manage test cases in the Repository