Test Case Management with Folder Hierarchy

Test case management in BesTest is built around a folder hierarchy that keeps even large test catalogs navigable. Create nested folders that mirror your product's architecture - a top-level "Payments" folder with sub-folders for "Checkout", "Refunds" and "Subscriptions" - and drag test cases between them, one or many at a time, without losing links or execution history.

Each test case holds sequential steps with an action, test data and an expected result, or a BDD scenario in Gherkin. The step editor works the same way when you create a test case and when you edit one: big step numbers you can scan, drag handles (or Alt + up/down) to reorder, and Tab to move through the fields - Tab in the last expected result adds a new step. The Gherkin editor grows with your text, shows line numbers and keeps a syntax guide at your side. A step that only needs an expected result, or only test data, saves just fine.

When a feature lands with a list of scenarios, Create in bulk turns one name per line into that many test cases, with the shared fields set once. Do it from the test case catalog, or from the BesTest panel on a Jira work item so every new test case is linked to the story from the start. Need your own vocabulary? Add custom fields (a "Component" or "Platform" select, for example) and filter or build Smart Collections on them. Filters range from a quick name or key search to BQL queries with ORDER BY.

BesTest stores test cases in its own data model rather than as Jira issues. Your backlog stays clean, your issue count stays low, and thousands of test cases never slow your instance down. Test cases still link to Jira work items and to requirements for full traceability - they just don't pollute your project's issue list.