Define the concept of a 'Test Checklist' in Software Quality Engineering. List three standard tasks verified in a web security checklist, and explain why functional testing is explicitly excluded from a test checklist.
Ch 09: Testing Basics and Techniques
In-depth study of dynamic software testing, equivalence partitioning, boundary value analysis, cyclomatic complexity calculations, code inspections, walkthroughs, and peer review methodologies.
106 Questions106 MCQs0 Short Questions0 Long Questions
SEMESTER PASS
CS611 - Software Quality Engineering Examination Practice
Timed practice exam simulation for CS611 - Software Quality Engineering.
Showing 91 โ 100 of 106 Questions
Page 10 of 11
According to the course handouts, which type of testing is classified as 'concrete testing from the code viewpoint' because the software is evaluated at the statement, module, or sub-system level?
Analyze the technical distinctions between Functional (Black Box) Testing and Structural (White Box) Testing as presented in the course materials. In your response, contrast their core evaluation goals, explain what elements are tested in each approach (such as statements and paths vs. specification checklists), and discuss which team members typically execute each type.
Analyze the technical rationale behind 'Branch-Level Testing' and 'Reviews' as core software quality verification strategies. In your response, explain who is responsible for executing branch-level testing and why, describe how 'Reviews' act as a static alternative to formal testing, and discuss the economic benefits of discovering defects during a review versus formal test execution.
Define a 'Test Case' in software quality engineering. List its standard components as documented in SQA guidelines and explain how test cases are typically derived at the artifact level.
Explain why Functional Testing is referred to as 'abstract-level testing' whereas Structural Testing is classified as 'concrete testing' from the code's viewpoint.
Analyze the technical goals, execution strategies, and SQA workflows of 'Structural Testing' and 'Requirement Change Management'. In your response, explain: (1) What structural testing verifies at the code level and who executes it, (2) The process a project team must follow under the change management framework when a new 'WishList' requirement is proposed, and (3) How impact analysis is used to prevent scope conflicts and protect the existing system baseline.
In Software Quality Assurance, what is a 'Test Checklist' and how does its purpose differ from functional testing?
When preparing for formal Quality Assurance (QA) testing, a SQA engineer performs preliminary tasks such as verifying database backups, checking data access privileges, and ensuring the network environment tiers are properly defined. Which of the following best categorizes this quality assurance activity?
What is 'Functional Testing' (or Black Box Testing) as described in the handouts, and how does it differ from 'Structural Testing'?