#Project Overview
A project represents a focused testing space within a workspace.
It is where day-to-day testing activities such as managing test cases,
executing test runs, and tracking defects take place.
Each project is isolated from others and has its own data, configuration,
and access control.
#Project vs Workspace
Understanding the difference between a workspace and a project helps
you navigate Hawzu effectively.
#Workspace
- Top-level container
- Used for administration and shared configuration
- Manages users, roles, custom fields, parameters, integrations, and shared steps
#Project
- Lives inside a workspace
- Used for execution and testing workflows
- Contains test cases, test runs, and defects
#Accessing a Project
To access a project:
- Open a workspace from the Workspaces page
- On the Projects page, click a project card
- You will enter the project and see the project overview
Project URLs follow this pattern:
/workspace/:workspaceId/project/:projectId
#Project Navigation
When you open a project, a left side panel appears.
This panel provides access to all project features.
The available sections include:
- Overview – Project summary and high-level status
- Observatory – Analytics, insights, and trend visualizations
- Repository – Test cases and test organization
- Requirements – Product requirements and traceability
- Test Suites – Logical grouping of test cases
- Releases – Release and version tracking
- Test Runs – Test execution and result tracking
- Defects – Defect and issue management
This side panel is available only inside projects and does not appear
at the workspace level.
#Core Project Features
Each project provides a set of features accessible from the left side panel.
These features support the complete testing lifecycle — from authoring tests
to execution, tracking, and analysis.
#Overview
The Overview page gives a quick snapshot of your work within the project.
It focuses on user-specific context, helping you resume work efficiently.
You can see:
- Your work items that need attention
- Recently accessed test cases, test runs, or defects
- High-level project context
The content shown may vary based on your role and recent activity.
#Observatory
Observatory provides insights and analytics at the project level.
It helps teams understand testing progress, trends, and overall quality
by visualizing data collected from test cases, test runs, and defects.
Use Observatory to:
- Analyze testing trends
- Review execution progress
- Gain visibility into project health
#Repository
The Repository is where test cases are authored and maintained.
You can:
- Create and manage test cases
- Organize test cases using folders
- Maintain structured test documentation
- Use shared steps and parameters where applicable
The Repository acts as the source of truth for all test cases in the project.
#Requirements
The Requirements section is used to manage product or feature requirements
and link them to test cases.
You can:
- Create and manage requirements
- Link test cases to requirements
- Track requirement coverage
- Improve traceability between requirements and testing
This helps ensure that all requirements are validated through testing.
#Test Suites
Test Suites allow you to group test cases logically for execution
and organization purposes.
You can:
- Create test suites for specific scenarios or features
- Group related test cases
- Use test suites when planning or executing test runs
Test Suites help structure large test repositories
without duplicating test cases.
#Releases
Releases are used to group and track testing activities
around a specific version or milestone of the product.
A release can contain multiple executions, such as:
- Sanity testing
- Smoke testing
- Regression testing
- UAT or other execution cycles
Releases provide a high-level view of testing progress
for a version, without directly owning or linking individual test runs.
Use Releases to:
- Represent product versions or milestones
- Track quality status at a release level
- Organize testing efforts conceptually by version
#Test Runs
Test Runs represent individual test execution cycles.
Test Runs are always standalone executions
and are not tied to any release.
You can use Test Runs for:
- Sanity, smoke, or regression testing
- Ad-hoc or exploratory testing
- Hotfix or patch verification
- One-off validation efforts
In a Test Run, you can:
- Select test cases or test suites
- Execute tests and record results
- Assign execution to team members
- Track execution progress and outcomes
Test Runs are the fundamental unit of execution in Hawzu
and exist independently of releases.
#Defects
Defects represent issues identified during testing.
You can:
- Create defects manually or from failed test cases
- Track defect status, priority, and severity
- Link defects to test cases or test runs
- Monitor resolution progress
Defects help teams track and resolve issues discovered during execution.
#Project Members & Roles
Projects have their own access control.
You can:
- Assign workspace users to a project
- Grant project-specific roles
- Control what actions users can perform within the project
Project roles are scoped to the project and do not affect
access to other projects.
#Best Practices
When working with projects:
- Use one project per application or major feature
- Keep project names and codes meaningful
- Organize test cases using folders
- Reuse shared steps for common workflows
- Assign roles based on responsibility
- Keep test cases and defects up to date
#Next Steps
After entering a project, you can:
- Organize test cases in the Test Repository
- Create and execute Test Runs
- Track Defects during execution
- Configure Project Settings