Ch 09: Testing Basics and Techniques

106 Questions106 MCQs0 Short Questions0 Long Questions
๐ŸŽฏ Exam Practice Papers
SEMESTER PASS

CS611 - Software Quality Engineering Examination Practice

Timed practice exam simulation for CS611 - Software Quality Engineering.

๐Ÿ“˜ VU MID TERM EXAMLectures 1 to 22
โฑ๏ธ 60 Mins

Mid Term Examination

Covers syllabus of Lectures 1 to 22 with 30 high-yield MCQs in a timed exam environment.

๐Ÿ“30 MCQs
โฑ๏ธ60 Minutes
๐Ÿ“— VU FINAL TERM EXAMLectures 23 to 45
โฑ๏ธ 90 Mins

Final Term Examination

Comprehensive semester exam preparation with 45 MCQs covering Lectures 23 to 45 with complete course coverage.

๐Ÿ“45 MCQs
โฑ๏ธ90 Minutes
Showing 61 โ€“ 70 of 106 Questions
Page 7 of 11
Q61
๐Ÿง  Long Problem๐Ÿ“˜ CS611๐Ÿ“‘ Lec 9๐Ÿท๏ธ 09.2. Rationale for TestingHard๐Ÿ”โญ๐Ÿ’ก๐ŸŒŸ๐Ÿ“„๐ŸŽ“VU๐Ÿ›๏ธVU
Analyze the 'Rationale for Testing' and the core purpose of executing a software product in a controlled or simulated environment as presented in Module 09. Detail how software testing builds stakeholder confidence and exposes implementation risks. Write a Python program that implements a class 'TestingRationaleManager' to simulate a controlled testing environment. The class should execute a batch of test cases, compare their actual and expected outputs, log detected defects, calculate the percentage-based stakeholder confidence, and list critical implementation risks in a formatted report when tests fail.
Q62
๐Ÿง  Long Problem๐Ÿ“˜ CS611๐Ÿ“‘ Lec 9๐Ÿท๏ธ 09.5. Functional TestingHard๐Ÿ”โญ๐Ÿ’ก๐ŸŒŸ๐Ÿ“„๐ŸŽ“VU๐Ÿ›๏ธVU
Detail the principles of 'Functional Testing' as presented in Module 09 of the course handouts. Contrast functional testing (the abstract level testing of external behavior against requirements) with structural testing (the concrete level testing of code block paths and programming architectures). Explain why both defect fixing and re-verification activities are critical to closing the functional testing feedback loop. Finally, write a Python class 'FunctionalTestingSandbox' that models functional requirement validation. The class should execute an abstract application method against defined requirement assertions (inputs and expected outputs) without inspecting its internal code, automatically log defects on functional mismatches, track defect states (e.g., Fixed, Re-verified, Closed), and support re-running failed tests to verify successful hot-fixes.
Q63
๐Ÿง  Long Problem๐Ÿ“˜ CS611๐Ÿ“‘ Lec 9๐Ÿท๏ธ 09.1. What is Software TestingHard๐Ÿ”โญ๐Ÿ’ก๐ŸŒŸ๐Ÿ“„๐ŸŽ“VU๐Ÿ›๏ธVU
According to Module 09 of the course handouts, analyze the concept of Software Testing, including its formal definition, its primary goals, and how it translates to comparing expected vs. actual behaviors. Write a Python class 'SoftwareTestingSimulator' that takes a list of test cases (each containing input parameters, expected output, and actual executable function), runs the test cases, compares actual outputs with expected outputs, automatically logs a defect if a mismatch is detected, and outputs a formatted test report detailing the total number of passed and failed test cases.
Q64
๐Ÿง  Long Problem๐Ÿ“˜ CS611๐Ÿ“‘ Lec 9๐Ÿท๏ธ 09.6. Structural TestingHard๐Ÿ”โญ๐Ÿ’ก๐ŸŒŸ๐Ÿ“„๐ŸŽ“VU๐Ÿ›๏ธVU
Provide a comprehensive comparative analysis of Functional Testing and Structural Testing as detailed in Module 09 of the course handouts. Explain the differences in terms of abstraction level, the perspective of the tester (internal vs. external behavior), who typically conducts the testing, and the units under verification (requirements vs. code blocks/data structures). Finally, write a Python program that implements a class 'SoftwareVerificationSuite' which models both functional and structural testing strategies. The class should support: 1) A functional test execution method that checks actual outputs against expected inputs without inspecting internal branches. 2) A structural test execution method that tracks and validates internal control flows (such as statement coverage or branch coverage paths). 3) Automating defect logging when either a functional mismatch occurs or when structural statement coverage falls below a pre-defined threshold.
Q65
๐Ÿง  Long Problem๐Ÿ“˜ CS611๐Ÿ“‘ Lec 9๐Ÿท๏ธ 09.3. Artifact Level TestingHard๐Ÿ”โญ๐Ÿ’ก๐ŸŒŸ๐Ÿ“„๐ŸŽ“VU๐Ÿ›๏ธVU
Discuss the significance of Artifact-Level Testing as detailed in Module 09 of the course handouts. Explain what the primary software artifact under test is and how use cases are systematically translated into executable test cases to verify software behavior. Finally, write a Python program that models this translation by defining a 'UseCase' class and a 'TestCase' class, automatically maps the steps of a use case into test steps with pre-conditions and expected results, executes the test steps, and determines if the test case passes or fails.
Q66
๐Ÿง  Long Problem๐Ÿ“˜ CS611๐Ÿ“‘ Lec 9๐Ÿท๏ธ 09.8. Example-I: Black Box TestingHard๐Ÿ”โญ๐Ÿ’ก๐ŸŒŸ๐Ÿ“„๐ŸŽ“VU๐Ÿ›๏ธVU
Discuss the methodology of Black Box Testing when applied to arithmetic operations as detailed in Module 09. Explain how test ideas are generated to explore numeric boundaries, transient values, zero divisions, and user interface inputs (mouse, keyboard, pasting). Compare this abstract boundary verification with White Box execution testing. Write a Python program that implements a class 'ArithmeticBlackBoxTester' to simulate a black box testing engine. The class must define methods to: 1. Accept input test datasets (including integer boundaries, floating-point values, zero, and strings). 2. Execute a calculation method, catching any division by zero errors and type mismatch exceptions. 3. Track and print a test execution report detailing test passes, handled classic exceptions (like divide by zero), and unhandled crashes, thereby providing a concrete quality assessment of the arithmetic component.
Q67
๐Ÿง  Long Problem๐Ÿ“˜ CS611๐Ÿ“‘ Lec 9๐Ÿท๏ธ 09.4. Major Activities in Software TestingHard๐Ÿ”โญ๐Ÿ’ก๐ŸŒŸ๐Ÿ“„๐ŸŽ“VU๐Ÿ›๏ธVU
Discuss the three 'Major Activities in Software Testing' as presented in Module 09 of the course handouts. Detail the purpose of each phase (Test Planning & Preparation, Test Execution, and Analysis & Follow-up) and how they cooperate to detect, document, and resolve defects. Write a Python class 'SQATestingLifecycleManager' that implements this three-step lifecycle programmatically. The class must allow users to register test goals, compile a suite of test cases, execute those test cases, log failures, track corrective actions (re-verification), and output a complete testing progress report.
Q68
๐Ÿง  Long Problem๐Ÿ“˜ CS611๐Ÿ“‘ Lec 9๐Ÿท๏ธ 09.7. Black Box TestingHard๐Ÿ”โญ๐Ÿ’ก๐ŸŒŸ๐Ÿ“„๐ŸŽ“VU๐Ÿ›๏ธVU
Rigorously analyze the concept of Black Box Testing as described in Module 09. Contrast it with Structural/White Box Testing, explaining the differences in focus, visibility, conducting roles, and methodologies (such as specification checklists and smoke tests). Then, write a Python class 'BlackBoxTestingEngine' that models black box execution. The class should: 1) Maintain a specification checklist (inputs, expected outputs). 2) Execute a black-box function, comparing actual and expected results. 3) Automatically repeat failed test cases up to a specified retry limit to eliminate transient or hardware failure possibilities. 4) Log a verified software defect only if the failure persists across all repeated attempts.
Q69
๐Ÿง  Long Problem๐Ÿ“˜ CS611๐Ÿ“‘ Lec 9๐Ÿท๏ธ 09.14. Rationale of ReviewsHard๐Ÿ”โญ๐Ÿ’ก๐ŸŒŸ๐Ÿ“„๐ŸŽ“VU๐Ÿ›๏ธVU
Rigorously analyze the 'Rationale of Reviews' as presented in Module 09 of the course handouts. Discuss why reviews are considered time-saving, cost-effective, and how they foster knowledge sharing through informal code walkthroughs. Contrast this informal peer walkthrough approach with formal inspections. Finally, write a Python program that implements a class 'PeerReviewSession' to simulate an informal code review workflow. The program should support: 1. Registering code snippets with their authors. 2. Allowing a non-author reviewer (an experienced technical person) to inspect the code. 3. Checking the code for common issues (e.g., magic numbers, broad exception blocks). 4. Generating a review report that calculates cost savings (assuming defects found during reviews are 10x cheaper to fix than in formal testing) and logs the reviews.
Q70
๐Ÿง  Long Problem๐Ÿ“˜ CS611๐Ÿ“‘ Lec 9๐Ÿท๏ธ 09.10. White Box TestingHard๐Ÿ”โญ๐Ÿ’ก๐ŸŒŸ๐Ÿ“„๐ŸŽ“VU๐Ÿ›๏ธVU
Contrast Black Box Testing and White Box Testing as described in Module 09 of the course handouts. Discuss how their objectives, visibility, executor roles, and coverage levels (such as statement, branch, and path levels) differ. Then, write a Python class 'WhiteBoxTestCoverageSimulator' that simulates statement and branch coverage of a function. The class should take a set of inputs, execute a test function, trace which conditional blocks/statements are executed, calculate the percentage-based branch coverage achieved by a suite of test cases, and log a defect if branch coverage is less than 100%.