Ch 10: Test Activities and Management

What is 'Feature-Level Testing' in Software Quality Engineering? Describe its primary objective and list the underlying units that must be tested to verify a 'Booking of a Hotel Room' feature as specified in the handouts.

What is a 'Test Dashboard' in Software Quality Assurance? Describe its primary purpose and explain how it assists SQA teams in making informed testing decisions.

What is a 'Test Case' in Software Quality Engineering? List at least four best practices that must be followed when designing and writing test cases as detailed in the handouts.

Explain the concept of 'Sanity (Integration) Testing' in Software Quality Engineering, detailing who executes it and how it relates to Software Configuration Management (SCM).

Analyze the role, classification scheme, and defect management workflows of Sanity (Integration) Testing and Feature-Level Testing as described in the handouts. Explain how sanity test reporting helps categorize bugs, why cosmetic bugs are deferred, and discuss how multiple units are verified together in feature-level testing using the 'Booking of Hotel Room' scenario as an example.

Analyze the operational role of 'Project Audits', SQA's status as the 'internal customer', and the criticality of 'Domain Knowledge' in software engineering. In your response: (1) Identify who is responsible for providing the necessary audit data during a project audit, (2) Explain why subjective requirements like 'provide alerts quickly' violate verifiability and how to resolve them, and (3) Discuss how a lack of domain-specific knowledge impacts both requirement comprehension and team morale.

Explain why software requirements differ significantly from requirements in other physical engineering domains (such as construction), highlighting the role of software tangibility and client demos. In addition, list the essential elements that must be included within a standard written test case to verify these volatile requirements systematically, and describe their purpose.

Analyze the role and integration of 'Regression Testing' and 'Test Reporting/Dashboards' in the Software Quality Engineering lifecycle. Explain how regression testing verifies that original features remain unchanged, discuss how a Test Dashboard visualizes metrics such as open defect counts by status and feature, and describe how these visual statistics guide the overall testing strategy.