#Test Suites Overview
Test Suites are logical collections of test cases used primarily for test execution and planning. They allow teams to group test cases without changing the repository structure and make it easy to reuse the same set of tests across different executions.
Unlike folders, test suites do not control where test cases live—they define which test cases should be executed together.
#Core Concepts
#What Are Test Suites?
A test suite represents a curated set of test cases that can be reused across test runs.
Test suites help teams:
- Group related test cases for execution
- Reuse the same test selection across multiple runs
- Avoid duplicating or reorganizing test cases
- Define execution scope clearly
Test suites reference test cases from the repository but do not own them.
#Test Suites vs Folders
It’s important to distinguish between folders and test suites:
Folders
- Used for organizing test cases in the repository
- Define where a test case lives
- Static and structural
Test Suites
- Used for grouping test cases for execution
- Define what gets executed together
- Logical and reusable
- Do not affect repository structure
A single test case can belong to multiple test suites.
#How Test Suites Work
Test suites can include test cases in different ways, depending on how they are configured.
#Manual Inclusion
In manual suites:
- Test cases are explicitly selected
- The suite contains a fixed list of test cases
- Adding or removing test cases is done manually
This approach is useful when you want precise control over execution scope.
#Filter-Based Inclusion
In filter-based suites:
- Test cases are included dynamically
- Filters define which test cases belong to the suite
- New test cases matching the filters are automatically included
This is useful for scenarios like:
- Regression suites
- Smoke suites
- Automation-based execution sets
#Hybrid Suites
A test suite can combine both approaches:
- Manually selected test cases
- Dynamically included test cases via filters
This provides flexibility when some tests must always be included while others are conditionally added.
#Why Use Test Suites?
Test suites are especially useful for:
- Repeated executions (regression, sanity, smoke)
- Automation planning
- Release validation
- Cross-team testing coordination
- Reducing duplication of execution setup
They provide a clean separation between test organization and test execution planning.
#Best Practices
- Use folders to organize test cases structurally
- Use test suites to define execution scope
- Prefer filter-based suites for evolving test sets
- Keep suite names descriptive and purpose-driven
- Avoid creating too many overlapping suites without clear intent
#Permissions
Access to test suites depends on project role:
- Project Manager – Full access
- Project Coordinator – Full access
- Project Member – View and use test suites
- Project Viewer – Read-only access
Permissions respect project-level access controls.
#Next Steps