Test like a team.

.｡oO(さっちゃんですよヾ(〃l _ l)ﾉﾞ☆)

「Testは對話」

Test code. test “鳴く” = do meow cat Application code. meow :: Cat -> IO () meow cat = do print “Meow”

Application codeはuserの環境で動く。 Test codeはuserの環境で動かない。

Application codeはuserの環境で動く。 Test codeはuserの環境で動かない。 ? それはそうだが、 切り口はそれか?

Application codeは育つもの。 Test codeはそれを育てるもの。

Old `testing` flow. (i.e. regression test, proof) Application code Test code Test code

Agile flow. Application code Test code 何をしているの? これでよくない? 難し過ぎ

Like pair programming. Guido Gloor Modjib “Pair Programming” (CC BY-NC-ND 2.0) https://flic.kr/p/qAPhza

Test code. Application code. meow :: Cat -> IO ()

Test code. Application code. meow :: Cat -> IO () meow cat = do print “Meow” 實裝します

Test code. test “鳴く” = do assert $ meow cat Application code. meow :: Cat -> IO () meow cat = do print “Meow” 呼び出してみるよ

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” 難し過ぎんよ 任せるよ 何て鳴くの?

その行が 何をしてゐるか理解し、 何をすべきか育てる。

「Testは對話」

https://speakerdeck.com/ne_sachirou/librarywozuo-rutoyun-hukai-fa- shou-fa

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)