Skip to main content
UploadLanguage (EN)Support
BusinessMobileSocial MediaMarketingTechnologyArt & PhotosCareerDesignEducationPresentations & Public SpeakingGovernment & NonprofitHealthcareInternetLawLeadership & ManagementAutomotiveEngineeringSoftwareRecruiting & HRRetailSalesServicesScienceSmall Business & EntrepreneurshipFoodEnvironmentEconomy & FinanceData & AnalyticsInvestor RelationsSportsSpiritualNews & PoliticsTravelSelf ImprovementReal EstateEntertainment & HumorHealth & MedicineDevices & HardwareLifestyle
Deepak Sharma, profile picture
Uploaded byDeepak Sharma
PPTX, PDF1,403 views

3.software testing

This document discusses software testing principles and methodologies. It defines software testing as executing a program under various conditions to check for correctness, completeness, and quality. The document outlines different testing levels from unit to system testing. It also distinguishes between black box and white box testing methods. Finally, it describes different types of system testing like alpha, beta, acceptance, and performance testing.

Education◦
Downloaded 54 times
SOFTWARE TESTING BCA 5th Sem DEEPAK SHARMA 12KSSB6031
INTRODUCTION  It is the process used to identify the correctness, completeness and quality of developed computer software.  It is the process of executing a program/application under positive and negative conditions by manual or automated means. It checks for the : -  Specification  Functionality  Performance
SOFTWARE TESTING PRINCIPLES:  All tests should be traceable to customer requirements.  Testing should be planned long before testing stage begins .  Testing by third party will be very effective.  All tests should be traceable to customer requirements.  Testing should begin “in the small” and progress towards testing “in the large”.
Module Testing Unit Testing Sub System System Testing Acceptance Testing TEST PROCESS
TESTING METHODOLOGIES  Black box testing  White box testing
Black box testing  No knowledge of internal program design or code required.  Tests are based on requirements and functionality. White box testing  Knowledge of the internal program design and code required.  Tests are based on coverage of code statements, branches, paths, conditions.
TESTING LEVELS  Unit testing  Integration testing  System testing
UNIT TESTING  Tests each module individually.  Follows a white box testing (Logic of the program).  Done by developers.
INTEGRATION TESTING  Once all the modules have been unit tested, integration testing is performed.  It is systematic testing.  Produce tests to identify errors associated with interfacing. Types:  Big Bang Integration testing  Top Down Integration testing  Bottom Up Integration testing  Mixed Integration testing
SYSTEM TESTING The system as a whole is tested to uncover requirement errors. Verifies that all system elements work properly and that overall system function and performance has been achieved. Types:  Alpha Testing  Beta Testing  Acceptance Testing  Performance Testing
ALPHA TESTING It is carried out by the test team within the developing organization . BETA TESTING It is performed by a selected group of friendly costumer. ACCEPTANCE TESTING It is performed by the customer to determine whether to accept or reject the delivery of the system. PERFORMANCE TESTING It is carried out to check whether the system meets the nonfunctional requirements identified in the SRS document.
THANK YOU