Software Testing & Quality Assurance

A Traceability Matrix maps requirements to test cases to ensure all requirements are covered by testing. Test Matrix and Checklist are different (broader) concepts. Test bed refers to the test environment. Only Traceability Matrix specifically validates requirement coverage.

A Mitigation Plan (option D) is a strategy to reduce or eliminate the impact of identified risks. A Migration Plan focuses on data/system transitions. A Master plan is an overarching strategy. A Maintenance plan deals with ongoing system support.

TQM stands for Total Quality Management (option C), a comprehensive management approach focused on continuous improvement of processes, products, and services. It's not about tools or individual managers but an organizational philosophy.

A Test Bed (option A) is the configured environment including hardware, software, network, and data setup required to execute tests. It provides the infrastructure for running the application under test. A checkpoint is a verification point. Code walkthrough is a review technique. A checklist is a testing aid.

Severity (option A) measures the technical impact of a bug on the application's functionality. Priority indicates how urgently the bug needs to be fixed based on business needs. Fix ability refers to how easily it can be resolved. Traceability tracks the bug's lifecycle.

The V-Model (option C) emphasizes that for every development phase, there is a corresponding testing phase. Testing begins in parallel with development activities - test planning starts during requirements, test cases during design, etc. Waterfall has sequential phases. Spiral is iterative risk-based. Linear is sequential like waterfall.

CMM Level 3 (option B) is the Defined level where organizations have standard processes for both development and maintenance, including integration. Level 1 is Initial (ad-hoc). Level 2 is Repeatable (basic project management). Integration requires standard processes, placing it at Level 3.

The Plan-Do-Check-Act (PDCA) cycle follows the sequence: Plan (P) → Do (D) → Check (C) → Act (A). Option B correctly shows this order. This is the Deming Cycle/Shewhart Cycle used for continuous improvement in quality management.

Testing levels include Unit Testing (individual components), Integration Testing (combined components), System Testing (complete system), and Acceptance Testing (user validation). Option D 'All the above' correctly captures that these are all testing levels in the hierarchy.

Ad hoc Testing (option A) is informal testing done without planning, documentation, or formal test cases. It's exploratory and relies on the tester's intuition and experience. Unit testing is formal. Regression testing is planned. Functional testing follows requirements.

Defects typically fall into three categories: WRONG (incorrect functionality), MISSING (absent functionality), and EXTRA (unintended features). Option D 'All the above' correctly includes all three categories. This classification helps in defect analysis and prevention.

Usability testing is a non-functional testing type that evaluates how easy and intuitive a user interface is for end users. It checks if users can understand and navigate the interface effectively. Security testing focuses on vulnerabilities, unit testing tests individual code units, and black box testing examines functionality without seeing internal code.

White box testing is called glass box testing, open box testing, and clear box testing because the tester can see inside the code. It is NOT called 'closed box testing' - that term would refer to black box testing where you cannot see the internal code structure. Option B is the correct answer.

White box testing involves examining and testing the internal code structure, logic, and implementation of a program. The tester has access to the source code and understands how the software works internally. Unit testing is a type of white box testing but more specific, black box testing doesn't look at code, and regression testing checks for unintended changes.

Quality Assurance (QA) is a proactive, preventive process that focuses on improving the development processes themselves to ensure quality. It applies to the entire software life cycle and involves management activities, process standards, and methodologies. Quality Control is reactive product testing, Verification checks against specifications, and Validation checks against user needs.

White box testing examines the program's internal structure, logic, and code to derive test cases. It ensures all statements and branches are executed at least once (statement and branch coverage). Black box testing doesn't look at code, gray box combines both approaches, and 'closed box' isn't a standard testing term (black box is the correct opposite of white box).

In IBM MQ, dspmq is the standard control command used to display the names and details (such as status) of queue managers. Commands like mqs, dspmqs, and dspmqcsv are incorrect and do not exist.