Software Testing and Quality Control

A Quorum server is optional but recommended for Serviceguard clusters to prevent split-brain scenarios during network partitions. The other options are required: nodes must be on the same IP subnet for heartbeat communication, heartbeats are mandatory for cluster operation, and each node must run its own OS instance (which is standard, not optional).

The cmcld (cluster membership daemon) must run on all nodes in a Serviceguard cluster. It monitors node status, communicates membership changes, and ensures all nodes agree on cluster composition. Running it only on some nodes would break cluster integrity and communication.

Non-functional testing validates quality attributes rather than specific behaviors. Performance testing checks speed, scalability, and stability under load, while usability testing evaluates user experience and interface quality. System testing is functional as it verifies the system meets specified requirements.

Capture/playback tools record manual test interactions and replay them automatically, making them ideal for regression testing. They allow tests to be executed repeatedly without manual intervention, ensuring that recent changes haven't broken existing functionality. The other options are either not standard tools or not primarily used for regression automation.

To solve this question, the user needs to know about software testing techniques, specifically unit testing. The user must identify the correct term for a program that calls a function with test data to test its functionality.

Now, let's go through each option and explain why it is right or wrong:

A. Stub: A stub is a piece of code that simulates the behavior of a function or module. It is used in place of the actual function or module during testing. While a stub can be used in testing, it is not the correct term for a program that calls a function with test data to test its functionality.

B. Driver: A driver is a program that calls a function with test data to test its functionality. It is used to test functions that rely on input from other functions or modules. This option is correct.

C. Proxy: A proxy is an intermediary between two systems that allows them to communicate with each other. It is not the correct term for a program that calls a function with test data to test its functionality.

D. None of the above: This option is incorrect because option B, Driver, is the correct answer.

The Answer is: B

Boundary value testing focuses on testing at and around the boundaries of equivalence classes because errors often occur at edges. It tests values below, at, and above the boundaries of input and output ranges. It is distinct from equivalence partitioning (which divides inputs into classes) and is a black-box technique, not white-box. Combinatorial testing is a separate method.

Fault masking occurs when one defect or error condition prevents another defect from being observed or activated during software execution.

Developers struggle to test their own work effectively due to a lack of objectivity; they are naturally biased toward proving their code works rather than finding hidden faults.

ETL job unit testing MUST include negative scenario validation (A) - handling wrong data types, nulls, malformed data. Boundary testing (B) - field length limits, min/max values - is also essential. Option C is incorrect because jobs SHOULD abort for unrecoverable errors. Option D (unsolicited cleansing) is typically out of scope for unit testing.

Developers are responsible for ensuring numeric fields are properly tested with negative values, zeros, boundaries, and invalid inputs. This is a fundamental testing responsibility for any code handling numeric data. The statement correctly asserts this duty.

Performance testing is a broad category of testing. Load testing, volume testing, and stress testing are all specific sub-types of performance testing designed to evaluate system behavior under various conditions.

When a Windows application is already running before a test starts, configuring the tool to 'Record and Run test on any open Windows-based application' allows it to attach to and interact with the active process instead of attempting to launch a new instance.

The default add-ins loaded with QTP are ActiveX, Web, and Visual Basic (VB). These three add-ins provide foundational support for the most commonly used application technologies in automated testing.

Testers and the testing process require comprehensive access to all system resources: the database for test data and verification, host systems where the application runs, and input/output data files needed for testing. All these permissions are necessary for thorough test execution.

Setting initial and end conditions establishes a clear starting state and expected completion state for the test. This allows the same test to be executed multiple times with predictable behavior. Without defined conditions, tests may produce inconsistent results across iterations.