Software Testing Fundamentals and Methodologies

Stochastic testing uses random inputs and statistical models to test systems, which makes it a model-based testing approach. It relies on probabilistic models and statistical distributions to generate test cases, rather than following deterministic algorithms or heuristics.

Test support tools require ongoing maintenance to remain effective. Organizations often underestimate the effort needed to update test scripts, maintain tool configurations, and manage test assets as the system under test evolves. This is a recognized risk in test automation.

Operational acceptance testing is typically performed by system administrators to verify that the system meets operational requirements such as backup/recovery procedures, performance under load, and manageability. Customer acceptance is done by users, contractual by legal/business stakeholders, and regulatory by compliance auditors.

Structural testing (also known as white-box testing) can be performed at all test levels - unit, integration, system, and acceptance. It examines the internal structure and implementation of the software. System and Operational testing are primarily at the system level, while Integration testing focuses on interfaces between components.

Operational acceptance testing is performed by the end users or operators who will actually use the system in production. This is different from user acceptance testing (which may include business users) - operational testing focuses on operational readiness, maintainability, and recoverability from the operator's perspective.

A Test Plan document includes test items (features to test), test deliverables (reports, logs, etc.), and responsibilities (roles and tasks). Test Scripts are not part of the Test Plan outline - they are created during test design/specification, which comes later.

For a valid range of 18-25, the equivalence classes are: valid (18-25), invalid below (less than 18), and invalid above (greater than 25). Option A (17) is invalid because it's below the minimum valid value of 18. Options B (19), C (24), and D (21) are all valid values within the accepted range.

The valid equivalence class for passing the exam is scores from 24 to 40 (inclusive). Option C (29, 30, 31) contains only valid passing scores. Option A includes 22 and 23 which are failing. Option D includes 0, 15, and 22 which are all failing. Option B has 21 (failing) and 39, 40 (passing) - mixed classes.

Static testing involves testing without executing the code - it includes reviews, inspections, walkthroughs, and static analysis tools that examine code structure. Statement B is false because static testing by definition does NOT require running code through execution - that's dynamic testing. Statements A, C, and D correctly describe aspects of static testing.

Link Testing, which tests the interactions between integrated components, is also known as Component Integration Testing. It focuses on verifying that components can correctly communicate and exchange data. System testing and subsystem testing are broader scopes, and maintenance testing occurs after deployment.

Configuration management tools provide version control, traceability, and audit capabilities. Statement C is correct because these tools establish and maintain traceability links between testware (test cases, test scripts) and software work products (code, requirements) across different product variants. They don't typically provide statistical analysis (A), don't store bug reports (B) - that's bug tracking tools, and don't analyze structures (D) - that's static analysis.

Coverage measurement tools are primarily used by the development team during unit and integration testing to measure how much of the code is being exercised by tests. The testing team typically focuses on test design and execution rather than coverage measurement itself.

Based on technology and business experts, the Consultative Approach is most likely to be true as it involves seeking guidance from domain experts who understand the technical and business context. Reactive approach responds after problems occur, while Preventive approach tries to prevent issues.

Exploratory technique comes under the Dynamic Approach because it involves simultaneous learning, test design, and execution - all dynamic activities. Model Based Approach uses predefined models, Consultative Approach relies on expert input, and Preventive Approach focuses on prevention.

Live data is not under configuration management because it constantly changes and is transient. Configuration management controls versioned artifacts like documents, code, and controlled processes including Change Control, Reports, and Problem reporting.

When software is not user-friendly as expected, it indicates a Product Risk because it directly relates to the product's quality and fitness for use. Customer risk relates to customer satisfaction, Project risk relates to project constraints, and Organizational risk relates to organizational impact.

Risk analysis helps decide where to test more, what adverse effects might occur, and the impact of those effects. However, determining if coverage is complete is a coverage assessment decision, not a risk-based decision.

Incident Management covers tracking incident status, maintaining references to related incidents, and documenting expected versus actual results. However, finding the solution to an incident is typically handled by Problem Management, which investigates root causes.

User Acceptance Testing (UAT) validates that the system meets user requirements and is ready for production. The best source for Expected Outcomes in UAT scripts is the User Requirements, as these define what users actually need the system to do. Program specifications and System specifications are more technical and implementation-focused. Actual results are what you observe during testing, not what you expect.