LogoLogo
  • About SimplifyQA
  • Get Started with SimplifyQA
    • Agile & Non-Agile Framework
    • OS Support
    • SimplifyQA Hosting
      • On-premise Installation Guide
        • Pre-requisites
        • Installation Guide
      • Support and Resources
      • Training and Onboarding
    • Explore SimplifyQA for your Application Lifecycle Management
  • SimplifyQA Installation & Setup
    • Setup QAWizard
    • Register QAWizard
    • Setup Android Device
      • How to enable settings in android device?
      • How to register android device?
      • Setup emulators on Android Studio for automation in SimplifyQA
    • Setup iOS Device
      • How to setup iOS device in Apple Developer Account?
      • How to register iOS device?
  • Get to know your Workspace
    • Blueprint of SimplifyQA
    • Key Terminologies
    • Search/Global Search
      • How to use global search?
      • How to use advance search?
      • How to use column sort?
      • How to use column filters?
      • Add or remove columns
    • Rich Text Editor
    • Import & Export
    • Add Attachments
    • Add Linkages
    • Add Comments
    • Manage Cards in board view
    • Configure Watchlist
    • Track Edit History
    • Hierarchy Tree
  • Admin Controls & Configurations
    • Manage Projects & Users
      • Create Project and Invite Users
      • Project Settings
        • Create and Manage Custom Fields
      • Grant Admin Privilege to User
      • Invite/Add Users to Team
      • User Directory and Access Control
      • Configure Page Layout
      • Manage Roles and Privileges
      • Configure Auto-logging of Defects
    • Configure your clients
    • Password settings
  • Release & Sprints
    • Introduction to Releases
    • Create & Manage Release & Sprint
    • Start & Close a Sprint
  • Create and Manage your Requirements
    • Introduction to Requirement Management
    • Create & Manage Epic
    • Create & Manage Features
    • Create & Manage User Stories
  • Introduction to Test Management in SimplifyQA
    • Create a Manual Test Case in SimplifyQA
    • Create an Automation Test Case in SimplifyQA
    • Learn API Testing in SimplifyQA
      • Create an API Test Case in SimplifyQA
      • Quick Test the API
      • Validating API Responses
      • Understanding API Parameterisation
      • Save API Response Data
      • Achieve Data flow for E2E Testing
    • Create Hybrid Test Case in SimplifyQA
    • Leverage Re-usability in your Tests
    • Organise your Test Cases
    • Linking a Test Case to User Story
    • Linking a Test Case to Defect
    • Version Control your Test Case
    • Create a Copy of your Test Case
    • Copy Test Case to different Project
    • Conditional Statements
      • Decision Making Statement
      • Looping Statement
      • BREAK & CONTINUE Statement
    • Supported Actions
    • Utilising Mobile Inspector in SimplifyQA
  • Introduction to Script-less Recording of Test Case
    • Record a Web Test Case in SimplifyQA
    • Record an Android Test Case in SimplifyQA
      • Record an Android Test Case
    • Record Functions in SimplifyQA
    • Understand Object Recognition Mechanism & Self Healing in SimplifyQA
  • Test Data Management
    • Work with the Formulas to Optimise Test Data
    • Import and Export Test Data Sets
  • Introduction to Object Repository
    • Capture Objects for your Tests
    • Organise your Test Objects
    • Parameterise your Test Object Properties
  • Introduction to Parameters
    • Various Types of Parameters
    • Create and Utilise Parameters in your Test Case
    • Understanding Runtime Parameters
  • Defect Management
  • Marketplace
    • Integration with Project Management Tools
      • Integrating SimplifyQA with Jira
        • Configure Web-hooks
        • SimplifyQA Setup for Integration
          • Setup your Account for Jira Integration
          • Configuration in SimplifyQA Admin
          • Steps to Generate a Jira API Token
          • Steps to create SimplifyQA token
          • Steps to get Jira Account ID
          • Synchronisation Functionality Between SimplifyQA and Jira
          • Analyse Logs for Data Synchronisation
        • Mapping Fields for Issue Types
        • Viewing SimplifyQA Test Cases in Jira
  • Legal Documents
    • End-User License Agreement
Powered by GitBook
On this page
  • Why Organise Test Cases?
  • How to Organise your Test Cases
  • Best Practices for Organising Test Cases
  • How Organised Test Cases Help
  1. Introduction to Test Management in SimplifyQA

Organise your Test Cases

PreviousLeverage Re-usability in your TestsNextLinking a Test Case to User Story

Last updated 1 month ago

Organising your test cases effectively is key to smooth testing and better project management. SimplifyQA makes this easy with features like mapping test cases to modules and submodules, as well as a handy tree view for navigation.

Why Organise Test Cases?

  1. Enhanced Clarity: Maintain a structured hierarchy for better visibility and easy access.

  2. Improved Navigation: Quickly locate specific test cases using the tree view structure.

How to Organise your Test Cases

1. Map Test Cases to Modules and Submodules

Mapping test cases to relevant modules and submodules helps categorise them based on application functionality.

Steps to Map Test Cases:

  • Create Modules and Submodules:

    • Navigate to the Test Case section in SimplifyQA from the left-hand panel.

    • Click "Add Module" from the left-hand section to create a new module and provide a meaningful name (e.g., "Login Module").

    • Add submodules under the module as needed (e.g., "Forgot Password", "User Authentication").

  • Assign Test Cases to Modules:

    • Go to the Test Cases section.

    • Open the desired test case.

    • Select the Module and Submodule from the dropdown menus within the test case details.

    • Save your changes.

2. Navigate Test Cases using the Tree View

The tree view provides a hierarchical representation of your modules, submodules, and associated test cases.

Steps to Use the Tree View:

  • Open the Test Cases section.

  • The tree view will display all modules and submodules in a collapsible structure.

  • Click on a module or submodule to view the associated test cases in the table on right side.

Benefits of Tree View:

  • Quickly locate test cases without searching through lists.

  • Provides a clear overview of the module hierarchy and test case distribution.

  • Easily navigate between different modules and submodules.

Best Practices for Organising Test Cases

  1. Use Meaningful Names: Assign descriptive names to modules, submodules, and test cases to make navigation intuitive.

  2. Adopt a Standard Structure: Follow a consistent hierarchy for all projects to simplify understanding across teams.

  3. Regularly Update Mappings: Ensure test cases remain mapped correctly when new modules or submodules are added.

How Organised Test Cases Help

  1. Faster Test Execution: Locate and execute test cases quickly during sprints or regression cycles.

  2. Comprehensive Coverage: Ensure no modules are left untested by tracking test cases linked to each functionality.

  3. Simplified Maintenance: Update or modify test cases with ease by navigating directly to the relevant module.

Frequently Asked Questioons

Can I assign a test case to multiple modules or submodules?

No, a test case can only be mapped to one module and submodule to maintain clarity and avoid duplication.