Software Testing and Quality Control

The 'Select Test' button in Test Lab opens a dialog where you can browse and select tests from the Test Plan tree to add into your test sets. This is how tests move from planning to execution.

Live Analysis graphs provide a visual overview of all tests contained within a selected folder in the Test Plan tree, showing execution status and other metrics at a glance for that test group.

In HP ALM/Quality Center, a live analysis graph in the Test Plan module typically provides a visual overview of the status and distribution of tests within a specific selected folder.

When a defect cannot be fixed due to missing requirements or insufficient code (a gap), it cannot be immediately resolved. 'Deferred' is the appropriate state because the defect is acknowledged but requires future work when requirements are clarified. 'Rejected' would imply the defect is invalid, while 'Fixed' and 'Closed' suggest completion.

Error guessing is an experienced-based testing technique where testers use their intuition to guess potential error conditions. Structuring this technique by enumerating possible errors (null inputs, boundary conditions, invalid formats, etc.) makes it more systematic and thorough than relying solely on intuition.

Testing finds defects so they can be fixed - it doesn't improve defects themselves. The benefit is improved software quality and reliability through defect detection and removal, not improvement of the defects. Testing identifies problems, fixing resolves them.

The Checkpoint timeout property in QTP specifies the time interval (in seconds) during which QuickTest attempts to perform a checkpoint successfully. If the checkpoint cannot be verified within this time, the step fails.

The Checkpoint timeout setting in QTP specifies the maximum time duration (in seconds) that QTP will attempt to successfully verify a checkpoint. During this period, QTP retries the checkpoint verification at regular intervals. If the checkpoint cannot be verified within the timeout, the step fails. This applies to all checkpoint types.

The OSS_TestExecution Sheet is the central spreadsheet where all components for a specific proposition are listed. This sheet contains an Execute flag (Yes/No) for each component, which determines which component scripts should be executed during the test run. OSS_cfg contains configuration settings, and Inter_TestCase_DataTransition handles data passing between test cases.

Log files in the logs folder contain detailed initialization information including whether required files like OSS_TestExecution Sheet and OSS_cfg were loaded successfully. The logs capture any loading errors, file path issues, or initialization failures that might occur when the framework starts up. HTML reports show test results, not initialization status.

To enable Quality Center to execute QTP tests remotely, you must configure QTP to allow remote test execution by setting the 'Allow QC to run tests remotely' option. This permission must be enabled in QTP before Quality Center can control test execution.

HP LoadRunner, Segue Silk Performer, and OpenSTA are all established performance testing tools. HP Performance Tester is not a standard product name (HP's performance tool is LoadRunner). The question correctly identifies A, C, and D as valid performance testing tools.

Performance testing mistakes include running tests for too short a duration (insufficient to reveal steady-state behavior or memory leaks) and using insufficiently populated test data (fails to represent real-world volume and variety). Tests that are too long or have adequate data are not mistakes - they're good practices.

Think time is the pause between receiving a response and submitting the next request, representing the time a user spends reading/processing the response before taking action. This is distinct from server response time (request to response) or other testing activities. Think time is critical for realistic load testing.

Stress testing evaluates system stability under extreme load (beyond expected capacity). Sustainability (endurance) testing checks performance over extended periods. Reliability testing ensures consistent behavior over time. Functionality testing verifies features work correctly, not performance - it's a functional test type.