1. Test Your Shit
Friday, July 22, 11

2. Test Your Shit
...please
Friday, July 22, 11

3. bob remeika
Friday, July 22, 11

4. foobarfighter
(twitter, github and freenode)
Friday, July 22, 11

5. i work at
Friday, July 22, 11

6. larry wall is my jesus
Friday, July 22, 11

7. so testing...
Friday, July 22, 11

8. so testing... why?
Friday, July 22, 11

9. your codebase will
evolve
Friday, July 22, 11

10. your priorities will
change
Friday, July 22, 11

11. but you already knew
that
Friday, July 22, 11

12. that means your code
will change
Friday, July 22, 11

13. that means your code
will change
often
Friday, July 22, 11

14. so what are you going
to do about it?
Friday, July 22, 11

15. some of you will do
nothing
Friday, July 22, 11

16. you will fail
Friday, July 22, 11

17. unless you’re
facebook ;-)
Friday, July 22, 11

18. you’re not facebook
Friday, July 22, 11

19. you will hire new
people
Friday, July 22, 11

20. they will break things
Friday, July 22, 11

21. tests help them ramp
up
Friday, July 22, 11

22. better codez
Friday, July 22, 11

23. tests force decoupling
Friday, July 22, 11

24. separate the shit out of
those concerns
Friday, July 22, 11

25. tests at yammer
a brief case study
Friday, July 22, 11

26. just ship™
Friday, July 22, 11

27. just ship™
we launch features... not tests
Friday, July 22, 11

28. features are why we are
having success
Friday, July 22, 11

29. but things are changing
Friday, July 22, 11

30. stability matters
Friday, July 22, 11

31. speed matters
Friday, July 22, 11

32. quality matters
Friday, July 22, 11

33. we share code
internally
Friday, July 22, 11

34. we have a lot of paying
customers now
Friday, July 22, 11

35. they are enterprises
Friday, July 22, 11

36. breaking them is not
cool
Friday, July 22, 11

37. ‘this.updateMessageList’
is not a method
Friday, July 22, 11

38. ‘this.updateMessageList’
is not a method
you didn’t even run that code????????!?!!?!
Friday, July 22, 11

39. how could we have
caught that?
Friday, July 22, 11

40. how could we have
caught that?
we only had three javascript engineers
Friday, July 22, 11

41. our codebase was
growing
Friday, July 22, 11

42. we needed to be more
stable
Friday, July 22, 11

43. we needed some
controls
Friday, July 22, 11

44. we needed some more
beer
Friday, July 22, 11

45. so now we have tests
Friday, July 22, 11

46. (insert graph)
Friday, July 22, 11

47. fewer face palms
Friday, July 22, 11

48. better reliability
Friday, July 22, 11

49. improved new
employee ramp up
Friday, July 22, 11

50. fearless refactoring
Friday, July 22, 11

51. because we rarely get it
right the first time
Friday, July 22, 11

52. so testing...
Friday, July 22, 11

53. so testing... how?
Friday, July 22, 11

54. i can’t cover everything
Friday, July 22, 11

55. stop!
Friday, July 22, 11

56. go!
Friday, July 22, 11

57. you need a ci
environment
Friday, July 22, 11

58. you might need unit
tests
Friday, July 22, 11

59. you definitely need
functional tests
Friday, July 22, 11

60. (c)ontinuous
(i)ntegration
Friday, July 22, 11

61. i’m a street light
hi, i’m paul hi my name is peter
we have this setup at yammer
Friday, July 22, 11

62. if you are writing tests
for the browser
Friday, July 22, 11

63. require(‘saucelabs’)
Friday, July 22, 11

64. use your vc money
Friday, July 22, 11

65. we use saucelabs at
yammer
Friday, July 22, 11

66. Friday, July 22, 11

67. because it is awesome
Friday, July 22, 11

68. awesomesauce
Friday, July 22, 11

69. how do you know if
you need unit tests?
Friday, July 22, 11

70. Friday, July 22, 11

71. unit tests
Friday, July 22, 11

72. convenience to the
developer
Friday, July 22, 11

73. convenience to the
next developer
Friday, July 22, 11

74. writing libraries
Friday, July 22, 11

75. require(‘unit tests’)
// doesn’t run
Friday, July 22, 11

76. require(‘foounit’)
// totally runs... teh asum
Friday, July 22, 11

77. foounit
a brief intro
Friday, July 22, 11

78. another javascript test
framework
Friday, July 22, 11

79. another javascript test
framework
really?
Friday, July 22, 11

80. ... ya but
Friday, July 22, 11

81. it has some lofty goals
Friday, July 22, 11

82. cross host
Friday, July 22, 11

83. test shared code on
client/server
Friday, July 22, 11

84. test shared code on
client/server
these shenanigans exist at yammer
Friday, July 22, 11

