Manual testing Interview Question

This Page contains links to the Questions asked by the Reader's and as well as Question's written by the Author.

1. Manual Testing: Question and Answer (Part 1)

Manual Testing Interview Question and Answer

       1.) What is the difference between Sanity and Smoke testing

       2) What is the difference between Load and Stress Testing?

1. What is the difference between Sanity and Smoke testing?

Sanity Testing: Sanity testing is also known as mini regression testing. Sanity testing is done when you get a release after your bug fixes and that bug has impact on other module as well then we perform sanity testing to make sure that other module is working fine.

Smoke Testing: Smoke testing is done in the beginning when you get the release for the first  time then we perform smoke testing to verify that is the system is ready to go into testing phase or in other words we can say that it is done to verify that if the build is ready for testing.

2. What is the difference between Load and Stress Testing?

Load Testing: Load testing is done to find out the response of the application under heavy load.

Goal:  Goal of load testing is to find out the response of the application under heavy loads.

Example: If your application can handle the load of 1000 user then, in load testing you will test that what will the response of your application when this load is increased. You can use different scenarios in that like observing the response when the load is static means all the user login at the same time, observe load when the load is increases. These are few scenarios whereas in actual we can use different scenarios for getting the response.

Stress Testing: Stress testing means observing the response of the application when the load is increased up to the limit when your application gets crashed.

Goal:  Goal of load testing is to find out how your system will behave when it will fail. The purpose of this testing is to make sure that even if your application gets crashed then also it should not compromise on the security front.

Example: If your application can handle the load of 100 users then execute your test with more than 100 users until your application gets crashed and then see the how it fails, Does it fail smoothly and able to recover? These are the few things which we need to do while doing stress testing.

Domain Knowledge and Software Testing

Domain Knowledge and Software Testing

Many times we have heard this sentence that Domain knowledge is important or not for a software Tester.

Recently one of my friend called me asked me that how important it is to have domain knowledge for testing?

This is what I told her:

Yes it is important to have domain knowledge but it does not mean that you need to be an expert of a particular domain. You can still test the Application if you have not worked earlier in a particular domain.

What I have experienced in my testing carrier is that it is important to have domain knowledge but it is just one skill out of other skills which are required for doing testing.

Skill Required for Software Testing:

There are many skills which are required in a candidate like:

Technical Skills (Testing)

Logical Thinking

Domain Knowledge

Programming knowledge (for automation)

Communication skill

Note: The list may include some other skill too

So if you are not expert in one of the skill then that is not a blocker; it’s just that you will have to work on that particular area. So if a candidate is having good technical testing skills then he/she can test the application with a little assistance.

How to Start Testing if you don’t have domain Knowledge:

I have worked in e-learning and payment domain and when I joined the organization I was not having any knowledge about these domains but I have done the good work; I learn about these domain after joining the organization; did lots of search and worked on the assigned project; So basically if you are new to particular domain then you will have to put the effort to learn that domain So it’s not something without which you can not do the testing.

Besides all these things when you get a project for testing then we get the Requirement document and from that document you can write you test cases for testing the functionality of the application and while you prepare your test cases you can learn the domain from different sources like document available in the company; search in Google; communication with the team members, business analyst etc.

Thanks Harish for reviewing the article