Manual Testing Interview Questions - Part 10
In continuation with the latest series of Manual Testing Interview Questions, we present you the part 10 of the course structure. Click on below links for previous parts.
Manual Testing Interview Questions - Part 10
- What is GUI testing?
- GUI Testing is nothing but testing the product or application that uses Graphical User Interface, to ensure that it meets the customer requirement.
- What is Security Testing?
- Security Testing is nothing but to test how well the system protects against unauthorized internal and external access, willful damage etc. In security testing we are finding out the vulnerabilities of the application
- What is Stress Testing?
- Stress Testing is nothing but to test the software beyond its limit. Stress Testing are of two types:
- By Keeping the H/W resources constant and increasing the load of the user.
- By keeping the load of the user constant and gradually decreasing the H/W resources.
- E.g. to test the software using Low Ram, Low Hard Disk, Low CPU etc.
- What is Load Testing?
- Load Testing is nothing but to test the software at its limit. Load testing is mainly performed to find out how much maximum user application can handle without losing the performance.
- What is Soak Testing or Endurance Testing?
- To Test the Software at its limit for a longer period of time e.g. for more than 2 days. The main purpose of Endurance Testing to check the behavior of application if it is under heavy load for a longer period of time.
- What is the difference between Load and Stress Testing?
- In Load testing we are testing the software at its maximum limit. The basic purpose of Load testing to find out how many maximum user applications can handle without losing the performance.
- But in Stress Testing we are testing the software beyond its limit to check the behavior of application when it crosses the maximum limit of user.
- Tell me the difference between functional and system testing?
- In Functional Testing we are testing the functionality of the application while in system testing we are testing the functional as well as non functional aspects i.e. Security, Performance, Installation, Up gradation, etc of the application along with functionality
- What is mean by Ad-hoc testing and exploratory testing? Or what is the difference between Ad-hoc testing and Smoke testing?
- Exploratory testing is nothing but testing the application without having requirements. So here in Exploratory testing first we explore the application and then test.
- Ad-hoc means we know our final target but don’t know how to reach to that target. So Ad-hoc testing is nothing but to test the application with the intention of finding the bugs. This type of testing is carried out without any test cases or test plan.
- Smoke Testing is nothing but testing the main-main functionality of the application to ensure that nothing has been affected and we can go for further exhaustive testing.
- What is Requirement Understanding Document (RUD)?
- When analyst gathers the requirement from the customer, he prepares a document where he puts all the requirements told by the customer, we called this document as Requirement Understanding document. By going through this document customer gets the confidence whether analyst properly understood his requirement or not?
- Explain the testing cycle you will follow if you have 100 test cases in the first cycle... 25 failed and 75 passed. How many test cases you will pick for the second cycle?
- I will pick all the 100 Test Cases in second cycle, to ensure that there should not be any side effect of fixing the bugs on other functionality.
Comments
Post a Comment