Software Quality Assurance and Testing

A program misbehavior can go unnoticed (appearing to pass) due to automated tests lacking specific assertions (option 1), manual testers focusing on other UI elements (option 2), or lack of oracle knowledge (option 3). Therefore, all of these options are valid reasons.

Risk-based testing uses identified risks to prioritize, design, and guide tests, ensuring resources are optimized to expose serious problems early. The other options describe risk documentation, execution constraints, or field evaluation rather than the design of risk-based tests.

Quality Assurance methods are considered preventive because they focus on process improvement and preventing defects before they occur. QA examines the development process to eliminate root causes of potential issues.

Quality control methods are considered corrective because they focus on detecting and fixing defects after they occur. QC involves inspection, testing, and correction of completed work to identify and address issues.

From an end-user perspective, testing seeks to address problems like defects, faults, and flaws, which represent incorrect or undesirable behaviors. Routine checks and monitoring are testing activities, and zero defects is an objective, not a user-facing problem.

Quality Control in testing focuses on inspection of deliverables, aiming for zero defects through routine checks, and continuous monitoring of the testing process. Warranty and customer satisfaction, while important, are outcomes of Quality Assurance rather than direct testing QC activities.

Customer service encompasses ensuring customer satisfaction, providing compensation for service failures, delivering after-sales care, and collecting feedback through questionnaires. Routine checks and monitoring are backend operational processes rather than direct customer service activities.

Standard test coverage metrics include statement coverage (executing each statement), branch coverage (testing each branch decision), and basic path coverage (covering independent paths). Point to point coverage is not a recognized or standard coverage metric in software testing.

Control totals are a batch control technique used to verify file integrity by summing numeric fields before and after processing. Compliance testing checks business rules compliance but uses different methods. Black box testing examines inputs/outputs without internal path coverage. Regression testing is performed by testers, not end users.

Quality culture originates from leadership. Senior management establishes the organizational tone, priorities, resource allocation, and behavioral expectations that shape culture. Quality and Training departments support implementation but cannot primary responsibility for setting culture.

Pareto analysis applies the 80/20 rule to identify the 20% of problem types that cause 80% of defects. It highlights which problems occur most frequently, enabling focused improvement efforts. It does not explain root causes or compare testing techniques.