Test Case For Single User Login Test Cases
Before Writing the test case for Single sign-on, let us know how the Single sign-on works. Which helps in writing the test cases accurately.
What is a single sign-on?
Single sign-on (SSO) is a property of identity and access management (IAM) that enables users to securely authenticate with multiple applications and websites by logging in only once—with just one set of credentials (username and password).
The application or website that the user is trying to access relies on a trusted third party to verify that users are who they say they are with SSO.
|Test Scenario Overview|
|Post On:||Test Case For Single User Login|
|Post Type:||Test Case Template|
|Applicable For:||Freshers & Experience|
How does authentication work without SSO?
Without single sign-on, each website maintains its database of users and their credentials. This is what happens when you try to log in to an app or website:
The website first checks to see whether you’ve already been authenticated. If you have, it gives you access to the site.
If you haven’t, it asks you to log in, and it checks your username and password against the information in its user database.
After login, the site passes authentication verification data as you move through the website to verify that you are authenticated each time you go to a new page. The authentication verification data is usually passed as either cookie with session data or as tokens, which don’t track the session and are faster to process.
|Related Test Cases|
|☑️ Test Case For Search Functionality||☑️ Test Case For Shopping Scenario|
|☑️ Test Case For Slow Website||☑️ Test Case For SMS|
Test Case For Single User Login
I provide you a list of test scenarios, some functional test cases for single user login:
- All mandatory fields should be validated and indicated by an asterisk (*) symbol.
- Field length validation for the User name (6-12 chars) and Password (6-12 chars)
- Field labels should be standard, e.g. field accepting user’s first name should be labeled properly as ‘First Name.’
- Validation error messages should be displayed properly in the correct position.
- All error messages should be displayed in the same CSS style (e.g., using red color).
- General confirmation messages should be displayed using CSS style other than error messages style (e.g., using green color).
- Tooltips text should be meaningful.
- Dropdown fields should have first entry as blank or text like ‘Select’.
- Delete functionality for any record on a page should ask for confirmation.
- Input fields should be checked for the max field value. Input values greater than the specified max limit should not be accepted or stored in a database.
- Check all input fields for special characters.
- Check for timeout functionality. Timeout values should be configurable. Check application behavior after an operation timeout.
- Check numeric input fields with character input values. A proper validation message should appear.
- All fields on a page (e.g., text box, radio options, dropdown lists) should be aligned properly.
- Enough space should be provided between field labels, columns, rows, error messages, etc.
- The scroll bar should be enabled only when necessary.
- Font size, style, and color for headline, description text, labels, infield data, and grid info should be standard as specified in SRS.
- Upon click of an input text field, the mouse arrow pointer should get changed to a cursor.
- The user should not be able to type in the drop-down, select lists.
- Information filled by users should remain intact when there is an error message on page submit. The user should be able to submit the form again by correcting the errors.
- Check if proper field labels are used in error messages.
- Tab and Shift+Tab order should work properly.
- Default radio options should be pre-selected on page load.
- Dropdown field values should be displayed in defined sort order.
- Field-specific and page-level help messages should be available.
- Check if correct fields are highlighted in case of errors.
- Check if dropdown list options are readable and not truncated due to the field size limit.
- All buttons on a page should be accessible by keyboard shortcuts, and the user should be able to perform all operations using a keyboard.
- Clicking on Sign Up should take the user to a registration page.
- Clicking on ‘Log out’ should take the user back to Home Page.
- If the user clicks on the “Remember me” option, he should be redirected to the appropriate page on the next login.
- The user should be redirected to an appropriate page for the Forgot password option.
- Forgot Password link should be present on the form.
- The reset button should clear data from all the text boxes in the form.
- The user should be redirected to the Login page if the Login URL is bypassed.
- All the test cases should be separately run for logged In and not logged in user
- Browser compatibility for the search functionality should be verified.
- The User Interface of the page, which shows only one search result or does not give any search results, should be presentable and consistent.
Thank you. I think it will help you.
Below mentioned are some of the functional test cases for a single user login of a web application:
- Verify that user gets validation message if Login button is clicked leaving all fields blank
- Verify that the user gets a validation message if an invalid username and valid password is used.
- Verify that the user gets a validation message if a valid username and invalid password is used.
- Verify that the password field is encrypted.
- Verify that the user can log in successfully if a valid username and password are entered.
- Verify that user if the user is logged in the system using the first browser, if he attempts to log in from the second browser, then he should automatically be logged out from the first browser.
- Verify max length and field validation for different characters in the fields
- Verify that password is not passed as clear text after clicking on the login
- Verify that the password is not saved in clear text in cookies also.
- Verify that cookies are persistent or non-persistent
Hope this helps 🙂
- Log in to the app with valid cred
- When a user already logged in, try to login with same credentials of the user already logged in a different environment as it is expected not to allow the user to log in since a user is already logged in
- Try to login with both invalid creds (UID, PWD)
- Try to login with anyone is wrong, i.e. UIDor PWD
- Go on with field-level, i.e. specific field has to accept specific like if the password is accepting any unknown values which are deviated from the requirement.
|Tasks To Improve Your Knowledge|
|☑️ Basic test scenarios for SSO login authentication||☑️ Test cases for login page Xls|
|☑️ Negative test cases for login page||☑️ Negative test cases for search functionality|
|☑️ Test cases for user profile page||☑️ How to write negative test cases for login page in selenium|
|☑️ Pagination test cases example||☑️ Forgot password test cases|
|Let We Inform you, For improves your knowledge you can take the above as a task and you can work on that. But from the above task list some of the tasks we have already completed and you can find those on our blog. After Completion if you want to share with us that then you can write to us at firstname.lastname@example.org.
In return for that maybe we plan something more surprising for your career.
I hope you have found some valuable information on this post. Feel free to update us, and you can do that by putting the update information in the comment section. Let me know if you need more information or have any suggestions. Then you can comment that in the comment section.