I have always encountered a lot of fights when I test the back button. Many of them say its required only in the usability tests. Some of them claim it is 'OUT OF SCOPE'. I feel as a tester or a quality analyst you have to test the back button for all instances.
Lets explain why?
Usability Answer.
From the usability perspective and according to various surveys most of the online users is used to press the back button on the browser or press the backspace key on the keyboard. Users are used to such a scenario and we are not allowed to stop the user one fine morning saying "Hey don't use back button it will cause many issues to my application". So the option lies to the developer to disable it. I can understand for a finance or banking application using back button might create chaos, so warn the user or disable it. But for a shopping user back button is an easy mechanism for him to traverse and u cant stop it except for payment pages. So I believe the usability answer gives some solution to our viewpoint.
Functionality Answer.
Many a times functionality is affected while back button testing is done. Lot many times I have observed the login is affected when back button is pressed immediately after the user logging in. Also a lot of issues while during checkout for back button traversing. Majorly I have found this for online shopping websites. These instances affect the basic requirements of the application and thus black box or functionality fails.
Security or penetration testing.
This was one of the most interesting instance where back button really increased the bug count for me in various projects.
Some instances.
1. Able to send a request for forgot password for a logged in user.
2. The logged in user seems to be logged out and when the user tries to login again the system issues an error.
3. able to manipulate and play with jsessionids on all instances of back button.
These are some of the core problems (we call bugs) we might face along with the back button. Either tackle it or avoid.
So never give up when developers say that back button is not be tested, go on and show your testing skills all over it. Also make sure your test the backspace key too. Thanks to my developers who gave me a chance to write this blog.
Happy bugging ..... :)
Lets explain why?
Usability Answer.
From the usability perspective and according to various surveys most of the online users is used to press the back button on the browser or press the backspace key on the keyboard. Users are used to such a scenario and we are not allowed to stop the user one fine morning saying "Hey don't use back button it will cause many issues to my application". So the option lies to the developer to disable it. I can understand for a finance or banking application using back button might create chaos, so warn the user or disable it. But for a shopping user back button is an easy mechanism for him to traverse and u cant stop it except for payment pages. So I believe the usability answer gives some solution to our viewpoint.
Functionality Answer.
Many a times functionality is affected while back button testing is done. Lot many times I have observed the login is affected when back button is pressed immediately after the user logging in. Also a lot of issues while during checkout for back button traversing. Majorly I have found this for online shopping websites. These instances affect the basic requirements of the application and thus black box or functionality fails.
Security or penetration testing.
This was one of the most interesting instance where back button really increased the bug count for me in various projects.
Some instances.
1. Able to send a request for forgot password for a logged in user.
2. The logged in user seems to be logged out and when the user tries to login again the system issues an error.
3. able to manipulate and play with jsessionids on all instances of back button.
These are some of the core problems (we call bugs) we might face along with the back button. Either tackle it or avoid.
So never give up when developers say that back button is not be tested, go on and show your testing skills all over it. Also make sure your test the backspace key too. Thanks to my developers who gave me a chance to write this blog.
Happy bugging ..... :)
Tackling is the right way to go. Even with banking applications, I haven't encountered one where back button is disabled here in the UK.
ReplyDeleteYep I would always agree the 'tackling' one. But there would be developers or even PO (product owner -agile) questioning the back button functionality saying
ReplyDeleteBack button never initiatives the server call as it only deals the cache. But i would recommend a big no as it os a back button is a necessity. Now its the stakeholders and POs call on whether to initiate a server call or not. There are occassions where some clients insist on disable the back button functionality or give an indication to the user back button should not be used to tackle the risk component.