Sample QA Assessment
This published report demonstrates exactly how Cypher QA documents an assessment: reproducible findings, severity classification, screenshot evidence, and a clear release recommendation.
A focused exploratory QA assessment was performed against the publicly accessible OWASP Juice Shop demonstration application. Testing concentrated on normal user-facing behavior: product browsing, product details, reviews, registration and login, basket behavior, responsive layout, and common UI states.
Multiple confirmed UI, responsive, and functional findings were observed. The strongest business-impact findings were the inability to authenticate using a newly registered test account (CY-005) and the ability to add a sold-out product to the basket (CY-006).
Authentication and inventory-state behavior require review.
Several narrow-viewport layout issues observed.
Typography, spacing, and overlap issues observed.
Only limited exploratory checks performed.
Basket slowdown observed, but no timing data was captured.
Opera on Windows (ultrawide desktop) plus a narrow, mobile-like viewport for responsive checks. Exploratory functional and UI style. No security testing performed.
Assessed on 23 August 2026. Credentials are intentionally omitted from the report.
Each finding follows the same contract: what actually happens, what should happen, severity, category, and evidence where supplied.
Actual: The Apple Juice product title and “(1000ml)” quantity visually overlap in the product details view.
Expected: The title and quantity should remain visually separated with adequate spacing.
UI / Visual · Product Details
Actual: Review text can wrap at an unnatural character boundary, producing a word split such as “bri” followed by “ght”.
Expected: Words should wrap naturally without arbitrary character-level breaks where the layout permits.
UI / Typography · Product Reviews
Actual: Leaving the repeat-password field empty displays validation feedback that overlaps the nearby password advice/help control.
Expected: Validation feedback should appear without covering or colliding with surrounding controls.
UI / Form Validation · Registration
Actual: The cookie notification is displayed without an obvious close/dismiss control; the banner shows its primary action but no visible close control.
Expected: Users should have an obvious way to dismiss the notification where the consent design permits dismissal, and the banner should avoid obstructing important controls at supported viewport sizes.
UX / Cookie Consent · Global UI
Actual: A test account created successfully through the normal registration flow could not subsequently authenticate using the credentials established during registration. Login returned “Invalid email or password”.
Expected: A successfully registered user should be able to authenticate using the credentials established during registration, subject to any documented verification requirement.
Functional / Authentication · Registration / Login
Documented from the observed test result; no screenshot supplied in this version of the report.
Actual: A product visibly marked “Sold Out” can still be added to the basket through the normal user interface.
Expected: A sold-out product should either be unavailable for addition or clearly communicate that it cannot currently be purchased.
Functional / Inventory State · Product Listing / Basket
Actual: At a narrow/mobile-like viewport, the Google sign-in button has very little horizontal padding and the Google icon sits extremely close to the button edge.
Expected: The button should maintain consistent spacing around its icon and content across supported viewport sizes.
Responsive / UI · Authentication / Registration
Observations are deliberately kept separate from confirmed defects: reporting a performance problem without measurement data would be speculation, not QA.
HOLD / FIX AND RETEST
Based on the limited exploratory scope, the application should not be treated as release-ready without review of the confirmed authentication and inventory-state findings and correction of the identified responsive/UI issues. A full release decision would require broader browser/device coverage, additional functional coverage, and regression testing.
This web page is a faithful representation of the downloadable DOCX report. The original document remains the canonical version of the assessment.