Software Testing Fundamentals

The best tester is measured by bugs FIXED, not found. A tester who finds 100 bugs that get ignored is less valuable than one who finds 10 critical bugs that all get fixed. The goal is improving software quality, which only happens when bugs are actually resolved. Option D (a & c) would be correct if both A and C were right, but finding the most bugs alone doesn't make someone the best.

Static testing involves evaluating software artifacts without executing code. Options A, B, and C (black box, structural, path testing) are all dynamic testing techniques that require running the program. Therefore D (None of the above) is correct - none of the listed options are static testing methods.

System testing validates the entire integrated system against requirements. Options A, B, and C (business process testing, performance/load/stress testing, usability testing) are all system-level activities. Top-down integration testing is an integration testing strategy, not system testing - it's about combining modules, not testing the complete system.

Walkthrough is a form of static testing where peers review documents or code informally to find defects. Appraisal, Assessment, and Gap Analysis are not standard static testing techniques. Walkthroughs, inspections, and technical reviews are the primary static testing methods.

Reviews serve multiple purposes: making decisions, evaluating alternatives, finding defects, solving technical problems, and checking conformance to specifications and standards. Inspections and walkthroughs are specific types of reviews, but 'Reviews' is the broader category that encompasses all these objectives.

A testable requirement must be objective, quantifiable, and measurable. Specifying a response time of 'less than one second for the specified design load' provides a clear, measurable threshold, unlike subjective terms like 'user friendly' or 'portable'.

Integration testing focuses on relationships and interfaces between components. Option B correctly describes this - testing bugs in relationships and interfaces between pairs and groups of components. Option C is also correct because integration testing often happens in stages (incremental integration). Therefore D (B & C) is the correct answer.

Structural testing (also called glass box or white box testing) involves examining internal code structure and selecting specific paths through the program. Option C describes black box testing - feeding inputs and examining outputs without knowledge of internal structure. Since structural testing DOES involve internal knowledge, C is what it is NOT.

Estimating re-testing effort should be based on historical data from similar projects (metrics) AND discussions with the development team about expected changes and code quality. Time allocated for regression testing is a result of the estimate, not an input to it. Therefore D (a & b) correctly combines the two estimation approaches.

JUnit is an open-source framework (Option A) designed specifically for regression testing (Option B) in Java applications. It is NOT a general Java application development framework (Option C) - that would be something like Spring or Java EE. It is also NOT a web application framework (Option D) - that would be frameworks like JSF or Spring MVC.

Unit testing specifically focuses on testing the smallest testable part of an application - a single unit of code such as a method, function, or class (Option A). It does NOT test entire modules (Option B), whole applications (Option C), or database data directly (Option D) - those are integration or system testing levels.