sl4m

Keybase proof

I hereby claim:

• I am sl4m on github.
• I am skim (https://keybase.io/skim) on keybase.
• I have a public key whose fingerprint is 1969 1388 9423 B407 6EFD ED76 731A 9DF5 5732 A0C8

To claim this, I am signing this object:

sl4m

Keybase proof

I hereby claim:

• I am sl4m on github.
• I am skim (https://keybase.io/skim) on keybase.
• I have a public key whose fingerprint is EA0E 259C B4B4 A1F4 A959 E839 2574 4DCC 3A0C EF66

To claim this, I am signing this object:

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; }

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

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

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

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

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

edge case
happy/sad paths
refactor

sl4m

First, I would like to start out by recommending that anyone who is
serious about software craftsmanship go out and read Pete McBreen's
book "Software Craftsmanship".  I think it's a critical starting place
for these discussions, and on a more personal note, the book had a
huge impact on me.  Probably the biggest reason I am a part of this
group is that I have no where else to go.  :)  I was a later-in-life
self-taught programmer who had a wife and child(ren) to support from
the day I wrote my first for loop, so I have no formal scientific or
engineering education, and I don't have the option of taking time off
to obtain one.  And yet I want to become great at what I do.  In my

sl4m

Ruby VMs

YARV
Rubinius
JRuby
IronRuby
MacRuby