AI Prompt (UI level)
Prompt text
“List
UI test cases for \[page/feature]. Include happy paths, form
validations, accessibility focus/keyboard/ARIA, error states,
responsive breakpoints, and localization if applicable.”
How to apply critical
thinking
·
Understand the user goal
·
What is
the primary job of the page/feature?
·
What are
the critical user journeys and failure modes?
·
Generate test cases
·
Happy paths: user completes the main task with valid inputs
on supported devices/browsers.
·
Validation:
client-side + server-side checks; inline vs global errors.
·
Accessibility:
keyboard-only navigation, screen reader semantics,
focus management, ARIA attributes.
·
Responsiveness:
layout/behavior at different breakpoints and orientations.
·
Localization:
long translations, RTL layouts, number/date formats.
·
Questions on ambiguities
·
Which browsers/devices and assistive technologies are
in scope?
·
What is the expected behavior
for validation error prioritization?
·
How should error messages be phrased (tone,
length, localization)?
·
What test ideas might be missed
·
Interruptions (network flaky,
modal dialogs, session timeout).
·
Browser autofill,
password managers, copy-paste behaviors.
·
Color contrast changes in dark/light modes.
Output template (UI/functional
testing)
Context: [page/feature name, platform (web/mobile), key user goals]
Assumptions: [supported browsers/devices, accessibility level (e.g., WCAG 2.1 AA), feature flags]
Test Types: [UI, functional, accessibility]
Test Cases:
ID: [TC-UI-001]
Type: [UI/functional]
Title: [e.g., "User submits valid signup form"]
Preconditions/Setup:
- [User state (logged out/in), necessary data]
- [Screen resolution, theme (light/dark)]
Steps:
1. [Navigate to page]
2. [Fill form fields]
3. [Submit]
Variations:
- [All required fields valid]
- [Each field invalid individually]
- [Keyboard-only navigation]
- [Screen reader focus order]
- [Different breakpoints: mobile/tablet/desktop]
- [Different languages/locales]
Expected Results:
- [UI state: success banner, redirect, error messages]
- [Focus placement, ARIA attributes, role announcements]
Cleanup:
- [Delete created user/data, reset UI state]
Coverage notes:
- [Covered form paths, validations, accessibility checks, responsive states]
Non-functionals:
- [Perceived performance, loading indicators, smooth transitions]
Data/fixtures:
- [Test accounts, localized strings, feature flags]
Environments:
- [Staging with prod-like assets and CDN]
Ambiguity Questions:
- [Accessibility expectations, supported locales, auto-save behavior]
Potential Missed Ideas:
- [Offline/low-bandwidth, browser extensions, system zoom/high-contrast modes]