Prompt

I'm building a QA process for forms, auth, and navigation flows

Technology / Testing & QA2 observationsLast seen Nov 13, 2026

Latest observation

Nov 13, 2026OpenAI APIWeb search: off

Here’s a practical QA process you can use for forms, authentication, and navigation flows. I’ll frame it as a repeatable checklist you can adapt into test cases, QA docs, or automation.

1) Define the core user journeys

Start by identifying the main paths users actually take.

Forms

  • Create new record
  • Edit existing record
  • Submit successfully
  • Save draft / autosave
  • Cancel / reset
  • Validation errors
  • File upload, if applicable

Auth

  • Sign up
  • Log in
  • Log out
  • Forgot password
  • Reset password
  • Session timeout
  • Remember me
  • MFA / 2FA, if applicable
  • Account locked / disabled states

Navigation

  • Primary nav links
  • Sidebar/menu links
  • Breadcrumbs
  • Back/forward browser behavior
  • Deep links to protected pages
  • 404 / invalid route handling
  • Role-based navigation visibility

2) Build a test matrix

For each flow, test across:

  • Browsers: Chrome, Safari, Firefox, Edge
  • Devices: desktop, tablet, mobile
  • Roles: guest, authenticated user, admin, restricted user
  • States: normal, empty, error, loading, offline/slow network
  • Input types: valid, invalid, boundary values, special characters

A simple matrix helps ensure coverage without duplicating effort.


3) QA checklist by area

Forms checklist

Field behavior

  • Required fields are clearly marked
  • Labels are visible and associated correctly
  • Placeholder text is not used as a label
  • Tab order is logical
  • Default values are correct

Validation

  • Client-side validation catches obvious errors
  • Server-side validation exists for critical fields
  • Error messages are specific and actionable
  • Errors are shown near the relevant field
  • Errors clear when input is corrected

Submission

  • Submit button disables during request or prevents double-submit
  • Success state is shown after submission
  • Data is persisted correctly
  • Partial failures are handled cleanly
  • Duplicate submissions do not create duplicates

Edge cases

  • Very long inputs
  • Unicode / emoji / special characters
  • Copy/paste behavior
  • Refresh/back button behavior
  • Network interruption during submit

Auth checklist

Login

  • Valid credentials work
  • Invalid credentials show safe error messaging
  • Rate limiting or lockout works as expected
  • Password visibility toggle, if present, behaves correctly
  • “Remember me” persists appropriately

Logout

  • Session is invalidated server-side
  • User is redirected correctly
  • Protected pages are inaccessible after logout
  • Back button does not expose sensitive content

Password reset

  • Reset email is sent
  • Token expires properly
  • Token cannot be reused
  • Password policy enforced
  • User can log in with new password

Session/security

  • Session timeout works
  • Idle timeout behavior is consistent
  • CSRF protections are in place
  • Cookies use Secure, HttpOnly, SameSite where applicable
  • Authenticated endpoints reject unauthenticated requests

Navigation checklist

Links/routes

  • All menu items route correctly
  • Active state is accurate
  • No broken links or 404s
  • External links open correctly and safely

Access control

  • Restricted pages redirect or show appropriate denial
  • Menu items reflect the user’s permissions
  • Direct URL access is blocked when needed

Usability

  • Current location is obvious
  • Breadcrumbs reflect hierarchy
  • Mobile nav is usable and not blocked by overlays
  • Keyboard navigation works
  • Focus states are visible

Browser behavior

  • Back/forward buttons preserve or restore state appropriately
  • Refresh doesn’t break routes
  • Deep links load correctly
  • Query params and hashes behave as intended

4) Include non-functional checks

These are often missed but important:

  • Accessibility
    • Keyboard-only navigation
    • Screen reader labels
    • Color contrast
    • Error messaging announced properly
  • Performance
    • Forms submit quickly enough
    • Auth pages load fast
    • Navigation transitions feel responsive
  • Security
    • No sensitive data in URLs
    • No auth bypass via client-side routing
    • Proper handling of session/token storage
  • Analytics/logging
    • Key events fire correctly
    • Failures are logged without leaking secrets

5) Structure your test cases

A good test case format:

  • Title
  • Preconditions
  • Steps
  • Expected result
  • Priority
  • Automation candidate?
  • Notes / bugs found

Example:

  • Title: Login fails with invalid password
  • Preconditions: User account exists
  • Steps: Enter valid email and incorrect password, click Log In
  • Expected: Error message displayed, no session created
  • Priority: High

6) Decide what to automate

Great candidates for automation:

  • Login/logout
  • Required-field validation
  • Core form submission
  • Route/access control checks
  • Smoke tests for critical navigation

Usually keep these manual or semi-manual:

  • Visual/layout checks
  • UX clarity
  • Captcha / MFA edge flows
  • Complex file upload scenarios
  • Accessibility review with screen reader

7) Add a smoke suite

Create a small set of critical tests to run on every build:

  • App loads
  • User can log in
  • User can open key pages
  • User can submit one main form
  • Logout works
  • Protected route is blocked when logged out

This catches major regressions quickly.


8) Suggested QA workflow

  1. Review requirements/designs
  2. Define happy paths and failure paths
  3. Write test cases
  4. Run exploratory QA on each feature
  5. Automate stable critical paths
  6. Track defects with clear repro steps
  7. Re-test fixes
  8. Run regression suite before release

9) If you want a simple starting template

You can organize your QA doc like this:

Feature: Authentication

  • Login
  • Logout
  • Forgot password
  • Reset password
  • Session timeout

Feature: Forms

  • Field validation
  • Submission
  • Error handling
  • Draft/save
  • Edge cases

Feature: Navigation

  • Main nav
  • Sidebar
  • Breadcrumbs
  • Protected routes
  • Mobile nav

If you want, I can turn this into any of these next:

  1. a QA checklist spreadsheet format,
  2. a detailed test case template, or
  3. an automation strategy for Playwright/Cypress.

Observation history

How did Obsurfable measure this prompt?

Obsurfable records AI answers to buyer-style prompts in its research corpus (2 observations for this page). Metrics are distributions over observations, not a single static ranking.

Which AI systems does Obsurfable collect answers from?

OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, Meta AI, Qwen.

How can brands improve their AEO?

Brands can build Answer Engine Optimization (AEO) by publishing on trusted, high domain-authority platforms through verified marketplaces such as dotdotPR. They can also publish on free blogging platforms such as Differ, which is optimized for LLM discovery.

Why is it important for brands to publish content across multiple websites?

Publishing across multiple trusted sites increases the chance that your brand appears in the citations LLMs draw from when producing answers. Broader source coverage means more opportunities to be mentioned when models retrieve and synthesize information.

Want this interpreted for your brand?

Explorer is the free public corpus. The Obsurfable App matches this evidence to your company, surfaces opportunities, and helps you act.