- Get link
- X
- Other Apps
Beginners Level Software Testing Interview Questions
What are the phases involved in Software Testing Life Cycle?
Different phases involved in Software Testing Life Cycle. They are given below:- Test Planning
- Test Case Development
- Environment Setup
- Test Execution
- Test Cycle Closure
Test Planning: Test strategy is defined.
Test Case Development: In this phase, Detailed test cases are defined and developed.
Environment Setup: It is the setup of software and hardware for testing teams to execute the test cases.
Test Execution: A process of Executing the test cases and meanwhile comparing the expected and actual result.
Test Cycle Closure: It is conducted by calling the testing team, meeting & evaluating cycle completion criteria based on test coverage, quality, cost, time, critical business objectives, and software.
What are the different methods of Software Testing?
There are 3 methods of software testing, which are as follows:
- Black Box Testing
- White Box Testing
- Grey Box Testing
Black Box Testing: It is testing based on complete requirements and specifications, It requires knowledge of internal paths, structures, or implementation of software being tested.
White Box Testing: It is testing based on internal paths, code structures, and implementation of the software being tested. White box testing generally requires detailed programming skills.
Grey Box Testing: It is a testing strategy for Software debugging in which the tester has limited knowledge of the internal details of the program.
What are the different Levels of Testing?
There are four levels of testing.
- Unit Testing
- Integration Testing
- System Testing
- Acceptance Testing
Explain the Bug Life Cycle or Defect Life Cycle?
A Defect Life Cycle is the process of finding the defect first and open when it is close after fixing the defect, after ensuring it's not reproducing.
A Bug or Defect Life Cycle includes the steps as illustrated as follows:
What are the Categories of Defects?
We have 3 main categories of Defects:
Wrong: It implies that requirements have been implemented incorrectly. It is a variance from the given specification.
Missing: It is a variance from the specifications, an indication that a specification was not implemented, a requirement of the customer was not noted properly.
Extra: It is a requirement incorporated into the product that was not given by the end customer. It is always a variance from the specification but may be an attribute desired by the user of the product.



Comments
Post a Comment