85. test shared code on
client/server
these shenanigans exist at yammer
i’m not gonna lie, this is hard to do
Friday, July 22, 11

86. beautiful syntax
Friday, July 22, 11

87. not owned by the man
Friday, July 22, 11

88. where it’s going
Friday, July 22, 11

89. great ehraaahs
Friday, July 22, 11

90. great doc generation
Friday, July 22, 11

91. jellyfish integration
Friday, July 22, 11

92. ui sandboxing
Friday, July 22, 11

93. easy to use ui
Friday, July 22, 11

94. turn into a jet and fly
into the sun
Friday, July 22, 11

95. var f = require(‘foounit’).globalize();
describe(‘this is a group’, function (){
it(‘has a test’, function (){
expect(myTest).to(runEverywhere);
});
});
f.run();
Friday, July 22, 11

96. it’s a lot like jasmine
Friday, July 22, 11

97. it’s a lot like jasmine
there’s reasons for that
Friday, July 22, 11

98. check it out
http://foounit.org
Friday, July 22, 11

99. functional tests
Friday, July 22, 11

100. test end result
Friday, July 22, 11

101. test your application
Friday, July 22, 11

102. test what the user sees
Friday, July 22, 11

103. require(‘jellyfish’)
Friday, July 22, 11

104. h8rz g0n h8
Friday, July 22, 11

105. h8rz g0n h8
testing fallacies
Friday, July 22, 11

106. fallacy #1
Friday, July 22, 11

107. people will tell you that
you don’t need tests
Friday, July 22, 11

108. let’s analyze that
Friday, July 22, 11

109. successful open source
projects have tests
Friday, July 22, 11

110. rails
Friday, July 22, 11

111. one million tests
Friday, July 22, 11

112. jquery
Friday, July 22, 11

113. 1336 tests
Friday, July 22, 11

114. dojo
Friday, July 22, 11

115. 1337 tests
Friday, July 22, 11

116. 1337 tests
one more than jquery cause it’s better
Friday, July 22, 11

117. 1337 tests
one more than jquery cause it’s better
l337
Friday, July 22, 11

118. you want to be
successful, right?
Friday, July 22, 11

119. you want to be
successful, right?
write tests
Friday, July 22, 11

120. if you really care about
the numbers
Friday, July 22, 11

121. if you really care about
the numbers
you can run the suites yourself
Friday, July 22, 11

122. fallacy #2
Friday, July 22, 11

123. you don’t need to test
view code
Friday, July 22, 11

124. you don’t need to test
view code
if your ‘view code’ is just html... cool
Friday, July 22, 11

125. you don’t need to test
view code
if your ‘view code’ is just html... cool
but you are building a big client side app
Friday, July 22, 11

126. do you consider jquery
to be just ‘view code’?
Friday, July 22, 11

127. no
Friday, July 22, 11

128. it has a lot of tests
Friday, July 22, 11

129. because it’s
complicated
Friday, July 22, 11

130. complex ui interactions
are not just ‘view code’
Friday, July 22, 11

131. fallacy #3
Friday, July 22, 11

132. tests slow you down
Friday, July 22, 11

133. until the next guy
needs to change
something
Friday, July 22, 11

134. until you spend hours
face palming
Friday, July 22, 11

135. until you need to test
error conditions
Friday, July 22, 11

136. fallacy #4
Friday, July 22, 11

137. you need 100%
coverage
Friday, July 22, 11

138. you aren’t building the
space shuttle
Friday, July 22, 11

139. you don’t even need
90%
Friday, July 22, 11

140. you need enough to
help you refactor with
confidence
Friday, July 22, 11

141. it’s hard to find the
balance
Friday, July 22, 11

142. but you should try
Friday, July 22, 11

143. what’s a good unit test?
Friday, July 22, 11

144. tdd/bdd dictates that
you should test
everything
Friday, July 22, 11

145. sure you can do that
Friday, July 22, 11

146. ... if you have that
culture
Friday, July 22, 11

147. i’m looking at you
pivots
Friday, July 22, 11

148. but there are
diminishing returns
Friday, July 22, 11

149. this.prototype.start = function (){
if (this.isStarted()){ return; }
this._start()
}
Friday, July 22, 11

150. find a happy place
Friday, July 22, 11

151. some things are hard to
test
Friday, July 22, 11

152. your mileage will vary
Friday, July 22, 11

153. emulating xhr
Friday, July 22, 11

154. multi-step interactions
Friday, July 22, 11

155. consider integration
tests
Friday, July 22, 11

156. mock services ftw
Friday, July 22, 11

157. please talk to me
Friday, July 22, 11

158. or contact me online
Friday, July 22, 11

159. i actually like people
Friday, July 22, 11

160. foobarfighter
(twitter, github and freenode)
Friday, July 22, 11

161. foounit
http://foounit.org
Friday, July 22, 11