Scribd
Upload
4 views

software_testingfull

The document outlines the necessity and importance of software testing, highlighting its role in ensuring quality, reliability, and security. It details various types of testing, the software testing life cycle, and principles that guide effective testing practices. Additionally, it discusses the differences between validation and verification, as well as the significance of software reviews.

Uploaded by

vishalshinde4511
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
4 views

software_testingfull

The document outlines the necessity and importance of software testing, highlighting its role in ensuring quality, reliability, and security. It details various types of testing, the software testing life cycle, and principles that guide effective testing practices. Additionally, it discusses the differences between validation and verification, as well as the significance of software reviews.

Uploaded by

vishalshinde4511
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Software Testing Questions and Answers

1. Need of Software Testing


Software testing is essential to ensure software quality, reliability, and security. It helps to:
- Detect and fix bugs early.
- Ensure the software meets business and user requirements.
- Improve performance and security.
- Reduce maintenance costs and risks.

2. Importance of Software Testing


Software testing is crucial because:
- It prevents defects before software release.
- It ensures functionality, performance, and security.
- It builds user confidence in the product.
- It reduces the cost of fixing bugs in later stages.

3. Types of Software Testing


1. Functional Testing - Tests the functionality of software based on requirements.
2. Non-Functional Testing - Tests performance, security, and usability.
3. Manual Testing - Executed by human testers without automation tools.
4. Automated Testing - Uses software tools to execute test cases.
5. Regression Testing - Ensures new changes do not break existing functionality.
6. Unit Testing - Tests individual components/modules.
7. Integration Testing - Tests interaction between integrated modules.
8. System Testing - Tests the entire system as a whole.
9. User Acceptance Testing (UAT) - Ensures the system meets business needs.

4. Objectives of Software Testing


- Identify defects and bugs before deployment.
- Ensure software meets business and technical requirements.
- Validate software against functional and non-functional requirements.
- Improve software reliability and security.
- Reduce maintenance and operational costs.

5. Software Review and Its Types


A software review is a process of evaluating software documents and code to improve quality.
Types include:
- Formal Technical Review (FTR) - A systematic evaluation of software.
- Peer Review - Review conducted by colleagues.
- Walkthrough - Informal step-by-step review.
- Inspection - A detailed analysis to identify defects.

6. Role of Formal Technical Review (FTR)


FTR is a structured process to ensure:
- Early detection of errors and inconsistencies.
- Improved software design and maintainability.
- Adherence to coding and documentation standards.
- Increased team collaboration.

7. Software Testing Life Cycle (STLC)


STLC is a step-by-step process for software testing:
1. Requirement Analysis - Understanding testing requirements.
2. Test Planning - Defining scope, strategy, and resources.
3. Test Case Design - Creating test cases and test data.
4. Test Environment Setup - Preparing test environments.
5. Test Execution - Running test cases.
6. Test Closure - Analyzing results and reporting defects.

8. Five Principles of Software Testing


1. Testing shows the presence of defects - It can detect bugs but not prove there are none.
2. Exhaustive testing is impossible - Only selective testing is practical.
3. Early testing saves time and cost - Detecting defects early is cost-effective.
4. Defect clustering - A small number of modules contain most defects.
5. Testing is context-dependent - Different applications require different testing approaches.
9. Fundamentals of Testing
- Software testing ensures software quality.
- It involves both functional and non-functional aspects.
- It helps in preventing defects, not just detecting them.
- It should be conducted systematically and continuously.

10. Difference Between Black Box, White Box, and Grey Box Testing
- Black Box Testing: Tests functionality without knowing internal code.
- White Box Testing: Tests internal logic and structure.
- Grey Box Testing: Tests with partial knowledge of internal code.

11. Types of Integration Testing


1. Big Bang Integration Testing - All modules are tested together.
2. Top-Down Integration Testing - Testing starts from high-level modules to lower ones.
3. Bottom-Up Integration Testing - Testing starts from lower-level modules to higher ones.
4. Hybrid (Sandwich) Integration Testing - Mix of Top-Down and Bottom-Up approaches.
5. Incremental Integration Testing - Modules are tested one by one.

12. Software Testing Process


1. Requirement Analysis - Understanding software requirements.
2. Test Planning - Creating a strategy for testing.
3. Test Case Design & Development - Writing test cases.
4. Test Environment Setup - Configuring test environments.
5. Test Execution - Running test cases and logging defects.
6. Test Closure - Finalizing test results and reporting.

13. System Testing


System Testing verifies the complete application. Types include:
- Functional Testing - Validates system functions.
- Performance Testing - Evaluates speed and stability.
- Security Testing - Ensures data protection.
- Usability Testing - Checks user-friendliness.
- Compatibility Testing - Ensures software works on different platforms.
14. Inception and Walkthrough
- Inception: Initial phase where project goals, requirements, and feasibility are analyzed.
- Walkthrough: An informal review where a document or code is presented for feedback.

15. Difference Between Validation and Verification


- Verification: Ensures the product is being built correctly.
- Validation: Ensures the final product meets user needs.

Conclusion
Software testing ensures that software meets quality, security, and user expectations. A structured
testing approach helps reduce risks and deliver reliable software.

You might also like