Software Testing and QA Fundamentals

ISO 9126 defines six main quality characteristics: Functionality, Reliability, Usability, Efficiency, Maintainability, and Portability. Supportability is not explicitly listed as a main characteristic in ISO 9126, though it may be considered a sub-characteristic of Maintainability or related to other quality models.

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.

In quality management, the classic definition of quality is 'conformance to requirements', ensuring the product meets all specified criteria and user expectations.

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.

An ETL developer can identify and report defects during all stages of development, including requirements walkthroughs, code reviews, and unit testing phases.

Mainframe files traditionally use EBCDIC encoding, not UNICODE, Hexadecimal, UTF-8, or ASCII. Since EBCDIC isn't listed among options A-D, option E (None of the above) is the correct choice.

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.

In COBOL, COMPUTATIONAL (or COMP) is the general category for binary data types. COMP-1 and COMP-2 are for floating-point numbers (single and double precision). COMP-3 (or COMPUTATIONAL-3) is for packed decimal data. PACKED by itself is not a valid COBOL data type declaration - you must use COMP-3 or PACKED-DECIMAL for packed decimal format.

In DataStage development, omitting annotations or postponing them is bad practice. The options stating that comments are not mandatory/time-consuming, can be ignored during critical delivery, or added later are false.

EBCDIC is an 8-bit character encoding scheme developed by IBM for mainframe computers. It stands for Extended Binary Coded Decimal Interchange Code, which extends the earlier 6-bit BCDIC format to represent 256 different characters (as opposed to BCDIC's 64 characters).

The statement is false because NULL values mapping to non-nullable target fields MUST be handled in code through validation logic, default value assignment, or data cleansing rules. Without such handling, the ETL process would fail with constraint violations when attempting to insert NULL into NOT NULL database columns.

The declaration PIC 9(6)V99 COMP-3 represents 8 digits. In packed decimal (COMP-3) format, the formula for byte size is (N/2) + 1, rounded down. Thus, (8/2) + 1 equals 5 bytes.

If a Mainframe source file contains only standard text data without packed decimal fields (COMP-3), the test file can be easily created and read across Windows, Unix, Linux, or Mainframe environments.

When the ETL source lacks packed decimal fields, the test file is platform-independent because packed decimal is a mainframe-specific binary format that requires special handling. Without this complexity, test files can be created on any platform (Mainframe, Windows/DOS, or Unix/Linux) and will be readable by the ETL process.

ETL developers can and should identify defects throughout the development lifecycle: during requirement walkthroughs (logic gaps, unclear specs), code walkthroughs (implementation errors, logic flaws), and unit testing (functional bugs, edge cases). Each phase catches different classes of defects.

Add-ins extend QTP's object recognition capabilities to support specific technologies or applications. Loading the appropriate add-in enables QTP to identify, interact with, and properly record/test objects in the application under test.

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.