sl4m

customer (business) facing test
technology (code) facing test
whole team approach
power of three
iteration
feedback

edge case
happy/sad paths
refactor

sl4m

8 core agile testing practices

Acceptance Test Driven Development
Automated Functional Testing
Test Driven Development
Automated Unit Testing
Exploratory Testing
Collective Test Ownership
Continuous Integration
Rehearse Release

sl4m

exploratory testing studies

@jamesmarcusbach: I have seen a few studies of exploratory testing that were scientifically respectable, but none of those used the term "exploratory testing"

@Rob_Lambert: Care to share the scientifically respectable studies? Genuinely interested to find out how they studied ET.

@jamesmarcusbach: Study #1: See the book "Exploring Science." It is the chronicle of a group of experiments in figuring out technology.

@jamesmarcusbach: See Jerry Weinberg's 1965 Ph.D. dissertation on exploratory problem-solving: http://bit.ly/KTXML

sl4m

no tests

legacy code base
"dirties" design
it doesn't catch bugs
it's slower
it's boring
hard to change
too many interfaces
testing is for qa

sl4m

my software testing blogs in google reader (by order of first name):

Abby Fichtner
http://www.thehackerchickblog.com/search/label/testing

Adam Goucher
http://adam.goucher.ca/

Aidy Lewis
http://agiletester.blogspot.com/

sl4m

// insert in core.js
JS.singleton = function(name, parent, methods) {
	var args = arguments;
	return (function(args) {
		// store instance and class in private variables
		var instance = null;
		var klass = new JS.Class(name, parent, methods);
		return {
			getInstance: function() {
				if (instance) { return instance; }