Hawzu Docs

Hawzu Documentation

Go to App
getting-startedtutorial

Quick Start Guide - Test Case Management Setup

This guide will help you get started with Test Case Management in minutes. You’ll learn how to:

  1. Create a project that will contain all your artifacts
  2. Create a test suite with test cases to store test details
  3. Create a test run to define which tests should be executed
  4. Create a defect based on failed test results

Prerequisites

Before you begin, ensure you have:

  • An active account (sign up at app.hawzu.com)
  • Access to your workspace
  • Basic understanding of test case management concepts

Projects

Projects are workspaces to keep all parts related to a specific application together. Let’s create your first project.

To create a project:

  1. Open https://app.hawzu.com and log in. As a result, the “Projects” page is shown.

  2. Click on the button “Create New Project”. A popup “Create New Project” is shown. Fill in the name and description. Notice that the field “Project Code” is automatically filled in with the first letters from the project name. You can edit this code if needed.

    You can also select who gets access to the project:

    • Public: All users in the workspace have access to the project
    • Private: Only selected users have access to the project

  3. Click on the button “Create Project”. As a result, the new project is created and its Test Repository page is shown.

Congratulations! You have created a project and now it’s time to add some test suites and test cases.

Test Suites

Test Suite is similar to a folder where you store your test cases organized by sections and subsections. You can create several test suites. For example, Functional and Non-Functional test suites or anything else that should be treated as a separate group of tests.

To create a test suite:

  1. On the page “Repository”, click on the button “Create new suite” or click on ”+ Suite” next to the search bar on the top.

  2. As a result, the popup “Create Suite” is shown. Fill in the suite name and optionally other fields. To create a test suite, click on the button “Create”.

  3. As a result, the repository now displays your newly created Suite.

Now, we can add test cases, so let’s create our first test case.

Test Cases

A test case contains all the details about your test. Only the title is enough to create a Quick test case. For a more detailed test case, you can define prerequisites, steps, expected and actual results, etc.

Quick test case

  1. On the page, under your suite, click on the link ”+ Create quick test”.

  2. As a result, the cursor will start blinking on the page and you can start typing the title. As soon as you are done, click Enter to save the test case. As a result, a new test case under the suite is shown with ID and a title.

This is the fastest way to add a test case. Let’s see how to create a more detailed one.

Detailed test case

  1. On the main repository page, click on the button ”+ Case”.

  2. As a result, a new page “Create test case” is shown. Let’s fill in the most important fields:

    Title: describes what is being tested by the test case

    Status: denotes the status of the case itself (Draft, Ready, etc.)

    Suite: which suite the test case belongs to

    Priority: how important is this test case during test execution? (Low, Medium, High, Critical)

    Severity: what is the impact on your app’s quality status if this test case fails? (Low, Medium, High, Critical)

    Is Flaky: determines if the test case is flaky (unstable results)

    Automation Status: denotes if the test case is automated, to be automated, or not automated

    Pre-conditions: the prerequisites for your test

    Steps: list of actions and expected results after each action

  3. To save a test case, click on the button “Save”. As a result, the page “Test repository” is shown with a new test case.

We have added our test cases. Let’s execute them in a new test run.

Test Run

Test Run represents a set of test cases to be executed on a specific app build along with the status of their execution. You can have multiple versions of your app (e.g., iOS and Android), and for each version, you can perform the same test cases in separate Test Runs.

To create a test run:

  1. Navigate to the “Test Runs” section and click the “Start New Test Run” button.

  2. In the configuration form, fill out the following fields:

    Run Title: the name of your test run (pre-filled with the current date, but you can change it)

    Description: additional details about the test run

    Environment: define in which environment the test run should be performed (e.g., testing, staging, production)

    Milestone: select which Milestone the Test Run is tied to

    Default Assignee: choose whether all Test Cases within the Test Run should be automatically assigned to a specific teammate

    Tags: assign any tags that you have used previously, or create new ones

    Test Cases: pick and choose specific test cases from the repository

  3. Click “Create Test Run”. As a result, the new Test Run is created and displayed in the Test Runs view.

With the new Test Run configured, you will now see it in the Test Runs view with a summary showing:

  • Time: how much time has been spent on performing Test Cases in this run
  • Status: summary of test cases per status (passed, failed, skipped, blocked, invalidated, or untested)
  • Environment: the environment of the run

Defects

In this section, let’s see how a new defect can be reported for a failed test case.

To create a defect from a test run:

  1. During a test run, mark a Test Case as “Failed”.

  2. You will be prompted to a Run result window, where you can:

    • File additional comments
    • Record how much time was spent on test case execution
    • Attach files
    • Create/attach a defect

  3. With the “Create Defect” checkbox checked, you will be prompted to fill out Defect properties:

    • Defect Title: descriptive title for the defect
    • Severity: impact level of the defect
    • Custom Fields: any custom fields you’ve created for defects
    • Integration: opt to send the connected issue to integrated third-party software systems

  4. Click “Create Defect”. As a result, a new Defect is created and can be found under the “Defects” section and the “Defects” tab of your test run.

What’s Next?

Now that you’ve completed the quick start guide, you can:

Was this page helpful?