Ch 10: Test Activities and Management

180 Questions180 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 121 – 130 of 180 Questions
Page 13 of 18
Q121
🧠 Long ProblemπŸ“˜ CS611πŸ“‘ Lec 10🏷️ 10.7. Writing Test CasesHardπŸ”β­πŸ’‘πŸŒŸπŸ“„πŸŽ“VUπŸ›οΈVU
Discuss the methodology and guidelines for writing software test cases as presented in Module 10, Section 10.7 of the course handouts. Explain the strategic importance of the 'single condition' rule, why testing multiple test cases inside a single script is discouraged, and the purpose of ensuring both positive and negative scenario coverage. Finally, write a Python class 'TestCaseValidator' that acts as an automated SQA auditor. The class must allow: 1) Registering multiple test case profiles (checking scenario, steps list, expected result, and scenario type). 2) Executing a programmatic compliance check that flags violations if a test case has empty steps, tests multiple conditions, lacks complete details, or fails to define positive/negative tags. 3) Generating a summary audit report.
Q122
🧠 Long ProblemπŸ“˜ CS611πŸ“‘ Lec 10🏷️ 10.19. Sanity Testing ReportingHardπŸ”β­πŸ’‘πŸŒŸπŸ“„πŸŽ“VUπŸ›οΈVU
Explain the processes of software release construction and sanity testing reporting under CMMI frameworks, referencing Module 06, Section BB and Module 10, Section S of the course handouts. Address: 1. The inputs required for building a release and which teams provide them. 2. The concept of 'reporting features' in sanity testing and why features are identified with data requiring bug fixing. 3. The four severity categories used to classify bugs/defects during sanity testing. Finally, write a Python class 'ReleaseSanityEngine' that constructs a software release from features and environment variables, simulates sanity testing, registers reported bugs with their respective severity levels, and outputs a structured sanity testing report with recommendations.
Q123
🧠 Long ProblemπŸ“˜ CS611πŸ“‘ Lec 10🏷️ 10.26. Regression TestingMediumβ­πŸ’‘πŸ“„πŸŽ“VUπŸ›οΈVU
What is verified and ensured by Regression Testing? Explain with an example.
Q124
❓ MCQπŸ“˜ CS611πŸ“‘ Lec 10🏷️ 10.17. Sanity (Integration) TestingMediumπŸ”β­πŸ’‘πŸ“„πŸŽ“VUπŸ›οΈVU
In software configuration management and testing, how is Sanity (Integration) testing performed?
  1. A.Developers test individual code statements, blocks, and data structures in isolation.
  2. B.The Software Configuration Management (SCM) team merges separate codebases from multiple developers, and developers then test this integrated codebase to ensure components work together.
  3. C.Independent external auditors review high-level process documentation to assign maturity ratings.
  4. D.A prototype is shown to the customer to secure formal requirement approval.
Q125
❓ MCQπŸ“˜ CS611πŸ“‘ Lec 10🏷️ 10.26. Regression TestingEasyπŸ”β­πŸ’‘πŸ“„πŸŽ“VUπŸ›οΈVU
What is the primary objective of performing Regression Testing after adding a new feature or making updates to a software product?
  1. A.To verify that newly added features or code changes have not negatively impacted or broken existing, previously verified features.
  2. B.To test the maximum concurrent user capacity and identify the breaking point of the system.
  3. C.To dry-run the system without database connections on localized hardware.
  4. D.To capture high-level business goals and map them directly into a project budget roadmap.
Q126
❓ MCQπŸ“˜ CS611πŸ“‘ Lec 10🏷️ 10.32. Testing: Release Notes BasicsEasyπŸ”β­πŸ’‘πŸ“„πŸŽ“VUπŸ›οΈVU
According to the course handouts on testing and release management, which of the following is a key component included in Software Release Notes to build customer and end-user confidence?
  1. A.The source code files and compiler warning logs of the current build
  2. B.Detailed test reports, results, and information about the test procedure
  3. C.The list of development team members along with their individual salaries
  4. D.The SQA team's internal payroll configuration files
Q127
πŸ“ Short QπŸ“˜ CS611πŸ“‘ Lec 10🏷️ 10.32. Testing: Release Notes BasicsMediumβ­πŸ’‘πŸŒŸπŸ“„πŸŽ“VUπŸ›οΈVU
List five (5) key types of information that should be included in a professional Software Release Notes document to guide the customer and end users, as outlined in the handouts.
Q128
🧠 Long ProblemπŸ“˜ CS611πŸ“‘ Lec 10🏷️ 10.32. Testing: Release Notes BasicsHardβ­πŸ’‘πŸ“„πŸŽ“VUπŸ›οΈVU
Explain the role and significance of Software Release Notes in deployment and client-relationship management. Detail the comprehensive five-point content structure conventionally included in this document, and discuss how sharing test reports and outstanding issue lists impacts client trust.
Q129
❓ MCQπŸ“˜ CS611πŸ“‘ Lec 10🏷️ 10.22. Example-I: Feature Level TestingEasyπŸ”β­πŸ’‘πŸ“„πŸŽ“VUπŸ›οΈVU
A QA team is testing a software application where a user books a hotel room via a website. The testing spans several sequential steps: user registration, searching for hotel rooms, selecting a room, filling in payment details, verifying payment details, generating a unique booking ID, and sending the ID to the user via email. Which level of software testing does this represent?
  1. A.Unit Testing
  2. B.Feature-Level Testing
  3. C.Stress Testing
  4. D.Static Review Testing
Q130
🧠 Long ProblemπŸ“˜ CS611πŸ“‘ Lec 10🏷️ 10.14. Unit TestingHardβ­πŸ’‘πŸŒŸπŸ“„πŸŽ“VUπŸ›οΈVU
Analyze the technical role, operational execution, and SQA impacts of 'Unit Testing' as described in the course materials. In your response, define what constitutes a 'unit', explain why unit testing is considered both a development process and the first level of testing, and evaluate its specific impacts on early defect removal, debugging complexity, and cost containment.