Skip to content
This repository

Testing: Not Too Early, Not Too Late #44

Open
wants to merge 3 commits into from

5 participants

Thomas Symborski Andrew Grimm MOROHASHI Kyosuke SHIMADA Koji Andrew Culver
Thomas Symborski
zsiec commented May 23, 2012

It seems many of the most vocal advocates of test-driven development (TDD) teach an absolute approach. However, over-testing and premature testing do exist, and both present their own set of risks. Let there be no mistake: It's not whether you test. It's when. Automated testing is an essential skill for any developer. However, recognizing when tests provide true value is a skill many developers have acquired over time.

We're seeking to provide a balanced view of the general consensus within the Rails community about when to test. No software project fits in a standard mold, so why have an absolute standard approach? The better all developers can learn to adapt their approach to fit the need, the more they'll increase their ability to be successful. In grand scheme of things, tests are only a part of the larger software development process. As such, they should be utilized to help the developer, not make their lives more difficult or stifle productivity or creativity.

After years of test-driven development and a fearful session of joint confession, we realized we've come to a lot of the same conclusions independently of one another. Neither one of us wants to tread this dangerous terrain alone, so we've decided to team up in this attempt at a balanced discussion of our experiences keeping code clean and keeping clients happy.

Andrew Grimm
agrimm commented May 25, 2012

:+1:

MOROHASHI Kyosuke
moro commented May 26, 2012

:+1:

SHIMADA Koji
Owner

English

Thank you for your proposal for Sapporo RubyKaigi2012.

We are sorry to inform you that we could not allocate time for your presentation in the plenary session.
We are also planning to have lightning talk sessions.
If you are intrested, please submit a lightning talk.
Furthermore, there will be a parallel "Unconference" and you may have opportunity to present there.

About ticket reservation

All proposal submitters are welcome to participate in SPRK2012. We would like to offer you one free ticket to the plenary session.

If you would like to attend, please send the following information to sapporo2012@rubykaigi.org no later than Wednesday, June 7, 2012.

Japanese

この度はご応募いただきありがとうございました。

Sapporo RubyKaigi2012 に応募いただきましたこの発表ですが、
大変残念ですが採択に至りませんでした。

LT を合計11枠用意する予定ですので、
ぜひ LT での応募をご検討頂ければと思います。
また会期中にアンカンファレンスも並行で実施する予定ですので
こちらへの参加も併せてご検討ください。

チケットの取り置きについて

今回発表のお申し込みをいただいた方には、是非とも
Sapporo RubyKaigi2012 に参加してほしいと考えています。

6/7までに以下のフォーマットで申し込みをいただければ
本編チケットを無料で提供するようにいたします。
是非ともご検討下さい。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
This page is out of date. Refresh to see the latest.
BIN  .DS_Store
Binary file not shown
BIN  andrew_culver_thomas_symborski-testing_not_too_early_not_too_late/.DS_Store
Binary file not shown
36  andrew_culver_thomas_symborski-testing_not_too_early_not_too_late/README.md
Source Rendered
... ...
@@ -0,0 +1,36 @@
  1
+# Testing: Not Too Early, Not Too Late
  2
+
  3
+It seems many of the most vocal advocates of test-driven development (TDD) teach an absolute approach. However, over-testing and premature testing do exist, and both present their own set of risks. Let there be no mistake: It's not whether you test. It's when. Automated testing is an essential skill for any developer. However, recognizing when tests provide true value is a skill many developers have acquired over time.
  4
+
  5
+We're seeking to provide a balanced view of the general consensus within the Rails community about when to test. No software project fits in a standard mold, so why have an absolute standard approach? The better all developers can learn to adapt their approach to fit the need, the more they'll increase their ability to be successful. In grand scheme of things, tests are only a part of the larger software development process. As such, they should be utilized to help the developer, not make their lives more difficult or stifle productivity or creativity. 
  6
+
  7
+After years of test-driven development and a fearful session of joint confession, we realized we've come to a lot of the same conclusions independently of one another. Neither one of us wants to tread this dangerous terrain alone, so we've decided to team up in this attempt at a balanced discussion of our experiences keeping code clean and keeping clients happy.
  8
+
  9
+- Preferred presentation day: no preference
  10
+- Presentation language: English
  11
+
  12
+## Andrew Culver & Thomas Symborski
  13
+## We Are Titans
  14
+
  15
+## Our Bios
  16
+
  17
+__Andrew Culver__
  18
+
  19
+Andrew is a Ruby on Rails and iOS Developer at We Are Titans in Norfolk, VA. He also runs Limelight for app developers. Andrew graduated from the Software Engineering program at Mohawk College in Hamilton, ON, Canada and has been practicing and teaching test-driven development consistently since 2007. He loves Japan and Japanese, productivity hacking, and providing for his wife and kids doing what he loves.
  20
+
  21
+- [We Are Titans](http://www.wearetitans.net)
  22
+- [Limelight](http://limelightapp.com/)
  23
+- [@andrewculver on Twitter](https://twitter.com/#!/andrewculver)
  24
+- [Comments on Hacker News](http://news.ycombinator.com/threads?id=aculver)
  25
+- [Past Talk: "Being Good at Life"](http://public.iwork.com/document/?a=p115143142&d=Being_Good_At_Life.key)
  26
+
  27
+__Thomas Symborski__
  28
+
  29
+With a degree in Electrical Engineering and a masters in Mathematics nearing its completion, Thomas has a strong background in algorithms, complex discrete systems, and data structures. He has been programming web applications for the last 5 years (for government and commercial entities) and enjoys building cutting-edge solutions.
  30
+
  31
+- [We Are Titans](http://www.wearetitans.net)
  32
+- [@zsiec on Twitter](https://twitter.com/#!/zsiec)
  33
+- [Upcoming Talk: "Cucumber: The Right Way"](http://www.rubyday.it/talks/12/)
  34
+
  35
+![Andrew](https://github.com/zsiec/sprk2012-cfp/raw/master/andrew_culver_thomas_symborski-testing_not_too_early_not_too_late/andrew.jpg)
  36
+![Thomas](https://github.com/zsiec/sprk2012-cfp/raw/master/andrew_culver_thomas_symborski-testing_not_too_early_not_too_late/thomas.jpg)
BIN  andrew_culver_thomas_symborski-testing_not_too_early_not_too_late/andrew.jpg
BIN  andrew_culver_thomas_symborski-testing_not_too_early_not_too_late/thomas.jpg
Commit_comment_tip

Tip: You can add notes to lines in a file. Hover to the left of a line to make a note

Something went wrong with that request. Please try again.