Software testing interview questions
Continuing the previous article (Link), I attached an addition 15 questions that relevant for the“Theoretical” side if testing.
Q1: Explain the “Verification” process
The real question that we need to answer is: Are we building the product right?
The verification process is executed to make sure that each phase of the SDLC cycle (Development, Testing Etc.) is built based on the predefined requirements and specifications (in other we want to make sure that each step is meet the predefined requirements and without any deviation from it).
Q2: Describe different activities of the verification process
- Analysis of different testing aspects (Timelines, Resources, testing tools Etc.)
- Statement, Condition and decision coverage
- Reviews (Technical, documentations Etc.)
Q3: can you provide verification examples for based on “Testing” levels?
Level 1: Unit testing
Verifying the software design implementation
Level 2: Integration
Testing the integrations between all the corresponding components until the software can move to the next level (System).
Level 3: System
Ensuring that the system meets the predefined requirements and specifications (Notice, The validation process is the actual testing that performed while running the code.)
Level 4: Acceptance
Ensure that the system meets the client requirements.
Q4: Explain the “Validation” process
The real question that we need to answer is: Are we building the right product?
The process that allows the tester to evaluate the software after the development stage is done and before the software released to the customer, in this process, we need to ensure that the software is working based on the user needs.
Remember, the validation process embraces the “Dynamic” side of testing, where the actual software is tested and evaluated against the predefined SRS documentation.
Q5: Explain few reasons that lead to software bugs?
There are too many, this list will do the trick:
- Human errors (Design process).
- Human errors (Implementation process).
- Changing requirements while the software is under testing.
- Failure to understand the predefined requirements and specifications.
- Time pressures.
- Poor testing prioritization.
- Migrations between versions.
- Software complexity.
Q6: Explain “Test Procedure”?
A documented algorithm that provides a detailed instructions for how to execute a test case.
Q7: Explain software component?
In its basic, software components are small software items that built from small units that integrated together, examples:
- Stored procedures.
- Functionality of Binary trees.
Q8: Explain “Code” Coverage?
In code coverage, we want to determine which part in code are tested with a dedicated “Test” cases, and which part are not yet executed (And should be…) during the testing matrix. Code coverage allows the project owner to see the testing progress/coverage and get control on the project status.
Q9: Explain “Code” inspection?
Testing technique that determines the quality of the application source code, in this testing process. The engineer that set as the code owner review the code for a group of people that make the inspection with different types of tools, Examples:
- Inspection made to the code logic
- Inspection made to the code Design
- Checklists against the design requirements and specifications
- Different suggestions to improve the inspected code.
- Comparing the code design to the industry coding standards
- Different questions about the issues that that programmer encountered while coding the
Q10: Explain “Code” complete?
Very simple term that relevant to specific phased of the SDLC process, when speaking about “Code” complete, we actually want to say that the code implementation is completed (The entire software functionality is implemented successfully).
In addition, reminder that although the code is fully implemented, there are always new bugs that discovered in the testing cycles/Clients, that doesn’t affect the fact that No more coding is needed based on the original requirements and specifications
Q11: Explain “Code” walk-through?
Don’t confuse with code “inspection”… code “walk-through” is a testing technique that used to review the code implementation by the programmer and the testing team, during this walk through the code is executed with a few simple tests to determine the quality of the code and the code logic.
Q12: Explain software “Debugging”?
The most basic process to search and remove any risks that may cause software errors/bugs.
Q13: Explain “Emulator”?
Any object (System/Software) that simulate the same behavior of the original software, using emulators, we can use the same inputs that used to test the original software and examine the outputs (should be the same results as the original software).
Q14: Explain software “Specifications”?
Specifications comes from the customer needs, in the first interaction the customer provides few requirements that translated into high detailed design that will use by the engineering team.
Stage 1: Requirements
Stage 2: Analyze and investigation
Stage 3: Requirements translated into specifications.
Q15: Explain “Coding”?
Any programing activity that generates a source code.