triage

QA failure analysis evaluates screenshots, logs, network evidence, and run artifacts to determine likely root causes and generate structured issue reports. It classifies severity and updates result status fields to keep the triage workflow organized.

Triaging blocked and partial QA test results involves grouping findings from the run folder and classifying their severity. This process separates true product defects from confusing but technically working behavior, creating actionable follow-up notes.

UX risk triage separates true product defects from confusing but technically working behavior that could still hurt users. It reviews run artifacts and evidence files to classify whether findings represent actual failures or usability hazards.

To classify severity and review root causes, you need to provide the run folder, qa-results.json, and related evidence files. These inputs allow the system to analyze screenshots, logs, and network evidence to write issue reports.

Yes, the triage process updates qa-results status fields automatically after analyzing failures. It writes structured failure reports and maintains the triage state directly inside the current run folder.

Automated issue reporting turns raw QA failures, blocked checks, and UX risks into clear reports so teams can quickly understand what went wrong. Manual review lacks the structured grouping, severity classification, and state updates needed for organized workflows.