Testing types "A5" 1 / 50 White box vs Black box testing – Same Only UI Only code coverage White = code structure, Black = functionality without code knowledge 2 / 50 White box testing किसे validate करता है? Only UI Only database Only functionality Internal code structure, paths & logic 3 / 50 Volume testing किसे check करता है? Code logic Module correctness UI elements Large data handling capacity 4 / 50 Usability testing क्या validate करता है? Ease of use, user experience Code coverage Database only Functionality only 5 / 50 Unit testing का main purpose क्या है? Entire system test करना Functional requirement validate करना Multiple modules integrate करना Single module / unit validate करना 6 / 50 Test case design main focus – UI colors Code structure Deployment nodes Scenarios, inputs, expected outputs 7 / 50 System testing कौन करता है? Developer Client Tester only Testing team complete system validate करती है 8 / 50 Stress testing का main goal – System break point determine करना UI testing Database correctness Normal conditions performance 9 / 50 Static analysis क्या है – Code execute करना Functional test UI check Code without execution review करना 10 / 50 Statement coverage किसे measure करता है – UI elements Code statements executed percentage Functional paths Database operations 11 / 50 State transition testing focus – Code statements Random inputs State changes & events validate करना UI colors 12 / 50 Smoke testing का focus क्या होता है? Basic functionality quickly verify करना All modules check Critical functionality Detailed functionality 13 / 50 Security testing main focus – Functionality UI design Workflow Vulnerabilities & data protection 14 / 50 Security testing focus – Functionality Performance only UI layout Vulnerabilities, data protection & unauthorized access 15 / 50 Scalability testing main focus – System expandability & resource handling UI workflow Regression only Single module 16 / 50 Sanity testing कब जरूरी होता है? Complete system test के लिए Major module changes के बाद Minor functionality changes verify करने के लिए New features add करने पर 17 / 50 Sanity testing vs Smoke testing – Same Both detailed Only UI focus Sanity = minor changes, Smoke = critical functionalities 18 / 50 Reliability testing measure करता है – Functional correctness System uptime, fault tolerance Code quality UI consistency 19 / 50 Regression testing कब किया जाता है? Existing functionality verify करने के लिए after changes Entire module rebuild करने पर Minor changes के बाद system check करने पर New functionality add करने पर 20 / 50 Regression suite use होता है – Only new features Only UI Only module test Existing features after changes test करना 21 / 50 Recovery testing किसे check करता है – UI only Functionality Database System crash after recovery capability 22 / 50 Recovery testing का goal – Functionality check UI correctness System crash के बाद recovery capability validate करना Performance only 23 / 50 Performance testing क्यों जरूरी – y Response time, throughput, resource utilization validate करना Only regression Only database Only functionalit 24 / 50 Performance testing का focus – Code paths Regression defects Functional correctness Response time, throughput, resource utilization 25 / 50 Path coverage का मतलब – All possible paths through code executed Single path execution Random paths UI navigation 26 / 50 Pairwise testing क्यों use होता है – Combinations efficiently cover करना Single value test All inputs individually test UI validation 27 / 50 Non-functional testing validate करता है – Functionality only Regression only Performance, security, usability, maintainability Unit tests 28 / 50 Monkey testing क्या है – Regression test Predefined scripts Only functional paths Random input, random behavior test 29 / 50 Manual testing किसके लिए है? Human tester द्वारा test cases execute करना Load testing Regression only Automated execution 30 / 50 Maintainability testing focus – Functionality UI layout Database only System easy update, fix & modify करना 31 / 50 Load vs Stress testing difference – Only UI Same Only database Load = expected workload, Stress = maximum load 32 / 50 Load testing किसे measure करता है? Module correctness Code logic Functional flow System under heavy load performance 33 / 50 Integration testing का goal क्या है? Individual module correctness Deployment environment check Performance testing Modules interactions validate करना 34 / 50 Installation testing validate करता है – Functional flow Database only Code correctness Software proper installation & setup 35 / 50 Grey box testing क्या है? Partial knowledge of code & functional testing Only code access Only UI testing Only functional testing 36 / 50 Gray box testing main benefit – Full code access Only UI knowledge Only database testing Partial code knowledge & functional testing 37 / 50 Functional testing validate करता है – UI correctness Performance Software requirements & functionality Security 38 / 50 Exploratory testing क्या है – Automated scripts Predefined test cases Only UI Tester dynamically test & learn during execution 39 / 50 Equivalence partitioning का goal – Valid & invalid input classes identify करना Only valid inputs test करना Test all inputs separately Only invalid inputs test करना 40 / 50 Dynamic analysis क्या है – Documentation check Inspection only Code review Code run करके behavior & performance check करना 41 / 50 Decision table testing useful है – Single condition check Multiple condition Multiple conditions & business rules test करना Random input Random Only UI 42 / 50 Compatibility testing validate करता है – Different platforms, browsers, OS UI colors Functional flow Code paths 43 / 50 Compatibility testing goal – Only code correctness Only UI colors Only functional flow Different platforms, OS, browsers validate करना 44 / 50 Cause-effect graphing किसके लिए – Only database UI only Random inputs Logic & condition relationships derive करना 45 / 50 Boundary value analysis क्या validate करता है – Only average values Extreme values ignore करता है Random inputs Input field boundaries & edge cases 46 / 50 Black box testing किस पर focus करता है? Internal code paths UI layout Database structure Functionality without code knowledge 47 / 50 Beta testing किया जाता है – Developer environment Internal team Code review team Real users / client environment में 48 / 50 Automated testing किसके लिए है? Regression only Tool / script द्वारा test cases execute करना Manual execution Smoke testing only 49 / 50 Alpha testing किया जाता है – Client site पर Third party environment Developer’s site internal team के द्वारा Real users के साथ 50 / 50 Acceptance testing का main purpose क्या है? Module integration check Client requirements satisfy हुए या नहीं verify करना UI correctness Code quality check Your score isThe average score is 0% 0% Restart quiz
