Logout Test Case Template: In this post, we are going to discuss the test cases for logout functionality. Every web app has a user account feature that allows sign in and signs out option and in the previous post, we have to discuss on Login Page test case. When you click on the sign-out link cookies gets deleted and the session is cleared. This way you get to the public pages and secure private pages remain restricted. This is pretty much is the work of the logout link. It redirects you from the private use an only area to the public. Behind the scenes, many small changes happen while you log out.
More Web Test Cases: File Upload Test Case
We are going to take a look at those small changes along with the test scenarios. Few things to consider while testing a logout feature are – security, accessibility and HTTPS support. These are the things that most of the modern web apps require for safe and accessible usage.
Accessibility
- Is the logout link or button easy to use?
- Does the link or button recognizable?
- Is the link or button easy to find?
- Is the link or button for logout accessible for all users?
Security Logs
- Check the logs for the login and logout session.
- Check if the logs contain multiple IPs for single ID at the same time.
- Check if the logs contain a denial of service attack for the login or log out.
- Check if the unauthorized IP makes a request for the log out.
- Check if the log has the suspicious activity.
HTTPS Logout Page
Most of the member areas are secured with HTTPS. However, we have to test the code in both productions and on the release server. So we have to check whether the https remains on both signs in and sign out page. Like the sign in page, it has to be encrypted as well. The HTTPS certificate has to be genuine and should be easy to verify. It should not be expired while using the sign in or sign out. Make sure the security service provider for the HTTPS certification is genuine and supports 128 bit SSL connection.
Here are some of the test cases and scenarios for the logout functionality.
- Make sure app allows single sign off from all the devices.
- Make sure app lets you sign off for multiple accounts.
- Does the app clear cookies after sign off?
- Does the app clear the session for the user after sign off?
- Does the app remember the username after signoff?
- Does the app take more time for signoff at different connection speeds?
- Is the sign off link easy to find?
- Is the sign off link or button easy to click?
- Is the sign off link or button positioned as per specification?
- Is the sign off button or link readable?
- Does the power outage retain the session if not signed off?
- Does the sign off functionality require face recognition or fingerprint (in case of desktop app)?
- Does the sign off page redirects to the page where it allows login?
- Does the sign off page allow redirection to the home page?
- Is sign off page going to remove the window or tab automatically? (If it’s bank account sign off link)
- Does the sign off button or link work on all devices?
- Is sign off button or link broke after clicked?
These are some of the test cases you can use for testing the sign-off or the logout functionality of the web-app. If it’s a desktop app then the working would be slightly different and the test cases will be different too. Hope this post helps you answer some of the questions related to the manual testing interview. Do let me know if you can think of additional test cases. I’d appreciate if you share the post on social media.
Leave a Reply