Test Cases

Author test cases with ordered steps, sync them to your PM tool, group them into plans, link them to the work they verify, and let the project AI use them as context.

Each Fabric project has a Test Cases tab where you author test cases the way you would in Azure DevOps Test Plans or TestRail — ordered Action + Expected steps, a state, a priority, an owner, and tags. From there you can sync cases to your project-management tool, group them into plans, link them to the features and bugs they verify, and draft new cases from a feature's acceptance criteria with AI.

In Fabric, each case carries a TC-001 identifier (per project) and each plan a TP-001. A case has a lifecycle state — Draft, Ready, or Closed — and a priority from Low to Critical.

Test Cases are authored, not run. This release is about writing and organizing test cases and keeping them in sync with your PM tool — there is no test-run engine, and no pass/fail results yet. A case can be marked Ready, but Fabric does not execute it.

Open the tab

In a project, open the Test Cases tab. It has two segments:

Cases — the list of test cases, with search and filters (state, priority, tag). Each row shows the TC-NNN identifier, title, status, priority, step count, any linked feature, and tags.
Plans — your test plans (TP-NNN, name, state, number of cases).

The tab works in both personal and organization projects; cases never leak across that boundary.

Create a case with steps

Click New

On the Cases segment, click New. The case editor slides out from the right.

Fill in the basics

Give the case a title, an optional description (use it for preconditions or a summary), and set its state, priority, automation status, owner, and tags.

Add ordered steps

In the Steps editor, add rows of Action and Expected result. Use the row controls to insert, delete, and reorder steps — by dragging the handle or with the keyboard. The order you set is the order the case is read and synced in.

Save

Click Save. The case gets its next TC-NNN identifier and appears in the list. You can reopen it any time to edit fields or steps.

Clone to reuse a case. Use Clone on a case to copy it — fields and steps included — as a new DRAFT case. A clone is local: it starts unlinked from any PM tool.

Link a case to a feature

Connect a case to the work it verifies so coverage shows from both sides.

Open the case and find Linked work items

In the case editor, use the Linked work items control to search your project's features and bugs.

Pick a feature and (optionally) an acceptance criterion

Select the feature or bug. If the case verifies one specific acceptance criterion, set Covers AC N to record which one.

See coverage on the feature

The feature now shows a read-only Tested by N cases line, so anyone looking at the feature can see it has test coverage. Remove a link from either side at any time.

Build a plan

A test plan is a flat collection of cases — no nested suites.

Create the plan

On the Plans segment, click New plan and give it a name. It gets a TP-NNN identifier.

Add cases

Open the plan and add cases with the picker. Reorder them by drag or keyboard, and give a case an optional section label to group it within the plan.

Reuse cases across plans

The same case can belong to many plans — adding it to a second plan does not move it out of the first. A case can appear only once per plan.

Sync to your PM tool

Test cases sync through the same connection your features use — Azure DevOps, Jira, GitLab, or Fizzy — so there is nothing new to connect. (See Project Management Sync for connecting a PM tool to your project.)

Turn on auto-sync (optional)

In the case editor, toggle Auto-sync to push the case to your PM tool every time you save it.

Sync now

Click Sync now to push the case immediately, or pull updates from the linked work item. A status chip shows whether the case is Connected, needs to Reconnect, or hit a conflict.

Resolve drift

If both Fabric and the tool changed the case, the chip shows a Conflict. Use Retry to push again, or Dismiss to clear the failure once you've handled it.

Your steps travel with the case — on every tool. When a case syncs, its ordered Action/Expected steps are written into the work item's description, so they show up in any PM tool. On Azure DevOps, the steps also populate the work item's native Steps field, so they render as a proper step grid.

Generate with AI

Let Fabric draft cases from a feature's acceptance criteria as a starting point.

Click Generate with AI

On the Cases segment, click Generate with AI and pick a feature.

Review the drafts

Fabric reads the feature's description and acceptance criteria and drafts editable cases with titled, ordered steps. Every generated case is created as Draft and linked to that feature.

Edit and promote

Open each draft, refine the steps, and move it to Ready when it's good. AI never finalizes a case — it only gives you a head start.

Every case is available to the project AI. Each case you author is mirrored into the project's knowledge so the AI assistant takes it into account when it helps your team — the same way it considers your documents and decisions. Deleting a case removes it from that context.