Software Testing (CA-602) - Model Answer Sheet (70 Marks)
Q1) Attempt any Eight (2 marks each)
a) Software Testing: Process of evaluating software to identify defects and ensure it meets
requirements.
b) Alpha Testing: Internal testing conducted before releasing the product to users.
c) Software Metric: Quantitative measure used to assess software quality and performance.
d) Unit Testing: Testing of individual components or modules independently.
e) Cyclomatic Complexity: V(G)=E-N+2P, measures number of independent paths.
f) Static Testing: Testing without executing code (reviews, inspections).
g) GQM: Goal Question Metric approach for defining metrics.
h) Test Case Design: Process of creating test cases to validate functionality.
i) Load Runner: Tool used for performance testing under load.
j) Failure & Defect: Defect is a flaw; failure is incorrect output.
Q2) Attempt any Four (4 marks each)
a) Testing Principles:
1. Testing shows presence of defects.
2. Exhaustive testing is impossible.
3. Early testing reduces cost.
4. Defect clustering.
5. Pesticide paradox.
b) White Box Testing:
Testing internal code structure. Techniques: statement, branch, path, loop testing.
c) Top-down & Bottom-up Testing:
Top-down uses stubs, starts from main module.
Bottom-up uses drivers, starts from lower modules.
d) Verification & Validation:
Verification: Are we building right product?
Validation: Are we building product right?
e) Acceptance Testing:
Performed by users to ensure system meets requirements.
Q3) Attempt any Four (4 marks each)
a) Performance Testing:
Evaluates system speed, stability, scalability. Includes load, stress testing.
b) Client/Server vs Web Testing:
Client/server focuses backend; web includes UI, browser compatibility.
c) GUI Testing:
Checks layout, usability, navigation, and functionality.
d) STLC:
Phases: Requirement → Planning → Design → Execution → Closure.
e) Boundary Value Analysis:
Tests minimum, maximum, and edge values.
Q4) Attempt any Four (4 marks each)
a) SQA:
Ensures quality through standards, audits, and processes.
b) Debugging:
Steps: Identify → Isolate → Fix → Verify.
c) Testing Fundamentals:
Includes concepts like defects, test cases, validation, verification.
d) System Testing:
Testing complete system; includes functional and non-functional testing.
e) Inspection & Walkthrough:
Inspection is formal review; walkthrough is informal review.
Q5) Short Notes (Any Two)
a) Testing Documentation:
Includes test plan, cases, reports.
b) Real-Time System:
System with strict timing constraints.
c) JUnit:
Framework for unit testing in Java.