ALM and PEST Management Fundamentals

The test schedule section specifically details timelines, planned start and end dates, and testing milestones. The test plan section covers scope and strategy, requirements covers what to test, and summary provides a high-level overview.

Work items (for defect tracking, task management, or follow-ups) can be created at any level of the testing hierarchy. This provides flexibility - you can track issues at the test case level, test suite level (affects multiple tests), or individual test script level.

Standard software testing includes five phases: Unit testing (individual components), Integration testing (combined components), System testing (complete system), Acceptance testing (user validation), and Regression testing (ensuring new changes don't break existing functionality).

The Precondition section specifies the required state, setup, or conditions that must exist BEFORE a test case can be executed. This ensures the test starts from a valid, known state. Postconditions describe the state after execution, while Test case design covers the test logic itself.

In Application Lifecycle Management (ALM) tools, defects are opened as 'New ALM requests.' This creates a defect ticket that can be tracked through the lifecycle (assignment, investigation, fix, verification). Tasks, comments, and phases are different entities in the ALM workflow.

This statement refers to a specific system configuration or workflow rule where resolving a PEST (possibly a typo or system-specific defect acronym) does not automatically trigger an owner notification. Without external context, we accept the stored key.

The RCI (Requirement Change Impact or Request/Change/Impact) workflow tab consolidates critical metadata including Business Priority (for triage and scheduling) and Environment Details (hardware/software configuration needed). This centralization supports impact analysis and execution planning. The Related Records, Project, and Request tabs serve different purposes (linkages, project classification, and request details).

A single project can have multiple enhancement requests addressing different features, improvements, or change requests. Enhancement requests track specific desired changes, and projects typically evolve through multiple enhancements over time. The relationship is one-to-many (one project, many enhancement requests).

The Related Records tab in ALM (Application Lifecycle Management) requests establishes traceability between different artifacts. Its specific purpose for PEST (likely Product/Project Enhancement/Defect tracking) is linking it to Enhancement requests, showing how a defect or enhancement connects to formal change requests. Options A (linking PESTs together) and C (linking test cases) are handled through different relationship mechanisms.

Query by Release is a standard query template that locates projects within specific release cycles or versions, providing release-based filtering and organization. Public queries and personal queries are query access/organization categories, not specific query templates. Query by Role filters by user roles, not project location.

The RCI (Request/Change/Impact) workflow tab contains the field or mechanism to mark a defect as a Showstopper (critical severity that blocks release). Related Records handles linkages, Attachments stores files, and Comments captures discussion. Severity classification like Showstopper is a workflow/decision attribute typically in the workflow tab.

When a PEST (defect/enhancement) is retested and passes verification, it moves to Completed status indicating the issue is resolved and verified closed. Activated would mean it's open/in progress, Opened is the initial state, and Accepted is an intermediate approval state but not the final closed state after successful retest.

The Related records tab in an ALM task allows linking related PEST (likely Problem/Enhancement/Software Task) items with a retest task. This maintains traceability between the original issue and its verification task. Options A, C, and D are incorrect - the tab is for linking PEST items, not test cases or projects, and 'None' is false since B is correct.

The Resolution tab is a feature specific to ALM tasks, not ALM requests or comments. Tasks require resolution documentation when closed, whereas requests track issues and comments are discussion threads. Option B is correct; A, C, and D are incorrect.

Root Cause Investigation (RCI) details are documented in the dedicated RCI workflow tab. This tab is specifically designed for capturing and tracking root cause analysis. The Related records, Project, and Attachments tabs serve different purposes (linking, project metadata, file storage).

ALM requests can be viewed in two ways - likely a detail view and a list/grid view. This is a UI feature question specific to the ALM system being referenced. Without access to the specific ALM tool documentation, I cannot verify if this is accurate.

To retest a PEST, a new ALM task must be created. This is standard workflow practice - retesting is a separate activity requiring its own task entity. ALM requests track issues, comments are for discussion, and phases are workflow stages, not retest vehicles.

The Utility menu in ALM provides the option to mark a PEST as a duplicate. 'Modify' is for editing, 'Change status' updates the workflow state, and 'None of the above' is incorrect since Utility is the correct answer.

Priority 1 (highest severity) PEST items must be addressed within 24 hours per standard SLA practices. Options A (48h), C (72h), and D (36h) are incorrect - they represent lower priority SLAs or arbitrary times not matching P1 urgency.

Email notifications in ALM are sent using the Notify List feature. This allows users to specify who should receive alerts. 'Build found in' and 'comments' are not notification mechanisms, and Microsoft Outlook is an email client, not an ALM notification feature.