Testing & QA

Once a PR is merged, the task enters the testing pipeline. Konductro supports configurable test phases — internal QA, client UAT, or both — with automatic tester assignment and structured checklists.

Internal QA

Auto-assignment

When a PR is merged, the task transitions to internal_qa and a tester is auto-assigned. Assignment follows a simple rule: the tester with the fewest active QA tickets gets the next one. The developer who built the feature is excluded from assignment if other testers are available.

Acceptance criteria become a checklist

The acceptance criteria from the original story are transformed into a structured test checklist. Each criterion becomes a line item the tester evaluates: pass or fail, with space for notes.

Konductro also generates functional test instructions — step-by-step guidance a non-technical tester can follow to verify the feature.

Pass or fail

All pass — the task moves to the next configured test phase (Client UAT or Done)
Any fail — the task moves to fix_required and is auto-reassigned to the original developer

Fix Required

When a test fails, the task is automatically reassigned to the developer who built it. A bug/fix task is created with the failure notes attached. The developer fixes the issue, creates a new PR, and the task cycles back through QA.

This loop continues until all acceptance criteria pass. No manual reassignment, no lost context.

Client UAT

For projects that require client sign-off, UAT runs after internal QA using the same testing framework. The client sees the same acceptance criteria checklist and follows the same pass/fail process.

Same structured checklist as internal QA — consistent experience for the client
Failures follow the same fix-and-retest cycle
UAT is optional and configured per project

Configuring Test Phases

Test phases are set in Project Settings. Options:

Configuration	Behaviour
Internal QA only	Merged PRs go through internal QA, then Done
Internal QA + Client UAT	Internal QA first, then Client UAT, then Done

The Full Status Flow

in_progress → pr_open → merged → internal_qa → client_uat → done
                                      ↓                ↓
                                 fix_required ←────────┘
                                      ↓
                                 in_progress (fix cycle)

Every status transition is automatic. The sprint board and task detail update in real time. Notifications fire on assignment changes — via in-app alerts and Teams DM if configured.