you an existing library (the horse is probably your ego) 

you your ideal library 

language ✘ app framework ✘ test framework ✔ 

test/unit rspec cucumber 

before / setup test ... should ... it ... after / teardown 

blah = Hubris.new do before do @x = 1 end it “works” do raise unless 1 == @x end after do @x = nil end end blah.run 

class Hubris def initialize(&block) instance_eval(&block) end def before(&block) @before = block end def it(name, &block) @test = block end # etc ... def run instance_eval(&@before) instance_eval(&@test) instance_eval(&@after) end end stash evaluate evaluate 

before / setup test ... should ... it ... after / teardown @f = File.new @f.unlink @f.read 

subcontexts: parent & child def run_befores @parent.run_befores if @parent instance_eval(&@before) end def run run_befores instance_eval(&@test) # etc ... end 

Hubris.new do def some_method @x = 1 end it “works” do raise unless 1 == some_method end end where does this method live? 

all of this has happened before; and it will all happen again. 

No content

AXIS OF WTF 

it’s probably OK. 

except maybe it’s not OK? 

maybe don’t write anything. 

maybe become a contributer. 

open source responsibility. 

give some context. 

kill-ish your darlings. bit.ly/rubytesting