Interview questions for Testing Engineer

Test engineers are the unsung heroes who keep the wheels turning at any generative company. A quality product that does what it says on the box maintains a returning customer base and ensuring that your company is delivering its best to the customers is what test engineers are all about.
So what exactly do test engineers do? In the simplest terms, test engineers create and run quality assurance (QA) operations on products or systems to confirm that they function properly and meet the needs of the final audience. Test engineers also run case-scenarios to determine what problems could arise during the use of the product or system and how these issues can be addressed.

1. What is the difference between static and dynamic testing?

Static testing: During Static testing method, the code is not executed, and it is performed using the software documentation.
Dynamic testing: To perform this testing the code is required to be in an executable form.

2. What are verification and validation?

Verification is a process of evaluating software at the development phase. It helps you to decide whether the product of a given application satisfies the specified requirements. Validation is the process of evaluating software at the after the development process and to check whether it meets the customer requirements.

3. What are the different test levels?

There are four test levels
1. Unit/component/program/module testing
2. Integration testing
3. System testing
4. Acceptance testing

4. What is Integration testing?

Integration testing is a level of software testing process, where individual units of an application are combined and tested. It is usually performed after unit and functional testing.

5. What Test Plans consists of?

Test design, scope, test strategies, approach are various details that Test plan document consists of.
1. Test case identifier
2. Scope
3. Features to be tested
4. Features not to be tested
5. Test strategy & Test approach
6. Test deliverables
7. Responsibilities
8. Staffing and training
9. Risk and Contingencies

6. What is the difference between UAT (User Acceptance Testing) and System testing?

System Testing: System testing is finding defects when the system undergoes testing as a whole; it is also known as end-to-end testing. In such type of testing, the application suffers from beginning till the end.
2. What are the different methods of testing?
There are three methods of software testing and they are as follows:
• Black-box testing: It is a testing strategy based solely on requirements and specifications. In this strategy, it requires no knowledge of internal paths, structures, or implementation of the software being tested.
• White box testing: It is a testing strategy based on internal paths, code structures, and implementation of the software being tested. White box testing generally requires detailed programming skills.
• Gray box testing: It is a strategy for software debugging in which the tester has limited knowledge of the internal details of the program.

7. What are the different levels of testing?

There are mainly four testing levels and they are:
 Unit Testing
 Integration Testing
 System Testing
 Acceptance Testing
Basically, it starts with the Unit Testing phase and ends with Acceptance Testing.

8. Explain Bug Life Cycle or Defect life cycle?

A defect life cycle is a process in which a defect goes through various phases during its entire lifetime. It starts when a defect is found and ends when a defect is closed, after ensuring it’s not reproduced.
Bug or defect life cycle includes the steps as illustrated in the below figure. If you wish to learn in depth about Bug Life Cycle then you can refer my article on Software Testing Tutorial.

9. What is test coverage?

Test coverage helps in measuring the amount of testing performed by a set of tests.
Test coverage can be done on both functional and non-functional activities. It assists testers to create tests that cover areas which are missing.

10. What is Code coverage?

Code coverage is different from Test coverage. Code coverage is about unit testing practices that must target all areas of the code at least once. It is usually done by developers or unit testers.
Refer Test Metrics.

11. List out Test Deliverable?

1. Test Strategy
2. Test Plan
3. Effort Estimation Report
4. Test Scenarios
5. Test Cases/Scripts
6. Test Data
7. Requirement Traceability Matrix (RTM)
8. Defect Report/Bug Report
9. Test Execution Report
10. Graphs and Metrics
11. Test summary report
12. Test incident report
13. Test closure report
14. Release Note
15. Installation/configuration guide
16. User guide
17. Test status report
18. Weekly status report

12. What is Dynamic Testing?

Dynamic testing involves in the execution of code. It validates the output with the expected outcome.

13. What is White Box Testing?

White Box Testing is also called as 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:
i. Statement Coverage
ii. Decision Coverage
iii. Condition Coverage
iv. Multiple Condition Coverage

14. On what basis you can arrive at an estimation for your project?

To estimate your project, you have to consider the following points:
• Divide the whole project into the smallest tasks
• Allocate each task to team members
• Estimate the effort required to complete each task
• Validate the estimation

15. Which test cases are written first: white boxes or black boxes?

Usually, black box test cases are written first and white box test cases later. To write black box test cases we need the requirement document and, design or project plan. These documents are easily available at the initial start of the project. White box test cases cannot be started in the initial phase of the project because they need more architecture clarity which is not available at the start of the project. So normally white box test cases are written after black box test cases are written.