Software Testing and RFT Fundamentals

Contracts are legally binding agreements where promises are exchanged for consideration (something of value). Copyrights protect intellectual property rights, Patents protect inventions, and Torts deal with civil wrongs - none of these primarily focus on binding promises in exchange for consideration.

A quality record (D) documents what happened during past activities, making it evidence of compliance rather than a requirement standard. Coding standards, requirements specifications, and tailored processes all define expected behaviors that auditors would evaluate against.

The customer typically has final authority over requirements and priorities since they fund the project and define business value. Business analysts gather requirements, project managers coordinate execution, and direct users provide input - but none have the customer's ultimate decision authority.

A phase gate review is a key project review marking the transition between project phases, making its completion a major milestone. A critical activity is a task on the critical path rather than a milestone, while a peer review or a test case represents individual tasks that do not signify phase transition.

Phase containment, defect detection efficiency, and test case execution cycle time all measure aspects of test process capability. Test case defect density (D) is a product quality metric, not a process capability metric - it measures test thoroughness, not execution process performance.

Boundary testing requires testing at the exact boundaries (4, 5, 25, 26) to verify correct handling of minimum, maximum, and just-outside-bounds values. Option C only tests within valid range (5, 6, 24, 25) and misses the critical boundary failure cases, while Option A includes arbitrary values.

Tracking defect report status through their lifecycle is a core change management function. Option B describes build automation, Option C describes configuration library management, and Option D describes versioning/baseline management - these are SCM functions but not the primary change management role.

Data pools in RFT can be copied between projects using copy/paste or export/import functionality. This allows reusing test data across different test projects without recreating it manually.

The dpNext() method is the standard RFT API call to advance the datapool cursor to the next row. Other options like dpMoveCursor(), dpNextRow(), or dpMoveNext() are not valid RFT methods.

Datapools in RFT are independent resources that can be referenced by multiple test scripts. This design promotes test data reuse and consistency across different test cases.

RFT supports multiple log types including Text log (default) and HTML log for formatted output. Java is not a log type in RFT - it is the scripting language used to write tests, not a logging format.

Scripts in RFT are tightly coupled to object maps that are project-specific. When copying a script to another project, the associated object references do not automatically transfer and must be remapped to the new project's object map.

The inputKeys function simulates physical key press events (such as pressing the Enter key on a keyboard), whereas inputChars enters literal character strings (typing out 'E-N-T-E-R' letter by letter). The distractor options either invert these definitions or incorrectly assert that they perform identical operations.

Java uses the 'import' statement to include packages and classes. In RFT scripts written in Java, you use 'import com.rational.test.*' style statements to access RFT-specific classes and functionality.

RFT datapools use the .rftDP file extension (note the capital DP). The .dp extension is not used by RFT, and file extensions are case-sensitive in most operating systems.

Rogers applications that can be launched through SSO include CIM (Customer Interaction Management), SGI, CSM (Customer Service Management), and TOE Fido. SSO (Single Sign-On) allows users to access multiple applications with a single authentication, improving user experience and security across these Rogers systems.

CIM (Customer Interaction Management) system supports three main types of contacts: Consumer customers, Business - Cable customers, and Business - Wireless customers. This categorization helps Rogers organize and manage different customer segments based on their service type (residential vs. business) and service category (cable vs. wireless).

The contact status lifecycle in Rogers' CIM system includes four main statuses: New (newly created contact), Active (currently engaged contact), Inactive (temporarily inactive), and Obsolete (no longer valid or relevant). These statuses help track the current state and lifecycle of customer contact records.