IBM Rational Quality Manager (RQM) Testing Fundamentals

The 'order source reference number' field in NRIS specifically stores the sales order number from the originating system. This serves as the cross-reference between NRIS and the source sales system. Option B refers to the order vector's internal number, not the reference field.

For tracking inbound interface errors (like CO2 documents) in custom Oracle integrations, errors are typically logged in a common logging table like wli_logging.XXRCI_commonlog. XXRCI.XXRCI_ERROR_TRACKING is a distractor.

Before creating an order, SKU and serial number combinations must be validated in both Oracle (the ERP system) and V21 (the inventory/fulfillment system). This dual validation ensures the product exists and is serial-tracked in both systems before order entry.

Collaterals in NRIS contain comprehensive order-related documentation including item warranty details, quantity information, shipping specifics, and consumer details. The 'all the above' option (E) correctly indicates that all these elements exist in the collateral records.

The Expected Result section defines what the test should produce when it executes correctly, which serves as the acceptance criterion for determining if the test case passes or fails. Post-conditions define system state after execution, Actual Result is what occurs during execution, and Result is just a general term.

Test cases and test plans typically start in the Draft state when first created. Other statuses like Under Review, Ready for review, or Approved represent subsequent stages in the lifecycle.

Not every test case requires a TER (Test Execution Record). TERs are created when test cases are actually executed, but test cases can exist in repositories without being executed. The relationship is one-to-many (one test case can have multiple TERs for different executions), not one-to-one mandatory.

A Test Execution Record (TER) comprehensively documents test execution details including the environment where tests ran (hardware/software configuration), high-level results (summary statistics), the owner/responsible tester, and test milestones (timeline and progress tracking). This complete audit trail supports traceability and reporting.

CQ (ClearQuest for defect tracking) integrates with RQM (Rational Quality Manager) allowing bidirectional launching. Users can initiate CQ directly from the Defects section, or from the test execution screen when adding a new defect triggered by test failure. This integration streamlines the defect lifecycle from test execution to defect creation.

A work item tracking system allows team members to assign, monitor, and update tasks, requirements, bugs, and other activities, facilitating status tracking. Assigning a test case or defect alone is too narrow to describe a work item's general purpose.

Test cases are not required to be linked to test plans. While linking provides traceability and organization, test cases can exist independently in repositories, be reused across multiple test plans, or be created ad-hoc for exploratory testing. The linkage is a best practice for structured testing, not a mandatory requirement.

Test management tools provide multiple access paths to test cases for flexibility and traceability. From Test Plans (organized by scope), Requirements (for requirement-test coverage), and Construction (test development/build phase). This multidimensional access supports different workflows: planning, verification, and execution.

TER stands for Test Execution Record, which documents the execution details and results of test cases. Option A (Test Execution Result) is incorrect because TER refers to the record itself, not just the outcome. Option C (Test Environment Report) is unrelated - TER tracks test execution, not environment configuration.

Severity (impact on system functionality) and priority (order of fixing) are independent attributes. A critical-severity bug affecting a rarely-used feature may have low priority, while a minor bug affecting a core feature may be high priority. Therefore, they do NOT need to match.

Test cases can have multiple valid statuses throughout the testing lifecycle. 'Passed' indicates successful execution, 'Failed' indicates defect discovery, 'Blocked' means execution cannot proceed due to dependencies, and 'Deferred' means postponement to a future iteration. All are legitimate states.

In IBM Rational Quality Manager (RQM), a 'release' maps to a 'Project' and a 'project' maps to a 'Test plan'. This is the standard terminology mapping in RQM's hierarchical structure.

Test plans are created and accessed through the 'Planning' section of testing tools like RQM. This section provides dedicated features for designing, organizing, and managing test plans. Construction and Requirements are different sections, and Builds refers to compiled code versions.

RQM provides three distinct views for test plans: Planning view (for designing tests), Execution view (for running tests and tracking results), and Reporting view (for analyzing test outcomes and metrics).

Test plans progress through a lifecycle with multiple states. 'Draft' is the initial state during creation, 'Ready for review' indicates completion pending approval, 'Approved' means authorized for execution, and 'Retired' indicates the plan is archived. All are valid states.

The Keyword view in test scripts is designed to organize commonly-used test steps into reusable components. This promotes modularity, reduces duplication, and allows teams to create libraries of standardized test actions that can be shared across multiple test scripts.