# NIZU Live Testing  Connected Apps and Modules

> How NIZU Live Testing connects to other NIZU modules: Projects, Tasks, Team Management, Support Tickets and Roles and Permissions (Apps: Live Testing)

- Page: https://dashboard.nizu.io/knowledge_base/view/146-nizu-live-testing-connected-apps-and-modules
- Part of: [Knowledge base](https://dashboard.nizu.io/knowledge_base/llms.txt) on NIZU — https://dashboard.nizu.io/llms.txt
- Updated: 2026-10-25T11:50:03Z

## NIZU Live Testing Connected apps

NIZU Live Testing is not a standalone island. It reuses and connects to the modules already in your NIZU workspace, which is what makes the testing workflow flow end to end.

### Projects

Projects are the centre of the app. Every test suite, cycle, defect and regression is scoped to a project. Each project is bound to one product, and a **Testing** tab is added to the project details page so you can see and start that project's test cycles without leaving the project. The cycle view links back to the project.

### Tasks

When a test case fails and is saved, NIZU Live Testing automatically creates a **task** in the same project. The task description is auto-generated from the failure (the case, severity, reproducibility, steps, expected vs actual result) and includes a link back to the test cycle. The task is linked to the defect, opens in a popup directly from the cycle, and re-running the same failure updates the existing task instead of creating duplicates.

A test case can also be **linked to an existing developer task** when it is written. If that case later fails or regresses, the generated bug task is **assigned to the owner of the linked task** automatically so the fix lands with the developer responsible for the underlying work. The suite's case list also shows each case's author and its linked task and owner, giving a project manager clear accountability.

### Team Management

Testers are your existing project members there is no separate tester registry. Each team member can pick a personal pixel-art racing avatar from their own profile preferences, which then appears in the live race.

### Support Tickets

A defect can be linked to a NIZU support ticket by id, so a bug found in testing can be tied to the customer-facing ticket that reported it.

### Roles & Permissions

The app plugs into the standard NIZU role system. Granular permissions (access, manage products, manage suites & cases, execute, file defects, sign off, override gate) are added to the role editor. They are off by default, so the app is automatically hidden from roles such as Sales or Support until you grant access.

### Settings

The app adds its own page under **Settings → Live Testing** for the pass-rate threshold and the live-race refresh interval, and a settings link from the Apps management screen.

### Files

Step attachments, expected-result attachments and defect evidence (screenshots, recordings, documents) are stored in your workspace's file storage and served securely through the app.