Crack QA Interview: QA Interview: Top 80: Manual Testing Interview Questions

Other Useful Links:
Selenium With Java Interview Questions - (01-35)
Selenium With Java Interview Questions - (36-70)
Java Interview Questions for QA (01-50)
Java Interview Questions for QA (51-100)
Java Programs for QA Automation Interview (01-15)
Java Programs for QA Automation Interview (16-30)
TestNG Interview Questions for QA (01-20)
TestNG Interview Questions for QA (21-40)
Maven Interview Questions for QA Automation Interview (01-15)
Maven Interview Questions for QA Automation Interview (16-30)
Most Frequently Asked API Testing Interview Questions (01-20)
Most Frequently Asked API Testing Interview Questions (21-40)

1. What made you decide to pursue a profession in software testing?

I love solving logical puzzles.
I enjoy assisting others.
I enjoy taking on new tasks.
I enjoy coding as well.
I enjoy communicating with others.
I enjoy being part of a team that produces high-quality items.
My work improves the quality of sleep for stakeholders.

2. What is software testing?

Software Testing is a process of identifying correctness, completeness and quality of developed software.

3. Define Quality Assurance and Quality Control?

Quality Assurance:

Quality Assurance involves in process-oriented activities.
It ensures the prevention of defects in the process used to make Software Applications. So the defects don’t arise when the Software Application is being developed.

Quality Control:

Quality Control involves in product-oriented activities.
It executes the program or code to identify the defects in the Software Application.

4. Manual Testing vs Automation Testing

Manual Testing	Automation Testing
Done manually by QA tester	Done automatically using automation tools and scripts
Time Consuming and less efficient	Less time and great efficiency
Initial time investment is comparatively lower	Initial time investment is comparatively higher
Less Accuracy	More Accuracy
Programming knowledge is not required	Programming knowledge is must

5. Manual Testing Benefits and Drawbacks

Advantages:

No environmental limitations.
Programming knowledge is not required.
Recommendable for dynamically changing GUI Testing.
Recommendable for usability Testing.
Human Observation useful to find potential defects.

Drawbacks:

Require more time and more resources.
Less accuracy
Performance testing is impractical in manual testing.
Regression testing in manual way is tiresome.
Comparing large amount of data is impractical.

6. Unit testing

Unit Testing involves testing of each unit or individual component of software application. It is the first level of testing.

7. System testing

System Testing is a level of testing that validates the complete and fully integrated software product.
In this, we navigate through all the necessary modules of the application and check if the end feature works fine and test the product as a whole system.

8. What is Acceptance Testing?

It is also known as pre-production testing. This is done by the end-users along with the testers to validate the functionality of the application.
After successful acceptance testing, formal testing conducted to determine whether an application is developed as per the requirement. It allows the customer to accept or reject the application.
Types of acceptance testing are Alpha, Beta & Gamma.

9. Alpha Testing

Alpha Testing is a Software testing performed to identify bugs before releasing the product to real users or public.

10. Beta Testing

Beta Testing is performed by real users of the software application in a real-time environment. It is performed by a client who is not part of the organization.

11. What is Gamma Testing?

Gamma testing is done when the software is ready for release with specified requirements. It is done at the client place.
It is done directly by skipping all the in-house testing activities.

12. What is Integration Testing?

Integration Testing is the process of testing the interface between the two software units.
Integration testing is done in three ways. Big Bang Approach, Top-Down Approach, Bottom-Up Approach.

13. What is Big Bang Approach?

Combining all the modules once and verifying the functionality after completion of individual module testing.
Top-down and bottom-up are carried out by using dummy modules known as Stubs and Drivers.
These Stubs and Drivers are used to stand in for missing components to simulate data communication between modules.

14. What is Top-Down Approach?

Testing takes place from top to bottom.
High-level modules are tested first and then low-level modules and finally integrating the low-level modules to a high level to ensure the system is working as intended.
Stubs are used as a temporary module if a module is not ready for integration testing.

15. What is Bottom-Up Approach?

It is a reciprocate of the Top-Down Approach.
Testing takes place from bottom to up. Lowest level modules are tested first and then high-level modules and finally integrating the high-level modules to a low level to ensure the system is working as intended.
Drivers are used as a temporary module for integration testing.

16. What is Exploratory Testing?

Exploratory testing as the name suggests is a type of testing in which the simultaneous learning, test design and test execution are done.
We can say that in this testing - analysis, test planning, design and test execution are all done together and instantly.
The testing is about exploring the system and encouraging real-time and practical thinking of a tester.

17. What is ad-hoc testing?

When a software testing is performed without proper planning and documentation, it is said to be ad-hoc testing.

18. Ad-hoc Testing vs Exploratory Testing

Ad-hoc Testing	Exploratory Testing
Informal Testing	Formal Testing
It begins with learning application first and then work with actual testing process	It begins with exploring the application while learning.
Documentation is not needed in this type of testing	Documentation is must in this testing
It works on the negative testing mostly	It works on positive testing niche

19. What is White Box Testing?

White Box Testing is also called Glass Box, Clear Box, and Structural Testing.
It is based on applications' internal code structure. In white-box testing, an internal perspective of the system, as well as programming skills, are used to design test cases. This testing usually was done at the unit level.
Various white-box testing techniques are:

Statement Coverage
Decision Coverage
Condition Coverage
Multiple Condition Coverage

Statement coverage:

It makes sure that each line of source code has been executed and tested.

Decision coverage:

It ensures that every decision (true/false) in the source code has been executed and tested.

Path coverage:

It ensures that every possible route through a given part of the code is executed and tested.

20. What is Black Box Testing?

Black Box Testing is a software testing method in which testers evaluate the functionality of the software under test without looking at the internal code structure.
This can be applied to every level of software testing such as Unit, Integration, System and Acceptance Testing.
Black Box Testing Techniques:

Equivalence Partitioning
Boundary Value Analysis
Decision Table
State Transition

Equivalence Partitioning:

Equivalence Partitioning is also known as Equivalence Class Partitioning.
In equivalence partitioning, inputs to the software or system are divided into groups that are expected to exhibit similar behavior, so they are likely to be proposed in the same way. Hence selecting one input from each group to design the test cases.

Boundary Value Analysis:

Boundary value analysis is based on testing the boundary values of valid and invalid partitions.
The Behavior at the edge of each equivalence partition is more likely to be incorrect than the behavior within the partition, so boundaries are an area where testing is likely to yield defects.

Decision Table:

The decision Table is aka Cause-Effect Table. This test technique is appropriate for functionalities which has logical relationships between inputs (if-else logic).
In the Decision table technique, we deal with combinations of inputs. To identify the test cases with the decision table, we consider conditions and actions.
We take conditions as inputs and actions as outputs.

State Transition:

Using state transition testing, we pick test cases from an application where we need to test different system transitions.
We can apply this when an application gives a different output for the same input, depending on what has happened in the earlier state.

21. Which test cases are written first white or black box test cases?

Black-box test cases are written first.
The prerequisites to start writing black-box test cases are Requirement documents or design documents. These documents will be available before project work start.
The prerequisites to start writing white box test cases are the internal architecture of the application. The internal architecture of the application will be available in designing phase.

22. What is Smoke Testing?

Smoke Testing is done to make sure if the build we received from the development team is testable or not. It is also called as “Day 0” check.
It is done at the “build level”.
It helps not to waste the testing time to simply testing the whole application when the key features don’t work or the key bugs have not been fixed yet.

23. What is Sanity Testing?

Sanity Testing is done during the release phase to check for the main functionalities of the application without going deeper.
It is also called as a subset of Regression testing. It is done at the “release level”.

24. Sanity Testing vs Smoke Testing

Smoke Testing	Sanity Testing
Smoke Test is done to make sure if the build we received from the development team is testable or not	During the release phase, a sanity test is performed to verify the application's main functionalities without digging deeper.
Both developers and testers perform smoke testing.	Sanity testing is done solely by testers.
Smoke Testing simulates the complete process from start to finish.	Sanity testing is limited to a particular component of the whole application.
In Smoke Testing, build may be stable or unstable.	In Sanity Testing, build is comparatively stable
It is done on initial builds.	It is done on stable builds.
It is a part of basic testing.	It is a part of regression testing.
It is usually done every time a new build is released.	It is planned when there is not enough time to do in-depth testing.

25. Static Testing

Static Testing involves reviewing the documents to identify defects in early stages of SDLC.

26. Dynamic Testing

Dynamic Testing involves the execution of code. It validates the actual output with the expected outcome.

27. Positive Testing

Positive Testing is done to determine what the system is supposed to do.

28. Negative Testing

Negative Testing is done to determine what the system is not supposed to do.

29. Regression Testing

Regression Testing is a type of testing to confirm that the recent program or code changes have not adversely affected the existing features.

30. What is Retesting?

Retesting is done to ensure that the defects which were found and posted in the earlier build were fixed or not in the current build.

31. What is Load Testing?
It is to verify that the system/application can handle the expected number of transactions and to verify the system/application behavior under both normal and peak load conditions.
32. Stress Testing
Stress Testing refers to the testing of software or hardware to determine whether its performance is satisfactory under any extreme condition, which may occur as a result of network traffic, process loading, under-locking or overlocking.

33. Performance Testing

Performance Testing is a non functional testing technique that determines how the speed, stability, scalability and responsiveness of an application holds up under a given workload.

34. End to End Testing

End to End Testing is a technique that tests the entire software product from beginning to end to ensure that application flow behaves as expected.

35. What is Usability Testing?

To verify whether the application is user-friendly or not and was comfortably used by an end-user or not.
The main focus in this testing is to check whether the end-user can understand and operate the application easily or not. An application should be self-exploratory and must not require training to operate it.

36. What is Security Testing?

Security testing is a process to determine whether the system protects data and maintains functionality as intended.

37. What is Monkey Testing?

Perform abnormal action on the application deliberately in order to verify the stability of the application.

38. What is Globalization Testing?

Globalization is a process of designing a software application so that it can be adapted to various languages and regions without any changes.

39. What is Test Strategy?

Test Strategy is a high-level document and usually developed by the project manager.
It is a document that captures the approach on how we go about testing the product and achieve the goals.
It is normally derived from the Business Requirement Specification (BRS). Documents like Test Plan are prepared by keeping this document as a base.

40. What is Test Plan and contents available in a Test Plan?

Test plan document is a document which contains the plan for all the testing activities to be done to deliver a quality product.
Test Plan document is derived from the Product Description, SRS, or Use Case documents for all future activities of the project.
It is usually prepared by the Test Lead or Test Manager.