1
Topics to be discussed Introduction Objectives Testing Life Cycle Verification Vs Validation Testing Methodology Testing Levels 2
INTRODUCTION It is the process used to identify correctness, completeness and quality of developed computer software. It is the process of executing the program/application under positive or negative conditions by manual or automated means. It checks for the:- Specification Functionality Performance BACK 3
OBJECTIVES Discover as many errors or bugs as possible in a product. Demonstrate a given software product matching its requirement specification. Validate the quality of a software testing using the minimum cost and efforts. Generate high quality test cases, perform effective tests and issue correct and helpful problem reports. BACK 4
ERROR, BUG, FAULT & FAILURE Error: It is a human action that produces the incorrect result that produces a fault. Bug: The presence of error at the time of the execution of the software. Fault: State of software caused by an error. Failure: It is the deviation of the software from its expected results. It is an event. BACK 5
TESTING LIFE CYCLE 6
TEST PLAN It is a systematic approach to test the system or software. The plan typically contains a detailed understanding of what the eventual testing flow will be. BACK 7
VERIFICATION VS VALIDATION Verification: The software should confirm to its specification( Are we building the product right ?). Validation: The system should do what the user really requires(Are we building the right product?). BACK 8
TESTING METHODOLOGIES Black Box Testing No knowledge of internal program design or code required. White Box Testing Knowledge of the internal program design or code required. 9
10
11 BACK
TESTING LEVELS Unit Testing Integration Testing System Testing BACK 12
DISCUSSION In order to be cost effective, testing must be concentrated on areas where it will be more effective. The absence of an organizational testing policy may result in too much efforts and money will be spent on testing. BACK 13
THANK YOU BACK 14