#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
-
Logical Grouping
Group test cases by feature, module, workflow, or business capability.
-
Clear Naming
Use names that clearly reflect intent, such as:
Login – SmokePayments – RegressionCalendar – High Priority
-
Meaningful Descriptions
Describe why the suite exists and when it should be used.
-
Reusability First
Design suites so they can be reused across multiple test runs and releases.
#Using Manual Selection (Green)
Manual selection is best when test inclusion must be explicit and stable.
Recommended when:
- Selecting critical-path test cases
- Creating fixed regression or certification suites
- Defining smoke suites with a small, known set
- Ensuring specific test cases always execute
Why manual works well:
- Predictable execution
- No dependency on metadata
- Ideal for release gates
#Using Filter-Based Selection (Violet)
Filters are ideal for dynamic and evolving test coverage.
Recommended when:
- Test cases change frequently
- Coverage should grow automatically
- Grouping is rule-driven instead of curated
Common filter strategies:
- Priority-based (e.g., High, Critical)
- Status-based (e.g., Active)
- Tag-based (e.g.,
smoke, api)
- Folder-based (entire modules or features)
- Custom field–based
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 (green) and filters (violet).
Best practices:
- Manually include non-negotiable test cases
- Use filters for coverage expansion
- Allow deduplication to handle overlaps automatically
- Review filters periodically, not manually selected tests
Result:
- Stable core
- Flexible growth
- Minimal upkeep
#Common Use Cases
#Feature Testing
- Create a suite per feature
- Use folder or tag-based filters
- Manually add critical edge cases
- Execute during feature validation cycles
#Regression Testing
- Create a regression suite
- Manually include historically sensitive test cases
- Add filters for high-priority or critical tests
- Run regularly or before releases
#Smoke Testing
- Create a small, fast-executing suite
- Manually select essential workflows
- Keep the suite intentionally small
- Use it post-deployment or post-build
#Environment-Specific Testing
- Tag test cases by environment
- Use filters to include environment-specific tests
- Manually add exceptions if needed
- Execute environment-aligned suites
#Repository Organization
- Create suites by test type (manual vs automated)
- Use filters to separate automation-ready tests
- Maintain suites aligned with testing phases
- 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
-
Overly complex filters
Keep rules simple and readable.
-
Manual-only everywhere
This increases maintenance effort over time.
-
Unclear suite intent
Always document why a suite exists.
-
Ignoring hybrid capability
Hybrid suites are often the most practical choice.
#Next Steps