QA Issues

QA issues

A QA issue (QI-0001) is a defect found by testing. It's born from a failed or blocked execution, and it carries everything a developer needs to reproduce the problem, without a single "works on my machine" conversation.

Reporting one

On a failed or blocked execution, click Report QA Issue (or the ⚑ flag on a failed step). The Create or Link QA Issue form opens, already filled in:

• Title: built from the case and the failure, e.g. [QA Issue] [TC-0007] Valid login - Step #2: Login button does nothing.
• Priority: taken from the test case priority (Critical → Urgent, High → High, Low → Low); otherwise High for failures.
• Description: a full report, generated for you, and editable:
  • the test case, Development, environment, result, plan, run, tester and date;
  • Failure details: the failed step, the expected outcome, the observed behaviour, your notes;
  • preconditions and test data;
  • Steps to reproduce: every step with its expected result, status and actual result;
  • acceptance criteria, postconditions and the list of evidence.
• Copy attachments: the evidence of the execution and of the failed step is copied to the issue (skipping files it already has).

Avoiding duplicates

If open QA issues already exist for the same test case, Studio warns you and lists them:

Open QA Issues already exist for this Test Case. Check the list below and link the execution to one of them instead of creating a duplicate.

Choose Link an existing QA Issue, pick it, and the execution is added to that issue instead. One bug, many executions that show it. Much tidier.

flowchart TD
    F[Failed or blocked execution] --> W[Create or Link QA Issue]
    W --> D{Open issues for<br/>the same test case?}
    D -- yes --> L[Link to existing issue]
    D -- no --> C[Create new issue<br/>title + report + priority]
    L --> E[Evidence copied · activity logged on both]
    C --> E

Loading

The life of an issue

stateDiagram-v2
    direction LR
    [*] --> Open
    Open --> InProgress: Start
    Open --> Resolved: Resolve
    InProgress --> Resolved: Resolve
    Open --> Cancelled: Cancel
    InProgress --> Cancelled: Cancel
    Resolved --> Open: Reopen
    Cancelled --> Open: Reopen
    state "In Progress" as InProgress

Loading

An issue has an assignee, a priority (Low, Normal, High, Urgent) and shows its test context: the execution it came from, the related test case, run and plan, and every linked execution. Its activity log records who changed what.

Rules worth knowing

• An issue and all its executions belong to the same Development.
• Testers can report issues only on executions they can see, which means their own runs.
• Reporting works on completed runs too: only the issue is written, the run stays untouched.
• Issues can be traced to what they affect, like any other record.

Finding issues

• QA issues in the sidebar: open issues first, filter by state.
• The Quality tab of a Development: its open issues.
• My test runs: the issues assigned to you.
• Each execution lists its QA issues, and runs show how many each execution has.