#Getting Started with Hawzu
Hawzu helps teams organize testing work, run test cases, track defects, and review product quality from one workspace.
Use this section when you are new to Hawzu and want the fastest path from account access to useful testing work.
#How Hawzu Is Organized
Hawzu starts with a workspace. A workspace contains projects, users, groups, roles, integrations, shared configuration, and workspace-level settings.
Inside a workspace, a project represents an application, product, or testing area. Project work can include repository test cases, requirements, releases, executions, test runs, defects, labels, custom fields, shared steps, parameters, and Observatory dashboards.
#Core Areas
The main Hawzu areas are:
- Workspaces: choose assigned workspaces, star frequent workspaces, and set a default workspace.
- Projects: open project cards and manage project-level testing work.
- Repository: create and organize test cases.
- Requirements: track requirement coverage and traceability.
- Test Suites: group test cases for reuse in test selection.
- Releases: plan release milestones and run release-bound executions.
- Executions and Test Runs: record test results, assignments, notes, attachments, and defects.
- Defects: create, triage, link, and review product issues.
- Labels: categorize test cases, requirements, releases, and other supported work.
- Observatory: build project analytics panels and charts.
- Integrations: connect external issue tools and Slack notifications.
#Recommended First Steps
- Open your first workspace.
- Create your first project.
- Add your first repository test case.
- Run a standalone test run or create a release execution.
- Create or link defects when testing finds issues.
- Review progress and quality insights.
#Next Steps