Test like a team.

Tesing is a discussion.
Testは對話。

Transcript

1. Test like a team.
2. .｡oO(さっちゃんですよヾ(〃l _ l)ﾉﾞ☆)
3. 「Testは對話」
4. Test code. test “鳴く” = do meow cat Application code. meow :: Cat -> IO () meow cat = do print “Meow”
5. Application codeはuserの環境で動く。 Test codeはuserの環境で動かない。
6. Application codeはuserの環境で動く。 Test codeはuserの環境で動かない。 ? それはそうだが、 切り口はそれか?
7. Application codeは育つもの。 Test codeはそれを育てるもの。
8. Old `testing` flow. (i.e. regression test, proof) Application code Test code Test code
9. Agile flow. Application code Test code 何をしているの? これでよくない? 難し過ぎ
10. Like pair programming. Guido Gloor Modjib “Pair Programming” (CC BY-NC-ND 2.0) https://flic.kr/p/qAPhza
11. Test code. Application code. meow :: Cat -> IO ()
12. Test code. Application code. meow :: Cat -> IO () meow cat = do print “Meow” 實裝します
13. Test code. test “鳴く” = do assert $ meow cat Application code. meow :: Cat -> IO () meow cat = do print “Meow” 呼び出してみるよ
14. Test code. test “鳴く” = do assert $ meow cat test “鳴き声” do assert (“Meow” == whatMeow cat) Application code. meow :: Cat -> IO () meow cat = do print $ whatMeow cat whatMeow :: Cat -> String whatMeow cat = “Meow” 難し過ぎんよ 任せるよ 何て鳴くの?
15. その行が 何をしてゐるか理解し、 何をすべきか育てる。
16. 「Testは對話」
17. https://speakerdeck.com/ne_sachirou/librarywozuo-rutoyun-hukai-fa- shou-fa
18. Can you share any tips or techniques you have found useful in uncovering bugs? I suppose the biggest tip would be to become a better programmer. In particular, study what functions that programs are calling, and ensure that the calling code is following the rules of those functions 100%. (Theo de Raadt, of OpenBSD)