Test like a team.
- 1. Test like a team.
- 3. 「Testは對話」
- 4. Test code. test “鳴く” = do meow cat Application code. meow :: Cat -> IO () meow cat = do print “Meow”
- 8. Old `testing` flow. (i.e. regression test, proof) Application code Test code Test code
- 9. Agile flow. Application codeTest 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” 難し過ぎんよ 任せるよ 何て鳴くの?
- 16. 「Testは對話」
- 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)