Software Testing and Quality Control

According to standard ISTQB testing guidelines, designing test specifications, preparing test data, and executing/logging tests are core tasks of a tester. Interacting with tool vendors to leverage tools on the project is typically a test manager's responsibility, making statement i false and statements ii, iii, and iv true.

OAT (Oracle Application Testing) focuses on validating documentation existence and log file creation, but does not include performance testing of the Oracle service from connected entities. This specific performance check falls outside the standard OAT testing scope and requires separate testing tools or methodologies.

System testing produces multiple key documents throughout its lifecycle: a Test Plan outlines the approach, Traceability Matrices map requirements to test cases, and a Test Completion Report summarizes results. All three are standard deliverables from a system testing phase.

At the start of System Testing, the System Test Plan (STP) is prepared. This document defines the scope, approach, resources, and schedule for system-level testing. DTP (Detail Test Plan) comes later for specific test cases, MTP (Master Test Plan) is for overall test strategy across all test levels, and Traceability Matrices are prepared during test planning.

Test Plans are the designated tab or section in test management tools where test scripts and test cases are uploaded, organized, and executed. Test tabs typically show test execution status, while Defects tabs track bugs.

Quality Center Checker is the official tool used to verify that HP Quality Center (formerly TestDirector/QuickTest Professional QC) has been installed properly. It checks all components, database connectivity, permissions, and configuration settings. The other options (QC Install Checker, QC Install Inspector, QC Install Check) are not the correct names of the official verification tool for Quality Center installations.

When a defect is raised during a manual test run in Quality Center, it is directly linked to the specific Test Step that failed. This provides traceability from the defect to the exact step in the test case where the issue was detected. The defect is not directly linked to the Test (test case), Test Run (the execution instance), or Test Set (the collection of tests). The Test Step linkage allows precise identification of where in the test flow the defect occurred.

When a defect is raised during a manual test run in Quality Center, it is directly linked to the specific Test Step that failed. This provides traceability from the defect to the exact step in the test case where the issue was detected. The defect is not directly linked to the Test (test case), Test Run (the execution instance), or Test Set (the collection of tests). The Test Step linkage allows precise identification of where in the test flow the defect occurred.

Quality Center Checker is the official tool used to verify that HP Quality Center (formerly TestDirector/QuickTest Professional QC) has been installed properly. It checks all components, database connectivity, permissions, and configuration settings. The other options (QC Install Checker, QC Install Inspector, QC Install Check) are not the correct names of the official verification tool for Quality Center installations.

In manual testing, when a defect is found during test execution, it is linked to the specific test step that failed. This allows precise tracking of which part of the test case uncovered the issue. Test steps are the granular actions within a test case, making them the appropriate level for defect linkage.

OAT (Operational Acceptance Testing) includes test items related to the IT system itself. Maintainability and Reliability are quality attributes but are not OAT test items - they are characteristics that would be evaluated through testing. 'IT system' refers to the system as a test item within the OAT framework. 'All the above' is incorrect because maintainability and reliability are attributes, not test items.

Configuration testing ensures that artifacts (documents, code, settings) are properly maintained in a configuration management tool with proper version control. This is essential for tracking changes and maintaining system integrity. The other options are incorrect - there is a clear goal, and continuous monitoring is separate from configuration management.

BS 7925-1 is the British Standard 'Glossary of Testing Terms' that defines software testing vocabulary. IEEE 829 covers test documentation format, not definitions. ISO/IEC 12207 is for software lifecycle processes. ANSI/IEEE 729 does not exist as a testing standard.

Acceptance testing is performed to establish confidence that the system is ready for deployment and meets the business requirements. Finding faults is the focus of earlier testing phases, whereas acceptance testing evaluates usability, workflow alignment, and business readiness rather than component integration or system performance.

Agile Testing in Extreme Programming (XP) emphasizes test-first design where tests are written before code. XP treats development as the customer of testing, reversing traditional dynamics. Beta and Alpha testing are user acceptance phases, while Monkey Testing is random input testing.