Unit 7, Systems Analysis and Design
7.8 System Development & Testing
This lesson introduces the principles of software testing during the System Development Life Cycle (SDLC). It details the testing strategies of White Box and Black Box testing, and outlines the hierarchical testing phases from individual Units to System Integration, System Verification, and final Acceptance Testing.
ප්රධාන සංකල්ප
- Test Cases
- A documented set of steps, test data, and expected outcomes designed to verify a specific feature or function of software during the development phase.
- White Box Testing
- A software testing methodology that examines the internal code structure, paths, and logic of a program using statement, branch, and path coverage techniques.
- Black Box Testing
- A testing technique where the internal code structure, implementation details, and processes of the software are unknown to the tester, focusing strictly on inputs and outputs against requirements.
- Unit Testing
- The lowest and earliest phase of testing, performed by software developers to verify that individual, isolated components like functions, classes, or procedures function correctly.
- Integration Testing
- A phase of testing where individual software modules are combined and tested as a group to identify interface defects and interaction issues between integrated units.
- System Testing
- An end-to-end testing phase conducted by an independent team to evaluate the complete, integrated system's compliance with functional and non-functional requirements.
- Acceptance Testing
- The final testing phase conducted before system handover to ensure the software satisfies business needs and user requirements, categorized into internal (beta) and external (customer/user) testing.
MCQ කට්ටල
MCQ 12විභාගයේදී
- Differentiating between White Box and Black Box testing
- Calculating Statement, Branch, or Path coverage percentages
- Writing or completing a Test Case sheet (inputs, expected results, actual results, status)
- Ordering the hierarchy of software testing (Unit -> Integration -> System -> Acceptance)
- Identifying the responsible parties for each testing level (e.g., developers for Unit testing, customers for Acceptance testing)
