Software Testing and Quality Control

Testability characteristics include Operability (ease of operating the system), Observability (ease of seeing results), Simplicity (ease of understanding), and also Controllability and Understandability. Robustness is a separate quality attribute that describes a system's ability to handle errors and unexpected inputs, not a characteristic of testability itself. A robust system might actually be harder to test because it handles errors gracefully.

Cyclomatic complexity is a white-box testing method used to measure the number of linearly independent paths through a program's source code. It requires examining the internal structure of the code (control flow graph), which is the defining characteristic of white-box testing. Black-box testing (B) focuses on inputs and outputs without examining internal structure, while green-box (C) and yellow-box (D) are not standard testing methodology classifications.

HP QC (now ALM) or MQC (Mercury Quality Center) is an industry-standard testing tool specifically designed for writing, organizing, loading, and executing test scripts during system implementations. While it tracks defects, its primary overarching purpose is managing the overall testing cycle and loading scripts.

User Acceptance Testing (UAT) is performed in the EAQ (Quality Assurance) system. EAD typically refers to Development, EAP to Prototype/Pre-production, and EAR to Recovery or another environment. UAT is the final testing phase before production deployment.

Inspection for SFG/FG is NOT involved in QM Level 2, E0 at Kraft. This indicates a specific quality management setup where intermediate and finished product inspection follows a different workflow than Level 2. QM levels determine inspection severity based on vendor performance or material criticality.

Service Trace Viewer (SvcTraceViewer.exe) supports multiple trace formats including Windows Event Tracing (.etl) files, Crimson tracing files, and WCF's own .svcLog format. This flexibility allows developers to view traces from various sources in a single tool.

The Controller component in Load Runner is responsible for executing and managing load test scenarios. It coordinates multiple Vuser groups generated by VuGen and monitors the test during execution. VuGen (Option A) creates scripts, and Analyzer (Option C) analyzes results after the test completes. Options D and E are incorrect.

Load Runner is primarily used for performance testing types including volume testing (testing with large data volumes) and endurance testing (testing system stability over extended periods). It is not designed for functional testing, which validates software functionality rather than performance. Option A alone is incomplete, Option C alone is incomplete, and Option E incorrectly includes functional testing.

The load testing process follows a logical sequence: Plan the test, Create scripts using VuGen, Define the scenario (load patterns, Vusers), Run the scenario using Controller, and Analyze results using Analyzer. Option A presents this correct sequence. Options B and D disrupt the logical flow by running scenarios before script creation or scenario definition, and Option C reverses the entire process.

web_reg_find is the LoadRunner function used for text validation - it checks whether a specific text string exists in the server response. web_reg_save_param is for correlation, lr_get_attrib_string gets parameter attributes, lr_check_text doesn't exist in LoadRunner.

QTP (QuickTest Professional, now Unified Functional Testing) is primarily used for functional testing to verify applications work as specified, and regression testing to ensure code changes don't break existing functionality. It is NOT used for load testing (that requires tools like LoadRunner) nor primarily for integration testing.

Context Sensitive recording is QTP's default and most commonly used mode because it records at the object level, making scripts more maintainable and readable. Analog recording captures exact mouse movements and keystrokes (useful for drag operations), while Low-level recording is a fallback when object recognition fails.

A test oracle is a mechanism or principle by which a tester determines whether a software has passed or failed a test. It requires the tester to know or identify the expected correct outcome to compare against the actual result.

A test plan is a comprehensive document outlining Scope (what will be tested), Resources (personnel, tools, equipment needed), Schedule (timeline, milestones, test cycles), and Quality (acceptance criteria, success metrics). Unit testing cases are part of test execution, not the planning document.

Software testing follows four hierarchical levels: Unit Testing (individual code components/modules), Integration Testing (combined modules working together), System Testing (complete integrated system), and User Acceptance Testing (end-user validation before deployment).