Software Testing and QTP Fundamentals

The Keyword View's four main columns are Item (the object being acted upon), Operation (the action performed), Value (the data or parameters for the operation), and Documentation (auto-generated description). Item-Operation-Value forms the core test step, while Documentation provides readable explanations. The Comments column exists but is not considered one of the four MAIN columns.

In HP QuickTest Professional (QTP), the standard keyboard shortcut to start and stop analog recording mode is SHIFT+ALT+F3. This mode records precise mouse movements and keyboard inputs relative to the screen, whereas other function keys like F3 or F10 trigger different application actions.

A Reusable Action in QTP is specifically designed to be called from other tests or actions, enabling code reuse and modularity. Regular actions are local to their test, but Reusable Actions can be invoked externally with optional parameter passing. Call Action is not a type of action, and Split Action divides an action: it doesn't make it reusable.

GetCellData(Row,Col) is the correct method to retrieve data from an HTML Table in QTP/UFT. The other options (GetData, GetRowValue with various signatures) are not standard methods for table cell extraction.

QTP/UFT allows working with multiple function libraries simultaneously. You can have multiple function library files associated with a test and can edit them concurrently.

After recording stops, the Active Screen captures the test objects visible at that moment. You can insert additional steps on these captured objects because QTP maintains their object repository information.

QTP checkpoints can be renamed after creation. Right-clicking the checkpoint in the Expert View or accessing checkpoint properties allows you to modify the name for better identification.

QTP tracks execution time for each action within a test. You can view timing information in the Test Results window or programmatically access it through Reporter.ReportEvent or internal properties.

In HP QuickTest Professional (QTP), testers can easily associate external function libraries, typically stored as .vbs files, with a test. This feature allows scripts to call shared and reusable functions, which promotes modular test design and simplifies maintenance across multiple test cases.

Different test stages have distinct objectives: unit testing verifies individual components, integration testing checks interfaces, system testing validates the complete system, and acceptance testing confirms business requirements. Each stage serves a unique purpose.

Regression testing benefits most from capture/replay tools because it involves repeatedly executing the same tests after changes. Capture/replay allows quick re-execution of existing test suites without manual recreation, making it ideal for regression cycles.

C is correct because it specifies a measurable criterion (response time < 1 second) under defined conditions (specified design load), making it verifiable through testing. A is untestable because 'user friendly' is subjective without quantified metrics. B is untestable because proving zero faults is impossible - you can only demonstrate the absence of known faults. D is untestable because 'portable' is not defined with specific platforms or measurable criteria.

D is correct because testing high-risk areas first maximizes the value of testing effort - failures in critical functionality cause the most damage. A is suboptimal because finding many trivial faults is less valuable than finding critical ones. B is incomplete - coverage is meaningless if it doesn't target risk. C is wrong because ease of testing has no correlation with business impact or technical risk.

The statement that is NOT true is D. While end-users are involved in User Acceptance Testing (UAT), system testing itself is typically performed by independent test teams, not end-users. System testing focuses on verifying the system against specifications, while UAT focuses on business fitness. Options A, B, and C are all true: system tests use independent teams, functional (black-box) testing is more common than structural (white-box) testing at this level, and faults found later are indeed expensive to fix.

Testing is complete when the required level of confidence has been achieved (option B). This is the ISTQB principle: you test enough to meet the quality criteria and risk assessment. Option A (time runs out) is pragmatic but not ideal. Option C is impossible - you can never find all faults. Option D is unrealistic - users will always find some faults. The key is testing sufficiently to meet quality standards within constraints.

Stress testing (option C) is not described in unit test standards. Unit testing focuses on individual components and their logic. Syntax testing (A) can apply to code parsing, equivalence partitioning (B) is a black-box technique applicable at unit level, and modified condition/decision coverage (D) is a white-box coverage metric used in unit testing. Stress testing is a system-level non-functional testing technique that tests system behavior under heavy load, not individual units.

Boundary value analysis (option A) is a functional testing technique. It's a black-box test design technique that checks behavior at input/output boundaries. Options B, C, and D are non-functional testing types: usability testing focuses on user experience, performance testing checks speed/scalability, and security testing verifies protection against threats. Functional testing examines 'what' the system does, while non-functional testing examines 'how' the system works.

State transition testing (option D) is NOT a white box technique - it's a black-box technique that tests system states and transitions without looking at internal code. Options A, B, and C are all white-box techniques: statement testing checks executable statements, path testing analyzes execution paths through code, and data flow testing tracks variable usage. White box techniques require code visibility, while state transition testing only requires knowledge of system states.

Data flow analysis (option C) studies how data is used and flows on paths through code - where variables are defined, used, and killed. It's a white-box technique that identifies potential anomalies like using variables before initialization. Option A refers to performance analysis, not data flow. Option B is incorrect - data flow doesn't study rate of change. Option D describes complexity metrics like cyclomatic complexity, which is different from data flow analysis.

User requirements (option A) are the best source for expected outcomes in UAT scripts because UAT validates that the system meets business needs from the user's perspective. Actual results (B) are what happens during testing, not what should happen. Program specification (C) and system specification (D) are technical documents that describe implementation, not business requirements. UAT focuses on 'does this solve the user's problem?' not 'does this match the spec?'