NOTE : If you ask how simple is it? it depends😉
Twitter changed the way I communicate. It is simple, sweet, short and faster way to share information.
Recently I started using HootSuite, a social media tool to manage my social networking activities. This has a nice little option to view twitter profiles. On clicking a twitter handle opens a pop up that displays bio, picture options to reply, DM, follow, unfollow and few others. I clicked on my own twitter profile. To my surprise that also has follow, unfollow, DM options enabled. So first tried to Follow myself (a tester in full swing😉 ) got a message “You can’t follow\unfollow yourself” hmm that looks good.
Then, I clicked on Direct Message(DM) to myself and was able to send a DM successfully to myself. I am not sure if this is the correct behavior or is a problem? If it is a problem, where is the problem?
I never tried sending DM to myself from twitter, so next tried to send DM to myself from twitter.
From the Direct Message options, tried sending a DM, it was not allowed.
Next tried with other option available to send DM, home page directly.
Oh! it is possible and the DM delivered to my twitter inbox. So there is inconsistency in handling DM to oneself in twitter. So, it is a problem.
So,as a tester should look for as many details as possible like trying out all possible input and output options at API level, DB levels and UI levels, before logging a bug. That will help report the problem clear thus issue might get fixed faster and better.
Above all, first thing you should do on finding an issue is check if that is already logged. If yes, compare with your observation with those details, and provide information if you feel something is missed out.
Exploring more on this, Twitter help on DM says DM cannot be send to a user who is not following you and there is no mention of DM to yourself. Since I can send a DM to myself but I am not following myself, so does this mean the claim made by twitter that “you cannot send a DM to a user who is not following you” is wrong?
What is your view?
Now your turn to investigate the not so user friendly message.
Below error message was from Windows XP with SP2, this happened while renaming a normal windows folder. As a user what did you understand from this message? And what actions would you perform as a user to solve this problem?
Here is the investigation report of above Windows bug
Click here to see more such bug(?) posts.