2 Marks Answers
1. What is Debugging?
Debugging is the process of identifying, analyzing, and fixing errors (bugs) in a software
program after they are detected during testing.
2. What is Verification?
Verification is the process of checking whether the software is being built correctly
according to specifications without executing the program.
3. Define Software Review
Software review is a systematic examination of software documents, design, or code to
detect errors and improve quality.
4. Define Regression Testing
Regression testing is the process of retesting the software after changes or modifications to
ensure that existing functionality still works correctly.
5. What is Dynamic Testing?
Dynamic testing is a testing method where the software is executed with test cases to
check its behavior and output.
6. Explain terms – Fault and Error
• Fault: A defect or mistake in the software code or design.
• Error: A human mistake that leads to incorrect results in the software.
7. Explain Types of Acceptance Testing
1. Alpha Testing – Done by developers or testers at the developer's site.
2. Beta Testing – Done by real users at the customer's environment.
8. What is Static Testing?
Static testing is the testing of software without executing the program, such as reviews,
inspections, and walkthroughs.
9. What is Gray Box Testing?
Gray box testing is a technique where the tester has partial knowledge of the internal
structure of the system.
10. What is Alpha Testing?
Alpha testing is testing performed by developers or internal testers at the development
site before releasing the software to customers.
11. What is Software Testing?
Software testing is the process of evaluating a software application to identify defects and
ensure that it meets specified requirements.
12. What is Structural Testing?
Structural testing is also called White Box Testing, where testing is based on the internal
structure, code, and logic of the software.
13. State the Advantages of Manual Testing
• Easy to perform without automation tools
• Suitable for exploratory and usability testing
• Cost-effective for small projects
• Human observation helps detect UI issues
14. Define Validation Testing
Validation testing ensures that the software meets the user needs and requirements.
15. Define Unit Testing
Unit testing is the process of testing individual components or modules of software
separately.
4 Marks Answers
1. Explain Testing Fundamentals
Testing fundamentals include the basic concepts of software testing:
1. Testing shows presence of defects
Testing can show errors but cannot prove that software is completely error-free.
2. Exhaustive testing is impossible
Testing every input and condition is impossible, so selective testing is done.
3. Early testing
Testing should start early in the software development process.
4. Defect clustering
Most defects are found in a small number of modules.
5. Pesticide paradox
Running the same tests repeatedly eventually stops finding new defects.
6. Testing is context dependent
Different applications require different testing techniques.
2. Explain Black Box Testing
Black box testing is a testing technique where the internal structure of the program is not
known to the tester.
Features
• Tests functionality of the software
• Focuses on inputs and outputs
• No knowledge of internal code required
Techniques
• Equivalence Partitioning
• Boundary Value Analysis
• Decision Table Testing
• State Transition Testing
Advantages
• Easy to perform
• User perspective testing
• No programming knowledge required
3. Explain Software Testing Process
The software testing process includes the following steps:
1. Requirement Analysis
Understand requirements and identify testable areas.
2. Test Planning
Prepare test strategy, schedule, and resources.
3. Test Case Design
Create test cases and test data.
4. Test Environment Setup
Prepare hardware and software environment.
5. Test Execution
Run test cases and record results.
6. Defect Reporting
Identify and report bugs.
7. Test Closure
Evaluate testing process and prepare reports.
4. Difference Between Verification and Validation
Verification Validation
Checks whether software is built correctly Checks whether correct software is built
Done without executing code Done by executing software
Uses reviews and inspections Uses testing
Early stage activity Later stage activity
5. Explain Software Testing Life Cycle (STLC)
Stages of STLC
1. Requirement Analysis
2. Test Planning
3. Test Case Development
4. Test Environment Setup
5. Test Execution
6. Test Cycle Closure
Simple Flow
Requirement Analysis
↓
Test Planning
↓
Test Case Design
↓
Environment Setup
↓
Test Execution
↓
Test Closure
6. Explain Integration Testing with its Types
Integration testing is the process of testing combined modules to check their interaction.
Types
1. Top-Down Testing
Testing starts from top-level modules and moves downward.
2. Bottom-Up Testing
Testing starts from lower modules and moves upward.
3. Sandwich Testing
Combination of top-down and bottom-up testing.
7. Explain Testing Principles
1. Testing shows presence of defects
2. Exhaustive testing is impossible
3. Early testing saves time and cost
4. Defect clustering occurs
5. Pesticide paradox
6. Testing is context dependent
7. Absence of error fallacy – Software without errors may still be unusable.
8. Explain Acceptance Testing
Acceptance testing is the final level of testing performed to verify whether the software
meets user requirements.
Objectives
• Validate system functionality
• Ensure readiness for deployment
• Confirm customer satisfaction
Types
1. Alpha Testing – Done at developer site.
2. Beta Testing – Done by users at their location.
3. User Acceptance Testing (UAT) – Done by the customer to approve the syste