Test Cases

User Guide

SaaSMap

1. Introduction

Test Cases in SaaSMap describe how your team will verify that software works as expected. Each Test case includes a Title, objective, prerequisites, test data, and step-by-step instructions with expected results. Test cases live inside a project and can be linked to requirements from your backlog or project phases.

This guide explains how to create, manage, and use test cases—from authoring through test execution and defect reporting. It is written for everyday users such as developers, test managers, and testers.

What you can do with Test Cases

  • View and search all test cases for a project in list or card (grid) view.
  • Create test cases with AI assistance.
  • Generate multiple test cases at once from linked requirements.
  • Edit, Publish, clone, link, import, and export test cases.
  • Assign test cases to test cycles for execution by Testers.
  • Trace test cases back to requirements and forward to defects when tests fail.

 

2. Accessing Test Cases

Test cases are managed at project level.

  1. Sign in to SaaSMap and open Home.
  2. Select the project you are working on.
  3. In the project workspace, click the Test Cases tab.
  4.  

Everything on this tab applies only to the project you have open. If you do not have permission to view Test Cases for a project, the tab may not be visible.

  •  

3. The Test Cases Screen

List view and grid view

Use the toolbar to switch between List View (table) and Grid View (cards). Both views show the same data; choose the layout that works best for you.

List View

Grid View

Columns you will see (list view)

ColumnWhat it means
Test Case IDUnique identifier (for example, TC0000010).
TitleShort description of the Test case.
RequirementsRequirement or user story IDs linked to this test case.
PhaseProject phase the Test case is associated with.
Test CyclesTest cycles this case has been assigned to.
PillarThe high-level software area or product suite the Test Case belongs to
EpicEpic or module (application area) for the Test case.
StatusDraft or Published.
Created On / ByWhen the test case was created and who created it.

Row actions menu

From the list, open the options menu (⋮) on a row for common actions:

  • Edit — open the test case editor.
  • Delete — remove the test case (Draft only, and only your own items if your role is limited to Own).
  • Clone — duplicate the test case.
  • Link — connect the test case to a sprint/milestone and user story or requirement.
  • Download — export when download is enabled for your role.

Search and filters

  • Global Search — type keywords and press Enter to search across the list.
  • Script Status — filter by All Status, Draft, or Published
  • Advanced Filters — build rules on fields such as Test Case ID, Title, Phase, Status, Test Case Type, Requirement ID, Created By, Created Date, Pillar & Epic. Combine rules with AND or OR.

Active filters appear as chips above the list. Your filter choices are remembered while you work in the same project.

Selecting multiple test cases

Use row checkboxes to select one or more test cases or select all on the current page. You can also select all test cases that match your current filters for bulk download.

4. Draft and Published Status

Every test case has a status that controls what you can change.

StatusTypical use
DraftWork in progress. You can edit, delete, and change requirement links (if you have permission).
PublishedReady for test cycles and execution. Edits are restricted until you convert back to Draft.
  • To edit a Published test case, use Convert to Draft & Edit when offered.
  • Test cases can only be deleted in Draft status.
  • De-link any linked requirements from the Test Case and then convert to Draft status.

5. Creating a Single Test Case (AI-Assisted)

When AI is enabled for your organization, you can create one test case at a time using the Add Test Cases button (+). You see this screen

  1. Open the project Test Cases tab.
  2. Click Add Test Cases (the + control). If AI is disabled for your tenant, this option may be unavailable; contact your administrator.
  3. Select a Pillar & Module, Phase and Test Case type
  4. Test Case Type can be : Positive, Negative, Boundary, or Edge.
  5. Phase is optional after which user can enter the prompt.
  6. Click Generate Test Case. Review the generated Test Data and Test Steps.
  7. Save the Test case. It is created in Draft status.

6. Generating Test Cases from Requirements

You can create many test cases at once from requirements already in your project—typically from the Phase tab or from backlog requirement packages.

  1. Select one or more requirements (User Stories or RTM items).
  2. Choose Generate Test Cases from the action menu.
  3.  
  5.  
  6. In the Project Analysis & Test Options dialog, review counts by module or epic.
  7. Select which types to generate: Positive, Negative, Boundary, and/or Edge.
  8.  
  10.  
  11. Click Generate Test Cases and wait for analysis and generation to complete.
  12. On the Results step, review the generated results and Save to add them to the project.

