Software Testing and QTP Fundamentals

Regular expressions in QTP are primarily used for three purposes: defining object properties in descriptive programming, parameterizing steps with dynamic values in object repositories, and creating checkpoints that match patterns. They are NOT used for creating function calls - that's done through standard scripting methods. Option D correctly identifies what regular expressions are NOT used for.

In QTP/UFT scripting, the SystemUtil object provides the Run method to launch external applications. The correct syntax is SystemUtil.Run "Notepad.exe" which opens the Windows Notepad application. Option B is nonsensical syntax, and Option C incorrectly references a Run object that doesn't exist in QTP.

QTP allows saving recorded scripts even when no active screens or applications are present. This is a standard feature - the recording captures object references and actions, not screen states. The script can be saved, modified, and replayed later regardless of what's on screen during the save operation.

In HP Unified Functional Testing, an External Action is a valid reusable action stored in a separate test that you can call from your current test. Recorded actions are simply local or reusable actions, and runtime actions are not a recognized category.

QTP uses mandatory properties (like class, name) as the primary object identification method. When these aren't sufficient to uniquely identify an object, QTP adds assistive properties to improve identification. If that still fails, it uses ordinal identifiers (index, location, creation time). Both assistive properties and ordinal identifiers are used when mandatory properties alone are inadequate.

Functions and actions are distinct concepts in modular programming. A function is designed to return a single value and can be used inline within expressions, whereas an action can have multiple output parameters and handles side effects.

In HP QuickTest Professional (QTP) / Unified Functional Testing (UFT), the Action toolbar contains options to view details of individual actions or the entire test flow. Other options like the Test Pane or Testing toolbar do not serve this specific navigation purpose.

In QTP (QuickTest Professional, now called UFT - Unified Functional Testing), F12 is the standard keyboard shortcut to insert a Standard Checkpoint during recording or editing test scripts.

A thoroughly specified test procedure is helpful but not always a strict precondition. Tests can sometimes be executed with minimal documentation or exploratory approaches. The other options (test environment, defect management, test oracle) are more universally required.

Profiling is a dynamic analysis technique that measures program behavior during execution to identify performance bottlenecks. Code complexity is static analysis, packet sniffing is network monitoring, and spelling checks are unrelated.

Experience-based testing (like error guessing or exploratory testing) relies heavily on tester skill and intuition. The other options suggest anti-patterns: utilization over skill, defect prevention focus, or defect-count metrics.

An audit is a formal review type specifically designed to determine compliance with standards, regulations, or requirements. Walk-throughs and inspections focus on defects, while management reviews address project status.

IEEE 829 (Standard for Software Test Documentation) specifies the format for test incident reports. 'Steps to reproduce' is a required section that documents the exact sequence of actions to recreate the incident. Test Items and Procedure Steps are not sections in an incident report template.

Verification ensures that the software meets its specified requirements at a particular phase, focusing on whether we are building the software correctly. Validation, conversely, asks if we built the right software. Other options are incorrect or incomplete phrasing.

Quality Assurance (QA) focuses on preventing defects through process improvement, standards, and guidelines implemented BEFORE testing begins. QA methods like audits, reviews, and training are preventive by nature. This distinguishes QA from Quality Control (QC), which detects defects through testing.

This is an exact duplicate of question 159088. Quality Assurance (QA) focuses on preventing defects through process improvement, standards, and guidelines implemented BEFORE testing begins. QA methods like audits, reviews, and training are preventive by nature. This distinguishes QA from Quality Control (QC), which detects defects through testing.

Quality Control (QC) activities like testing, inspection, and verification are detective in nature: they identify and detect defects AFTER they have been introduced. This is distinct from QA, which is preventive. The correct answer is 'Detective' because QC finds problems rather than preventing them.

Equivalence partitioning divides input into valid and invalid ranges. This question has three partitions: <10 (invalid), 10-21 (valid), >=22 (invalid). Option C (3,10,22) correctly samples all three: 3 from the low invalid partition, 10 from the valid partition boundary, and 22 from the high invalid partition boundary. Option A misses the invalid partitions entirely, B misses the high invalid boundary, and D misses the low invalid partition.

Boundary value testing focuses on testing at and immediately adjacent to the boundaries of equivalence partitions. This includes the boundary value itself, the smallest value just above it, and the largest value just below it. It is not the same as equivalence partitioning (which divides inputs into classes), does not test combinations of inputs (that's pair-wise testing), and is a black-box technique not specific to white-box testing.