ITEC 370 Lecture 19 Testing. Review Questions? Design document due by 10PM –System can be...
-
Upload
betty-wells -
Category
Documents
-
view
214 -
download
0
Transcript of ITEC 370 Lecture 19 Testing. Review Questions? Design document due by 10PM –System can be...
ITEC 370
Lecture 19Testing
Testing
Review
• Questions?• Design document due by 10PM– System can be implemented just by
following it
• Testing– Black, White, Glass– Different types, roles
Testing
Objectives
• Test plan–What, Why, How, Who– Explain what to test, how to test it, and
why
Testing
Sections
• Why do you think a test plan is recommended?
• What would you put in a test plan?• What might happen if a test plan is
not created / followed?
Testing
Sections
• Introduction• What is to be tested (tagged VCS)• What is to not be tested• Approach (manual, automatic)• Pass / fail criteria• When test should be stopped
Testing
Sections
• Deliverables– Document– Test cases (scenarios)– Scripts / scaffolding– Results (log files)– Report (sumary)
Testing
Sections
• Environment– OS, Pre-requisite versions, what other
processes are running, etc…
• Estimate• Schedule• Staffing needs• Responsibilities• Risks
Testing
Purpose
• Guide the testing process• No compile it and see if it works…• Can be quite tedious– iPod programming environment
• Only as useful as you make it– Out of date document not useful– Creating for sake of creating, not useful
either
Testing
Requirements
• If you didn’t have usage scenarios, create them
• Determine how to test each particular requirement in your SRS
• Ok to group several requirements together
• Make sure you cover common usage scenarios!
Testing
Design
• What classes does a particular test target?
• What parts of the design are the most complex?
• Are the tests covering the entire system?
• Are you testing parts in isolation or in collaboration
Testing
Implementation
• What part was the hardest to write?• What part “smells”• Who has the highest bug-rate?• Random test X part
Testing
Scale
• What happens if you spend too much time testing?
• What happens if you spend too little time testing?
• Adjust formality / amount of testing as project size increases
Testing
Report
• Determine who communicates with who
• What the test case is• What bug is present– Screenshots– Logfiles
• Whether or not the bug can be replicated
• Severity of bug– User / Developer
Testing
Your project
• I will expect a test plan from each of your groups
• Should cover each requirement• Whether you follow it and use it to
find/fix bugs is up to you
Testing
Review
• Test plan– Sections– Importance
• Next week– Bug tracking / Interface testing