Positive Scenario and Negative Testcases
Can somebody give answer for below question which I have been asked in the interview
Login Module :
1. 1 Positive Scenario and 2 Negative Testcases
2. 1 Negative Scenario and 2 Positive Testcases
Thanks in advance...
I don't see a question here
Interviewer asked me to write the Testcases for Login Module,
He asked that :
1. What is the Positive Scenario for Login..? and Write 2 Negative Testcases for it.
Similarly 2. what is the Negative scenario..? and write 2 Positive Testcases for it.
Pl let me know if you need more details..
And what were your answers?
1) Positive Scenario : Valid uid , Valid Pwd
Negative Test cases : Out of range (uid), Out of Range(pwd)
2) Negative scenario :I dint not find
Negative Test cases : I did not find
I'm confused by the term negative scenario. I see scenarios as definition of expected behaviors, no positive or negatives. When I think of use case scenarios, I don't know what makes them positive or negative. You'll have to give me an example of a 'negative scenario' in your context.
Say I have the following use case scenario...
As an unauthorized user, if I enter an invalid login, then I should not be allowed a login, and receive an error message saying I entered an invalid login.
To me, I see this as I don't see this as positive or negative. But from this, there's a number of negative test cases.
Negative scenario with positive testcases
Negative scenario with positive testcases:
Scenario :Login with invalid username and pwd and withut giving uId and PWD
For Invalid Username & Pwd - should prompt message saying Username/Pwd is invalid
For With out givng UID/PWD - should prompt message saying enter Username/Pwd
1.Positive Scenario - Enter valid username/password and verify the login.
2.Negative Testcases - Enter valid UN and Invalid PWD and verify the login.
Enter Invalid UN and Valid PWD and verify the ligin.
I'm with David, the terms positive and negative are unnecessarily confusing. SmartBear's website, for example, differentiates them as:
"Positive testing determines that your application works as expected. If an error is encountered during positive testing, the test fails.
Negative testing ensures that your application can gracefully handle invalid input or unexpected user behaviour."
To me, if my application is designed right then these are one and the same - if my application gracefully handles invalid input (a "negative" test) then it works as expected (a "positive" test).
I'd be asking the interviewer exactly what they meant by positive and negative first.
Although, I agree the way the original question is asked by the interviewer is absurd. However, I think it's good to differentiate between a positive & negative scenario from reporting perspective & help understanding business impacts if any production defect occurs.
Here's an example, based on my experience.
Let's assume a critical application with lot of defects & too less time to fix before a production issue. In this scenario (although I agree there can be many different correct answers, but let's look my solution in the context of problem), if I'm the business owner & if I think from customer's perspective to maintain my customer base without facing negative feedback. Below is the list of scenarios I would prefer to fix in the order mentioned.
1. I would not want a customer to place an order with all correct details & see a rejection (Positive scenario)
2. I'm ok, even if a customer placed an order with incorrect details & due to some defect in system the order is not rejected (negative scenario)
To summarize, a positive scenario is an end to end scenario from a customer's perspective, where when a customer places an order with all correct information should go on to completion successfully.
A negative scenario that results in any kind of (valid) rejection to a customer.
Tags for this Thread