STQA Worksheet Answer

---

SECTION A: TRUE / FALSE

No Statement Answer Explanation

1. Testing proves that a software system is completely free of defects. F

Testing can only show the presence of defects, not their absence.

2. Quality Assurance focuses on process improvement. T

QA is process-oriented, focusing on improving development and testing processes.

3. Verification answers the question “Are we building the product right?” T

Verification ensures that the product is built according to specifications.

4. Validation is performed without executing the program. F Validation involves executing the software
to ensure it meets user needs.

5. Black-box testing requires knowledge of internal code. F Black-box testing is based on external
behavior, not internal code.

6. Regression testing ensures that new changes do not break existing functionality. T Regression testing
re-tests existing features after changes.

7. Test cases should be traceable to requirements. T

Traceability ensures testing aligns with requirements.

8. Debugging and testing are the same activity. F

Testing finds defects; debugging fixes them.

9. A defect lifecycle starts with defect identification. T

The lifecycle begins when a defect is identified.

10. Quality Control is preventive in nature. F

QC is corrective, focusing on identifying defects in the product. QA is preventive.

SECTION B: MULTIPLE CHOICE QUESTIONS

Correct Answer Explanation

1. Which activity belongs to Quality Assurance?

B. Process auditing QA focuses on process improvement, not product checking.

2. Which testing level focuses on individual modules?

C. Unit Testing Unit testing tests individual components/modules.

3 Which document defines what needs to be tested?

B. Test Plan Test Plan defines scope, objectives, and approach.

4. Which testing is done without executing code?

C. Static testing Static testing reviews documents/code without execution.

5 Boundary Value Analysis is a:

B. Black-box technique BVA is a black-box testing technique.

6 A defect found after release is called:

C. Failure A defect found by the end user after release is a failure.

7 Which phase prepares test scenarios and cases?

B. Test Design Test Design phase involves creating test cases/scenarios.

8 Which tool is mainly used for defect tracking?

C. Jira Jira is widely used for defect/bug tracking.

9 Smoke testing is performed to:

C. Check basic stability Smoke testing checks if the build is stable enough for further testing.

10 Which metric measures testing effectiveness?

A. Defect Density Defect Density measures the number of defects per size of software.

SECTION C: SHORT ANSWERS

1. Software Testing – The process of evaluating a software system to identify differences between
expected and actual behavior.

2. QA vs QC – QA focuses on process improvement, QC focuses on product verification.

3. Verification – Ensuring the product is built correctly according to specifications (e.g., reviews,
inspections).

4. Validation – Ensuring the product meets user needs and requirements (e.g., testing, UAT).

5. Test Case – A set of conditions or steps to verify a particular functionality.

6. Defect Life Cycle – The stages a defect goes through from identification to closure.

7. Black-box Testing – Testing without knowledge of internal code, based on requirements and
functionality.

8. Regression Testing – Re-testing existing functionality after changes to ensure no new defects are
introduced.

9. Test Plan – A document describing the scope, approach, resources, and schedule for testing activities.

10. Static Testing – Testing without executing the code, e.g., reviews, walkthroughs, inspections.

SECTION D: SCENARIO-BASED / ANALYTICAL

1. Boundary Value Analysis (for password length 6–12).

2. Static Testing (reviewing documents for errors).

3. Regression Testing (old module broke due to new feature).

4. Validation / UAT failed (user needs not met).

5. Unit Testing (developer tests individual functions).

6. Defect (missing requirement is a defect; failure is the outcome).

7. Quality Assurance (process auditing is a QA activity).

8. Smoke Testing / Sanity Testing (checking readiness before release).

9. Black-box Testing (no code knowledge).

10. Post-release / Production defect (found after deployment).

---
SECTION E: PRACTICAL / CASE-BASED

1. ATM cash withdrawal test cases:

· Withdraw valid amount within balance.

· Withdraw amount exceeding balance (error message expected).

2. Two QA activities:

· Process audits

· Standards definition and compliance checks

3. Two black-box techniques:

· Equivalence Partitioning

· Boundary Value Analysis

4. Two attributes of a good test case:

· Clear and unambiguous steps

· Traceable to requirements

5. Two causes of software defects:

· Requirement misinterpretation

· Coding errors

6. Two advantages of automation testing:

· Faster execution

· Reusability of test scripts

7. Two testing tools:

· Selenium (automation)

· JMeter (performance)

8. Two test deliverables:

 · Test Plan

· Test Summary Report

9. Two differences between error and defect:

· Error: Human mistake in coding.

· Defect: Flaw in the software resulting from an error.

10. Two goals of Software Quality Assurance:

11. Ensure processes are followed

12. Prevent defects through process improvement