Smart Collections

Smart Collections are a core test management feature in BesTest that automates one of the most time-consuming parts of testing in Jira: building test cycles. Instead of manually selecting test cases and assigning testers for every regression run or sprint cycle, you define a collection once and reuse it to generate cycles with a single action. The collection stays current as your test catalog evolves, so your team spends less time on administration and more time on actual testing.

A collection in BesTest is a container that holds test cases. You can add test cases in two ways. The first is manual selection: browse or search your test case library and pick specific tests to include. The second is rules: use the Visual search editor to define criteria that dynamically match test cases. The editor provides dropdown selectors for fields, operators, and values with auto-complete, making it easy to build conditions like "Tag = regression AND Module = Payments AND Priority >= High." You can combine both approaches in a single collection - add a handful of critical tests by hand and let rules handle the rest.

What makes collections powerful is what happens when you use them to create a test cycle. At cycle creation time, BesTest evaluates every rule in the collection against the current test case library. If a teammate added new test cases that match a rule since the last time you created a cycle, those tests are automatically included. If test cases were deprecated or no longer match, they are excluded. The result is a cycle that reflects the current state of your Jira project without anyone having to manually update the collection.

Default assignees take this a step further. For each rule in a collection, you can specify which tester should be assigned to the resulting test executions. You can also set a default assignee for individually added test cases. When the cycle is created, BesTest fills in all the assignees automatically. This means you can route payment module tests to your payments specialist, security tests to your security tester, and API tests to your automation engineer - all without manually assigning dozens of test executions after cycle creation. For teams that run weekly regression cycles, this alone can save significant setup time every sprint.

Common patterns teams use with Smart Collections include: a "Quick Smoke" collection with a rule matching tests tagged "smoke" and critical priority, producing a focused 15-test suite for hotfix verification. A "Full Regression" collection with broader rules across all modules for major releases. A sprint-scoped collection that includes tests linked to stories in the current sprint. A module-specific collection for focused testing after a particular area of the product changes. Each collection can have different default assignees tailored to the team members who know that area best.

Smart Collections work alongside BQL (BesTest Query Language), which provides JQL-like search across all your test management data. While BQL is designed for ad-hoc searching and filtering across the application, the Visual search editor in collections is purpose-built for defining reusable rules that drive cycle creation. Together, they give Jira teams powerful search and automation capabilities without any of the issue bloat that comes from storing test data as Jira issues.