In this article, we discuss test cases for account deactivation. These days many webapps are offering the account removal feature for every user. Some webapps also offer personal data removal from the system. Some apps don’t offer the account deactivation for the user. In such case only the administrator can delete the user account and data. In this article, we are going to discuss some of the test cases for webapps that offer account deactivation feature.
There are few things to consider before we let users to deactivate their user account. Here are some questions that your quality assurance team should pay attention to.
- Why are users interested in removing their profile?
- Do users want to remove their personal data?
- Does system allows them to remove their personal profile and data?
- What information we are collecting from the users who are removing their profile?
- Do we give them a choice to reactivate their profile?
- Do the system retains data of user if they reactivate?
Once you answer these questions, you get the idea why the users want to remove their personal data and deactivate account. Based on that information we get the idea to effectively implement the account deactivation feature. Each webapp these days offer the system to removal of data. Also such feature has simple remove account feature. However you may find that social network like facebook don’t easily remove your data. So in such case you should focus more on the features that allow users to retain privacy while removing their account.
Take a look at Facebook deactivation dialog box.
Here are some of the test cases for the account deactivation.
- Does the system offer any form of email confirmations?
- Does the user loses data after removal of the account?
- Does the user gets back the data after reactivation?
- Is the feature irreversible or permanent?
- Does the account deactivation same as uninstalling or removing the app? (In case of android app)
- Do other people get to access the profile after removal? (In case of social network)
- Does the deactivation purges past data?
- 8. Is it possible to deactivate someone’s account by security leak?
- Does the administrator or moderator has privillege to deactivate others account?
- Does the deactivation feature requires two step authentication?
- Does the deactivation feature requires password verification for action?
- Does the deactivation feature asks for user intent behind action? (As in user is accidentally doing it or purposefully)
- Is it possible to deactivate accidentally?
- Is it possible to recover account if deleted accidentally?
- Does the system offers confirmation after deactivation?
- Does the system offers some confirmation before activation?
- Does the system allows registering the user account with same name and email?
- Does it require calling customer support to reactivate?
- Does the system offers information about what happens after deactivation?
- Does the support has FAQ on account deactivation?
- Does the support handles account deactivation issues?
- Does the data retention possible if security leak leads to account hacking?
- Does the user get to permanently remove the personal information?
- Does the account deactivation process checks for security leaks?
- Does the account deactivation removes the username from the system?
These are some of the test cases for account deactivation for profile system. Some webapps have different type of feature sets that gets deactivated. For example deactivation on facebook only means that users activity is restricted and others can’t access the profile. In such case facebook has different user account deletion which removes data from the account. So for some webapp account deletion and deactivation are not exactly the same features. I hope you find these test cases useful. If you have any other test cases and suggestions in mind then feel free to suggest in the comments. I’d appreciate if you share the post on social media. 🙂