This Article Answers Some of The Most Frequently Asked Software Testing Interview Questions. Read This Post to Prepare for Software Testing Interview:
In this post, I am going to answer some of the questions asked by one of the readers Srinivas M.
Q #1) In an application currently in production, one module of code is being modified. Is it necessary to re-test the whole application or is it enough to just test functionality associated with that module?
Vijay: Well, the answer is both. You will have to test the functionality of that module as well as the other modules. It also depends on the module you are modifying.
All the modules should be tested because new changes might have an impact on the other modules as well. You can, therefore, differentiate by the stress given on the module which is to be tested.
I think this scenario will explain the answer to your question well.
If Module A is modified, Module B is depending on module A, and Module C is a general module independent of module A.
In this case, you will first test the module A in depth. Your next stress will be on the module B. But what about module C? This module will be tested as well but with less stress, because module C does not depend on module A for its functioning, rather it depends on module B.
If you are a white box tester, you must be knowing which modules are to be tested and which ones can be affected. But in case you are a black box tester, you will be required to do Regression Testing as well.
Regression tests should be carried out on only those modules associated with the modified module.
Q #2) What is the most challenging situation you have faced during testing?
Vijay: A very good question indeed! A few years back, when I had switched my job, I had been asked the same question by my interviewer. A perfect answer to this question usually depends on the challenges experienced by an individual.
Software Testing has a lot of challenges both in the Manual as well as in Automation.
Discovering a bug that was difficult to be found out could be the answer to this question. It was quite challenging for me. Fixing these un-reproducible bugs can be difficult but is often possible.
Always keep in mind that whenever you are answering such a question, be realistic and don’t stress. Do not let anyone dull your sparkle. Just be yourself.
Q #3) What are you going to do if there is no Functional Spec or any documents related to the system and developer who wrote the code does not work in the company anymore, but you have a system and need to test?
Vijay: It is, unfortunately, one of the typical situations in Indian companies because of the high attrition rate.
In this case, you need to do the Exploratory Testing of the product. It is about exploring, finding out about the software, what it does, what it doesn't do, what works and what doesn't work.
In this testing, you will come to know about the system and its basic workflow. In Exploratory Testing, you can also discover ‘blocker’ bugs that are harmful to your system and therefore, protect your system from being crashed.
If you are a white box tester, the next step is to look for different module codes. By this, you will be able to analyze the test cases for different modules and their relations.
If you have any further questions please comment below.