soft_engg_lecture17 - Software Engineering Asim Banerjee...

Info iconThis preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon
Software Engineering Asim Banerjee 18 th March 2010 soft_engg@daiict.ac.in
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
IT314 - Software Engineering 2 Lecture Seating Plan (Sample) #1 #2 #3 #4 #5 #6 #7 #8 #9 Stage #10 #11 #12 #13 #20 #21 #24 #23 #22
Background image of page 2
IT314 - Software Engineering 3 Purpose of Testing Objective of testing: To identify all the defects existing in a software product Testing cannot guarantee error-freeness of the tested software product Because (except in case of trivial systems) input data domain of software products is very large and it is not practical to test the software exhaustively i.e. to cover all possible values in input domain Testing, however, provides a practical way of: Reducing defects Increasing user confidence in the software product Note : Because, testing does expose most of the defects in the software product
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
IT314 - Software Engineering 4 Levels of Testing Unit Testing Client Needs Requirements Design Code Acceptance Testing System Testing Integration Testing
Background image of page 4
IT314 - Software Engineering 5 Testing – Integration Testing (1/3) Integration testing Modules are integrated in planned manner During each integration step, partially integrated system is tested When ALL modules are integrated (and tested), the system is ready for system testing Types of Integration testing Top-down integration Bottom-up integration Regression Testing Smoke Testing
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
IT314 - Software Engineering 6 Testing – Validation Testing (1/2) Objective: To confirm that the developed system meets the requirements (as specified in SRS document in the section called validation criteria) Both plan and procedure are designed to ensure that All functional requirements are satisfied. All behavioral characteristics are achieved All performance requirements are attained
Background image of page 6
IT314 - Software Engineering 7 Testing – Validation Testing (2/2) Both plan and procedure are designed to ensure that (Continued) Documentation is correct Human-engineered and other requirements are met (e.g. transportability, compatibility error recovery, maintainability) Types of validation testing Configuration review Alpha testing Beta testing
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
IT314 - Software Engineering 8 Testing – System Testing (1/2) Objective: To confirm that the developed system meets the requirements (as specified in SRS document) Carried out according to the System Test Plan NOTE: System test plan is prepared during requirements phase (include test cases and expected results) Types of System testing Recovery testing Security testing Stress testing Performance testing
Background image of page 8
9 Testing – System Testing (2/2) Final output of this phase: Test report Tested System NOTE: 1.The test report may indicate a revisit to one of the previous phases. 2.Errors
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 10
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 33

soft_engg_lecture17 - Software Engineering Asim Banerjee...

This preview shows document pages 1 - 10. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online