SQA Q/A
Q1. What is Software Testing? Software testing is the process of executing a
program or application to find software bugs.
Q2. Why Software Testing is necessary? Software testing is necessary to identify
and correct mistakes made during development, ensure customer satisfaction,
deliver a quality product, provide reliable results, and ensure the effective
performance of the software application.
Q3. Software Testing objectives and purpose: Objectives include finding
defects, gaining confidence in the software's quality, preventing defects, meeting
business and user requirements, and ensuring customer confidence.
Q4. Two main categories of software testing:
Manual Testing: Testers manually execute test cases without automation tools.
Automation Testing: Test cases are performed with the assistance of tools, scripts,
and software for efficiency.
Q5. Why do we say testing is context dependent? Testing depends on the
specific context of the software, such as its intended industry or use case.
Q6. Different types of manual testing:
Black Box Testing
White Box Testing
Unit Testing
System Testing
Integration Testing
Acceptance Testing
Q7. Black Box Testing: Testing without knowledge of the internal workings,
focusing on input and output to evaluate system responses.
Q8. White Box Testing: Testing the internal structure, design, and coding of
software to improve design, usability, and security.
Q9. Unit Testing: Testing individual units or components of the software to
validate performance.
Q11. Integration Testing: Testing where software modules are integrated
logically and tested as a group.
Q12. Acceptance Testing: Real-world testing by the end-users to validate
software functionality.
Q14. Functional Testing: Validating software against functional requirements to
ensure it meets specifications.
Q15. Non-Functional Testing: Checking non-functional aspects like
performance, usability, and reliability.
Q16. Regression Testing: Ensuring an application functions as expected after
code changes.
Q17. Smoke and Sanity Testing:
Smoke Testing: Ensures critical functionalities work fine.
Sanity Testing: Checks new functionality or bug fixes.
Q18. UI Testing: Checking if all on-screen elements function as desired.
Q19. Responsive Testing: Ensuring a website/application behaves appropriately
on different devices.
Q20. Cross Browser Testing: Ensuring compatibility across various browsers and
operating systems.
Q21. Verification vs. Validation:
Verification: Checking if software is designed and developed as specified.
Validation: Checking if software meets the client's true needs.
Q22. Bug, Defect, Error:
Error: Mistake made by a programmer during coding.
Defect: Error found during testing.
Bug: Error found during the testing phase.
Q23. Test Case vs. Test Scenario:
Test Case: Detailed document with test steps to validate software.
Test Scenario: High-level classification of testable requirements.
Q24. Software Testing Life Cycle (STLC) Phases:
Requirement Analysis
Test Planning
Test Case Development
Test Environment Setup
Test Execution
Test Cycle Closure
Q25. SDLC (Software Development Life Cycle): A process for software project
development, including stages like planning, requirement analysis, design,
development, testing, deployment, and maintenance.
Q26. Bug Life Cycle:
New
Assigned
Open
Fixed
Pending Retest
Retest
Verified
Reopen
Closed
Duplicate
Rejected
Deferred
Not a Bug
Q27. Severity vs. Priority:
Severity: Denotes the total impact of a defect.
Priority: Decides the order in which defects should be fixed.
Q28. 7 Principles of Testing:
1. Testing shows the presence of defects.
2. Exhaustive testing is impossible.
3. Early testing saves time and money.
4. Defects cluster together.
5. Beware of the pesticide paradox.
6. Testing is context dependent.
7. Absence-of-errors is a fallacy.
Q29. Test Cases for Pen: Includes positive, negative, and performance test cases,
covering various aspects like grip, writing, ink flow, and material quality.
Q30. Test Cases for Chair: Covers stability, material, usability, support, and
various dimensions.
Q31. Test Cases for Login Functionality: Includes positive, negative, and
security test cases, focusing on user experience, validation, and security aspects.
This summary provides a comprehensive overview of the information you shared
on software testing.
