Software Testing and Quality Control

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.

Running SQL Alter in Report mode with 'Build Script file' option generates a script showing the discrepancies without executing changes. This lets you review differences between record definitions and SQL tables safely. The other options involve permissions or audit modes that don't generate comparison scripts.

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.

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.

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.

Based on the available options and elimination of other roles (Tester, Developer, End User), Sarah Clubley is identified as the Business Analyst. Business Analysts typically bridge the gap between business requirements and technical implementation.

TEST is a debugging utility/command in Natural that allows programmers to trace program execution, examine variable values, and set breakpoints. While modern development environments use SPoD (Single Point of Development) with graphical debugging, TEST remains the foundational debugging tool referenced in Natural programming curriculum and documentation.

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.