Software Testing Fundamentals and QTP Automation

QTP (QuickTest Professional) supports multiple Add-ins by default, including ActiveX controls, Visual Basic applications, and Web applications. Since all three individual options (a, b, c) are supported by default, option D (All of the above) is the correct answer.

White Box Testing techniques involve analyzing internal code structure, logic, and implementation. Equivalence Partitioning, Boundary Value Analysis, and Error Guessing are all Black Box Testing techniques that focus on inputs and outputs without examining internal code. Therefore, 'None of the above' is correct as none of these are White Box techniques.

Quality Control is defined as testing the software or product for its intended behavior - it involves actual testing activities to find defects. Quality Assurance focuses on process improvement and preventing defects. Option A correctly defines Quality Control as product testing for intended behavior.

Penetration Testing is specifically conducted to determine whether software is vulnerable to attacks by simulating real-world attacks. While Security Testing is a broader category, Penetration Testing is the specific technique mentioned for vulnerability assessment. Installation Testing and Recovery Testing serve different purposes.

The statement in option C is false: Verification is NOT a Quality Control activity. Verification is actually a Quality Assurance activity that involves reviewing documents and processes to ensure requirements are met. Validation is the Quality Control activity that involves actual testing. Options A and B correctly state the QA/QC distinctions, making C the false statement.

In automated testing with QTP/UFT, Add-Ins must be installed and loaded to enable the tool to recognize and interact with test objects of specific technologies in the target application. Add-Ons, Add-Froms, and Add-tools are incorrect terms and do not represent the required environment packages.

QTP/UFT is primarily designed for regression testing, which involves repeatedly running existing automated tests to verify that previously working functionality still works after code or configuration changes. While it can do GUI testing and web testing, its main strength and industry use case is automating regression test suites.

In test automation tools such as QTP/UFT, checkpoints are explicitly designed to verify properties and locations of objects like images in the application UI. Database values verify data integrity, output values capture runtime data, and images alone are assets rather than verification tools.

The Object Spy feature in QTP/UFT is used to view and analyze the properties, methods, and hierarchy of test objects and runtime objects in the application under test. While it helps with object identification, its primary purpose is to inspect object properties and methods, not to perform identification or verification operations.

In Oracle Order Management, when an order is imported successfully, the line status typically becomes 'Awaiting Shipping' once it passes through booking and eligibility checks. This indicates the order is ready for fulfillment processing but hasn't been shipped yet.

In this legacy enterprise architecture, dealer cable fulfillment is processed through Telnet rather than other platforms like Oracle, mobile applications, or SGI. Telnet serves as the primary system interface for completing these specific fulfillment actions, making the other options incorrect distractors.

This appears to reference a specific Oracle organization code used for cable order fulfillment/shipping. Without context about the specific organization codes (BA1, 867, 857, PMW), this is organization-specific knowledge rather than general networking/ERP concepts.

In Oracle Order Management, when assigning a picker (worker who picks items for shipping), the order is typically in 'Unreleased' status, meaning it's queued for picking but not yet released to the picker. After picker assignment, it would move to 'Active' or 'Queued' status.

This is a proprietary business workflow question. In this specific system configuration, order cancellation cannot be initiated or completed through either the DOAT tool or the Oracle database backend. Therefore, the statement is false, and the options asserting it can be cancelled via these platforms are incorrect.

In EDI systems, orders may not immediately sync to all visibility systems like DOAT due to integration delays or specific sync requirements. The visibility depends on system architecture and data transfer protocols.

The Warehouse Manager is responsible for warehouse operations and staff assignments, including roles like cable picker. This falls under warehouse operational management.

In HP/Micro Focus UFT, the Action toolbar provides options to view the details of a single action or navigate through the entire test flow. Other panels like the Test Pane show the hierarchy, but the Action toolbar specifically controls these view actions.

Quick Test users can add to the list of properties used to identify objects during test recording and runtime. Object identification properties are configurable and extensible in QTP.

The Object Spy in HP/Micro Focus UFT allows users to view both test object properties (static properties stored in the repository) and run-time object properties (dynamic properties of the actual object in the running application) along with their values.

GetROProperty (Get Runtime Object Property) retrieves the current actual property value of objects from the application during runtime. GetTOProperty gets test object properties (descriptive), while GetVisibleText retrieves visible text content.