Diff. b/w session issues anf functionality issues
Hi frens ! While testing an application manually I found some issues. But I was told dat they come under session issues and we are doing functionality testing.
Can anyone clear this doubt of mine regarding the difference between session issue and functionality issue with an example..
Thanks & Regards,
Saurabh Garg
Last edited by saurabh garg; 12-06-2007 at 06:45 AM.
Re: Diff. b/w session issues anf functionality issues
Hi Saurabh,
Every web application would have something called as Session for every User which would be marked uniquely by Session ID and Session timeouts. Whenever testing a web-based application, keeping the session timeout clause is very important.
Any issue we find that is directly or indirectly related to Session timings / variables would be called as Session Issues. We generally do not log these.
Example
In my Web-application that I was testing, Incase I left the application Idle for say 20 mins, there would be no apparent change in the UI of the application. But whenever I clicked on any button or field in the application, system would display an error page - "A General Error has Occured".
I could not log this as a functional defect as the functionality works perfectly as long as the session is active. This would be called as Session Issue.
A few other instances could be -
Application Logging out automatically once Session timing expires.
System displaying error message on functionalities working incase application is idle for Long time.
List Boxes or Combo boxes being displayed as empty without data incase application is left idle for specified time.
We could ascertain the session based information and carry out positive testing to ensure that it is followed as per specifications.
Cheers.....
Last edited by bizzzzzare; 12-06-2007 at 06:59 AM. Reason: Better Readability
Hi Saurabh,
Session is a time period or state in which the system is active. For example, the time period for which the web page is in active state when it is left undisturbed. For example if you are doing a Net Banking, if you are not accessing your accounting page for more than 5 minutes the page will become in active. In this case the period in which the page is active is the session time. When the session out happens none of the functionalities in the application will throw out error. So while testing a session you will be checking how long the application is active or the duration of the session state.
Where as in the Functionality testing you will be testing all the functionalities of fields like button, combo box, text box etc, that appears in the application. You will be testing whether all the fields are functioning as per the requirements.
You cannot perform the functional testing when the session failure happens.
Session issues are just how we identify user, nothing else.Originally Posted by saurabh garg
If user session get exipired very soon it is not functionality bug but it is session issue.
If user is not able to login then it is session + functionality issue, which should resolved on priority.
Regards,
Brijesh Jain
---------------------------------------------------------
Connect with me on Skype: jainbrijesh
Google Plus : jainbrijeshji
very nice info.......this forum is very useful for fresher in testing.......
specail thanks for sri,bizzzare and jainbrijesh
Posting Permissions
Reply With Quote