Test Case DesignPublished: 9 min read
Login Page Test Cases — The Complete 2026 Template
60+ login page test cases across happy path, negative, security, accessibility, and edge cases. Download as CSV or generate custom ones with AI.
SoftwareTestPilot
QA Editorial Team

2026-07-17 · By SoftwareTestPilot
Every QA engineer eventually writes login test cases. Here is the canonical list — 60+ cases across six categories — that senior testers reuse across projects.
Happy path (5)
1. Valid email + valid password → success
2. Remember me checked → session persists after browser close
3. Login with social (Google) → success
4. Login redirects to previous page
5. Login with unicode email (café@example.com)Negative (12)
Invalid email format, empty email, empty password,
wrong password, wrong email, both empty,
password with leading/trailing spaces, SQL injection,
XSS payload in email, password > 200 chars,
disabled account, unverified email.Security (10)
Rate limiting after 5 failed attempts,
CSRF token required, HTTPS enforced,
password never logged, no user enumeration
(same error for wrong email vs wrong password),
session cookie httpOnly + Secure + SameSite,
JWT expiry enforced, session fixation prevented,
brute-force lockout, 2FA fallback.Accessibility (8)
Keyboard-only navigation, screen reader reads labels,
error messages announced via aria-live,
sufficient colour contrast (WCAG AA),
form labels correctly associated,
autocomplete attributes present,
zoom to 200% remains usable,
password visibility toggle keyboard accessible.Edge cases (15) & UX (10)
Full 60-case CSV is one click away in the free QA tools suite — pick "Login page" preset and export.
Frequently asked questions
1.How many login test cases are enough?
40–60 for a typical enterprise app. Fewer misses security; more usually duplicates.
2.Should social login be a separate suite?
Yes — mock the provider and isolate flakiness to that path.
3.Do I need to test both mobile and desktop?
Yes — mobile autofill, biometric prompts, and viewport constraints all differ.
4.How often should login tests run?
Every deploy, plus a nightly full-suite that includes brute-force / rate-limit assertions.
