CHAPTER 1 – Introduction to Software Testing and Quality Assurance

Q11. Define Software Testing and Quality Assurance (QA). How do they differ in purpose
and scope?
📘 Source: “What is Software Testing?” & “What is Quality Assurance (QA)”
“Software Testing is the process of evaluating a software product or application to detect errors,
gaps, or missing requirements compared to the expected outcome.”
“Quality Assurance (QA) refers to the set of activities designed to ensure that development and
maintenance processes are adequate to produce high-quality software.”
Difference:
 Testing: Detects defects in products.
 QA: Ensures processes prevent defects.

Q1. Discuss three common reasons why software projects fail in terms of testing and QA
practices.
📘 Source: “Why Software Testing and QA Matter”
1. Late QA Involvement – Testing at the end leads to undetected major defects.
2. Poor Requirements – Unclear requirements cause incomplete or wrong tests.
3. Lack of QA Processes – No defined standard or documentation causes inconsistent
outcomes.
QA prevents costly post-release failures.

Q12. Why is software quality important in today’s technology-driven world? Provide at

least three justifications.
📘 Source: “Why Software Testing and QA Matter”
“Errors can lead to financial loss, legal issues, and damage to reputation.”
Reasons:
 Builds user trust.
 Improves reliability and satisfaction.
 Prevents downtime and losses.

Q14. List and explain at least three objectives of software testing.

📘 Source: “What is Software Testing?”
1. Identify defects before release.
2. Verify product meets requirements.
3. Build confidence that the software is ready for use.
“Testing is not just about finding bugs, but proving readiness.”
Q16. Explain the difference between an error, defect (bug), and failure with practical
examples.
📘 Source: General Intro Section
 Error: Developer’s mistake (wrong formula).
 Defect (Bug): Found during testing (system misbehaves).
 Failure: Occurs in production when users experience the issue.

CHAPTER 2 – The SDLC and QA Integration

Q2. Why is it important for requirements to be testable? Give an example.

Source: “QA Involvement in Requirement Gathering”
“QA ensures clear, testable, and complete requirements.”
 Non-testable: “App should be user-friendly.”
 Testable: “User completes registration within 2 minutes.”
Testable requirements ensure measurable success.

Q5. What role does a Requirement Traceability Matrix (RTM) play in QA, and why is it
important?
Source: “Test Case Design and Documentation (Traceability)”
“RTM maps requirements to test cases.”
Ensures full coverage, accountability, and no missed functionality.

Q6. Identify four major factors to include in a Test Plan for a mobile app.
Source: “Test Planning and Strategy”
1. Objectives – What to test.
2. Scope – Features included/excluded.
3. Resources – Tools, testers, devices.
4. Entry/Exit Criteria – When testing begins and ends.

Q9. How does QA contribute during the Maintenance Phase of SDLC?

Source: “QA Activities Across SDLC (Maintenance Phase)”
QA:
1. Runs regression tests after updates.
2. Monitors performance and logs defects.
“QA continues after release to ensure quality remains.”

Q10. With Agile, how have QA roles shifted compared to Waterfall?

Source: “Agile Development”
“In Agile, QA participates from the beginning.”
 Collaborates daily with devs.
  Automates frequent tests.
 Provides faster feedback.

Q13. Explain the concept of the V-Model in software testing.

Source: “V-Model (Verification and Validation Model)”
“Every development phase has a matching test phase.”
Dev Phase Test Phase
Requirements Acceptance Testing
Design System Testing
Implementation Unit Testing
Ensures early validation and structured flow.

Q15. What is the cost implication of finding defects late compared to early detection?
Source: “Early Testing Saves Time and Cost”
“Fixing bugs late can cost 100 times more than during design.”
Early testing reduces rework and total project cost.

Q27. Discuss the role of QA in the Requirement Analysis phase of SDLC.

Source: “QA Activities Across SDLC (Requirement Phase)”
“QA reviews requirements for clarity and testability.”
Ensures completeness before design begins.

Q28. What is Shift-Left Testing and why is it important in Agile and DevOps?
Source: “Shift-Left Testing Approach”
“Shift-Left means testing begins early.”
Benefits:
 Early defect discovery.
 Reduced cost.
 Faster releases.

CHAPTER 3 – Principles of Software Testing

