Manual testing guide

25 Registration Page Test Cases and Sign-Up Scenarios

Registration combines data validation, identity verification, consent and account creation. Good coverage verifies not only the happy path, but also duplicate prevention, interrupted flows and clear recovery from input errors.

Example requirement

A new customer can register using their name, unique email address and a password that follows the documented password policy. The customer must accept the required terms and verify their email before the account becomes active.

Generate test cases for this example

Test cases

Coverage types

High priority

CSV

Export format

Registration page and sign-up coverage

A useful registration test plan covers more than form validation. It proves that a new identity is created once, verified safely and recoverable when the flow is interrupted.

Test unique and duplicate email or phone identifiers.
Cover password, confirmation and field-length boundaries.
Verify consent, activation and verification-link lifecycle.
Check retries, accessibility and international user data.

25 example test cases

Filter the coverage, switch between card and table views, then copy or export the cases you need. Replace assumptions with the confirmed rules, environments and risks of your product.

Showing 25 of 25 cases

REG-001FunctionalHigh priority

Create an account with valid information

Precondition

The email address is not registered.

Expected result

The account is created in the expected pending-verification state and verification instructions are sent.

Steps

1.Open registration
2.Enter valid required information
3.Accept the required terms
4.Submit the form

REG-002NegativeHigh priority

Reject an already registered email address

Precondition

An account already exists for the email.

Expected result

A duplicate account is not created and safe next-step guidance is displayed.

Steps

1.Enter the existing email with otherwise valid information
2.Submit registration

REG-003BoundaryHigh priority

Enforce the documented password policy

Precondition

The password rules are known.

Expected result

The invalid password is rejected with actionable guidance and the compliant password is accepted.

Steps

1.Enter a password that violates one documented rule
2.Submit registration
3.Correct the password and resubmit

REG-004NegativeHigh priority

Require mandatory consent

Precondition

Required terms or privacy consent is displayed.

Expected result

Registration is blocked and the missing consent is clearly identified.

Steps

1.Complete all fields
2.Leave required consent unselected
3.Submit registration

REG-005SecurityMedium priority

Reject an expired verification link

Precondition

An expired verification link is available.

Expected result

The expired link cannot activate the account and a replacement can be requested safely.

Steps

1.Open the expired link
2.Request a replacement link

REG-006UsabilityMedium priority

Preserve valid values after a correctable error

Precondition

The registration form is open.

Expected result

Valid non-sensitive values remain populated while the invalid field receives clear feedback.

Steps

1.Enter valid information with one invalid field
2.Submit the form
3.Review the returned form

REG-007NegativeHigh priority

Validate the email address format

Precondition

The registration form is open.

Expected result

Malformed addresses are rejected with field-specific guidance.

Steps

1.Enter malformed email addresses
2.Complete the other required fields
3.Submit registration

REG-008BoundaryMedium priority

Accept values at documented length limits

Precondition

Minimum and maximum field lengths are known.

Expected result

Every value at an allowed boundary is accepted without truncation.

Steps

1.Enter values at each exact boundary
2.Submit registration

REG-009BoundaryMedium priority

Reject values above maximum lengths

Precondition

Maximum field lengths are known.

Expected result

Over-limit values are prevented or rejected without corrupting accepted data.

Steps

1.Enter a value one character above each maximum
2.Submit registration

REG-010NegativeHigh priority

Confirm the password fields must match

Precondition

Password confirmation is required.

Expected result

Account creation is blocked and the mismatch is clearly identified.

Steps

1.Enter different password and confirmation values
2.Submit registration

REG-011SecurityHigh priority

Prevent reuse of a verification link

Precondition

A verification link was already used.

Expected result

The link cannot repeat or alter verification and the existing account remains safe.

Steps

1.Open the consumed verification link again
2.Review the account state

REG-012FunctionalMedium priority

Resend verification without creating another account

Precondition

An unverified account exists.

Expected result

One account exists and verification follows the documented replacement rule.

Steps

1.Request another verification message
2.Open the latest link
3.Review the account record

REG-013NegativeHigh priority

Handle submission when the network is interrupted

Precondition

A valid registration is ready to submit.

Expected result

The outcome is communicated clearly and the retry does not create duplicate accounts.

Steps

1.Interrupt connectivity during submission
2.Restore connectivity
3.Retry once

REG-014AccessibilityMedium priority

Navigate registration using only the keyboard

Precondition

The registration page is open.

Expected result

Focus order is logical, visible and every required action is operable.

Steps

1.Navigate every field and consent control with the keyboard
2.Submit the form

REG-015UsabilityMedium priority

Handle international names correctly

Precondition

Names are collected during registration.

Expected result

Legitimate names are accepted and preserved according to documented product rules.

