Printable View
A login screen is there with two edit boxes as user id and password and two buttons ok and cancel.If we enter userid and password correct and click ok we need to go to other web page and it should display as welcome XXX where xxx is the userid we enter.
For this how many scenarios we can write and what are they.
What are important in that .
Hi Arunna,
Firstly it is pertinent that you differentiate Test scenarios from testcases.
A Test scenario is a possible workflow which could comprise of testcases.
For your prescribed Login page, there would be 3 valid scenarios -
1) valid Login
2) Invalid Login
3) Negative Testing scenario
I would categorize all 3 as important. Based on these scenarios you could develop tsetcases which would describe step-by step actions for testing each of these scenarios.
Just to Highlight, when I state Negative scenario seperate from Invalid Login, I do so because When User enters incorrect user ID and password, system is expected to prompt you with an error message.
But a negative testing scenario would be where you are trying to break the application - For Instance
1) leaving Password blank,
2) trying to navigate using the URL,
3) using the forward button of the IE bypassing the Login page etc.....
Cheers
Hi ,
Thanks for a very detailed answer.
But they have asked the important scenarios?
And we need to check also the webpage after clicking ok button as whether it is displayed as "welcome xxx" where xxx is userid.
Thanks & Regards
Aruna
[QUOTE=bizzzzzare;21549]Hi Arunna,
Firstly it is pertinent that you differentiate Test scenarios from testcases.
A Test scenario is a possible workflow which could comprise of testcases.
For your prescribed Login page, there would be 3 valid scenarios -
1) valid Login
2) Invalid Login
3) Negative Testing scenario
I would categorize all 3 as important. Based on these scenarios you could develop tsetcases which would describe step-by step actions for testing each of these scenarios.
Just to Highlight, when I state Negative scenario seperate from Invalid Login, I do so because When User enters incorrect user ID and password, system is expected to prompt you with an error message.
But a negative testing scenario would be where you are trying to break the application - For Instance
1) leaving Password blank,
2) trying to navigate using the URL,
3) using the forward button of the IE bypassing the Login page etc.....
Cheers[/QUOTE]
Hey Arunna,
Incase you really categorize, the important scenarios would be Valid Login and Invalid Login.
Also the part of checking whether the next page display "Welcome XXX' would be covered as part of a testcase and not be listed as a seperate scenario.
The testcase could be something like - On detail level :
[U]TestStep Description[/U]
Enter UserID abc Expected - The entered text should be displayed in the UserId field
Enter Password pertinent to UserID abc Expected - The entered password should be displayed as masked characters in Password field
Click on Login button Expected - System should validate the entered UserID and password credentials and should display the next page. Page should display title as "Welcome" appended to entered user ID.
Cheers.
Thankq for the reply.
Hi Umesh,
As you said if on invalid user name or password system is supposed to throw an error message. But still by testing the system for invalid username and password we are trying to break the system. same is the case with mandatory fields(user name and Password) missed out. In this case also you are expecting a system to throw an error message. How come you differentiate both of them stating one as Invalid Login and the other as Negative scenario. By giving the invalid user name and password as invalid Log in and not in negative scenario you are terming it as a positive scenario indirectly. So dont you think it is wrong to give invalid user name and password under the positive scenario.
Regards
Thilak