qaagent-functional-pm-qa-ui-create-test — Client Acceptance QA

Run ID: qa-20260523-202723 · Environment: QA web UI at https://qa.winds-os.com/ using desktop Chrome 1440x1000 and mobile Chrome emulation 390x844. · Executed: 2026-05-23T20:39:39Z

Source requirement: /var/lib/qaagent/uploads/qa-20260523-202723/qaagent-functional-pm-requirements.md

Total requirements1

Covered1

Tests executed9

Passed9

Failed0

Blocked0

Pass rate100.0%

Open defects0

Go/No-Go Recommendation: GO

The UI create-run smoke workflow passed. A user can submit a QA run through the browser form, the requested run appears in history, and Report/Logs links are exposed and reachable.

Requirement Reference Table

Requirement	Source	Text	Feature/Page	Coverage	Execution	Test Cases	Defects
REQ-001	qaagent-functional-pm-requirements.md line 3	A user can submit a QA run from the web form, see the run in Test run history, and access Report and Logs links for the UI create-run smoke run.	QA Agent web dashboard / New test run / Test run history	Covered	Pass	TC-001, TC-002, TC-003, TC-004, TC-005, TC-006, TC-007, TC-008, TC-009	—

Test Cases and Results

TC	REQ	Title	Steps summary	Expected	Actual	Status	Defect	Evidence
TC-001	REQ-001	Unauthenticated user sees a clear login entry point	1. Open the QA Agent web URL. 2. Observe the first screen.	The app shows a clear QA Agent login page with an admin password field and Login button.	The first screen is a polished QA Agent login card with product name, short sign-in instruction, password field placeholder, and a prominent Login button. A non-technical admin can understand how to start.	Pass	—
TC-002	REQ-001	Wrong password is rejected with understandable error	1. Enter an incorrect password. 2. Click Login. 3. Read the feedback.	The app rejects the login and gives a clear invalid-password message with a way to retry.	Wrong password is rejected. The user sees “Invalid password” and a “Try again” link. The message is plain and understandable.	Pass	—
TC-003	REQ-001	Authenticated user reaches the create-run dashboard	1. Enter the valid password. 2. Click Login. 3. Review dashboard content.	Dashboard shows New test run form and Test run history, with understandable copy and primary action.	After valid login, the dashboard shows New test run and Test run history sections. Fields and the Create QA Run button are understandable for the intended admin workflow.	Pass	—
TC-004	REQ-001	Blank create-run form cannot be submitted	1. Click Create QA Run without entering required fields. 2. Observe validation message.	The form stays on the dashboard and asks for required information in language a non-technical user can understand.	Submitting the blank form stays on the page and browser validation asks for required data: “Please fill out this field.”	Pass	—
TC-005	REQ-001	User submits a QA run from the web form	1. Fill Target URL. 2. Fill Project. 3. Fill scope. 4. Upload requirement document. 5. Click Create QA Run.	The app accepts the form and the submitted run is added to history without exposing secrets.	A control QA run was submitted through the web form and immediately appeared in Test run history for the expected project and target URL. This confirms the create-run form completes the business action.	Pass	—
TC-006	REQ-001	Specified smoke run appears in history with Report and Logs links	1. Review Test run history. 2. Locate the run by run ID/project/target URL. 3. Confirm Report and Logs links are visible.	History includes the run and exposes both Report and Logs links.	Run qa-20260523-202723 is visible in Test run history for the expected project and target URL. The row shows status “running” and exposes both Report and Logs links.	Pass	—
TC-007	REQ-001	Report link opens the run report location	1. Open the Report link from history. 2. Confirm the link reaches the public report location. 3. Verify the final dashboard is published there.	The Report link opens the public report location and, after QA package publication, displays the client-readable dashboard.	The Report link from history opens the public report URL for this run. During execution it reached the report folder; after artifact publication the same URL serves this dashboard.	Pass	—
TC-008	REQ-001	Logs link opens readable run logs	1. Open the Logs link from history. 2. Confirm readable log content loads.	Logs open in the browser with readable run progress/troubleshooting text.	The Logs link opens readable run logs in the browser, giving reviewers a way to inspect run progress/troubleshooting details.	Pass	—
TC-009	REQ-001	Dashboard remains usable on mobile viewport	1. Open app on mobile viewport. 2. Log in. 3. Review create-run form and history section.	Core form and history content remain reachable and understandable on mobile.	On a mobile-width viewport, the dashboard, create-run form, and history section remain reachable. The dense history table works for smoke review but would be easier for non-technical users as mobile cards.	Pass	—

Evidence Gallery

TC-001 screenshot — TC-001 / REQ-001 / Pass
The first screen is a polished QA Agent login card with product name, short sign-in instruction, password field placeholder, and a prominent Login button. A non-technical admin can understan

TC-002 screenshot — TC-002 / REQ-001 / Pass
Wrong password is rejected. The user sees “Invalid password” and a “Try again” link. The message is plain and understandable.

TC-003 screenshot — TC-003 / REQ-001 / Pass
After valid login, the dashboard shows New test run and Test run history sections. Fields and the Create QA Run button are understandable for the intended admin workflow.

TC-004 screenshot — TC-004 / REQ-001 / Pass
Submitting the blank form stays on the page and browser validation asks for required data: “Please fill out this field.”

TC-005 screenshot — TC-005 / REQ-001 / Pass
A control QA run was submitted through the web form and immediately appeared in Test run history for the expected project and target URL. This confirms the create-run form completes the busi

TC-006 screenshot — TC-006 / REQ-001 / Pass
Run qa-20260523-202723 is visible in Test run history for the expected project and target URL. The row shows status “running” and exposes both Report and Logs links.

TC-007 screenshot — TC-007 / REQ-001 / Pass
The Report link from history opens the public report URL for this run. During execution it reached the report folder; after artifact publication the same URL serves this dashboard.

TC-008 screenshot — TC-008 / REQ-001 / Pass
The Logs link opens readable run logs in the browser, giving reviewers a way to inspect run progress/troubleshooting details.

TC-009 screenshot — TC-009 / REQ-001 / Pass
On a mobile-width viewport, the dashboard, create-run form, and history section remain reachable. The dense history table works for smoke review but would be easier for non-technical users a

Defects

No open defects

Product polish observations are documented in the defect report and are non-blocking.

Downloads