Software Testing and Quality Control

GetCellData(Row, Column) is the correct QTP method to extract a specific cell value from a WebTable when you know the row and column numbers. The other options (CellData, TableCellData, CellDataValue) are not valid QTP methods.

RowCount is the correct property/method to get the number of rows in a QTP WebTable object. 'Rows' is not a valid property, GetRows is an ADO method, and 'None of the above' is incorrect since RowCount exists.

Testing cannot prove software has no faults - it can only demonstrate the presence of faults. Complete absence of faults is theoretically impossible to prove through testing alone. Finding faults, building confidence, and identifying performance problems are all valid testing objectives.

State Transition Testing is a black-box technique because it tests the system's external behavior as it transitions between different states without knowledge of internal code structure. The other options are all white-box techniques: Statement Testing examines code execution paths, Path Testing analyzes logical paths through code, and Data Flow Testing tracks how variables are used and defined throughout the code.

The statement is false because Alpha Testing is conducted internally at the developer's site, NOT at the customer site. Alpha testing is performed before release by the development team or internal testers. Beta Testing is the phase that occurs at customer sites after alpha testing is complete. This distinction is important in the software release lifecycle.

Option B is NOT a reasonable test objective because it's impossible to prove software has absolutely no faults - testing can only demonstrate the presence of defects, not their absence (Dijkstra's principle). The other options ARE reasonable: finding faults (A) is testing's primary purpose, giving confidence (C) through thorough testing is valid, and finding performance problems (D) helps ensure quality.

Static white box testing involves analyzing the internal structure, design, and source code of an application without actually running the program. This includes code reviews, inspections, and walkthroughs to identify logic errors or security vulnerabilities early in the development cycle.

Code coverage is a Dynamic White-box testing technique. It requires executing the code with test cases (dynamic) and analyzing the internal structure/branches (white-box). Static analysis examines code without execution, while black-box testing ignores internal structure.

Test-to-fail techniques intentionally push systems beyond normal operating conditions to expose weaknesses. Stress testing (overload), Repetition testing (endurance), and Load testing (volume) all target failure points. Data testing typically focuses on validation within normal parameters.

Parameterization is the technique of replacing hard-coded values in test scripts with variables that can take different values for each Vuser or iteration. This simulates real users entering different data (like different usernames, product IDs, or form entries) rather than all Vusers entering identical data.

web_reg_save_param is the LoadRunner function (in web Vuser scripts) that captures and saves dynamic values from server responses into parameters. These parameters can then be used in subsequent requests. lr_set_debug is for debugging settings, lr_think_time simulates user think time.

Web server plug-ins distribute incoming requests across multiple application server instances, while load balancers distribute network traffic across multiple servers. Both are essential for managing workload distribution and preventing overload on any single component.

The best practice for high availability is using multiple machines each capable of handling the full production load, allowing for failover when one machine fails. Load balancers alone between web and app servers don't provide complete HA. Authentication servers should be behind firewalls, not outside. Using fewer, larger machines creates a single point of failure.

In SQL Server, GETDATE() is the built-in function that returns the current system date and time. GetSystemDate() and GetCurrentDateTime() are not standard SQL functions, making B the correct choice.

In SQL Server, GETDATE() is the built-in function that returns the current system date and time. GetSystemDate() and GetCurrentDateTime() are not standard SQL functions.