Authentication Functional Test Cases Scenarios

Login Page:

• Verify that as soon as the login page opens, by default the cursor should remain on the username textbox.
• Verify that the user is able to navigate or access the different controls by pressing the Tab key on the keyboard.
• Check if the password is in masked form when typed in the password field.
• Check if the password can be copy-pasted or not.
• Verify that the user is able to login by entering valid credentials and clicking on the Login button.
• Verify that the user is able to login by entering valid credentials and pressing Enter key.
• Check that the user is not able to login with an invalid username and password.
• Verify that the validation message gets displayed in case the user leaves the username or password field as blank.
• Check that the validation message is displayed in the case the user exceeds the character limit of the user name and password fields.
• Verify that reset button functionality on the login page. Clicking on it should clear the textbox’s content.
• Verify if there is a checkbox with the label remember password on the login page.
• Verify that closing the browser should not log-out an authenticated user. Launching the application should lead the user to login state only.

Registration Form:

• Verify that the Registration form contains Username, First Name, Last Name, Password, Confirm Password, Email Id, Phone number, Date of birth, Gender, Location, Terms of use, Submit, Login (If you already have an account).
• Verify that tab functionality is working properly or not.
• Verify that Enter/Tab key works as a substitute for the Submit button.
• Verify that all the fields such as Username, First Name, Last Name, Password and other fields have a valid placeholder.
• Verify that all the required/mandatory fields are marked with * against the field.
• Verify that clicking on submit button after entering all the mandatory fields, submits the data to the server.
• Verify that system generates a validation message when clicking on submit button without filling all the mandatory fields.
• Verify that entering blank spaces on mandatory fields lead to validation error.
• Verify that clicking on submit button by leaving optional fields, submits the data to the server without any validation error.
• Verify that case sensitivity of Username (usually Username field should not follow case sensitivity – ‘rajkumar’ & ‘RAJKUMAR’ acts same).
• Verify that system generates a validation message when entering existing username.
• Verify that the character limit in all the fields (mainly username and password) based on business requirement.
• Verify that the username validation as per business requirement (in some application, username should not allow numeric and special characters).
• Verify that the validation of all the fields are as per business requirement.
• Verify that the date of birth field should not allow the dates greater than current date (some applications have age limit of 18 in that case you have to validate whether the age is greater than or equal to 18 or not).
• Verify that the validation of email field by entering incorrect email id.
• Verify that the validation of numeric fields by entering alphabets and characters.
• Verify that leading and trailing spaces are trimmed after clicking on submit button.
• Verify that the terms and conditions checkbox is unselected by default (depends on business logic, it may be selected or unselected).
• Verify that the validation message is displayed when clicking on submit button without selecting terms and conditions checkbox.
• Verify that the password is in encrypted form when entered.
• Verify whether the password and confirm password are same or not.

Application Test Cases Scenarios

1. Functionality Testing

Functionality Testing of a Website is a process that includes several testing parameters like user interface, APIs, database testing, security testing, client and server testing and basic website functionalities. Functional testing is very convenient and it allows users to perform both manual and automated testing. It is performed to test the functionalities of each feature on the website.

Web based testing activities includes:

• Test all links in your webpages are working correctly and make sure there are no broken links. Links to be checked will include:

  • Outgoing links
  • Internal links
  • Anchor Links
  • MailTo Links

• Test Forms are working as expected. This will include:

  • Scripting checks on the form are working as expected. For example- if a user does not fill a mandatory field in a form an error message is shown.
  • Check default values are being populated
  • Once submitted, the data in the forms is submitted to a live database or is linked to a working email address
  • Forms are optimally formatted for better readability

• Test Cookies are working as expected. Cookies are small files used by websites to primarily remember active user sessions so you do not need to log in every time you visit a website. Cookie Testing will include:

  • Testing cookies (sessions) are deleted either when cache is cleared or when they reach their expiry.
  • Delete cookies (sessions) and test that login credentials are asked for when you next visit the site.

• Test HTML and CSS to ensure that search engines can crawl your site easily. This will include:

  • Checking for Syntax Errors
  • Readable Color Schemas
  • Standard Compliance. Ensure standards such W3C, OASIS, IETF, ISO, ECMA, or WS-I are followed.

• Test business workflow – This will include:

  • Testing your end – to – end workflow/ business scenarios which takes the user through a series of webpages to complete.
  • Test negative scenarios as well, such that when a user executes an unexpected step, appropriate error message or help is shown in your web application.

2. Usability Testing

Usability Testing has now become a vital part of any web based project. It can be carried out by testers like you or a small focus group similar to the target audience of the web application.

• Test the site Navigation:

  • Menus, buttons or Links to different pages on your site should be easily visible and consistent on all webpages

• Test the Content:

  • Content should be legible with no spelling or grammatical errors.
  • Images if present should contain an alt text.

3.Interface Testing

Three areas to be tested here are – Application, Web and Database Server.

• Application: Test requests are sent correctly to the Database and output at the client side is displayed correctly. Errors if any must be caught by the application and must be only shown to the administrator and not the end user.
• Web Server: Test Web server is handling all application requests without any service denial.
• Database Server: Make sure queries sent to the database give expected results.

4. Database Testing

Database is one critical component of your web application and stress must be laid to test it thoroughly. Testing activities will include:

• Test if any errors are shown while executing queries
• Data Integrity is maintained while creating, updating or deleting data in database.
• Check response time of queries and fine tune them if necessary.
• Test data retrieved from your database is shown accurately in your web application.

5. Compatibility Testing

Compatibility tests ensures that your web application displays correctly across different devices. This would include:

• Browser Compatibility Test: Same website in different browsers will display differently. You need to test if your web application is being displayed correctly across browsers, JavaScript, AJAX and authentication is working fine. You may also check for Mobile Browser Compatibility.
• The rendering of web elements like buttons, text fields etc. changes with change in Operating System. Make sure your website works fine for various combination of Operating systems such as Windows, Linux, Mac and Browsers such as Firefox, Internet Explorer, Safari etc.

6. Performance Testing

This will ensure your site works under all loads. Software Testing activities will include but not limited to:

• Website application response times at different connection speeds.
• Load test your web application to determine its behavior under normal and peak loads.
• Stress test your web site to determine its break point when pushed to beyond normal loads at peak time.
• Test if a crash occurs due to peak load, how does the site recover from such an event.
• Make sure optimization techniques like gzip compression, browser and server side cache enabled to reduce load times.

7. Security Testing

Security Testing is vital for e-commerce website that store sensitive customer information like credit cards. Testing Activities will include:

• Test unauthorized access to secure pages should not be permitted.
• Restricted files should not be downloadable without appropriate access.
• Check sessions are automatically killed after prolonged user inactivity.
• On use of SSL certificates, website should re-direct to encrypted SSL pages.

8. Crowd Testing

You will select a large number of people (crowd) to execute tests which otherwise would have been executed a select group of people in the company. Crowdsourced testing is an interesting and upcoming concept and helps unravel many a unnoticed defects.