Functional test cases of login.

khyati sehgal
May 16, 2014
3 min read

Cracking an interview is not a Rocket Science to be frank , but yes for some it could be 😀

Lets talk in general , what is the expectation of an interviewer from an interviewee. Interviewer just want the best answer which is unique and different from the rest of the world. Err…What does that mean ?

For each answer, there should be an approach that a tester should mention while answering any question. And that is Always Start With Positive approach .!!

Be it writing test cases, or reading requirements, executing test cases, thinking of a scenario in testing,etc

Lets discuss how can we take an approach of writing test cases with an example which is asked in almost all QA – interviews.

How to design test cases for Log-in functionality..?
This is easy .. no ?

Let’s try to think in a broader and better way.

Start with open questions :

Why, on earth, the user needs to log into any system?
Why he would go for login if:.. he is new to the web ?
What he will miss if he does not log into the system?
Why log is required to anyone?
What process he has to go through if he opts for logging in?
What is the process to log into the system?
What credentials are required to get into the system?
What all basic information check is required to authenticate a user?

Service-oriented tests

Now go more into depth and think more about the architecture as in how MVC will work in this case as login is all- web-based and service-oriented process. So try applying Service Oriented Architecture Concepts:

How service-oriented tests can be applied to login?
How session will be maintained when the user logs into the system?
How session will be maintained when the user logs out from the system?
How session will be maintained when users switch logging in and out from the system?
How the system will behave when the user opens a new tab, after logging into the system?
What kind of response is expected when the submit button is hit by the system?
What all testing approaches you can apply, try thinking as much as you can and categorize your test cases?

Boundary values:

Check length of user name.
Check length of password.

Equivalent partition

Create a group of test cases including positive cases.
Enter the correct user-id and password and click on submit button
It should display welcome page

And negative cases:

Enter the correct user-id and wrong password and click on the Submit button.
It should display an error.
Enter the wrong user-id and correct password and click on the Submit button.
It should display an error.

COMPATIBILITY TESTING

Check application should work on different Operating systems.
Check application should work on different browsers.

Comparison Testing

Check application should work on different resolutions.

Usability Testing

Check the autofocus of mouse.
Mouse autofocus should be at UserId.
Check the password with Lower case and upper case.
The password should be case sensitive.
Check the autofocus of mouse.
Mouse autofocus should be at UserId.

Security Testing

After login with valid credentials, click on back button.
The page should be expired.
After login with valid credentials copy the url and paste in another browser.
It should not display the user’s welcome page.
Check the password with Lower case and upper case.
Password should be case sensitive.

And others could be :

Integration Testing

Test the log in functionality when all the other web pages are made and completed.
Click on next after log in , then a session should be maintained.
Now other functionalities should also work along with the log in when integrated with log in.