Software Testing and Quality Assurance

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).

Telecommunications operations are categorized into Fulfilment (ordering, provisioning, setup), Assurance (monitoring, maintenance, troubleshooting), Billing (rating, invoating, payment processing), and BSS/OSS systems. Ordering and provisioning are Fulfilment activities.

US telephone numbers follow the format NPA-NXX-Line where NPA is the Numbering Plan Area (area code), NXX is the central office code (exchange), and Line is the unique subscriber number. This creates the familiar (XXX) XXX-XXXX format.

Quality Assurance focuses on process improvement and preventing defects by evaluating and improving the development and testing processes themselves. Quality Control focuses on finding defects in the actual product. QA is proactive and process-oriented.

Static testing involves verifying software without executing it. Techniques like inspection, review, and walkthrough examine documents and code manually to find defects early in the development lifecycle. This is different from dynamic testing which requires running the software.

Black box testing focuses solely on inputs and outputs without knowledge of internal code structure. Testers validate software functionality based on requirements and specifications, treating the software as an opaque system.

Performance testing evaluates how a system performs in terms of responsiveness and stability under various conditions. It includes testing aspects like wait times, throughput, and resource utilization to ensure the system meets specified performance criteria.

Cost of Quality refers to the total investment made to ensure a product is defect-free and meets customer expectations. It includes prevention costs (training, process improvement), appraisal costs (testing, inspection), and maintenance costs associated with quality activities.

Dynamic testing involves executing the software with inputs to verify actual outputs match expected results. This is the validation part of Verification and Validation, where the system is run to check if it behaves correctly under various conditions.

A test case is a document that specifies inputs, actions, or events and their expected responses to verify that a feature works correctly. It provides step-by-step instructions for testers to validate specific functionality.

Test Bed is the environment in which testing is conducted, including hardware, software, network configurations, and test data. It provides a controlled setup that mimics production conditions for thorough application testing.

Severity indicates how critical a defect is with respect to functionality - the extent to which it impacts system operations. Unlike priority (which reflects urgency of fixing), severity measures the technical impact of the defect on the application.