Software Testing and Manual Interview Questions and Answers – Part 2
1) What is a Regression Testing?
Regression testing is a type of testing performed on the previous working functionality, to find out any issues that may have got introduced by newly adding or updating the application code base.
Read more about Regression Testing here.
2) When do we go for Automation Testing?
When the given application is functionally Stable and has ample time for the resources for creating the automated testing, then only we can opt for Automation Testing.
And also, one more major thing to consider for Automation Testing is ROI (Return on Investment). i.e. Whether the time spent by the resources in creating the automation scripts, can reduce their Test Execution time in future.
3) Why Automation Testing if the application is functionally Stable?
- To reduce the time taken for Testing the Application and thereby helping the testing resources in providing th ample time to focus on the required Testing tasks.
- On a Larger Run, the running cost of a Project can be reduced.
4) What are the Different models you are aware of in SDLC?
The below are the different SDLC models:
- Waterfall model
- V model.
- Incremental or Iterative model.
- RAD model.
- Agile model.
- Iterative model.
- Spiral model.
- Prototyping model.
- Big Bang Model
5) What is the Difference between Black-box and White-box testing?
Black-box testing is a type of testing in which internal architecture of the code is not required for testing. It is usually applicable for system and acceptance testing.
In simple terms, Black Box Testing is performed to test the visual functioning of the software without looking into its internal code structure, design and implementation.
Read more about Black Box Testing here.
Whereas White-box testing requires internal design and implementation of the application code being tested. It is usually applicable for Unit and Integration testing.
In simple terms, White Box Testing is a type of Software Testing, which tests the internal code and program structure of the Software.
Read more about White-box Testing here.
6) What are Different Types of Software Testing?
The are many different types of Software Testing. The below are few types:
- Unit Testing
- Integration Testing
- Functional Testing
- System Testing
- Stress Testing
- Performance Testing
- Usability Testing
- Acceptance Testing
- Regression Testing
Complete list of Software Testing Types – Click here
7) What is Re-Testing?
Re-Testing is a type of testing performed to check the test cases that were failed in the earlier execution causing defects, after they got fixed by developers.
In simple terms, Retesting is a type of testing which is performed to verify whether the defects reported earlier are fixed by the developer.
Read more about Retesting here.
8) What is Smoke Testing?
Smoke Testing is a testing technique that is inspired from hardware testing, which checks for the smoke from the hardware components once the hardware’s power is switched On.
Similarly, in Software testing context, smoke testing refers to testing the basic functionality of the build before proceeding further.
In order to perform Smoke testing we identify the basic test cases from each & every module to check crucial functionality present in the application. If these Tests fail, build is declared as unstable and it is NOT tested anymore until the smoke test of the new build passes.
In simple terms, Smoke Testing is a type of testing in which only the major or critical functionalities of the software are tested on the provided build before moving to the detailed testing phase.
Read more about Smoke Testing here.
9) When do we perform Smoke Testing?
Smoke Testing is done on Each & Every Build with an intention of accepting or rejecting the build. This testing is done as the first stage of testing even before we start of the detailed testing.
In simple terms, Smoke Testing is a type of testing in which only the major or critical functionalities of the software are tested on the provided build before moving to the detailed testing phase.
Read more about Smoke Testing here.
10) What is Sanity Testing?
Sanity testing is a kind of Software testing performed after receiving a software build, with minor changes in code, or functionality, to certain that the bugs have been fixed and no further issues are introduced due to these changes. The goal is to determine that the proposed functionality works roughly as expected. If Sanity test fails, the build is rejected to save the time and costs involved in a more rigorous testing.
In simple terms, Sanity Testing is performed to verify whether the minor bug fixes or minor changes (which are done on the stable software) are working fine, by only verifying the changed functionality and its related functionality in depth.
Read more about Sanity Testing here.
Please leave your questions/comments/feedback below.
Happy Learning 🙂
Connect to me on Linked In (Click here)
On a mission to contribute to the Software Testing Community in all possible ways.
