#Test Cases FAQs - Management Questions
This section answers common questions about creating, organizing, and maintaining test cases in Hawzu.
#What is a test case?
A test case defines what to test, how to test it, and what outcome to expect.
A typical test case includes:
- A clear title
- Description or context
- One or more test steps
- Expected results
- Optional prerequisites, parameters, and shared steps
Test cases live inside a project’s repository.
#How do I create a test case?
To create a test case:
- Navigate to the Repository
- Click Add in the sidebar header
- Select Add Test Case
- Enter the test case details (title, steps, expected results, etc.)
- Choose a parent folder
- Click Create
For a detailed walkthrough, see Creating Test Cases.
#What fields are required when creating a test case?
Only the Title is mandatory.
However, it’s strongly recommended to include:
- Description
- Test steps
- Expected results
- Prerequisites (if any)
Well-documented test cases reduce execution errors and rework.
#Can I edit a test case after creating it?
Yes.
If you have edit permissions:
- Open the test case
- Click Edit
- Make changes and save
Edits do not affect historical execution results.
#What is the difference between a test case and a test suite?
- Test Case: A single test with steps and expected results
- Test Suite: A logical collection of test cases used for execution
Test suites are used primarily for test execution planning, not storage.
Test cases are stored in folders inside the repository and can belong to multiple test suites.
#How should I organize test cases?
You can organize test cases using:
- Folders – Hierarchical structure inside the repository
- Test Suites – Logical groupings for execution
- Tags – Flexible labels for search and filtering
- Custom Fields – Project-specific metadata
For recommended strategies, see Best Practices.
#Can I import test cases from Excel?
Yes.
You can import test cases using Excel files from the Repository.
The import supports:
- Mapping columns to test case fields
- Steps and expected results
- Priority, severity, and other fields
Refer to Import & Export for supported formats.
#What are shared steps?
Shared steps are reusable step blocks that can be referenced in multiple test cases.
They help:
- Reduce duplication
- Keep common flows consistent
- Simplify maintenance
Updating a shared step updates it everywhere it’s used.
#Can I duplicate or copy a test case?
Yes.
You can duplicate test cases to:
- Create variations
- Speed up test case creation
- Reuse similar flows
The duplicated test case is independent and can be edited separately.
#Are test cases tied to a specific project?
Yes.
Test cases are project-scoped and cannot be moved between projects.
If similar test cases are needed in multiple projects, use:
- Shared steps
- Parameters
- Import/export workflows
#Still have questions?