Steps

1.Enter names with spaces, hyphens, apostrophes and Unicode characters
2.Complete registration

REG-016NegativeHigh priority

Validate required registration fields

Precondition

The registration page is open.

Expected result

Account creation is blocked and each required field receives clear guidance.

Steps

1.Leave every required field empty
2.Submit registration

REG-017BoundaryHigh priority

Accept the minimum allowed password length

Precondition

The minimum password length is documented.

Expected result

The password is accepted and registration can continue.

Steps

1.Enter a password exactly at the minimum length that satisfies all other rules
2.Submit registration

REG-018BoundaryHigh priority

Reject a password below minimum length

Precondition

The minimum password length is documented.

Expected result

Registration is blocked with an actionable password message.

Steps

1.Enter a password one character below the minimum
2.Submit registration

REG-019SecurityHigh priority

Prevent duplicate submission

Precondition

A valid registration is ready and the response can be delayed.

Expected result

Only one account is created and the pending state is communicated.

Steps

1.Activate Create account repeatedly
2.Inspect the created account records

REG-020UsabilityMedium priority

Return safely from the sign-in link

Precondition

The registration page links to sign in.

Expected result

Navigation is predictable and sensitive values are not exposed through browser history.

Steps

1.Enter registration information
2.Choose the sign-in link
3.Navigate back to registration

REG-021FunctionalHigh priority

Register using an approved social provider

Precondition

Social registration and an unlinked provider account are available.

Expected result

One account is created with the approved identity data and correct verification state.

Steps

1.Choose the provider
2.Approve the requested permissions
3.Return to the product

REG-022SecurityHigh priority

Handle an email already linked through social sign-in

Precondition

A local account already uses the social provider email.

Expected result

The documented linking or sign-in flow is used without silently creating a duplicate or enabling account takeover.

Steps

1.Start social registration with that provider
2.Complete provider authentication

REG-023SecurityHigh priority

Reject executable input in profile fields

Precondition

Text profile fields are available.

Expected result

Input is treated as data and cannot execute in confirmation or profile views.

Steps

1.Enter markup-like and script-like test strings
2.Submit registration
3.View the stored profile safely

REG-024UsabilityMedium priority

Keep the form usable on a mobile viewport

Precondition

A supported mobile viewport is available.

Expected result

Labels, fields, consent and actions remain visible and operable without horizontal scrolling.

Steps

1.Open registration
2.Complete every field with the on-screen keyboard
3.Review errors and submit

REG-025AccessibilityMedium priority

Announce sign-up errors to assistive technology

Precondition

A screen reader is available.

Expected result

Errors are announced, associated with fields and understandable without colour alone.

Steps

1.Submit invalid registration data
2.Navigate through the errors and affected fields

Coverage checklist

Verify the exact uniqueness rule for email addresses and phone numbers.
Test minimum, maximum and just-over-limit values for every constrained field.
Confirm verification links expire and cannot be reused.
Check consent text, links and recorded consent version.
Do not retain passwords or sensitive values when returning validation errors.

Common defects

• Duplicate accounts are created after a retry.
• Verification links remain reusable after activation.
• Valid international names are rejected by overly strict validation.
• Consent is not recorded with its displayed version.
• Correct fields are cleared after one validation error.

Suggested test data

• Unique and already registered email addresses
• Passwords at and around policy boundaries
• Expired, current and consumed verification links
• Names containing spaces, apostrophes, hyphens and Unicode
• Accepted and missing consent combinations

Automation notes

• Create unique addresses per run or clean them through an approved test fixture.
• Verify both the user-facing result and the created account state.
• Keep email-delivery checks separate from validation tests when the external mailbox is unstable.

Frequently asked questions

What are the most important registration test cases?+

Prioritise successful creation, duplicate prevention, required fields, password rules, verification, consent and safe retry behaviour.

How should duplicate registration be tested?+

Submit an existing identifier and verify that no second account is created, the response is privacy-safe and the user receives an appropriate next step.

Should registration support international names?+

If the product serves international users, its agreed name rules should support legitimate spaces, punctuation and Unicode rather than assuming one naming format.

Related test case examples

Practical login page test cases covering valid access, invalid credentials, validation, accessibility, session handling and security risks.

OTP testing

OTP test cases covering valid verification, expiry, one-time use, resend behaviour, attempt limits, privacy and input boundaries.

Password reset testing

Password reset test cases covering OTP delivery, expiry, one-time use, password policy, account discovery and active-session behaviour.

Mobile app testing

Mobile application test cases covering installation, permissions, connectivity, interruptions, orientation, accessibility and supported devices.

Generate cases for your own requirement

Paste your real user story, choose the coverage categories and receive structured manual test cases you can review and export.

Open the free generator