testing Online Quiz - 116

The Year() function extracts the four-digit year from a specific date variable, not from the system date. In this case, it returns 1962 from the MyDate variable, not the current year or the full date.

Bottom-up integration testing begins with low-level terminal modules that don't call other modules, then progressively integrates higher-level modules using driver programs. Top-down integration starts from the main module, not terminal modules.

Industry studies and research consistently show that testing and quality assurance activities consume approximately 40-50% of total software development budgets. This includes all testing phases from unit testing through system and acceptance testing across the lifecycle.

Quality Center (now known as HP ALM) requires Microsoft .NET Framework 2.0 during installation as it's built on .NET technology. Microsoft Excel and Word aren't required components, and .NET Framework 1.0 is too old - Quality Center needs version 2.0 or higher.

In HP Quality Center (QC), the common toolbar includes global navigation options like Back, Tools, and Help. Attachments are specific to individual entities (like a test or defect) rather than being part of the global, common toolbar that is always accessible.

Both Release Trees and Requirement Trees in Quality Center involve the same 3-step definition process: creating the folder structure, defining the entities, and establishing parent-child relationships. The process is symmetrical for both tree types.

QUICKTEST_TEST is the specific test type value used when creating tests in QuickTest Professional's API or object model. The other options (QTP_AUTOMATED, QUICKTEST_AUTOMATED, QTP_TESTSCRIPT) are not the correct test type constants used in QTP.

Performance testing focuses on system responsiveness, stability, and speed under load - NOT functional correctness. It identifies bottlenecks, aids performance tuning, and establishes baselines, but does not verify functional behavior which is the domain of functional testing.

Soak testing (also called endurance testing) is a performance testing type that checks system stability under extended load. Smoke testing is quick basic testing, adhoc is informal testing, and mutation testing involves modifying code to check test suite quality - none are performance testing types.

Standalone applications running on a single machine without network/server components have minimal performance testing scope. The other options (client-server, distributed, 3-tier) all involve multiple components, network communication, and concurrent users - key aspects for performance testing.

JMeter is a dedicated performance testing tool designed for load and stress testing. Options A, C (Silk Test, Rational Robot) are functional testing tools, and D (Bugzilla) is a bug tracking system - none are performance testing tools.

LoadRunner's key components are VuGen (Virtual User Generator for creating scripts), Controller (managing test execution), and Analysis (result analysis). 'Silent test runner' is not a LoadRunner component. Snapshot viewer is also not a standard LoadRunner component name.

Performance Testing is conducted during the final stages of STLC, specifically in the 'Final Testing and Implementation' phase. Before performance testing, the application must be functionally stable. Performance testing requires a near-production environment and comes after functional, integration, and system testing are complete.

Load testing specifically verifies application behavior under normal and peak load conditions. It measures response times, throughput rates, and resource utilization levels. The key phrase 'normal and peak load conditions' directly matches the definition of load testing, which differs from stress (beyond peak), endurance (sustained load), or capacity (maximum load) testing.

Acceptance testing is conducted to demonstrate that the system meets user requirements and is ready for deployment. Black box testing focuses on inputs/outputs without seeing internal code. System testing evaluates the entire system's compliance with specified requirements. Independent testing is done by a separate team, not specifically for user compliance.

Integration testing specifically focuses on testing the interactions and interfaces between different units or modules after they have been individually unit-tested. Unit testing tests individual components in isolation. Functional testing verifies specific functions. System testing tests the entire integrated system.

A test case is a documented set of steps, inputs, and expected results used to verify specific functionality. A test script is the automated code implementing test cases. A test condition is a specific state or situation to test. A test log records test execution results, not the procedure itself.

Verification means 'building the system right' - ensuring the software conforms to specifications and requirements (are we building it correctly?). Validation means 'building the right system' - ensuring it meets user needs (is this what users want?). Option A describes validation, not verification.