Software Testing and Quality Control

Apache JMeter is an open-source Java-based tool designed for load testing and performance measurement. It simulates heavy user loads on applications, servers, and networks to test performance under stress. JMeter supports various protocols including HTTP, JDBC, JMS, and SOAP, making it widely used for performance and load testing.

White box testing inspects the internal structures, logic, and implementation details of the software's source code. In contrast, black box testing is concerned with external functional behavior, and other testing types handle non-functional requirements such as reliability and portability without directly analyzing the source code.

Black box testing focuses exclusively on verifying that the software's functional requirements meet specifications, treating the internal code as a 'black box'. It does not inspect the source code, which is the domain of white box testing, nor does it primarily target portability or reliability directly.

Automated testing tools increase tester productivity by reducing manual effort, can lower infrastructure costs through efficient resource utilization and faster execution, and contribute to higher product quality through consistent, repeatable test coverage. Since all three benefits are valid advantages of test automation, 'all of the above' is correct.

Low-Level Recording records mouse clicks and keyboard actions using absolute screen coordinates, which is useful when QuickTest does not recognize standard objects. Analog recording tracks continuous movements like drawing, while Normal recording relies on identifying specific GUI objects. Therefore, Low-Level recording is the correct choice here.

Object Spy is the QTP/UFT tool specifically designed to investigate and view object properties, methods, and hierarchy. When you point Object Spy at an object in your application, it displays all the test object and runtime object properties, operations, and identification information. Object Repository and Object Repository Manager are for managing stored objects, not for ad-hoc investigation.

According to classic software testing principles, testing is defined as executing code with the primary goal of finding defects. Demonstrating that a program works or is defect-free is logically impossible because testing can only prove the presence of defects, not their absence.

Big-bang integration is not an incremental testing approach - it integrates all system components at once rather than in stages. Top-down (A) and bottom-up (C) are both incremental strategies that integrate modules gradually. Functional incrementation (D) is another incremental approach where features are added incrementally.

Exit criteria include thoroughness measures like coverage of code, functionality, or risk (i) - this measures how completely testing was done. They also include estimates of defect density or reliability measures (ii). Residual risks such as unfixed defects or lack of test coverage (iii) are also part of exit criteria. Verifying the test environment (iv) is typically done during test planning, not as an exit criterion. Therefore options i, ii, and iii are correct.

Test closure activities include checking which planned deliverables have been delivered (i) and finalizing and archiving testware (iii). They also involve analyzing lessons learned from the testing process (iv). Defect report analysis (ii) is typically part of test execution activities, not closure - closure focuses on completing and learning from the test process, not analyzing individual defects.

Regression testing should be performed after the software has changed (ii) to verify existing functionality still works. It should also be done when the environment has changed (iv) since environmental changes can affect behavior. It's not required every week (i), 'as often as possible' is impractical (iii), and doing it just when the project manager says (v) without trigger-based criteria is not proper practice. Regression testing is triggered by actual changes, not arbitrary schedules.

The Android emulator is launched using 'emulator -avd ' where is replaced with the actual AVD name. Option C shows the correct syntax with the placeholder. The 'emulator -test' option doesn't exist, and '-avd' alone without a name is incomplete.

Development is the environment where code/config changes are initially implemented and tested. Staging is for pre-production validation, and Production is the live environment. Making changes directly in Production is against standard practices, making Development the correct answer.

A SilkTest project is indeed a collection of files containing all necessary information about a test project, including test scripts, application states, test plans, and frame files. This is the fundamental organizational unit in SilkTest.

The SilkTest Agent is the component that resides on the target system (where the application under test runs) to execute commands received from the SilkTest Host. It interacts directly with the application, rather than wrapping interactions solely through a browser's DOM.