7. Viewing and Editing a Test Case

Open a test case from the list or grid to see the detail editor with these tabs:

  • Overview — ID, type, industry, software, epic/module, title, objective, prerequisites, requirements, and test cycles.
  • Test Data — key/value pairs used during the test.
  • Test Steps — numbered steps with expected results.
  • Comments — team discussion.
  • Attachments — supporting files.
  • Activity — history of changes          .

Required fields include Title and Objective. Save your changes with the save control.

  •  

8. Linking Test Cases to Requirements

Linking connects a test case to the requirement it verifies. This supports traceability and reporting.

  1. From the row menu, choose Link.
  2. Select Requirement (or use the requirement picker).
  3. Save the link.
  4.  

Some projects require every new test case to be linked to a requirement before save. Published test cases must be converted to Draft before you can change links.

9. Import and Export

Download (export)

  • Toolbar Download — export all test cases in the project as a ZIP, or only selected rows.
  • Row Download — export a single test case file (such as Excel) when permitted.
  •  

Import Test Cases ZIP

  • Click Import Test Cases ZIP.
  • Upload a ZIP file containing your test case data.
  • Map spreadsheet columns to SaaSMap fields.
  • Review the import summary (created, updated, skipped, errors) and finish.

10. Import Master Test Cases

If your organization uses the Testcase Library under Settings, you can import pre-built master test case sets into the current project. Use Import Master Test Cases and confirm project and industry context. See more details in the next section for Master test cases or the Test Case library.

11. Testcase Library (Using Templates)

Under Settings, Testcase Library lets administrators maintain reusable master test case sets. Authors can import these into a project instead of building every case from scratch.

See below the Tile to access the ‘Testcase Library’ under Settings.

Clicking on the Tile brings up the details below.

Each entry is an instance of a Test Case library import. Click on the count value to view the list of Test Cases imported in one of the imports. You will see the details below.

You can click on any of the Master Test Case ids and view its details.

Master Test Cases are view only and can be imported into a Project.

To create a single Master Test Case click on the ‘Create New Master Test Case’ button and fill out the details. AI will generate the Test Case based on the selected inputs and the input prompt.

To import a batch of Test Cases into the library start by clicking on the ‘Add Testcase Library’ icon. You see the screen below.

Upload a ZIP file or a .XLSX file with a set of Test Cases in it. Click Next to enter the Mapping details. The application does an analysis of the uploaded ZIP file.

It then prompts the user to enter key values like Industry, Software, Pillar & Epic.

If you have used the file earlier for upload and wish to skip any duplicate test cases from being imported, then keep the ‘Skip Duplicate’ flag selected.

Enter all the fields and Click on the Next button.

This step allows you to map the fields found in the Excel files with the System fields. AI tries to auto map most of the fields. So, any field where you see “Apply AI suggestion” is a field that can be automatically mapped by just clicking on the field in the Left side. The remaining fields can be mapped using drag and drop. After this step click on Import button.

After importing you see the final result.

User can click on the “Download log” button to view the processing details.

12. AI Features

When AI is enabled for your tenant:

  • Add Test Cases — AI drafts test data and steps from requirements and selected test types.
  • Generate Test Cases — AI does bulk generation from multiple requirements.
  • Regenerate — refresh AI content of an existing test case.
  • Master Test Case – AI creates Master Test Case

If AI is disabled, contact your organization administrator. If you exceed AI usage limits, you may see a token limit message—try again later or contact support.

  • Project Dashboard — charts for total test cases, Draft vs Published status, and requirement linkage.
  • Phase — generate test cases in bulk from phase requirements.
  • Backlog — requirements that can feed test case generation.
  • Test Cycles — schedule and run test cases with assigned testers.
  • Defects — log issues found during execution; defects can reference a test case.
  • Settings → Testcase Library — organization-wide master test case te emplates (if your subscription includes it).

14. Quick Reference Workflow

A typical end-to-end flow:

  1. Define requirements in Backlog or Phase (including from SOW or transcript if used).
  2. Create a Phase and import verified requirements into a Phase.
  3. Generate or create test cases from requirements in a Phase.
  4. Review and edit in Draft; then Publish.