10 Smoke and Acceptance Testing
Plumbers do a 'smoke test'
small number of tests to catch major problems
(Most Java students ONLY do 'smoke testing')

Is it even worth testing in its current version?
Weekly software updates in a lab;
if worse than current version, do not install!

Unscripted: play around
Scripted: specific plan

media testing:
make sure all files are readable
[I did this with the Lemuria and Canvas pages]

Acceptance Testing
	smoke testing is subset of acceptance testing
	e.g. 0 based counting may not be acceptable
	usually agreed in advance
	(may not get paid if does not pass)
Operational Testing/Field Testing
	actually running the system with real customers and real data
	(last testing of the system)
	Can be expensive to find errors this way!
User acceptance testing (UAT)
	(dont help! Most users wont have IT coaches)

'alpha testing' –team external to deveopment plays with (hopefully complete) system
	can be pre-selected actual customers
'beta testing'
	broader release to actual customers
	in computer games, beta testers often get the software for free
	GMAIL was a beta test for five years
	lots of (cheap realistic) testers!
dog-fooding—those writing the system are using the system
	first full screen text editors, team switched to the prototype ASAP