1Total requirements
1Covered requirements
6Tests executed
5Passed
1Failed
83.3%Pass rate
1Open defects
No-GoRecommendation

## Executive Summary

The create-run form successfully creates a history row, but the acceptance scope is not fully met because the newly submitted run did not expose Report or Logs links during the QA observation window.

## Search Tables

## Requirement Reference Table

Requirement | Source | Text | Feature/Page | Coverage | Execution | Test Cases | Defects
--- | --- | --- | --- | --- | --- | --- | ---
REQ-001 | qaagent-functional-pm-requirements.md line 3 | User can submit a QA run from the web form and see it in history. | QA Agent web dashboard: login, create run form, test run history | Covered | Fail | TC-001, TC-002, TC-003, TC-004, TC-005, TC-006 | DEF-001

## Test Cases and Execution Results

TC | Req | Title | Steps Summary | Expected | Actual | Status | Defect | Evidence
--- | --- | --- | --- | --- | --- | --- | --- | ---
TC-001 | REQ-001 | Invalid password is rejected before a user can access QA run creation | 1. Open QA Agent. 2. Enter an invalid admin password. 3. Select Login. | The product does not open the dashboard and shows a clear error with a path to try again. | Invalid password. Try again | Pass | — |
TC-002 | REQ-001 | Authorized user can reach the dashboard and understand where to create and review runs | 1. Log in. 2. Review the dashboard. 3. Confirm the create-run form and history table are visible. | Dashboard clearly shows New test run form, required fields, Create QA Run button, and Test run history with Report and Logs columns. | Dashboard opened after login. Visible sections/text: New test run, Target URL, Requirement doc, Create QA Run, Test run history, Report, Logs | Pass | — |
TC-003 | REQ-001 | Create-run form prevents submission when required fields are missing | 1. Leave required fields empty. 2. Select Create QA Run. | The form should not create a run and should tell the user which required information is missing. | Browser validation prevented submission and reported: [{"name":"target_url","message":"Please fill out this field."},{"name":"requirements","message":"Please select a file."}] | Pass | — |
TC-004 | REQ-001 | User can submit a QA run from the web form and see it as the newest history item | 1. Fill target URL. 2. Fill project name and scope. 3. Upload requirement document. 4. Select Create QA Run. 5. Confirm return to dashboard and newest history row. | The submitted run appears in Test run history with the entered project, target URL, timestamp, and a meaningful run status. | After form submission, the newest history row displayed: qa-20260523-213013 qaagent-functional-pm-qa-ui-create-test https://qa.winds-os.com/health queued — — 2026-05-23T21:30:13Z | Pass | — |
TC-005 | REQ-001 | Submitted history run exposes report and log links for user review | 1. Refresh the history after submitting. 2. Wait for the run row to become actionable. 3. Check Report and Logs cells. | The history row exposes user-clickable Report and Logs links so a non-technical reviewer can inspect output/evidence. | Newest run row after waiting: qa-20260523-213013 qaagent-functional-pm-qa-ui-create-test https://qa.winds-os.com/health queued — — 2026-05-23T21:30:13Z . Links visible: [{"text":"https://qa.winds-os.com/health","href":"https://qa.winds-os.com/health"}] | Fail | DEF-001 |
TC-006 | REQ-001 | Mobile-sized dashboard still exposes create-run and history areas | 1. Open the dashboard on mobile viewport. 2. Confirm create form and history area are available. | Core dashboard content remains reachable on mobile without blocking the user from creating or reviewing runs. | Mobile dashboard loads and retains the create form and history sections. Horizontal scrolling may be needed for the history table on a phone-sized screen. | Pass | — |

## Evidence Gallery

TC-001 / REQ-001 — Pass
Invalid password is rejected before a user can access QA run creation
TC-002 / REQ-001 — Pass
Authorized user can reach the dashboard and understand where to create and review runs
TC-003 / REQ-001 — Pass
Create-run form prevents submission when required fields are missing
TC-004 / REQ-001 — Pass
User can submit a QA run from the web form and see it as the newest history item
TC-005 / REQ-001 — Fail
Submitted history run exposes report and log links for user review
TC-006 / REQ-001 — Pass
Mobile-sized dashboard still exposes create-run and history areas

## Defects

### DEF-001 — Newly submitted run remains queued and does not expose Report or Logs links

Severity: High | Category: Functional | Requirement: REQ-001 | Test Case: TC-005

After a real user submits a QA run from the dashboard, the run appears in history but remains in queued state during the observation window. The Report and Logs columns display dashes, so a product reviewer cannot open the run output or logs from history.

Expected: The history row should expose clickable Report and Logs links for the submitted run, or clearly communicate when links will become available.

Actual: Newest run row after waiting: qa-20260523-213013 qaagent-functional-pm-qa-ui-create-test https://qa.winds-os.com/health queued — — 2026-05-23T21:30:13Z . Links visible: [{"text":"https://qa.winds-os.com/health","href":"https://qa.winds-os.com/health"}]

Evidence: screenshots/TC-005-fail-report-log-links.png

## Downloads

- Referenced Requirements
- Requirements Traceability Matrix
- Test Cases
- Test Execution Results
- Defect Report
- QA Summary
- Full QA Package Zip