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
  1. General
  2. Execute testing

Test plan

PreviousExecute testingNextTest runs

Last updated 4 months ago

What is a test plan in software testing?

Test Plan is your way to organize the various into a cohesive scenario that will encompass various cases from different domains (i.e., different ).

Later on, when performing , you will use a pre-created Test Plan, which already contains every Test Case and/or Test Suite necessary.

When composing a new Test Plan, you can add standalone Test Cases and entire Test Suites alike.

To create a new Test Plan, navigate to the "Test Plans" section, and hit "Create Test Plan":

Once in the Test Plan creation menu, fill in the Plan details:

  1. Title:

  2. Description:

Next, choose which Test Cases or Test Suites your new Test Plan will contain. You can add standalone Test Cases by highlighting a Test Suite and picking Test Cases from it individually and you can add an entire Test Suite by checking the box for it in the left-hand column.

Note: You can also use the search bar to search for specific cases that you would like to include in the plan. Also, while selecting cases, you can assign specific cases to certain users. The assignments can then be carried over to all future test runs built based on this test plan.

Finally, confirm by hitting the "Create plan" button below.

After a new Test Plan has been created, you will find it in the "Test Plans" section, with some of the Plan attributes shown - run time, number of cases, time of creation, and update time.

Note: Once a test run has been created from this plan, upon opening this plan you will see a tab “Test Runs” which shows all the runs started based on this plan.

From the Menu button "..." next to a test plan, you can Edit, Delete or Export your Test Plan as XLS:

You can also select multiple test plans to delete them in bulk.

Note: If you introduce changes to a Test Plan (add or remove cases into/from it), it may affect your currently active test runs, that use this plan. The table below shows which changes will be happening:

Active test run - (Run NOT completed),

No results

Active test run,

results have been added, but the run is not completed

A completed test run

Test Case is added to a Plan

Case is added to a run

Case is added to a run

Case is NOT added to a run

Test Case is removed from a Plan

Case is removed from a run

Case is NOT removed from a run

Case is NOT removed from a run

Test Cases
Test Suites
Test Runs