QA Dashboard — qaagent-functional-pm-qa-ui-create-test

QA Summary

The browser UI create-run smoke flow passed. A new run was created from the web form (qa-20260523-212010), the requested run qa-20260523-210349 appeared in history, and Report/Logs links were visible and usable. No defects were opened.

Go/No-Go: Go for this smoke scope.

Requirement Traceability

Requirement	Source	Text	Coverage	Status	Tests	Defects
REQ-001	/var/lib/qaagent/uploads/qa-20260523-210349/qaagent-functional-pm-requirements.md line 3	An admin user can sign in, submit a QA run from the web form, see the created run in Test run history, and access report/log links for the requested run.	Covered	Pass	TC-001, TC-002, TC-003, TC-004, TC-005, TC-006, TC-007, TC-008, TC-009	—

Test Cases and Execution Results

Test	Title	Steps	Expected	Actual product result	Status	Evidence
TC-001 REQ-001	Review unauthenticated login screen	1. Open https://qa.winds-os.com/. 2. Observe the login screen.	The user sees a clear QA Agent login screen with an admin password field and Login action.	Unauthenticated visitors are directed to a simple QA Agent login screen with an admin password field and Login button. The purpose is understandable for an admin user.	Pass	View evidence
TC-002 REQ-001	Reject invalid login safely	1. Enter an incorrect password. 2. Submit the login form.	The app rejects access and shows a plain-language error with a way to try again.	A wrong password is rejected and the user sees “Invalid password” with a “Try again” recovery link.	Pass	View evidence
TC-003 REQ-001	Open authenticated dashboard	1. Sign in with valid admin access. 2. Review the dashboard.	The dashboard shows New test run and Test run history in understandable product language.	After valid login, the dashboard shows a New test run form and Test run history. Labels and buttons are understandable for creating and reviewing QA runs.	Pass	View evidence
TC-004 REQ-001	Prevent blank create-run submission	1. Click Create QA Run without entering required data.	The form does not submit and tells the user which required data is missing.	The blank form does not submit. Browser validation tells the user: “Please fill out this field.”.	Pass	View evidence
TC-005 REQ-001	Submit a QA run through the web form	1. Complete Target URL. 2. Enter project name. 3. Enter scope. 4. Upload requirements document. 5. Click Create QA Run.	The app creates a run and returns to history where the submitted project and target URL are visible.	The submitted QA run appears in Test run history for project “qaagent-functional-pm-qa-ui-create-test” and target “https://qa.winds-os.com/health”. Visible run ID: qa-20260523-212010.	Pass	View evidence
TC-006 REQ-001	Verify requested run appears with report/log links	1. Open Test run history. 2. Locate run qa-20260523-210349. 3. Check the Report and Logs columns.	The requested run is visible and has both Report and Logs links.	The requested run qa-20260523-210349 is visible in Test run history and exposes both Report and Logs links. Row shown to the user: qa-20260523-210349 qaagent-functional-pm-qa-ui-create-test https://qa.winds-os.com/health running Report Logs 2026-05-23T21:03:49Z.	Pass	View evidence
TC-007 REQ-001	Open report link for requested run	1. Click/open the Report link for qa-20260523-210349.	A browser-readable report location opens for the run.	The Report link is exposed and points to a browser-openable report location for the requested run: https://files.winds-os.com/qaagent-functional-pm-qa-ui-create-test/qa-20260523-210349/. HTTP status observed during execution: 200.	Pass	View evidence
TC-008 REQ-001	Open logs link for requested run	1. Click/open the Logs link for qa-20260523-210349.	Readable run logs open without showing a broken page.	The Logs link opens readable run logs for qa-20260523-210349; the page returns HTTP 200 and displays log text.	Pass	View evidence
TC-009 REQ-001	Check mobile usability of create/history flow	1. Sign in on mobile viewport. 2. Confirm New test run and Test run history are reachable.	The create-run form and history remain usable on a phone-sized screen.	On a mobile-width viewport, the create-run form and history section remain reachable. The history table is dense and would be easier as mobile cards, but the flow is usable for smoke review.	Pass	View evidence

Evidence Gallery

One screenshot is included for every executed UI test case.

TC-001 evidence — **TC-001** · REQ-001 · Pass
Review unauthenticated login screen
Unauthenticated visitors are directed to a simple QA Agent login screen with an admin password field and Login button. The purpose is understandable for an admin user.

TC-002 evidence — **TC-002** · REQ-001 · Pass
Reject invalid login safely
A wrong password is rejected and the user sees “Invalid password” with a “Try again” recovery link.

TC-003 evidence — **TC-003** · REQ-001 · Pass
Open authenticated dashboard
After valid login, the dashboard shows a New test run form and Test run history. Labels and buttons are understandable for creating and reviewing QA runs.

TC-004 evidence — **TC-004** · REQ-001 · Pass
Prevent blank create-run submission
The blank form does not submit. Browser validation tells the user: “Please fill out this field.”.

TC-005 evidence — **TC-005** · REQ-001 · Pass
Submit a QA run through the web form
The submitted QA run appears in Test run history for project “qaagent-functional-pm-qa-ui-create-test” and target “https://qa.winds-os.com/health”. Visible run ID: qa-20260523-212010.

TC-006 evidence — **TC-006** · REQ-001 · Pass
Verify requested run appears with report/log links
The requested run qa-20260523-210349 is visible in Test run history and exposes both Report and Logs links. Row shown to the user: qa-20260523-210349 qaagent-functional-pm-qa-ui-create-test https://qa.winds-os.com/health running Report Logs 2026-05-23T21:03:49Z.

TC-007 evidence — **TC-007** · REQ-001 · Pass
Open report link for requested run
The Report link is exposed and points to a browser-openable report location for the requested run: https://files.winds-os.com/qaagent-functional-pm-qa-ui-create-test/qa-20260523-210349/. HTTP status observed during execution: 200.

TC-008 evidence — **TC-008** · REQ-001 · Pass
Open logs link for requested run
The Logs link opens readable run logs for qa-20260523-210349; the page returns HTTP 200 and displays log text.

TC-009 evidence — **TC-009** · REQ-001 · Pass
Check mobile usability of create/history flow
On a mobile-width viewport, the create-run form and history section remain reachable. The history table is dense and would be easier as mobile cards, but the flow is usable for smoke review.

Defects

No defects were opened. Product observations are listed in the defect report as non-blocking improvement notes.

Console/API Notes

No secrets or credential values are included.

verbose: [DOM] Input elements should have autocomplete attributes (suggested: "new-password"): (More info: https://goo.gl/9p2vKq) %o
error: Failed to load resource: the server responded with a status of 404 ()
error: Failed to load resource: the server responded with a status of 401 ()
verbose: [DOM] Input elements should have autocomplete attributes (suggested: "new-password"): (More info: https://goo.gl/9p2vKq) %o
error: Failed to load resource: the server responded with a status of 404 ()