Software Quality Assurance MCQ Questions

The correct Software Process Cycle under Six Sigma is Plan-Do-Check-Act (PDCA). This iterative four-step management method provides a structured approach for continuous improvement of processes and quality.

HTSM stands for Heuristics Test Strategy Model. It's a set of patterns for designing a test strategy, providing a systematic approach to test planning that helps testers identify relevant test techniques and areas of focus.

This question addresses key concepts in Software Quality Assurance (SQA). SQA encompasses planned activities ensuring software meets quality standards throughout the development lifecycle.

The purpose of an inspection is to find problems and see what's missing. It's a formal peer review technique focused on identifying defects in software artifacts like requirements, design documents, or code.

This question covers important concepts in software testing methodologies. Testing is a critical quality assurance activity that validates software against requirements and identifies defects before release.

Boundary value analysis is a process where testers take boundary values and middle values for testing. It focuses on testing at the boundaries of input domains, examining values at the edges (minimum, maximum) and just beyond them.

This question addresses key concepts in Software Quality Assurance (SQA). SQA encompasses planned activities ensuring software meets quality standards throughout the development lifecycle.

A walkthrough is an informal meeting for evaluation or informational purposes. It's a peer review where the author guides participants through a work product, explaining the material to gather feedback without focusing on defect detection.

The advantage of top-down integration testing is that major control functions can be tested early. This approach allows verification of critical system functionality earlier in the development cycle, enabling earlier feedback on architectural decisions.

Session-based testing combines accountability and exploratory testing to provide rapid defect discovery and creative on-the-fly test design. It structures exploratory testing into time-boxed sessions with specific charters, followed by debriefings.

Loader Runner is a tool to test the performance of applications. It helps measure how applications perform under different load conditions, identifying bottlenecks and performance issues before deployment.

This question covers important concepts in software testing methodologies. Testing is a critical quality assurance activity that validates software against requirements and identifies defects before release.

CMMI stands for Capability Maturity Model Integration. It's a process improvement approach that helps organizations improve their performance by providing a set of best practices for developing products and services.

A major shortcoming is the inability to automate localization tests that require configuration changes at the device level. Since instrumentation can't control the OS, tests requiring system-level settings like language, region, or permissions cannot be automated.

UAT stands for User Acceptance Testing. It is the final phase of software testing where actual users test the software to verify that it meets their business requirements and can handle required tasks in real-world scenarios.

This question addresses key concepts in Software Quality Assurance (SQA). SQA encompasses planned activities ensuring software meets quality standards throughout the development lifecycle.

Selenium is an automation tool for web applications. It provides a suite of tools for browser automation that supports multiple programming languages and platforms, making it widely used for automated testing of web applications.

The process is what must happen and the procedure is the step-by-step of how it will happen. Process defines the overall activity and desired outcome, while procedure specifies the detailed instructions for implementation.

Equivalence Classes involve sampling from groups of inputs rather than testing huge sets of inputs. This technique divides input data into partitions where all elements should behave similarly, allowing efficient testing of representative values.