Q15. What is the cost implication of finding defects late in the SDLC compared to early
detection?
Source: “Principles of Software Testing – Early Testing Saves Time and Cost”
“Defects detected early are cheaper to fix than post-release.”
Supports principle #3 – early testing saves cost and effort.

CHAPTER 4 – Types and Levels of Software Testing

Q17. Differentiate between Functional and Non-Functional Testing.
Source: “Functional vs Non-Functional Testing”
Type Focus Examples
Functional System actions Login, Signup
Non-Functional Quality attributes Speed, Security

Q18. Describe the four levels of testing (Unit, Integration, System, Acceptance).
Source: “Levels of Software Testing”
1. Unit: Tests smallest code unit (e.g., interest calc).
2. Integration: Checks data flow between modules.
3. System: End-to-end system validation.
4. Acceptance: Users verify against requirements.

Q29. For online banking, which levels and types of testing would you prioritize before go-
live?
Source: “Levels of Testing” and “Non-Functional Testing”
 Levels: Integration, System, Acceptance.
 Types: Security (data), Performance (speed), Regression (stability).

Q30. A login feature takes 10 seconds to load — which testing type does this relate to and
how would you report it?
Source: “Non-Functional Testing – Performance Testing”
Related to Performance Testing.
Defect Report:
Expected: 3 sec; Actual: 10 sec → performance issue.

CHAPTER 5 – Testing Techniques and Approaches

Q3. Differentiate between Smoke and Sanity Testing with examples.

Source: “Smoke Testing” and “Sanity Testing”
Aspect Smoke Sanity
Purpose Build stability Verify bug fix
Example Check app opens Check fixed login works

Q4. Explain Regression Testing vs Re-Testing with examples.

Source: “Regression Testing”
 Regression: Ensures new changes didn’t break old features.
E.g., After bug fix, check main modules.
  Re-Testing: Verify the specific fix itself works.
E.g., Test corrected total calculation.

Q19. Explain Black Box, White Box, and Gray Box Testing.
Source: “Testing Approaches”
Type Focus Knowledge Example
Black Box Functionality No code access Login page
White Box Logic, paths Full access If-else coverage
Gray Box Mixed Partial API Security

Q20. Discuss two test design techniques used in Black Box Testing.
Source: “Test Design Techniques”
1. Equivalence Partitioning: Group similar inputs (valid/invalid).
2. Boundary Value Analysis: Test edge values (e.g., 17, 18, 60, 61).

CHAPTER 6 – QA Processes and Best Practices

Q21. What are the key components of a Test Plan Document?

Source: “Test Planning and Strategy”
“A Test Plan outlines objectives, scope, entry/exit criteria, schedule, risks, and resources.”

Q22. Differentiate between Test Case, Test Script, and Test Scenario.
Source: “Test Case Design and Documentation”
Term Definition Example
Test Case Steps + Expected Result Login with valid input
Test Script Automated test Selenium login script
Test Scenario High-level goal “Verify login works”

CHAPTER 7 – Tools for Testing and QA

Q7. Which tool(s) would you recommend for API testing and why?
Source: “API Testing Tools”
“Postman simplifies sending requests and checking responses.”
“SoapUI supports REST and SOAP.”
Use for automation and validation of API endpoints.

Q23. List and explain three categories of testing tools with examples.
Source: “Categories of Testing Tools”
Category Description Example
Test Management Organize test cases TestRail
Bug Tracking Report defects Jira
Automation Run tests Selenium

Q24. Compare open-source and commercial testing tools.

Source: “Open-Source vs Commercial Tools”
Open Source Commercial
Free & customizable Paid with support
Requires scripting Easy UI, rich features

CHAPTER 8 – Automation in Software Testing

Q25. Identify three types of tests suitable for automation and why.
Source: “When to Automate Tests”
Test Reason
Regression Frequent repetition
Unit Quick validation
Smoke/Sanity Build verification

Q8. List three best practices to reduce flaky tests in automation frameworks.
Source: “Best Practices for Automation”
1. Avoid hard-coded waits.
2. Use stable environments.
3. Review test failures regularly.
Q26. What are common challenges when implementing test automation?
Source: “Challenges in Test Automation”
“High setup cost, tool selection, maintenance overhead, false failures.”