Testng level 1 Uni! Testing —» indadanl Modade Teshig > thle Bor Testi Qe Tategoabon Teshyg - inbegacde te ox More Medules —» Black Bax Testes 3. System i — Complete Module whale Systeen> Black Box Testi. ‘ facts Ta AlpheTestig Bela Tesh blyAlpha Testing Tester, User Poexent *Alpha testing is performed by the developers within the organization before releasing the software to actual users. *It is done in a controlled environment. *The main goal is to identify bugs or defects before delivery. *Usually includes both functional and non-functional testing. *Alpha Testing software #1 release #tt B Wel developer GANT organization far sat 1 ae controlled environment 4 @rar zl ‘FSI TEAVA F bugs A defects H Taal “gaa functional 3X non-functional testing dal wit et AHA FIKey Points /7ea fag: “Done before release / Release 8 Tee *Performed by developers / Developer zarn/ Testes +Environment: Controlled / fafa — De cpg Cioran B Fechig . “Cost-effective / Tec testing a 3Beta Testing *Beta testing is performed by actual users outside the organization after alpha testing. *Done in a real environment where the software will be used. *Goalis to find defects that may occur in real-world usage. *Feedback from users is used to improve software before final release. “Beta Testing software #Y alpha testing ® @q realusers qanT far oat 81 *ag real environment & grat zl TERRA t real-world usage A Het ae defects H Wale “Users #1 feedback software #1 finalrelease @ Yea improve Ha A Fag Ba FIKey Points / et fag: ‘Done after alpha testing / Alpha testing & aq *Performed by real users / Real user @4RT *Environment: Real-world / 378at STAT ATATALoT *Feedback helps improvement / Feedback @ quarPade The = User $B AchalReionat Med) ar 2) ¥ User Al aatS ITE Reqpivemant 3 Acconci System|fethere 5 Douche ran sven 1 zzr ath Nen-Paacheral Testa: ~User Expedbchan TeshesNon-Functional Testing (NFT) *Non-Functional Testing checks how wella system performs rather than what it does. *Focuses on quality attributes like performance, reliability, usability, security, and scalability. ‘Verifies system performance under various conditions. *Non-Functional Testing a aitadt & fF system Hal HA Far B, wort ae fH Fa Het Sra ZI *Focus: Performance, reliability, usability, security, scalability are “System #1 performance fafstet conditions 4 check dt a1Type Performance Testing Load Testing Stress Testing Usability Testing Description Measures speed, responsiveness, and stability Tests system under expected load Tests system under extreme conditions Checks user- friendliness Example Website handles 1000 users at once 500 concurrent users on app System under 2000 users: Ease of navigation onapp Hindi Speed 3 responsiveness check &taT safes load FT testing Maximum capacity ‘WW testing User-friendly interface check ateSecurity Testing Comp: ity Testing Reliability / Stability Testing Maintainability Testing Scalability Testing Checks protection against threats Checks system on different environments Checks uptime, error-free operation Checks ease of maintenance and updates Checks system growth capacity SQLinjection, password encryption Windows/Linux/Ma c, browsers ‘Server works 24x7 without crash Updating software modules Add more users without slow performance System axfarat @ at ae fafiter os sit devices TT testing System Waa Wer aI FT Werf aT System maintain art # amare aedt demand handle ta@ Difference Between Functional and Non-Functional Testing Feature Focus Based on Example Goal Test Type Functional Testing What system does Requirements / Functionality Login works correctly Correctness of features erect Black Box / White Box Non-Functional Testing How system performs Quality attributes iL Performance Login responds within 2 seconds Performance, security, reliability Usually Black Box/ Specialized toolsVoufshon Teshg 4 Valdshen Testi1. Verification Testing Verification is the process of checking whether the software is built correctly according to specifications. @ Are we building the product right? Verification 4 check #ta & fF software specifications * Hae wel cara war & aT aetl iP FA BF product Het aa Te A?Characteristics / faetware *Done during development *No code execution required *Static testing *Checks documents, design, code Examples Requirement review *Design review *Code review *Inspection2. Validation Testing Validation is the process of checking whether the software meets user requirements. @ Are we building the right product? Validation 4 check #taT = f¥ software user #1 requirement #1 QW ara & oT atl t Op FI BH AEF product aat WB? (eherhon ybdohon aay cet aft proluck sary ¥) Produc! Right Right Produc:Characteristics / faetvare *Done after development *Requires code execution *Dynamic testing *Checks actual working system Examples *Functional testing *System testing User acceptance testingVerification Are we building product right? Static testing No code execution During development Checks specifications Validation Are we building right product? Dynamic testing Code execution required After development Checks user requirements