Getting Started

Qase is a test management platform where you define test cases, execute them in runs, and track defects.

This tutorial walks you through the core workflow:

Before diving in, read Qase Concepts to understand how projects, suites, cases, plans, runs, and defects relate to each other. That mental model will make everything below click faster.

A project is the top-level container for all your testing artifacts — cases, runs, defects, and integrations. You'll typically create one project per product.

From the Projects page, create a new project. Give it a meaningful name — the project code auto-generates from the name but can be edited.

The code becomes a permanent prefix for all test case IDs (e.g., PROJ-42), so pick something short and recognizable.

Choose Public if everyone in the workspace should have access, or Private to control membership explicitly. For most teams starting out, public is fine — you can tighten access later.

Your test repository is organised by suites (folders) containing test cases. Suites can nest to reflect your product's structure — Authentication > Login > Social Login, for example.

Suites are organizational — they group related cases but don't affect execution. Create suites that mirror how your team thinks about the product's feature areas.

From the repository view, create a new suite. A name is all that's required; descriptions and parent suites are optional.

There are two ways to add cases:

Quick cases are the fastest path. Use the inline "+create quick test" option under any suite, type a title, and press Enter. This is ideal for capturing test ideas during planning — you can fill in details later.

Detailed cases let you define everything up front: preconditions, steps with expected results, priority, severity, automation status, and custom fields. Use the "+ Manual Test" button to open the full editor.

At minimum, a useful test case has:

Don't over-document at this stage. Start with titles and priorities for your critical paths, then add step-level detail to cases that other team members will execute.

A test run is where cases meet reality. You select which cases to execute, assign them to team members, and record pass/fail results.

The fastest way to run tests: select cases directly in the repository and hit ▶️ Run . Qase creates a run with those cases immediately. Use this for ad-hoc verification.

For structured testing, navigate to Test Runs and start a new run. A standard run lets you configure:

Open a test run and work through each case. For each one, record a result:

You can add comments, attachments, and time spent to any result. Step-level results let you pinpoint exactly where a failure occurred.

When a test case fails, Qase prompts you to create a defect — or link to an existing one if the bug is already known.

When you mark a case as failed during a run, check the defect option in the result dialog. The defect inherits context from the case and run. If you have an issue tracker integration (Jira, GitHub, Linear, etc.), you can push the defect to an external issue in the same step.

You can also create defects outside of a run from the Defects section. This is useful for bugs discovered during exploratory testing or reported by users.

You've completed the core workflow: project → cases → run → defects. From here: