10+ Manual Test Engineer Interview Questions and Answers for Freshers

Answers to common questions asked in a Manual Test Engineer interview

• Choose testing field for its importance in ensuring quality software

• Manual testing involves testing software manually without automation tools

• Traditional testing refers to the waterfall model of software development

• Functional testing checks if software meets functional requirements, while non-functional testing checks non-functional requirements such as performance and security

• Severity is the impact of a def...read more

Testing is the process of evaluating a system or component to determine if it meets specified requirements.

• Testing is done to identify defects or errors in software.

• Manual testing is performed by human testers, while automation testing is done using tools and scripts.

• Manual testing requires human intervention and is time-consuming, while automation testing is faster and more efficient.

• Manual testing is suitable for small-scale projects or scenarios that require human judgment...read more

Black Box testing focuses on testing the functionality of the software without knowing its internal code, while White Box testing involves testing the internal code structure of the software.

• Black Box testing is based on external specifications and is performed without knowledge of the internal code.

• White Box testing is based on internal code structure and logic, and requires knowledge of the code.

• Sanity testing is a subset of regression testing, focusing on testing specific ...read more

Software testing is the process of evaluating a software product to find defects and ensure it meets requirements.

• Test engineer is responsible for designing and executing test cases, reporting defects, and ensuring quality.

• Regression testing is the process of testing changes to ensure they do not impact existing functionality.

• Dtt stands for Design Transfer Testing, which ensures that the product design is transferred to production without errors.

• Test case templates are pre-de...read more

Product backlog is a list of all desired work on a project, while sprint backlog is a subset of the product backlog for a specific sprint.

• Product backlog includes all features, bug fixes, enhancements, and other work needed for a project.

• Sprint backlog is a subset of the product backlog selected for a specific sprint.

• Product backlog is constantly updated and prioritized based on business needs.

• Sprint backlog is fixed for the duration of a sprint and can only be changed with t...read more

A test case is a set of instructions or conditions used to determine if a software application is working correctly.

• Test cases are designed to verify specific functionality or features of the software.

• They can be written in a variety of formats, including manual or automated scripts.

• Test cases should be repeatable and cover all possible scenarios.

• They are used to identify defects or bugs in the software and ensure that it meets the requirements.

• Examples of test cases include ...read more

Integration testing is a type of testing where individual units or components are combined and tested as a group.

• It focuses on testing the interactions between different components/modules of a system.

• It ensures that the integrated components work together as expected.

• Examples include testing the communication between a database and a web application, or between different software modules in a complex system.

Sanity testing is a quick and focused testing to ensure that the most critical functionalities of a software application are working correctly after changes.

• Sanity testing is a subset of regression testing.

• It is usually performed after a minor change in the code or functionality.

• The main goal is to verify that the key features of the application are still functioning properly.

• It is not exhaustive and does not cover all aspects of the application.

• Example: After fixing a critic...read more

Smoke testing is a preliminary testing to check if the software build is stable enough for further testing.

• Smoke testing is a subset of regression testing.

• It is performed to verify if the critical functionalities of the software are working fine.

• Smoke tests are quick and shallow tests that aim to catch major issues early on.

• It is usually conducted before more detailed testing like functional testing or regression testing.

• If the smoke test fails, further testing is halted unti...read more

Regression testing is the process of retesting a software application to ensure that new code changes have not adversely affected existing functionality.

• Regression testing is performed after code changes to verify that the existing features still work correctly.

• It helps in identifying any defects introduced by new code changes.

• Automated testing tools are often used for regression testing to save time and effort.

• Regression testing can be done manually as well, by retesting cri...read more

Types of testing include functional testing, non-functional testing, manual testing, automated testing, regression testing, and performance testing.

• Functional testing: Testing the functionality of the software against the requirements.

• Non-functional testing: Testing aspects like performance, usability, and security.

• Manual testing: Testing performed manually by testers.

• Automated testing: Testing performed using automation tools.

• Regression testing: Testing to ensure that new co...read more