Hawzu Docs

Hawzu Documentation

Go to App
projectrepositorytest-cases

How to Create Test Cases - Step by Step Guide

Test cases are the foundation of your test repository. They document what to test, how to test it, and what results to expect. This guide covers creating comprehensive test cases with all necessary details.

Accessing Test Case Creation

To create a new test case:

  1. Navigate to the Repository page.

  2. Click the “Add” button in the sidebar header.

  3. Select “Add Testcase” from the dropdown menu.

  4. Alternatively, use the keyboard shortcut Ctrl+K (or Cmd+K on Mac).

  5. As a result, the “Create Testcase” modal will open.

Test Case Creation Form

The test case creation form is divided into several sections:

Basic Information

Title (Required):

  • Enter a descriptive test case title
  • Should clearly indicate what is being tested
  • Example: “Verify user can login with valid credentials”

Description:

  • Add a detailed description of the test case
  • Explain the purpose and context
  • Use rich text formatting for clarity

Parent Folder:

  • Select the folder where the test case should be placed
  • Choose “Root” for uncategorized test cases
  • The folder determines the test case’s location in the hierarchy

Test Case Properties

Type:

  • Select the test case type:
    • Functional: Tests specific functionality
    • Regression: Tests to ensure existing features still work
    • Smoke: Quick tests to verify basic functionality
    • Integration: Tests interactions between components
    • Performance: Tests system performance
    • Security: Tests security aspects
    • Usability: Tests user experience

Priority:

  • Set the priority level:
    • Critical: Must be executed immediately
    • High: Important, should be executed soon
    • Medium: Normal priority
    • Low: Can be executed when time permits

Severity:

  • Set the severity level if the test fails:
    • Critical: System unusable
    • High: Major functionality broken
    • Medium: Some functionality affected
    • Low: Minor issues

Automation Status:

  • Choose the automation status:
    • Manual: Test case is executed manually
    • Automated: Test case is automated

Tags:

  • Add tags for categorization and filtering
  • Separate multiple tags with commas
  • Use consistent tag naming conventions
  • Examples: “login”, “api”, “ui”, “critical-path”

Requirements:

  • Link the test case to product requirements
  • Select from available requirements
  • Multiple requirements can be linked
  • Enables requirement traceability

Preconditions

Preconditions specify what must be true before executing the test:

  1. Click “Add Precondition” to add a new precondition.

  2. Enter the precondition description using the rich text editor.

  3. You can add multiple preconditions.

  4. Preconditions are displayed in order.

Example Preconditions:

  • “User must be logged in”
  • “Test data must be set up”
  • “Application must be running”

Test Steps

Test steps define the actions to perform and expected results:

  1. Click “Add Step” to add a new test step.

  2. Fill in the step details:

    Step Description:

    • Describe the action to perform
    • Use clear, actionable language
    • Example: “Enter username in the username field”

    Expected Result:

    • Describe what should happen
    • Be specific and measurable
    • Example: “Username field displays the entered text”

  3. Use the rich text editor for formatting:

    • Bold, italic, underline
    • Lists and numbered lists
    • Code blocks
    • Links

  4. Reorder steps by dragging and dropping.

  5. Delete steps using the delete icon.

Using Shared Steps:

  1. Click “Insert Shared Step” in a step.

  2. Select a shared step from the list.

  3. The shared step content is inserted into the test case.

  4. Updates to shared steps automatically reflect in test cases.

Step Attachments:

  1. Click the attachment icon in a step.

  2. Upload images or files.

  3. Attachments are displayed with the step.

Custom Fields

Custom fields are project-specific fields configured for your project:

  1. Fill in any required custom fields.

  2. Custom fields vary based on project configuration.

  3. Common custom fields include:

    • Test Environment
    • Test Data
    • Related Issues
    • Test Owner

Attachments

Add files and images to the test case:

  1. Click “Add Attachment” in the attachments section.

  2. Upload files or images:

    • Supported formats: Images (PNG, JPG, GIF), Documents (PDF, DOCX)
    • Maximum file size varies by configuration

  3. Attachments are stored with the test case.

  4. Use attachments for:

    • Screenshots
    • Test data files
    • Reference documents
    • Diagrams

Creating the Test Case

To create the test case:

  1. Review all sections to ensure completeness.

  2. Verify required fields are filled.

  3. Click “Create Testcase” to create the test case.

  4. As a result:

    • The test case is created in the selected folder
    • It appears in the test case list
    • You can view, edit, or execute it immediately

Editing Test Cases

To edit a test case:

  1. Click on the test case in the test case list.

  2. The test case view modal opens.

  3. Click the “Edit” button.

  4. Update any fields or properties.

  5. Click “Save Changes” to update the test case.

Note: Changes are saved immediately. You can also use bulk edit to update multiple test cases at once.

Cloning Test Cases

To clone a test case:

  1. Right-click on the test case in the list.

  2. Select “Clone Testcase” from the context menu.

  3. Optionally enter a new title for the cloned test case.

  4. Click “Clone” to create a copy.

  5. As a result:

    • A new test case is created with the same content
    • You can modify the cloned test case independently
    • Useful for creating similar test cases

Best Practices

When creating test cases:

  1. Clear Titles: Use descriptive titles that indicate what is being tested
  2. Detailed Descriptions: Provide context and background information
  3. Specific Steps: Write clear, actionable test steps
  4. Expected Results: Define measurable expected results
  5. Preconditions: List all necessary preconditions
  6. Use Tags: Add relevant tags for easy filtering
  7. Link Requirements: Connect test cases to requirements for traceability
  8. Attachments: Include screenshots or reference documents when helpful
  9. Shared Steps: Use shared steps for common sequences
  10. Review: Review test cases before marking them complete

Test Case Properties Summary

Each test case includes:

  • ID: Unique identifier automatically assigned
  • Title: Test case title
  • Description: Detailed description
  • Type: Test case type (Functional, Regression, etc.)
  • Priority: Priority level (Critical, High, Medium, Low)
  • Severity: Severity level (Critical, High, Medium, Low)
  • Automation Status: Manual or Automated
  • Tags: Categorization tags
  • Requirements: Linked product requirements
  • Preconditions: Prerequisites for execution
  • Steps: Test steps with expected results
  • Custom Fields: Project-specific custom fields
  • Attachments: Files and images
  • Created Date: When the test case was created
  • Created By: User who created the test case
  • Updated Date: Last modification date
  • Updated By: User who last updated the test case

Next Steps

Was this page helpful?