Qase Docs
Help CenterAPI DocsRoadmapSign up for free
  • General
    • Qase docs
    • Get started with the Qase platform
      • Account settings
      • Projects
      • Test suites
      • Test cases
        • Test Case Parameters
        • Test case review
        • Shared steps
        • Import test cases
        • Export test cases
        • Trash bin
        • Muted Tests
        • System fields
        • Nested steps
        • Test case actions
        • Filters
      • Requirements Traceability Report
      • AI Test Case Generator
    • Execute testing
      • Test plan
      • Test runs
      • Configurations
      • Environments
    • Issues tracking
      • Defects
      • Milestones
      • Requirements
    • Analytics
      • Dashboards
      • Queries (QQL, Qase Query Language)
      • Saved queries
    • Webhooks
      • Test Case
      • Test suite
      • Test plan
      • Shared step
      • Milestone
      • Custom field
      • Test run
      • Defect
      • Test review
  • AIDEN
    • AIDEN - QA Architect
  • Guide: Action editor
  • Administration
    • Workspace management
      • Users
      • Invites
      • Groups
      • Roles
      • Fields
      • Custom fields
      • Notifications
      • Tags
      • Attachments
      • Audit logs
      • Hotkeys
    • SSO / SAML instructions
      • AzureAD
      • OneLogin
      • Google Workspace
      • Okta
      • JumpCloud
    • SCIM
      • User lifecycle management with SCIM
      • Enable SCIM
      • Users
      • Discovery features
      • Errors
    • Security
      • SOC 2 Type II / SOC 3
      • ISO/IEC 27001:2022
      • Penetration testing report
      • Subprocessors
      • Qase IP addresses
    • Billing
      • Billing options
    • Subscriptions
      • Free plan
      • Startup plan
      • Business plan
      • Enterprise plan
  • Apps
    • Issue tracking
      • Jira Cloud
      • Jira Server/Datacenter Plugin installation
      • GitHub
      • Asana
      • Linear
      • Monday
      • ClickUp
      • Trello
      • Azure DevOps
      • GitLab
      • YouTrack
      • Redmine
    • CI/CD
      • Jenkins
      • BitBucket
      • GitHub CI
      • GitLab CI
    • Chats
      • Slack
  • Automation
    • Qase API
    • Reporters
      • JavaScript
        • Playwright
        • Cypress
        • Mocha
        • Newman
        • Jest
        • WebDriverIO
        • CucumberJS
        • TestCafe
      • Python
        • Pytest
        • Robot Framework
        • Behave
        • Tavern
      • Java
        • TestNG
        • JUnit 4
        • JUnit 5
        • Cucumber 3 (jvm)
        • Cucumber 4 (jvm)
        • Cucumber 5 (jvm)
        • Cucumber 6 (jvm)
        • Cucumber 7 (jvm)
      • PHP
        • PHPUnit
        • Codeception
      • Kotlin
        • Kaspresso
    • Qase CLI App
      • XCTest
Powered by GitBook
On this page
  • Suite Options
  • Views
  • Nested Tree View
  • Folder View
  • Mind Map view (Beta)
  1. General
  2. Get started with the Qase platform

Test suites

PreviousProjectsNextTest cases

Last updated 4 months ago

Test Suites are like containers for your Test cases, letting you organize them by specific areas of testing.

For example, in a Mobile game project, you need to test things like Background Music, User Interface, Performance, and Save Features. We'll create a separate Test Suite for each of these areas.

Since the project is new and doesn't have any suites or cases yet, you'll need to create your first suite by clicking the "+Suite" or "Create New Suite" buttons.

After clicking one of those buttons, a pop-up will appear where you need to fill in information about the suite.

  • Suite Name: Give your Test Suite a clear, descriptive name that shows what area or domain it covers. The Suite Name is the only required field when creating a Suite; the other fields are optional and can be filled in later or left empty.

  • Parent Suite: You can create a multi-level hierarchy of Test Suites. If your Suite is part of a larger group of testing scenarios, you can place it within a higher-level Parent Suite.

  • Description: Add details and context about which Test Cases should be included in the Test Suite.

  • Preconditions: Describe the steps that need to be completed before starting the Test Cases in the new Suite.

After creating one or more Test Suites, your Repository will now reflect how your Test Suites are structured and how they are related to each other.

Suite Options


If you hover your mouse over Test Suite while in Repository view, several controls will reveal itself:

  • Collapse / Expand: Clicking on the name of your test suite will either expand or collapse the suite:

  • Create Case / Create Suite: Clicking on the “+” icon opens up a menu with the options to “Create Suite” or “Create Case”:

  • Edit Suite: Clicking on the pencil icon allows you to edit the suite itself:

  • Clone Suite: Clicking on the two pages icon allows you to clone the suite. You also have the option to choose the project to which you would like the suite to be cloned to, the parent suite, the clone strategy, and the prefix, and you can choose to clone the suite with its children (suites and cases)

Views


To navigate around your Suite structure easier, there are three Suite Tree layouts available, which you can toggle between using the “Views” dropdown in the top-right corner of the Repository:

Nested Tree View


The default layout - “Nested Tree View”, shows all the Suites you currently have in your project; you can open up the Suite Tree sidebar to navigate from one suite to another:

Folder View


The alternative "Folders view" layout displays only the Test Suite and Test Cases you are currently focusing on. To navigate to a different Suite, you need to select it from the sidebar.

This layout is a better solution for large structures with complex hierarchies.

When a parent suite is selected in folder view, both the test cases within this suite and its child suites are displayed in the main view.

Mind Map view (Beta)


This view displays all the suites and test cases within a project as a mind map. It also provides the option to create quick cases or suites by clicking on the “+” icon. You can alter the hierarchy of display by dragging the suite up or down. You can also move a test case from one suite to another. Additionally, clicking on the case will allow you to update its title.

Moreover, in both the Nested Tree view and the Folders view, you can click on the “...” menu icon to Edit, Close, Select and Unselect all, Create Suite, Create Case, and Delete.

Delete Suite: Clicking on the trash can icon will allow you to delete the suite. Once you’ve deleted the suite, you will no longer be able to restore the suite from the “”:

Trash Bin