Slides de acompanhamento da palestra e discussão "O que não testar" na #AgileBR 2012

1. O que não testar no seu
projeto!

3. ?

12. Você APAGA seus
testes?

13. @klaus
apaguei um teste no avião vindo para
cá!

14. @dhh
I find over-testing to be most
common among those 1st adopting
TDD. So excited about the idea that
they go completely overboard.

15. Don’t use Cucumber
unless you live in the magic kingdom
of non-coders-writing-tests
(and send me some fairy dust if you are!)

16. @mfeathers
Ultimately, tests are a feedback
mechanism, and we should make
active decisions about what
feedback we need and when.

19. @unclebobmartin
1 of Kent’s older wise sayings was:
“Test everything that could possibly
break.” I think that’s a pretty good
recipe.

21. @joshuakerievsky
Test first/after misses the point that
TDD is more about emergent design
than it is about testing. Do you
practice emergent design?

23. @kentbeck
If I don’t typically make a mistake(...),
I don’t test for it.
Wish there were more examples of
“what not to test”.

37. 100% COVERED CODE.
LINE
OF CODE YOU COVER

38. PIXEL NAZI

45. fixtures
considered
harmful?

46. It will only run once

47. <- costumer
facing
VS
back
office ->

48. JAVASCRIPT?

50. Being good
at stupid
doesn’t
count.

51. POR QUE
TESTAMOS?

52. Lei de Murphy

53. D
O
R

55. FLUIDEZ

56. Velocidade Robustez
1500.00
1125.00
750.00
375.00
0
Untitled 1

57. @jamesshore
sacrifice the chicken
to the computer
gods

58. HUMILHAÇÃO
PÚBLICA

60. Quanta
qualidade é
suficiente?

61. Bugs/1KLOC
5
4
3
1
0
Indústria Nasa

62. Bugs/1KLOC
5
4
3
1
0
Indústria Nasa

63. Bugs/1KLOC
5
4
3
1
0
Indústria Nasa

64. Bugs/1KLOC
5
0,004
4
3
1
0
Indústria Nasa

65. Pair Programming

66. Cost($/LOC)
850
900
675
450
225
5
0
Indústria Nasa

67. Cost($/LOC)
850
900
675
450
225
5
0
Indústria Nasa

68. @marick
I test the high risk code thoroughly. I
use up most of the remaining time
testing the
medium risk code. I don’t
intentionally test the low risk code

69. @martinfowler
you’re doing enough testing if the
following is true:
■You rarely get bugs that escape
into production
■You are rarely hesitant to change
some code for fear it will cause
production bugs

70. @jamesshore
Skill and discipline give us fluency.
Then fluency gives us ease and joy.

71. O que é
difícil?
Como testar?

73. baby steps:
grow up, o
mundo real
não é um
dojo

74. D
R
Y

75. WET

76. Test
journeys

77. Acúmulo
de
sleep()

78. non-
deterministic
test suite

80. non-
deterministic
code

81. lack of isolation

82. @neal4rd
understand one layer bellow your
abstraction

83. external
dependencies:

84. NON-FUNCTIONAL
REQUIREMENTS

86. Love Metrics

87. Love Metrics
Delivered customer benefit?

88. Love Metrics
Delivered customer benefit?
Customers actively using it?

89. Love Metrics
Delivered customer benefit?
Customers actively using it?
Customers tellings
others about it?

90. técnica
vs
ferramenta

91. feedback
vs
noise

92. Evolução do
Desing
vs
Garantia de
Funcionamento

93. decidir o que
não testar é tão
importante
quanto
escrever testes

94. bring the
pain
forward

95. JOIN
THE
BETA
HELP
US
TEST
TDD
eLearning
exercises
in
Javascript JAVASCRIPT
industriallogic.com

96. agradecimentos:
@camiloribeiro, @lucabastos,
@neal4rd, @tottinge, @brownie490,
@hugocorbucci, @dtsato,
@p_balduino, @mauricioaniche,
@cecifernandes, @marick,
@mfeathers, @dhh, @martinfowler,
@jamesshore, @joshuakeriesvisky,
@kentbeck, @unclebobmartin,
@klauswuestefeld, @guilhermesilveira