How to Create Test Cases
Test cases define what to test, how to test it, and what outcome is expected. In Hawzu, test cases are created inside a project repository and can include metadata, preconditions, and structured test steps.
Accessing Test Case Creation
To create a new test case:
- Open a project
- Navigate to Repository
- Click Add in the folder sidebar
- Select Add Testcase
The Create Testcase screen opens in draft mode.
Test Case Information
This section captures basic metadata about the test case.
Title (Required)
A clear, descriptive title that explains what is being tested.
Example:
Verify user can log in with valid credentials
Description
Optional additional context about the test case.
Use this to explain:
- Purpose of the test
- Scope or assumptions
- Any special notes for execution
Properties
Properties help classify and organize test cases.
Priority
Indicates how important the test case is.
Common values:
- High
- Medium
- Low
Severity
Indicates the impact if the test case fails.
Common values:
- Blocker
- Critical
- Moderate
- Minor
- Enhancement
Test Type
Defines the nature of testing.
Examples:
- Functional
- Regression
- Smoke
- Sanity
- Exploratory
- Security
- Integration
- Performance
- UI / UX
Parent Folder
Select where the test case should live in the repository hierarchy.
If no folder is selected, the test case remains at the root level.
Automation Status
Indicates the automation state of the test case.
Examples:
- Manual
- Automated
- To Be Automated
- Automation In Progress
Requirements
Link the test case to one or more requirements.
This enables traceability between requirements and test coverage.
Tags
Add tags to help with searching and filtering.
Type a tag and press Enter to add it.
Custom Fields
Custom fields configured for the project appear here.
- Fields vary by project
- Required fields must be filled before creation
- Used to capture project-specific information
Preconditions
Preconditions describe what must be true before executing the test case.
To add a precondition:
- Click Add Precondition
- Enter the prerequisite using the editor
Examples:
- User is logged in
- Test data exists
- Application is running
Test Steps
Test steps define how the test should be executed.
Hawzu supports three step modes.
Step Modes
Multiple (Default)
Use structured steps with expected results.
Best for detailed, manual test cases.
Each step includes:
- Action
- Expected output
Single
Use a single, free-form step block.
Best for:
- Simple test cases
- High-level verification scenarios
Gherkin
Write test cases using Gherkin syntax.
Best for:
- BDD workflows
- Automation-friendly scenarios
Each Gherkin line is treated as a step.
Adding Steps
To add steps:
- Click Add a step for manual steps
- Click Add shared step to reuse predefined steps
Shared steps help maintain consistency across test cases.
Creating the Test Case
To create the test case:
- Review required fields
- Ensure required custom fields are filled
- Click Create
The test case is saved and appears in the selected folder.
Editing Test Cases
To edit a test case:
- Open the test case from the repository
- Click Edit
- Update fields or steps
- Save changes
Edits apply immediately.
Best Practices
- Use clear, action-oriented titles
- Choose the appropriate step mode
- Keep steps concise and testable
- Use shared steps for repeated actions
- Link requirements where applicable
- Keep automation status updated
- Review test cases periodically
Next Steps
- Organize test cases using folders
- Group test cases using Test Suites
- Execute test cases in Test Runs