Registration & Login Test Cases For eCommerce Website 2022 : Aalpha

Registration & Login Test Cases For eCommerce Website

Definition of Login or registration page for eCommerce

Test case for a login page

  • CAPTCHA
  • Link of Forgot Password
  • Link of Create/Sign up/ into an account
  • Remember Me Checkbox
  • Keep Me Signed In Checkbox
  • Login Button
  • Password Textbox
  • Phone Number/ Username/Email/ Textbox
  • Compose compatibility, performance, UI, and functional test cases
  • Write both negative and positive test cases
  • Compose both practical and non-functional experiments
  • Write experiments on each item in the login structure

Examples of non-functional and functional login page test cases

Test Scenarios For The Sign-up Page

  • Make sure that the user gets the clues for each field on the structure that might ease them
  • Confirm if the Password and Confirm Password fields are permitting comparable strings as it were
  • Check if the Password field will ask the user for the frail passwords
  • Confirm if a User can effectively join by filling in every one of the obligatory subtleties
  • Check if a client can sign in to fill invalid subtleties
  • Confirm if the exceptional characters and numbers are not allowed in the First and Last names
  • Check the user’s age when the DOB is chosen
  • Confirm if the user can’t push forward, leaving every one of the obligatory fields unfilled
  • Look at the directives for each required field

Mobile Application login page test case scenarios

  • Confirm if the Login page impeccably fits the portable screen
  • Ensure that the user can sign in utilizing those qualifications
  • Look at the ‘Failed to remember Password tab
  • Verify if this, of course, isn’t chosen
  • Confirm the choice ‘Keep me Sign In
  • Ensure that a client can sign in with a legitimate secret phrase and username
  • Confirm if a client can’t sign in with an invalid secret key or username

Experiments For CAPTCHA and Cookies

  • Verify the login usefulness when the user switches off the program treats
  • Make sure that the user can sign in even in the wake of the cleaning program treats
  • Confirm if the SSL authentication is carried out
  • Verify two-way verification through OTP is proceeding true to form on account of banking applications
  • Check if the virtual console is accessible and performing accurately to enter login accreditations in banking applications
  • Ensure if the CAPTCHA is case-delicate
  • Confirm if the CAPTCHA holds sound help to tune in
  • Make sure that the CAPTCHA’s invigorate interface is producing another CAPTCHA
  • Confirm if there is a client-side approval when the user neglects or does not enter the CAPTCHA

Gmail Login page test cases

  • Browse the ‘Forgot email’ tab
  • Look at the forgot Password tab
  • Ensure that a client can’t sign in with some unacceptable secret word and a substantial email address
  • confirm if a client can’t sign in with an invalid secret word and a legitimate telephone number
  • Check if the user can sign in by entering a substantial email address and secret word
  • verify if the user can sign in by entering a legitimate secret key and telephone number
  • Check if the user will receive the right message on entering an invalid telephone number
  • confirm if the user will receive the right message on entering an invalid email address
  • Check if the user receives the right message on the off chance that the unfilled field gets featured
  • Confirm if the client gets a method for entering the secret key

Non-Functional Security Test Cases

  • Confirm whether cross-site prearranging (XSS) weakness performs on a login page. Programmers might utilize XSS weakness to sidestep access controls
  • Make sure that the Login page is hazardous for SQL infusion
  • Check whether the login structure is uncovering any security data by permitting the page source to view
  • Check that the scrambled characters in the Password field shouldn’t allow translating whenever duplicated
  • Make sure that the “Recall Password” checkbox is unselected
  • Confirm the clients shouldn’t duplicate glue passwords, as the secret key can be duplicated and stuck
  • Confirm that when the secret word is placed in the secret word field, it gets saved in a data set in a veiled configuration
  • Check a breaking point on the all-out number of fruitless sign-in. According to the business rationale, the user will need to attempt once more post entering the manual human test; if not, the client will not log in
  • Make sure that tapping the program back button post-effective logout shouldn’t make the client arrive at a signed-in mode

Functional Test cases

  • Look at the ways of recovering passwords when the client fails to remember his secret word
  • Ensure that no spaces are permitted before any secret word characters endeavor
  • Check whether the User is as yet Logged in after a grouping of activities, similar to sign-in, resuming the application, and shutting the program
  • Confirm that the User login effectively with the new secret word after he changes the secret word
  • Make sure that the user shouldn’t sign in effectively with the old secret word post-changing the secret word
  • Confirm that when the client taps the Create/Sign up a record Link, he is diverted to the Create a record page
  • Make sure that the Logout connect diverts the client to the home/login page
  • Check that the user is diverted to the right page post fruitful login
  • Check that when the client taps the Forgot Password connect, he is diverted to the Forgot secret key page
  • Confirm that the “Keep me signed in” checkbox stays unrestrained as a matter of course.
  • Check the login session timeout
  • Make sure that an approval message is shown when an exceptional person is placed in the Username and Password fields
  • Check that the approval message is shown when the person furthest reaches the Username and Password fields surpass
  • Make sure that tapping the program back button post-effective login shouldn’t make the client reach log out mode
  • Check that the approval message is displayed in the condition when the user leaves the Username or Password clear
  • Make sure that the Reset button flushes the information from each text and confine the Login structure
  • Check that the Login qualifications, particularly passwords, get saved in a data set in a scrambled organization
  • Make sure that the user neglects to sign in with idle qualifications
  • Confirm that the user neglects to Login with a clear Username and Password
  • Check that the client neglects to sign in with an invalid Username and legitimate Password
  • Make sure that the user neglects to Login with an invalid blend of Username and Password
  • Check that the Enter/Tab key works as a substitute for the Sign-in button
  • Confirm if the client can sign in with their Credentials
  • Confirm that tab functionality works
  • Take a look at the cursor on the off chance that it’s focusing on the “Username” text box on the login page or not

Testing a Login Form

  • Check that a Login page does not work with some invalid login details
  • Verify if the secret key text is covered up.
  • Ensure that the Login works well with the right accreditations.
  • Check text field limitations and whether the program acknowledges text significantly more than the cutoff points.

--

--

Aalpha is specialist India based Software Solutions company providing solutions for Web and Mobile development, https://www.aalpha.net

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store