From 36106f27ccbf8c560b51dfe80f19eb68a2717037 Mon Sep 17 00:00:00 2001 From: Andrew Grimm Date: Thu, 17 May 2012 00:16:47 +1000 Subject: [PATCH 1/3] Proposal.new. Heckle: we break code --- andrew_grimm-Heckle_we_break_code/README.md | 26 +++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 andrew_grimm-Heckle_we_break_code/README.md diff --git a/andrew_grimm-Heckle_we_break_code/README.md b/andrew_grimm-Heckle_we_break_code/README.md new file mode 100644 index 0000000..8a71834 --- /dev/null +++ b/andrew_grimm-Heckle_we_break_code/README.md @@ -0,0 +1,26 @@ +# Heckle: we break code! + +Heckle evaluates the thoroughness of your unit tests. It does this by making modifications to your code, and seeing if those modifications cause any unit test failures. For example, it will turn ifs into unlesses, and replace strings and numbers with other strings and numbers or nil. If no failures occur, then that piece of code isn't being tested enough. + +In this talk, I will discuss how Heckle has been useful to me in maintaining a one person Plain Old Ruby Object project that's been worked on for over three years, has over 15K lines of production code, over 11K lines of test code, and varying degrees of unit testing. + +- Preferred presentation day: no preference +- Presentation language: English, hopefully with Japanese subtitles. + +## Andrew Grimm +## アンドリュー グリム + +## University of New South Wales. +## ニューサウスウェールズ大学 (UNSW) + +Andrew Grimm is a bioinformatician at the University of New South Wales in Sydney, Australia. He came across Ruby while using Rails at his previous job associated with the Encyclopedia of Life, but now specialises in Plain Old Ruby Objects. + +He has worked on various projects outside of work. One analyzed why you always end up at "Philosophy" in Wikipedia. Another was a fork of Heckle in which zombies eat your brains unless your unit tests can kill them all. At RubyKaigi 2011 he demonstrated the Small Eigen Collider, which generates random Ruby code that can be run under different implementations of Ruby to check for inconsistencies or bugs. + +バイオインフォマティクスの科学者 + +- [My website](https://andrewjgrimm.wordpress.com/) +- [My twitter](https://twitter.com/#!/andrewjgrimm) +- [Past talk slides](http://www.slideshare.net/agrimm) +- [Past talk videos](https://vimeo.com/channels/332579) +- [Past t-shirt](http://www.zazzle.com/small_eigen_collider_japanese_and_english_text_tshirt-235235813665782515) From 1bf794755bb3e80bb54587c862c73d429511636e Mon Sep 17 00:00:00 2001 From: Andrew Grimm Date: Sat, 19 May 2012 17:47:49 +1000 Subject: [PATCH 2/3] Minor improvements to heckle proposal. --- andrew_grimm-Heckle_we_break_code/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/andrew_grimm-Heckle_we_break_code/README.md b/andrew_grimm-Heckle_we_break_code/README.md index 8a71834..5702d40 100644 --- a/andrew_grimm-Heckle_we_break_code/README.md +++ b/andrew_grimm-Heckle_we_break_code/README.md @@ -1,8 +1,8 @@ # Heckle: we break code! -Heckle evaluates the thoroughness of your unit tests. It does this by making modifications to your code, and seeing if those modifications cause any unit test failures. For example, it will turn ifs into unlesses, and replace strings and numbers with other strings and numbers or nil. If no failures occur, then that piece of code isn't being tested enough. +Heckle evaluates the thoroughness of your unit tests. It does this by making modifications to your production code, and seeing if those modifications cause any unit test failures. For example, it will turn ifs into unlesses, and replace strings and numbers with other strings and numbers or nil, or even delete lines of code! If no failures occur when your unit tests are run on the modified production code, then that code isn't being tested enough. -In this talk, I will discuss how Heckle has been useful to me in maintaining a one person Plain Old Ruby Object project that's been worked on for over three years, has over 15K lines of production code, over 11K lines of test code, and varying degrees of unit testing. +In this talk, I will discuss how Heckle has been useful to me in maintaining a one person Ruby project that's been worked on for three years, has 15K lines of production code, 11K lines of test code, and varying degrees of unit testing. - Preferred presentation day: no preference - Presentation language: English, hopefully with Japanese subtitles. From 08587be2f193e79a15a327b85e04a7ac9cfc929b Mon Sep 17 00:00:00 2001 From: Andrew Grimm Date: Wed, 23 May 2012 22:15:42 +1000 Subject: [PATCH 3/3] Improve Japanese. Thanks Kazuki-san. --- andrew_grimm-Heckle_we_break_code/README.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/andrew_grimm-Heckle_we_break_code/README.md b/andrew_grimm-Heckle_we_break_code/README.md index 5702d40..42197c6 100644 --- a/andrew_grimm-Heckle_we_break_code/README.md +++ b/andrew_grimm-Heckle_we_break_code/README.md @@ -17,7 +17,13 @@ Andrew Grimm is a bioinformatician at the University of New South Wales in Sydne He has worked on various projects outside of work. One analyzed why you always end up at "Philosophy" in Wikipedia. Another was a fork of Heckle in which zombies eat your brains unless your unit tests can kill them all. At RubyKaigi 2011 he demonstrated the Small Eigen Collider, which generates random Ruby code that can be run under different implementations of Ruby to check for inconsistencies or bugs. -バイオインフォマティクスの科学者 +ニューサウスウェールズ大学(シドニー)のバイオインフォマティクスの研究者。 +Encyclopedia of Life関係の仕事でRailsを使ったことをきっかけにRubyと出会い、今はPlain Old Ruby Objectsを専門としている。 + +これまでに、Wikipediaのリンクを辿っていくと最終的に"Philosophy"のページに +到達するという事象についての分析や、Heckleというテストライブラリのフォークなどを行ってきた。 +RubyKaigi 2011では、ランダムなRubyコードを生成することでRubyの様々な処理系におけるバグを見つけるための +Small Eigen Colliderというライブラリについて発表した。 - [My website](https://andrewjgrimm.wordpress.com/) - [My twitter](https://twitter.com/#!/andrewjgrimm)