Software Testing and Quality Control

Active Screen captures and displays snapshots of your application at each step during the recording session. This feature helps testers visually verify what the application looked like at specific recording points, aiding in test maintenance and debugging.

In HP QuickTest Professional (QTP/UFT), objects that belong to a shared object repository are displayed in gray to distinguish them from local repository objects.

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.

In PRPC service configuration, three components are mandatory: Service Package (container for services), Service Method (defines the interface/operation), and Service Activity (contains the implementation logic). Service Architecture is not a standard component in PRPC service configuration.

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.

Form applets display data from multiple tables through joins and business component layer abstraction. They're not limited to one table or one column - they aggregate related data. Option B correctly states they access data from many tables and columns.

HP Quality Center is a web-based test management tool used to manage requirements, plan and schedule tests, execute test suites, and track defects throughout the software development lifecycle.

Tests are linked to requirements within the Requirements module using the Test Coverage tab, allowing users to map specific test cases to individual requirements.

When a defect is valid but cannot be fixed immediately due to a gap in requirements or lack of code/resources, its status is set to 'Deferred' to be addressed in a future release.

Establishing a Traceability Matrix in Quality Center involves linking requirements to tests (Requirements-Test coverage) and analyzing how requirements cover the test plan (Test Plan-Requirement coverage) to ensure full alignment.

In Quality Center (now HP ALM), test cases are executed in the Test Lab module. The Test Lab is specifically designed for test execution, where test sets are created and run. Test Plan is for design, Defects for tracking issues, and Releases for managing release cycles.

A test plan tree can be created by defining test folders and tests manually in the Test Plan module. This hierarchical organization allows grouping tests by subject area, feature, or other criteria. Converting releases or saving automated tests are different workflows.

Requirement traceability is the mechanism used in Quality Center to relate requirements to one another, establishing parent-child or peer relationships to track dependencies.